The problem is that my Weatronic system does not respond to the full stick movement. I have proved it on two different Tx which were both serviced by the authorised agent earlier this year. But Weatronic just keeps insisting that my Tx is faulty. I know my two Tx are not faulty so the last remaining element is that my Wea tx module may be faulty. However I am not getting a helpful response from Weatronic so I need to establish from other users if they get the same result as me, or not. If you get the same result as I do then we can make Wea listen, if you don’t then I can start trying to figure out what is wrong with my Wea system.

The Weatronic system stops responding to the Tx stick, which means servos stop, when the stick has been moved 93% of its travel. The last 7% of stick movement is ignored by Weatronics. This is a small amount of stick movement so if I just wiggle the stick I won’t realise that the servo is not working at the end of stick movement. I have to move the stick slowly at the edge of its movement in order to see it. Before I reach max stick movement the servo stops, and any movement of the stick in the last little bit is ignored. It means that if I use travel adjust to fine tune the travel of the servo, nothing happens in the range 93% to 109%, so if I want to reduce or increase travel slightly from 100%, nothing happens. Those values above apply to Multiplex. If I am correct, the problem will occur on JR and Futaba too but only at particular values above 100% travel.

All brands set their 100% travel to a different length of servo pulse so different values apply if you are using JR or Futaba with Weatronic. All brands use centre +-600 microseconds (µs) as a limit but choose a different 100% value. Multiplex uses +- 550µs, JR uses +-400µs and Futaba approx +-430µs. That’s why different brands have different max travels, JR is 150% (400*1.5=600) Futaba max is 140% (430*1.4=600) and Multiplex max is 109% (550*1.09=600).

I first noticed that the servo didn’t respond to Multiplex full stick movement and then hooked the radio up to GigaControl and proved it there too. In the servo mapping tab, right click on the servo to see its curve etc and watch the green bar along the bottom of the graph, it moves in response to the stick. For a Multiplex tx, the green bar reaches 100% travel and stops before the stick has been moved fully over, and as per the servo it does not respond to any stick movement in that last little bit. I discovered by altering the servo centre value in the tx and watching the servo move and the green bar in Gigacontrol move, that the point at which Wea reaches 100% travel and stops responding is 93% Multiplex Tx travel. All Multiplex travel values from 94% to max 109% are ignored.

I keep emailing Alwin at Wea and giving him my findings but he just says his same Multiplex Tx as mine works fine, my Tx must be faulty. I tried Weatronic on another Multiplex Tx and got the problem at precisely the same values but Alwin doesn’t change his response. Alwin then told me that Wea specifies that a servo pulse limit is +-512 µs. Straight away we see the problem. Multiplex at 550µs normal 100% travel exceeds the Wea artificial limitation. Now we can do a sum. 512/550 = 93% !!!!!!!! So Wea’s own figures agree exactly with my experimental result. I asked Multiplex to confirm their servo travels and have it from them in writing for everyone to see http://www.multiplexrcd.com/mms/publ...ueyonder.co.uk I sent this confirmation from Multiplex, along with the results of the arithmetic and my experiments to Alwin and he still refuses to discuss it, insists that 512 µs is the max servo signal even though I have got it in writing for him from Multiplex, and still says my tx must be faulty even though both of them do the same.

Why haven’t the rest of you encountered the problem? The 100% JR and Futaba pulses at 400 µs and 430 µs respectively are within the 512 µs Wea limit. You will only encounter the Wea limit if you turn your travels up to JR 128% and Futaba 119%. Since that’s pretty rare then it is likely that none of you have encountered the problem.

Now for the experiment to see if yours does the same as both my Tx do on Weatronic. For a Multiplex Profi 30xx or 4000 or Royal Evo, set transmission type to PPM9, servo type to other or uni. For other brands of Tx please use PPM and not PCM modulations as I don’t know if the PCM will behave differently. In gigacontrol set tx modulation to Auto or PPM UNI. Ensure in your Tx that all travels are set to the max for your brand, e.g 109%, 150%, 140%, that no travel limits will affect it (e.g. in Multiplex tx go to LIMIT screen and increase from 100% to 109%). In gigacontrol go to servo mapping tab and right click the servo. Move the stick and confirm that you see the green bar along the bottom of the graph moving in response to the stick. Connect a servo to the rx. Now move the stick to the end of its travel. Slowly move the stick back towards the centre and see that for some distance the servo does not move and the green bar in gigacontrol does not move. Only when you have moved the stick back a little bit will the servo and the green bar start moving. You can wiggle the stick in that last bit of movement and the servo and gigacontrol will not move.

Next put stick back at the centre and in your Tx go to whatever screen can adjust the servo’s centre point, e.g Multiplex 4000 in menu 1, servo, travel, point 2, or Royal Evo servo calibration, point 2. The value should be at default 0%, move it upwards and the servo should rotate with the changing value and the green bar along the bottom of the gigacontrol graph should also move. Watch the servo and the green bar. If you have a Multiplex tx, do they stop moving at 93%, and any changing value between 93 and 109 has no movement of the servo or gigacontrol? For JR do they stop moving at around 128% and for Futaba do they stop moving at around 119%?

I am eagerly waiting to hear if any of you can replicate the problem I am getting from both my Tx!