(Bytes)
RobotRx.JPG (1970109Bytes)
RobotSrvGndV.JPG (2069487Bytes)
RobotMeasure01.JPG (1643586Bytes)
RobotMeasure02.JPG (1392511Bytes)
RobotMeasure03.JPG (1496829Bytes)
RobotMeasure04.JPG (1561175Bytes)
RobotMeasure05.JPG (1565501Bytes)
RobotMeasure06.JPG (1515308Bytes)
RobotMeasure07.JPG (1509373Bytes)
RobotMeasure08.JPG (1358812Bytes)
RobotMeasure09.JPG (1358483Bytes)
RobotMeasure10.JPG (1297507Bytes)
RobotMeasure11.JPG (1270954Bytes)
RobotMeasure12.JPG (1363603Bytes)
RobotBack.JPG (1572675Bytes)
RobotFront.JPG (1731600Bytes)
Hi!
I create a new forum to talk about a trex controller issue I encountered after one hour of use of this controller. I mounted the dagu trex controller on the dagu wild thumper chassis with the 30+6mm given spacers . For testing purposes, I connected the trex controller in LV and no external switch mode (2 jumpers on) with Zippy LIPO 2S batteries and a D8RII FrSky receiver. The batteries are in series on the batteries input. The channel 1 and 2 of the receiver (which I programmed to be throttle and direction on the 9XR TX) are connected on the TX/RX pins of the controller.
I powered the TX and then the trex controller... 3 bips (what means that the RC mode described in the arduino sketch had been recognized)... And let's go! The wild thumper worked great... left, right, forward, rear... oops a restart, 3 bips and let's go again. A restart again... OK, that was coming from the accelerometer code : to be able to drive the wild thumper in real off-road condition, I modified the acceleromater code... No more restart, all fine...; Good! Very good... for one hour... After that : BIG FAIL! When I tried to connect the battery to power the trex controller, no boot, no bips, no light... Trex controller seemed to be dead. The battery delivered the right voltage to the trex but the output voltage at V+/Gnd, Srv/Gnd and 5V/Gnd (blue connectors) are jamming at 0.0V...
All that seems to indicate that there's a complete trex failure... But there was no short, no fumes (as explained in other forums), nothing particular happened... Maybe a component failure. I think about a switch mode regulator failure... And as I have no other idea, I post here to have your point of view on the issue and to know if it's possible to repair or only to send it back and go on another controller.
Some pictures attached or to be attached..
Thanks for your time.