Ebeo / opentx

Automatically exported from code.google.com/p/opentx
0 stars 0 forks source link

Trainer mode not turning TX all the way on. #48

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Which board (stock / gruvin9x / sky9x / Taranis) are you using?
stock

What is your openTx FW version?
opentx-r2413

What is your openTx EEPROM version?
213-0

What steps will reproduce the problem?
1. Get a simulator that uses the JR trainer cord/protocol.
2. Configure a model for it on your controller (use PPM output protocol).
3. Turn the controller off.
4. Plug in the trainer cord to the simulator, and notice that the controller 
comes on, but there is no PPM output from it.

What is the expected output? What do you see instead?
When I plug in the trainer cord, I expect the controller to come on, and PPM 
output to be sent out via that cord.

Please provide any additional information below.
I've been told, but not verified (sorry) that er9x does this properly. The 
sources were dissimilar enough that I couldn't see what might be causing such a 
difference.

Original issue reported on code.google.com by m...@mired.org on 10 Jun 2013 at 10:12

GoogleCodeExporter commented 9 years ago
Are you using the stock module? If yes, you need to either:
- Take it out when using the simulator cable
- Leave it in, but change the protocol in your model setup to PPMsim, and turn 
the radio on when using the simulator. 

Original comment by bernet.a...@gmail.com on 15 Jun 2013 at 9:52

GoogleCodeExporter commented 9 years ago
I normally use the PPMsim protocol. I get the same behavior if I remove the 
module.

The bug is that the transmitter comes on when you plug in the trainer cord, and 
the software is obviously running (I can go into config menus, etc.). However, 
you don't get PPM output until you move the power switch to on. As far as I can 
tell, the PPM output is the only thing *not* working. This is annoying, and 
makes using the simulator painful.

The fix I would prefer is that you get PPM output without having to flip the 
power switch, partly because I expect that can be done in software.

An alternative fix would be that the transmitter not turn on when you plug in 
the trainer cord. I suspect this can't be done in software

Original comment by m...@mired.org on 15 Jun 2013 at 8:22

GoogleCodeExporter commented 9 years ago
No, backlight (depending on how it's installed) and the beeper are not powered 
either. This is a hardware design issue. 
The PPM signal not being present is also a hardware issue, when the module is 
not powered it drags the signal down. This led to the "1k resistor mod" that 
was recommended at some point. 

Original comment by bernet.a...@gmail.com on 23 Jun 2013 at 8:43

GoogleCodeExporter commented 9 years ago
Let's be clear here. I do not have the the resister mod, and I *am* using the 
PPM setting on the transmitter. The Tx is *turned off*. The power switch is in 
the off state.

When I plug in a trainer line, it powers on, *without* touching the power 
switch. The backlight comes on. If the switches are in the wrong state, I get 
beeps for warning. I also get beeps on button presses. The beeper is working 
fine. The monitor changes as appropriate to changes in input controls. The only 
thing that I doesn't appear to be working is the PPM signal. Turning on the 
power switch causes the PPM signal to come on.

This behavior means that you have to remember to both turn off the power *and* 
unplug the trainer cable in order to shut the power off. No other Tx I've used 
does this - either it powers on completely when you plug in the trainer cable, 
or it doesn't power on at all then.

I have been told that er9x does *not* suffer from this problem, which would 
indicate that it's *not* a hardware issue. I'd intall er9x to test myself, 
except my 9x build VM is running linux, which has fried itself.

Original comment by m...@mired.org on 23 Jun 2013 at 9:34

GoogleCodeExporter commented 9 years ago
I just tried T9X and TH9X cooperation in trainer mode (FW r2413 OpenTx) and 
everything seems to be fine.

Original comment by ztrojanek on 1 Jul 2013 at 12:36

GoogleCodeExporter commented 9 years ago
I also checked during the week-end in a public meeting. No problem here. Please 
use the forum to ask questions, will be easier to answer. Unless there is a 
real bug, which seems not the case here.

Original comment by bson...@gmail.com on 1 Jul 2013 at 12:45

GoogleCodeExporter commented 9 years ago
One last note: I have done the usual PPM circuit hw modification (inserted 
resistance 1KOhm). 

Almost certainly not a FW bug.

Original comment by ztrojanek on 1 Jul 2013 at 12:52

GoogleCodeExporter commented 9 years ago
Ok understood, he doesn't have the 1k resistor mod. One possible fix would be 
to force PPMsim when the Tx is slave (main switch OFF).

Original comment by bson...@gmail.com on 1 Jul 2013 at 12:59

GoogleCodeExporter commented 9 years ago
@mwm@mired.org

Did you try the PPMsim protocol with Tx OFF?

Original comment by bson...@gmail.com on 1 Jul 2013 at 1:01

GoogleCodeExporter commented 9 years ago
The usual procedure:

1. Master TX is on
2. Slave Tx off
3. Connecting cable
4. Slave Tx is automatically switched on and collaborates with Master Tx.

On both Tx's was selected protocol PPM 8Ch.

When using protocol PPMsim 8Ch slave must be turned on.

Original comment by ztrojanek on 1 Jul 2013 at 1:22

GoogleCodeExporter commented 9 years ago
I actually did take this to the forums first (possibly rcgroups, not the 
9xforums). I was told this was a bug in openTx, as er9x did not have it. It's 
been a while, because I've moved (twice) while trying to find time to check the 
er9x & openTx sources to see if I could find a fix and submit a patch.

Seems that ztrojanek sees the issues I have - that with PPMsim 8ch the slave 
must be turned on to work, but comes on even if it's not turned on.

Yes, I've been using the PPMsim protocol.

Original comment by m...@fpcomplete.com on 1 Jul 2013 at 7:08

GoogleCodeExporter commented 9 years ago
As they say in some (not mentioned) company: This is not a bug, it is a 
feature. :)

Original comment by ztrojanek on 1 Jul 2013 at 10:09