Paul & Sabrina's cheap DIY 144v motor controller

[esoneson]

Originally Posted by charlie_fd

Yuppie!!! My mock-up controller section is now reporting via serial link the throttle, pwm value and current.

The code works! I've used a FIFO queue (ring-buffer) filled with values on timer2 overflow. The actual transmission is done using buffer empty interrupt. The impact on the code is thus minimal.

Next steps: Implement receive part so I can send 1 byte commands to the controller ("inhibit reporting" for instance).

Fantastic progress Charlie!
Data logging and Dynamic configuration.
Now all we need is to save the settings in eprom and away we go!

Great work Charlie, no matter what the code format is.

Eric

[MPaulHolmes]

I'm like 80% done converting the schematic to ExpressSCH. I'm also going to do the layout in ExpressPCB, which is also free with no size limitations. It seems like a decent choice for people that want to modify it to whatever they want. Free with no size constraints is good.

[charlie_fd]

Originally Posted by MPaulHolmes

That's awesome Adrian!!! How complete is your control board? Did you use an HIN202CP?

I used a max232. The board is just the brain part. A pot is connected to the pin for throttle, a LED to the output pin so I can see the PWM output. There is no current sensor. It will help me test the communications part until I get the real control board.

[blowncurtice]

Paul I have just been rereading and I see on page 107 that you only started to learn electronics last December . Terrific there is hope for me yet however I think I will be taking a free ride on your back along with many others for your controller . John

[charlie_fd]

If other people would like to test the serial link, I've uploaded the changes in the r16 on svn. Here are the modifications: Changeset 16 for trunk/HighVoltageController.c - Open ReVolt - Trac

For testing conect a null modem cable to your pc and receive at 19200baud with 8n1. Any java programmer outthere wants to make the client for this?

Ups! I had commented out the HighPedalLockout ... Restored it in r17.

[dcb]

Charlie, can you explain to Paul how he proceeds to make changes to the program now?

[charlie_fd]

I don't seem to be able to explain properly. Maybe someone else should try?

My answer would be:

(for a new local working copy):

- "Checkout" the project to the local disk
- If you don't have local modifications continue to work on the trunk/HighVoltageController.c file as it came from the svn.
- If you allready have modifications since your last commit replace the entire content of trunk/HighVoltageController.c with your code. Then "SVN Update" (will merge the modifications from the svn with your own). Then "SVN Commit" will publish your modifications to the svn.
- continue to work on this file from now on. Always do "update" before changing thinks and commit when your are satisfied with your changes.

(for an already existing local copy):
- Just do "SVN Update"
- Continue to work on it

[dcb]

Problem is that merge might to horrible things to his local copy if he doesn't just go get the latest before going back to work on it.

[charlie_fd]

Originally Posted by dcb

Problem is that merge might to horrible things to his local copy if he doesn't just go get the latest before going back to work on it.

I did work on his last published version (09.06.2009). Merge should not be a problem.

[dcb]

not a problem for who?