Guys,

I have a Weatron 12-22R Gyro II which I am fiddling with and, shamefully, I cannot get past the first steps

The TX unit is flashing/beeping 4 times, which I believe to be "no transmitter" signal but I have set the mode to PPM 12 (N 1.5), 35.250 and still I get the 4 beeps.

Connecting to the GigaControl, when I power up the TX (whilst USB connected) it auto switches to PPM-12 but the modulation status stays at no-signal BUT every 20secs or so it will flash up PPM-12 for about 0,5s and then back to no signal. []

Any ideas?

Rgds,
Mark

Did you go through the full binding procedure?

I have written a binding manual that you can find here:
http://www.geohei.lu/olin/data/model....33%20rev3.doc

If this does not work, please contact me by Skype ( MarcS will help you on this ).

Hi Oliver,

Not getting much luck binding. When I follow your instructions the red light flashes 3 times which I believe means 'threshold range limit'???

This is the blink pattern when I switch the TX on........ http://gallery.me.com/schroedm#100050

Rgds,
mark

OK Mark.

Your firmwares are probably not compatible.
You need to update both the transmitter module and receiver module to version 2.33:
http://www.weatronic.com/en/download...-12-22-r-serie
http://www.weatronic.com/en/download...l-24-dual-fhss

Make sure that you format the card correctly before doing the update ( FAT 32, cluster size default ). The card shall be a recent one, max 2 GB, formatted in a good quality reader/writer. The formatting process is essential for the firmware update to occur correctly.

Also read these instructions:
http://www.weatronic.com/en/download...-24-dual-fhss-

P.S: I can see that your receiver is already running on 2.33. So just check the transmitter firmware version on Gigacontrol and update if necessary.

Hi Oli,

Thanks! I'll try this tonight and let you know.

Cheers,
Mark

I've seen that message when messing about with the modulation in my tx compared to the modulation set in giga control. I see you have manually selected PPM12 in Wea. I think you will find it is set up for the Multiplex PPM12 (confusing I know, because there is a separate choice for mpx !). manually selecting PPM12 in Wea works with my Multiplex in 12 channel mode. Why should it be different? In 12 channel mode multiplex does shortening of the PPM signal to time compress it and give a faster refresh rate than say graupner in 12 channel mode. With the Wea manually set to look for this it may not be understanding a longer PPm12 data stream - what tx are you using Mark?

The tx and rx will be binding because the tx is sending its codes, but the tx module is not getting control data so no data is being sent to the servos and they won't move.

The problem that causes the "no signal" message is that the Wea module can't make sense of the data stream that the tx is giving to it. Try using a plain 9 channel or less, PPM with gigacontrol set to auto, that should work and prove that the components are basically sound. From there move on to the higher numbers, perhaps they are PCM only and maybe gigacontrol's auto setting can't decipher the different brands of PCm and has to be manually set to that type of PCM.

Harry

.

.

Harry you are right. However I have the feeling that Mark might have its transmitter module on firmware 2.04 whereas it's receiver is running on 2.33 as shown on the first picture.
In that case the first thing to do is to update the transmitter module.

Thanks Harry & Oli.

I am running a Futaba 14MZ

Oli, not that it makes much difference possibly, but the 2.33 you seen on that screen shot is the TX firmware. Is it possible the RX firmware is not 2.33?

Cheers,
Mark

Mark, does the 14MZ do 12 channel in PPM? Maybe it only does it in PCM in which case you probably need to manually select the Futaba PCM mode in the gigacontrol.

If you have just bought the module and rx direct from Weatronic, they ought to both be up to the latest firmware though its still worth checking.

Run everything in plain old 8 or 9 channel PPM mode, it should work and establish comms between tx and rx, if not then suspect a different firmware version.

H

Harry,

Yes, 14MZ does 12ch PPM. It is an option to choose.

Alwin sent me the set last week so I'd imagine they're on the same firmware but i will check.

Cheers,
Mark

might be worth checking your Tx is not too close to the model also whilst trying the setup.
>1m is best.

I will go as far as to say I am sure that your tx and rx are bound even though they don't appear to work!

I have done this myself by doing manual selection of the modulation in gigacontrol (PPM12 to suit a 12 channel model) and then being caught out at the airfield when I tried to quick bind to my 7 channel Typhoon. The tx and rx lights all showed they had rebound but I had no control - because the tx for that model memory was sending 9 channel data to the wea module which had previously been set manually to PPM12 and it could not match the 9 channel data to the 12 channel setting in the Wea. I had no laptop with me to change the Wea back to auto so I lost the day's flying session. Got home and connected it up and got the same screen as shown in mark's photo - PPM12 manually selected, and the box beneath that is blank (it should show the actual modulation being used) and to the right of it the message "no signal". I changed to auto, it instantly came to life proving that the binding at the airfield had worked as the lights on tx and rx had said, even when there was a modulation mis-match and it seemed that nothing worked.

