arduino code possible issue

[dtaminge]

Hi all, I am working on creating this project as just a cool project to pass time, but I am having tones of issues. I was wondering if someone could send me a copy of their code for me to use as an example, because I honestly have no clue what variables in the global variables page we are supposed to update (I assume that they should not all equal zero). I believe that I have all of my wiring correct as well, but I just cannot get anything to happen. Also do we need to use the 4a motor control board for this to work?
Thanks

[AlanFord]

If you hook up the Arduino IDE serial monitor you should be able to communicate with the controller and set quite a number of parameters. It looks like Mike Rouleau originally intended to use potentiometers connected to the Arduino to adjust the parameters, but then switched to a serial interface. To use a different motor control board, adjust the pin definitions in Controller_3.0.ino to match the motor control board that you intend to use.

[dtaminge]

If you hook up the Arduino IDE serial monitor you should be able to communicate with the controller and set quite a number of parameters. It looks like Mike Rouleau originally intended to use potentiometers connected to the Arduino to adjust the parameters, but then switched to a serial interface. To use a different motor control board, adjust the pin definitions in Controller_3.0.ino to match the motor control board that you intend to use.

Thanks for getting back to me. I got things communicating, but for some reason I have to just set stat equal to a value instead of allowing it to fluctuate. On top of that the arduino crashes after 30 seconds from an overflow of data

[AlanFord]

Ok, I'm starting to take Mike's code apart and see where there may be a bug. I don't see a crash from an overflow of data. My past experience with other projects would indicate that the code isn't handling interrupts fast enough and they over-run each other, causing a lockup. Try disabling your motors and encoders and see if crash continues. Without the encoders, the encoder interrupts shouldn't fire. If they still do, check for input noise on the encoder pins or proper pin assignment.