TReX is in R/C mode as video 1 demonstrated above. I am thinking that the linear actuator may be messing things up. As everytime I activate it is when I lose signal. I am going to remove it and use another 12 v motor I have. Then I'll input the range values I extracted and try again. Let you know how it goes.

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 when done.

Again thanks for all the help.

Will

Ok,

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

LOL, I'm not entirely sure but it sounds like the trex is buggy. You can look at the screen shots of the Standard servo in the Tutorials section. The EZ-B has amazingly accurate servo timing - and i stand by that... They are amazingly accurate. If the trex isn't liking what it is getting, i'd blame buggy firmware on the trex. Otherwise perhaps there is noise along the cables or some interference.

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 So it'll be a toughy to fit in! So if you have two units, you can donate one and i'll get around to it a bit faster

Well well. You brought up a good point, Firmware. I checked their site (I've had these for about 3 years), and here is what I found there:

"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 doesn't use a baud rate. serial mode will use a baud.

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.

Well poo. Ok throwing the towel in on this one. More building and less posting.

Thanks again I know you are busy..thanks for trouble shooting with me.

Will

Anytime dude

Try again at a later date. Usually things just "work" when you revisit them

True that!