Erratic behavior in ttl with arduino MEGA
Erratic behavior in ttl with arduino MEGA
Hello!
I have a roboclaw 2x15a connected to an arduino mega 2560 via de hardware serial 3. When the arduino boot, all the comunication with the claw works perfect. The problem arises when the sketch is running for a time (1hour), then the communication goes unidirectional and only works from arduino to the roboclaw. So the arduino still have control of the engines, but the voltage, current and temp readings of the claw are always 0. If i reboot the arduino then, the communications works bidirectional again but over time will fail again. I use the latest roboclaw library from the web. The constructor i use is: RoboClaw roboClaw(&Serial3, 10000);.
Thanks!
I have a roboclaw 2x15a connected to an arduino mega 2560 via de hardware serial 3. When the arduino boot, all the comunication with the claw works perfect. The problem arises when the sketch is running for a time (1hour), then the communication goes unidirectional and only works from arduino to the roboclaw. So the arduino still have control of the engines, but the voltage, current and temp readings of the claw are always 0. If i reboot the arduino then, the communications works bidirectional again but over time will fail again. I use the latest roboclaw library from the web. The constructor i use is: RoboClaw roboClaw(&Serial3, 10000);.
Thanks!
- Basicmicro Support
- Posts: 1594
- Joined: Thu Feb 26, 2015 9:45 pm
Re: Erratic behavior in ttl with arduino MEGA
What baudrate are you using? What arduino pins are you using to communicate? Are you using software serial or hardware serial?