I have several Pololu TReX motor controllers laying around. I hooked it up and connected a motor and a linear actuator to both channels. I started with an standard RC controller and made sure it was all set up. Worked fine.
Then I replaced the reciever with the EZB. It worked for about 10 seconds then stopped. I had used PWM slider, then I tried servo etc. Nothing would work again. The green LED on the TReX flashes when there is no recieved signal. It was flashing. So I replugged the RC set up and it all worked fine again. Then again with the EZB, this time only one channel worked for about 10 seconds then nothing. I could not get it to work again after that. Anybody tell me why the EZB will not send thru a simple PWM that the TReX expects to receive? Or how to keep it connected?!
Thanks!
Will
Asked
— Edited
The motor controller would require a servo connection, not PWM.
And even more specifically, you would use a Modified servo Control. If you have two connections on the motor controller, then use a Modified servo Movement Panel.
You can use the Tutorials section to read about how a servo works. It's a bit differnet to wrap your head around - but once you do, it'll be a breeze
Thanks
Will
You connect servo wires to the first two connnections on the left side for M1 and M2
I have included the following videos:
1) The setup running with just R/C
Click To Watch Video
2) The set up with EZB when it loses the signal.
Click To Watch Video
3) Set up trying to use the Modified servo panel
Click To Watch Video
Please excuse all the hammering. There is construction next door.
Cheers,
Will Huff
Either the Modified servo Movement Panel or Modified servo Control will work, you'll need to adjust the settings under CONFIG. The Forward and Reverse settings will need to be configured.
The best way to test to find the right settings is to first use a Vertical servo Control. Then start slowly moving the values until the motor begins to move one direction. Write down that value. (that'll probably be reverse value)
Then continue to move the slider until the motor stops.. Write down that value (that'll be the stop value)
Then continue to move the slider until the motor starts, but keep moving it until it's at full speed before it stops again. (That will be the maximum speed forward value probably)
Then add those values into the Modified Movement servo Panel
However, once you upgrade to 15.3, you'll have to do that process again becuase the servo values have changed
Thanks again I'll let you know how it goes.
Will
I guess for what ever the reason the TReX is not compatable with EZB.
I certainly gave it the ole one, two.
Thanks for all the help though.
Cheers,
Will
Because these things, like the trek are programmable (in a sense) by learning their limits (sometimes) its a bit more difficult to configure. So don't think it's not compatible, I assure you it is
Worst case if it still works erratically I can send you a TReX to test on and see what your results are. If you could send it back
Again thanks for all the help.
Will
Repeatable issue. I have reproduced the same results 10 times in a row. I removed the linear actuator and replaced with exact same type motor as on channel 1. This way loads etc will be the same. Results:
1) The TReX has the following values to work - forward/reverse,stop as follows: 15 min, 55 max, with stop at 35.
2) Created two vert servo panels, config to D8 and D9. Reset values to above numbers. Saved.
3) With both channels plugged in nothing happens. TRex blinks and i move from 15 to 55, nothing happens.
4)But if I UNPLUG one channel, I can get the other one to work. Then I plug in the other channel and both now work and have full control.
5) I then created 2 modified servo panels and added the correct port and values to match the servo panels I created in step 1. When I hit forward, they move and hit reverse they go in reverse as expected.
6) But if I hit STOP on both channels, the TRex loses signal and neither motor will move again (as in step 3) until I again UNPLUG one channel and repeat step 4 above.
7) Repeated 10 times, same results.
Any ideas what that sounds like may be happening?
Will
I guess it's difficult to diagnose from here. If you'd like to send a Trex, i can take a look at it but i'm how much free time i have for that. I work 12-14 hours per day developing the software
"TReX and TReX Jr firmware versions 1.0 and 1.1 have a bug that prevents the device from working at 28,800 and 38,400 bps baud rates. All other supported baud rates work correctly on versions 1.0 and 1.1, so if you do not need them, there is no need to perform a firmware update. "
And This:
"This firmware fixes a bug that affected the 38,400 and 28,800 bps baud rates, and it adds a configuration parameter that lets you optionally insert a 1 ms delay between the last byte of a received command packet and the first byte of the TReX's transmitted response. Without this delay, slower controllers, such as the Basic Stamp, can miss the first byte of the TReX's response. "
Possible this the problem? What is the default Baud rate of the EZB? I'll try upgrading the firmware and see how that goes. Thanks for suggesting it DJ!!
Will
r/c mode works like a servo. you can read about how a servo works in the tutorials section under Standard Servo. The servo uses a PWM (pulse width modulation). So, because all servos and all other r/c motor controllers work, i'd have to suggest there is a bug in the trex software. Or, you never know - maybe you'll find a differnet configuration setting that works.
Thanks again I know you are busy..thanks for trouble shooting with me.
Will
Try again at a later date. Usually things just "work" when you revisit them