Since then I have set the wea to auto and never change it, it reacts instantly to me changing the tx between models using 9 or 12 channel mode.

Mark has manually set the Wea to PPM12. Should that work with Futaba in PPM12 mode? Surprisingly, no! Weatronic publishes a table of modulation settings to use (in German only :-( ) and it says that the Futaba in PPM12 mode should use Wea in auto mode, and do not use Wea in PPM12 mode, it causes problems. http://www.weatronic.com/en/download...nic-sendemodul

Marc, set the Wea to auto and I expect it will all suddenly work!

H.

Thanks Harry, I'll try tonight but I am fairly certain I left it on Auto and then noticed it had changed itself to PPM-12?

I assume it is still ok to leave the TX in PPM-12 as per the instructions.....

I agree with Harry !
Set the modulation to auto and see if that changes anything
I run all my planes with weatronic and 14MZ, every model is set to "PPM12" in the transmitter, do NOT attempt to use PCM, you will get a small "jitter" every 60 seconds, that is when the transmitter sends out the failsafe configuration to the (Futaba) receiver, Weatronic has warned us of NOT using PCM on that one ! (I don't know if this has changed in the latest FW versions, but I doubt)!

Just one more note, I have had my tx adapter (the small box that goes into the 14MZ) go bad on me, I changed it to a new one, and it had worked ever since! The symptoms was exactly as you see them, 4 blinks, and "no signal". I'm not saying that this is what is wrong with your setup (probably not), just something to have in mind (could also be a bad cable/connector between the TX module and the adapter)

(and yes, I changed cables etc etc, moved back and forth with the broken tx adapter and a new one, and without any doubt it was the adapter that had turned me down, after approx 3/4 years of use)

Your tx seems to be set correctly Mark, and choose PPM12 in the Futaba. In gigacontrol there is the box for you to select a data mode (auto, PPM12, SPCM etc) but the box below that is used by gigacontrol to show the data mode actually in use. Your photo shows it is blank which is what happens when there is a mis-match. if you choose auto, that box below your choice will show whatever the auto has selected to use, such as PPM12 or PPM-uni. It is bizarre but the PPM12 selected by auto behaves differently to the PPM12 in the user selectable box! It could be that you had previously chosen auto, Wea then read the data and auto selected a correct variant of PPM12 and thus it puts "PPM12" in the box below "auto". That may explain why you did once look at it and see both auto and PPM12 on the screen at the same time and perhaps you then thought, quite reasonably, that you could manually select PPM12. The Wea will stick with whichever you choose in gigacontrol, it doesn't change with the tx memories etc.
H

Marc, if your receiver is new, then it is running on 2.33. Worth checking anyway.
The module stuff is a possibility as well. I've had a problem on my FG-12 module: it was not pushed enough inside the slot and was giving intermittent erratic orders and/or no transmission frames to the Tx module.
I use PPM-12 as well on my 12FG. The source frames are much higher than with PCM.

Hello everyone,

I am working with my 3rd weatronic receiver. Great stuff. But I have a quesiton too, hoping one of the gurus can help me!

I have been using ppm auto on my last 2.08 firmware and am about to update to 2.33.

Will I still be able to choose auto ppm for my JR 10X?

Thanks, I appreciate your help,
Dave

Yes Sir. This is one of my setup. Makes my 10X so much more powerful in terms of programming that I have not felt the need to upgrade to the 12x...
Bear in mind though that as soon as you have upgraded your transmitter, you'll have to upgrade all your receivers too, because 2.08 is not compatible with 2.33...

ok, beginning to suspect the 'switch' on the RX

Here's what happens...

1. Plug in red flag
2. Plug in both batteries
3. Remove red flag and RX switches on, green light flashes twice regularly (receiving no signal)
4. Plug the blue binding flag in and green light sequence does not alter to binding mode (0.5s flashes) (this is plugged in after about 10secs of unit switching on)

If I repeat the above steps but plug the red flag back in nothing happens. Only way I can get the unit to switch off is to unplug the batteries....

Am I really being this stupid or is something up?...........

M

Something wrong. Let me try to rplicate that stuff at the workshop...

Thanks Oli. Does this help.......

http://gallery.me.com/schroedm/100055

I got that once a long time ago and can't remember the circumstances. There was no subsequent fault in the switch or rx and they have worked fine ever since so I put it down to me stumbling across some odd sequence of events that fooled the firmware!
H