Weatronic 2.4 RF diagnostic tool
#2326
Junior Member
My Feedback: (7)
Join Date: Jun 2011
Location: Moscow, RUSSIA
Posts: 6
Likes: 0
Received 0 Likes
on
0 Posts
Weatronic system oficially! working with ppm, zpcm, spcm modulations. No matter pcm or ppm modulation used, because this is a power trouble.
I flying 5 years on DV3 module on Jet and other planes and helis on JR 12x in Spcm modulation, and Im scared how flying next....
I flying 5 years on DV3 module on Jet and other planes and helis on JR 12x in Spcm modulation, and Im scared how flying next....
#2327
At the moment I use 3 older FC28's with DV3 and recently I moved to FX30's with DV4, one with BTa.
I am flying every week with jets, large tug planes and large gliders. I have about 20 WEA receivers in use, from the smallest to the Gizmo. I fly at many places, sometimes busy, sometimes quiet.
As most other users I have never, (or had only once or twice) an inflight reset. (higher altitudes). The effect on the flight was near zero.
It is strange that You have some much trouble. Only two weeks ago, when I was flying very close to another pilot, I heard a warning indicating reception was minimal, later I saw on the software that the frames indeed were almost zero for a few seconds. Flying itself was not disturbed. I stepped a few feet aside and it was all OK again.
Do You fly in the same location that You have the trouble? Maybe an airbase? It might be interesting to check with a scanner if there is no large external source, interfering with Your equipment. Do pilots with other equipment on the place You fly, have the same problems?
BTW I cannot find any info about the warnings that might be triggered, did I overlook some info?
I am flying every week with jets, large tug planes and large gliders. I have about 20 WEA receivers in use, from the smallest to the Gizmo. I fly at many places, sometimes busy, sometimes quiet.
As most other users I have never, (or had only once or twice) an inflight reset. (higher altitudes). The effect on the flight was near zero.
It is strange that You have some much trouble. Only two weeks ago, when I was flying very close to another pilot, I heard a warning indicating reception was minimal, later I saw on the software that the frames indeed were almost zero for a few seconds. Flying itself was not disturbed. I stepped a few feet aside and it was all OK again.
Do You fly in the same location that You have the trouble? Maybe an airbase? It might be interesting to check with a scanner if there is no large external source, interfering with Your equipment. Do pilots with other equipment on the place You fly, have the same problems?
BTW I cannot find any info about the warnings that might be triggered, did I overlook some info?
#2328
Senior Member
Join Date: Dec 2011
Location: , GERMANY
Posts: 190
Likes: 0
Received 0 Likes
on
0 Posts
argentin,
I can only stick to what is written in the posts before... I do not think that your problem is related to a "going down expirience at Wea"! That is nonsense. See the Weatronic innovations coming up after 2009... So no more discussion on that theme.
To solve your problem:
As sidgates wrote, logically there must be another reason for your faults. Also never heard about mass-failures like the one you told us with Wea. And no mass-faults with WEA in general.
You write that this is a power problem. Do you _know_ that or do you _think_ that ? Did you measure in the power supply line coming from the TX adapter module going to the WEA module ? Did the voltage drop when the DV3 / DV4 resets ? You say with power supplied via USB there are NO resets. That would mean that the the TX-modules were all going bad. Maybe you did something wrong to them when you did the soldering task with the patch cables ? Maybe your in-official! soldering modifications applied to the sets you sold have all the same mistakes in them ? That _could_ be an explaination why all the sets you sold and modified show the same incident...
What do the log files read ? Did they clearly show the messages which show up when a regular power-on is done ? Or is there something else to interpret. Really would like to help you but is is hard to do it remote and with that small amount of information.
Regarding the video itself and with no more additional information, one can not decide if this reset is done by the watchdog in the module itself or by external power failure. Remove the SD card and try again... Flash the latest FW and try again. You can always downgrade afterwards if you like to. (If you have ie an HP server and it fails and you call support, the first question is if you are running latest FW. If you don´t, you have to upgrade, regardless if your server has run flawlessly up to the point where the error occurs. Otherwise they will not give you any further support...)
Give us more detailed information and i am sure everyone here will try to help you.
best regards
tom
I can only stick to what is written in the posts before... I do not think that your problem is related to a "going down expirience at Wea"! That is nonsense. See the Weatronic innovations coming up after 2009... So no more discussion on that theme.
To solve your problem:
As sidgates wrote, logically there must be another reason for your faults. Also never heard about mass-failures like the one you told us with Wea. And no mass-faults with WEA in general.
You write that this is a power problem. Do you _know_ that or do you _think_ that ? Did you measure in the power supply line coming from the TX adapter module going to the WEA module ? Did the voltage drop when the DV3 / DV4 resets ? You say with power supplied via USB there are NO resets. That would mean that the the TX-modules were all going bad. Maybe you did something wrong to them when you did the soldering task with the patch cables ? Maybe your in-official! soldering modifications applied to the sets you sold have all the same mistakes in them ? That _could_ be an explaination why all the sets you sold and modified show the same incident...
What do the log files read ? Did they clearly show the messages which show up when a regular power-on is done ? Or is there something else to interpret. Really would like to help you but is is hard to do it remote and with that small amount of information.
Regarding the video itself and with no more additional information, one can not decide if this reset is done by the watchdog in the module itself or by external power failure. Remove the SD card and try again... Flash the latest FW and try again. You can always downgrade afterwards if you like to. (If you have ie an HP server and it fails and you call support, the first question is if you are running latest FW. If you don´t, you have to upgrade, regardless if your server has run flawlessly up to the point where the error occurs. Otherwise they will not give you any further support...)
Give us more detailed information and i am sure everyone here will try to help you.
best regards
tom
#2329
Junior Member
My Feedback: (7)
Join Date: Jun 2011
Location: Moscow, RUSSIA
Posts: 6
Likes: 0
Received 0 Likes
on
0 Posts
Hi
This problem on soldered and not soldered is same.
I'm thinking that is power trouble, because with usb it working. We checked every adapter and on tx module voltage. Its correct. Futaba 14mz powered from 2s lipo, jr 10 and 9x from 3s lipo, futaba 9c and graupner mc-24 from standard 8cells ni-mh.
Other our transmitters, like futaba fx-40 - 2pcs working fine, but scary to flying. Jr 12x powered from 3s lipo and working correctly too.
Modules which have troubles used different firmware, from 2.3 to 2.61. By the way, when this trouble begin, it cant be updated! Also mo matter with or without sd card, it restarting. Module on 14mz is dv4, working fine 1 year, and after one flight - result on video.
Same trouble has been in few days with jr9x on dv3....
No matter where, on field, in building another field.
Our customers go to us from another sides of Moscow city.
I only want tell all about that, because using it too dangerous for large scale planes and jets.
I have 3 sets of weatronic on jr 10x, and 12x. I like it, sorry liked before this troubles. I have more than 20 different receivers, from tiny 5 to gizmo 12-22r hv
This problem on soldered and not soldered is same.
I'm thinking that is power trouble, because with usb it working. We checked every adapter and on tx module voltage. Its correct. Futaba 14mz powered from 2s lipo, jr 10 and 9x from 3s lipo, futaba 9c and graupner mc-24 from standard 8cells ni-mh.
Other our transmitters, like futaba fx-40 - 2pcs working fine, but scary to flying. Jr 12x powered from 3s lipo and working correctly too.
Modules which have troubles used different firmware, from 2.3 to 2.61. By the way, when this trouble begin, it cant be updated! Also mo matter with or without sd card, it restarting. Module on 14mz is dv4, working fine 1 year, and after one flight - result on video.
Same trouble has been in few days with jr9x on dv3....
No matter where, on field, in building another field.
Our customers go to us from another sides of Moscow city.
I only want tell all about that, because using it too dangerous for large scale planes and jets.
I have 3 sets of weatronic on jr 10x, and 12x. I like it, sorry liked before this troubles. I have more than 20 different receivers, from tiny 5 to gizmo 12-22r hv
#2332
Senior Member
Join Date: Dec 2011
Location: , GERMANY
Posts: 190
Likes: 0
Received 0 Likes
on
0 Posts
Just to be sure, you measured the voltage _coming out_ of the TX-Adapter ? What voltage did you measure there ? Did you use a voltmeter which has a graph display so you can see short voltage drop-outs ?
Next, what happens if you power up the TX (with the DV3/4) and have no matching (binded) RX switched on for at least 15 or 30 minutes. What do you observe ? Is it going in that escalating reset loop anyway ? See also the refering logs. Maybe it is first a good idea not to physically move any component involved during the test periods.
Next, what happens if you reset the TX module using GigaControl ? (Binds are stored on the RX...) Does that change something ?
Since the error seems to be reproduceable, it is not required to fly a model until the failure is found. It seems it does not have to do something with the RF link.
Alan (and others) have reported about the patch cable which can lead to failure over the time. Maybe you have two different error-sources in the same time interval. Since you did not solder all sets. We fly with the original patch cable and swap it every year as a "wearable sparepart".
Do the tests and report as precise as possible please...
Tom
Next, what happens if you power up the TX (with the DV3/4) and have no matching (binded) RX switched on for at least 15 or 30 minutes. What do you observe ? Is it going in that escalating reset loop anyway ? See also the refering logs. Maybe it is first a good idea not to physically move any component involved during the test periods.
Next, what happens if you reset the TX module using GigaControl ? (Binds are stored on the RX...) Does that change something ?
Since the error seems to be reproduceable, it is not required to fly a model until the failure is found. It seems it does not have to do something with the RF link.
Alan (and others) have reported about the patch cable which can lead to failure over the time. Maybe you have two different error-sources in the same time interval. Since you did not solder all sets. We fly with the original patch cable and swap it every year as a "wearable sparepart".
Do the tests and report as precise as possible please...
Tom
#2333
My Feedback: (6)
Argentin,
I agree with the comments of the others and would suggest that you try to isolate the failing component. There are 3 components to the Wea system that could fail: the tx adapter, the patch cable and the DV3/4 unit.
Fortunately, you have both working and non working systems on hand to test with.
I would suggest starting by replacing the patch cable on a non-working system and check the results as this is the most likely failure point. If it still fails in the same manner, I would replace the DV3/4 with one from a "working" system. If the known good one now fails, this will tell you that it is likely a problem in the adapter. etc. Try to isolate which component is causing the issue.
Mike
I agree with the comments of the others and would suggest that you try to isolate the failing component. There are 3 components to the Wea system that could fail: the tx adapter, the patch cable and the DV3/4 unit.
Fortunately, you have both working and non working systems on hand to test with.
I would suggest starting by replacing the patch cable on a non-working system and check the results as this is the most likely failure point. If it still fails in the same manner, I would replace the DV3/4 with one from a "working" system. If the known good one now fails, this will tell you that it is likely a problem in the adapter. etc. Try to isolate which component is causing the issue.
Mike
#2334
Junior Member
My Feedback: (7)
Join Date: Jun 2011
Location: Moscow, RUSSIA
Posts: 6
Likes: 0
Received 0 Likes
on
0 Posts
Hi
Some weeks ago I tried to change adaptors, modules in any combination. So, 100% working adapter giving on output: ppm, +12v, gnd, +6,6v.
From Futaba 14mz +8,2v, ppm, gnd, +8,2v.
No matter soldered or used standard cable, main module restarting. I have on hands 4 modules, and trouble is same. One man thinking about capacitors 16v 10mf. Hi opened their module and foud 5pcs. As he told me, one capacitor (electrolyth) drop out voltage. He replace it to new one from motherboard, and his module worked 12hours. (All night) without any restarting. I cant meet him now, because we are on holidays on different sides of Russia. Only by phone call he gave me this information.
One dv4 module will be send to weatronic, Germany in a few weeks, other 2 modules with 1 working as example has been gave to our electric specialists.
Now I dont have more information.
My opinion - for safety, I and our friend will go to JR DSMJ, EZUhF and Fasst.
Too dangerous use it.
Some weeks ago I tried to change adaptors, modules in any combination. So, 100% working adapter giving on output: ppm, +12v, gnd, +6,6v.
From Futaba 14mz +8,2v, ppm, gnd, +8,2v.
No matter soldered or used standard cable, main module restarting. I have on hands 4 modules, and trouble is same. One man thinking about capacitors 16v 10mf. Hi opened their module and foud 5pcs. As he told me, one capacitor (electrolyth) drop out voltage. He replace it to new one from motherboard, and his module worked 12hours. (All night) without any restarting. I cant meet him now, because we are on holidays on different sides of Russia. Only by phone call he gave me this information.
One dv4 module will be send to weatronic, Germany in a few weeks, other 2 modules with 1 working as example has been gave to our electric specialists.
Now I dont have more information.
My opinion - for safety, I and our friend will go to JR DSMJ, EZUhF and Fasst.
Too dangerous use it.
#2335
Senior Member
Join Date: Dec 2011
Location: , GERMANY
Posts: 190
Likes: 0
Received 0 Likes
on
0 Posts
...yeah, and for sure, those brands also use capacitors... :-) That is no real solution, no logical decision. You just shift the problem; what will you do when their capacitors or other board components will give up ;-) ? (Of course you should use what you think is best for you...)
Tell us what Weatronic reports when they have their hands on the DVx module you will send them. Never the less, it makes no real sense to me what you are reporting. One defect module - OK. Can happen to any electronics. But that much, and in DV3 and DV4 generation ? This doesn´t match my Wea experience at all. There must be some other reason for this failures; in case this are real failures... too hard to evaluate over that distance and with the given information.
Tell us what Weatronic reports when they have their hands on the DVx module you will send them. Never the less, it makes no real sense to me what you are reporting. One defect module - OK. Can happen to any electronics. But that much, and in DV3 and DV4 generation ? This doesn´t match my Wea experience at all. There must be some other reason for this failures; in case this are real failures... too hard to evaluate over that distance and with the given information.
#2337
Senior Member
Join Date: Aug 2006
Location: rishon lezion, ISRAEL
Posts: 127
Likes: 0
Received 0 Likes
on
0 Posts
Hi every one
my son LIAD BARNES is sponsered by Weatronic As team pilot
we have just informed that the BAT 60 will be on the market from aogust and that will sell the TX in the next Jet Power show in this September
this is great news for all the weatronic costumes
no more cables
best
zeev
my son LIAD BARNES is sponsered by Weatronic As team pilot
we have just informed that the BAT 60 will be on the market from aogust and that will sell the TX in the next Jet Power show in this September
this is great news for all the weatronic costumes
no more cables
best
zeev
#2338
I have been very fond of Weatronic receivers in the past and I would consider buying a BAT 64 if they ever come to materialize. But as for now, I believe it when I see it.
#2341
Junior Member
Join Date: Dec 2011
Location: Terneuzen, NETHERLANDS
Posts: 29
Likes: 0
Received 0 Likes
on
0 Posts
Hi
We have global trouble with weatronic transmitter modules. We are producing jet planes, and used 5 years weatronic production. More than 20 sets has been sold to our jet customers, and many recommended to buy. But at last 3 months we have 6 times returned our customers to us with same tx module trouble. No one plane has been crashed. Trouble in next. At first time seen of trouble.
After 10-15 minutes, module begin restarting or rebooting, such You turn On and Off transmitter. All 3 leds blinking, so no RF connection with receiver. It constantly repeating 1-2 times in minute, but it repeating more and more... After more 5 mins, it restarting nonstop....
So All 6(six ) weatronic making it same, if plug usb- it working normally.
All our weatronic soldered directly to tx adaptor. Firmware different on sets. 2.3 to 2.61.
One set is DV4, other 5 is old, DV3.
I have video, but cant upload right now, because problems with hi speed wifi...sorry
We trying contact with weatronic, but they can't help.
Their main electronic specialist go out from company at 2009, now their experience going down....
We have global trouble with weatronic transmitter modules. We are producing jet planes, and used 5 years weatronic production. More than 20 sets has been sold to our jet customers, and many recommended to buy. But at last 3 months we have 6 times returned our customers to us with same tx module trouble. No one plane has been crashed. Trouble in next. At first time seen of trouble.
After 10-15 minutes, module begin restarting or rebooting, such You turn On and Off transmitter. All 3 leds blinking, so no RF connection with receiver. It constantly repeating 1-2 times in minute, but it repeating more and more... After more 5 mins, it restarting nonstop....
So All 6(six ) weatronic making it same, if plug usb- it working normally.
All our weatronic soldered directly to tx adaptor. Firmware different on sets. 2.3 to 2.61.
One set is DV4, other 5 is old, DV3.
I have video, but cant upload right now, because problems with hi speed wifi...sorry
We trying contact with weatronic, but they can't help.
Their main electronic specialist go out from company at 2009, now their experience going down....
Almost looks like the same problem I'm dealing with for almost or more than a year by now on my Futaba FX30. Had worked like a charm for perhaps 6 months but then trouble started.
But in my case it doesn't really restart due to a power failure, it just logs the codes "Framedekodierung unerbrochen" and "Framedekodierung gestartet".
Most of the times it starts after about 15 minutes (or sooner) with a few alarms, then it increases to a couple of alarms in like 30 secs but once I hear it starting I need to get my stuff down since it will go into a constant flow of errors within a few minutes. Same problem on DV4 and on DV4BT (all standard items new out of the box and not been fiddled with)
During such an error it goes into failsave since there is no connection....and that is quite a problem since we fly RC planes.
Must admit that in the beginning it got my adrenaline pumping trying to land a 1000+ euro glider from 300 meters high between almost constant failsave holds......
After the 4th time (also with different planes since at first I had the idea that the problem was with just 1 plane) I could crash land without shouting "No Control" and peeps wouldn't even notice that I was actually travelling in deep ***** 9.
Knocking on wood here...I've kept everything in one piece and undamaged until now.
^^ Click on the picture above
To my understanding one gets a load of new log-files in case of a power down due to that (crappy) cable. Since I have to deal with them crappy cables I have enough experience by now to know that when it restarts it starts a new log file.
Already have sent all my Weatronic stuff to Weatronic but nothing was found by them.
Also bought new modules, cables and adapters...
Changing to a DV4BT module did give some results though; It gave the verbal warning: "Transmitter not recognized". Now that doesn't comfort you when floating around at 300 meters height.
Besides telling me to buy more new connection cables Weatronic doesn't know a solution to above problem and by now they won't respond on my emails anymore (perhaps I was a little bit too frank in my last email when I brought the topic connection cable up again).
I have the feeling that they won't bother to find proper cables so that people are forced to buy their new TX (when it will be sold in like 20 years or so).
Did some testing last weekend with the new modules and stuff on my old FF9 TX for 2 days (about 5-6 hours of flight time in total).
Besides the really annoying crappy-connection-cable-disease with occasional power out restarts and/or erratic and stupid TX-voltage readings during flight no notifications as in the picture came up (need to check on the log files of day 2 though).
I have a 2nd FX30 coming in this week and I will put the Weatronic stuff on that one and do some testing in about 2 weeks.
If FX30 #1 shows problems and FX30 #2 doesn't ==> the problem is in the 1st FX30 and that one will be sent to the repair guy for check up and maintenance.
Reading your story, I have the feeling that FX30 #2 most likely might start to show the same problems as #1 after a few months.
But, let's wait and see what #2 will do.
In the end it might be that FX30/FX40 and Weatronic just can't stand each other on a certain way.
The connection cable is really a black page....omg...I even have one D.O.A..
Weatronic told us all 5 years ago that they would come up with a proper solution as soon as possible.............but hey...guess that will be just as soon as with their new BAT transmitter (winter 2021 perhaps).
The biggest problem is that these cables are led outside and come into contact with other things quite easily on Futaba radio's. Even when you take care not to bounce into something.
Only for that reason I would advise people to stay away from Weatronic refit kits (especially in combination with Futaba FX-series).
By the way, does anyone build/sell reliable 200mm connection cables? They have been out of stock at Weatronic for really quite some time now and mine is def. busted (again).
#2342
Junior Member
Join Date: Dec 2011
Location: Terneuzen, NETHERLANDS
Posts: 29
Likes: 0
Received 0 Likes
on
0 Posts
But anyway, I don't want their TX, it's hiddeous :-)
I like the Futaba transmitters and don't want to spend 1600 euro on their TX just to get rid of a 10 euro costing stupid cable (which probably is bought by them from China for not even 5 cents)
#2344
As some may know I am a strong advocate of the Weatronic system, and not because I am sponsored, I'm certainly not, but I use this system because of its technical capabilities, which also, I believe, makes it the safest system.
I have now used the Wea 2.4 since its inception and the first Micro is STILL in place in a Bobcat a hundred or so flights later.
Of the systems I am now flying, (16 receivers of all types and three Tx units. (two on JR 12X, one is DV4 and one on JR10 X) the ONLY problem I have had was with an original type patch cable.
All patch cables were changed to newer type and positively anchored using tie wraps to the Tx handle to prevent movement. A tiny touch of CA locks the plugs I avoid touching the cables and I keep my Txs scrupulously clean.
On the 12X units I now have Alan's cables (they are light blue not grey so easily identifiable. ) but have left an original type on the 10X which flies only gliders, (but gets most use, 40 mins. or so thermalling almost every day) to see any developments.
So far I have experienced absolutely zero problems, and I check every flight on GigaControl. Of course I don't doubt that some users HAVE had, and are having, problems and you have my sympathy, and in that case I suggest step 1 is to change the patch cable to one of Alan's versions. Then see how you go. My guess is you will see your problems disappear.
I have just returned from SegelFluggeMesse near Munich (JetPower for gliders) I was very impressed at the amount of Weatronic electronics being used in VERY expensive (and exquisite) sailplanes. I spoke to one rep. ( a highly respected German electric flier) from one of the major high end brushless motor manufacturers (Plettenberg) who said that they did a technical analysis of Weatronics and found it to be exceptionally good, the best, use patch antennae and range is truly incredible.
I spent some time with Weatronics at SFM and Stephan and Ralph (a former Airbus, EADS electronics engineer) explained the new Wizard on the Tx, quite mazing. My own beta test Tx is back with them for upgrade to latest firm/software then I can begin to really explore it. I can't say I am a fan of the cosmetic appearance but judging by what Wea have done with their receivers etc. the Tx functionality should be quite something.
As for availability of the BAT 60, next Jet Power possibly, following Christmas certainly, their words on Sunday.
Deviating slight, I spent yesterday afternoon at the Deutches Museum aviation exhibition at OberSchleissheim, not far from Munich airport, what an absolute treasure, with many jets including the surviving X31 and the Dornier VTOL transport with all ten engines still installed !
Regards,
David.
I have now used the Wea 2.4 since its inception and the first Micro is STILL in place in a Bobcat a hundred or so flights later.
Of the systems I am now flying, (16 receivers of all types and three Tx units. (two on JR 12X, one is DV4 and one on JR10 X) the ONLY problem I have had was with an original type patch cable.
All patch cables were changed to newer type and positively anchored using tie wraps to the Tx handle to prevent movement. A tiny touch of CA locks the plugs I avoid touching the cables and I keep my Txs scrupulously clean.
On the 12X units I now have Alan's cables (they are light blue not grey so easily identifiable. ) but have left an original type on the 10X which flies only gliders, (but gets most use, 40 mins. or so thermalling almost every day) to see any developments.
So far I have experienced absolutely zero problems, and I check every flight on GigaControl. Of course I don't doubt that some users HAVE had, and are having, problems and you have my sympathy, and in that case I suggest step 1 is to change the patch cable to one of Alan's versions. Then see how you go. My guess is you will see your problems disappear.
I have just returned from SegelFluggeMesse near Munich (JetPower for gliders) I was very impressed at the amount of Weatronic electronics being used in VERY expensive (and exquisite) sailplanes. I spoke to one rep. ( a highly respected German electric flier) from one of the major high end brushless motor manufacturers (Plettenberg) who said that they did a technical analysis of Weatronics and found it to be exceptionally good, the best, use patch antennae and range is truly incredible.
I spent some time with Weatronics at SFM and Stephan and Ralph (a former Airbus, EADS electronics engineer) explained the new Wizard on the Tx, quite mazing. My own beta test Tx is back with them for upgrade to latest firm/software then I can begin to really explore it. I can't say I am a fan of the cosmetic appearance but judging by what Wea have done with their receivers etc. the Tx functionality should be quite something.
As for availability of the BAT 60, next Jet Power possibly, following Christmas certainly, their words on Sunday.
Deviating slight, I spent yesterday afternoon at the Deutches Museum aviation exhibition at OberSchleissheim, not far from Munich airport, what an absolute treasure, with many jets including the surviving X31 and the Dornier VTOL transport with all ten engines still installed !
Regards,
David.
Last edited by David Gladwin; 07-22-2014 at 12:27 AM.
#2345
Senior Member
Join Date: Dec 2011
Location: , GERMANY
Posts: 190
Likes: 0
Received 0 Likes
on
0 Posts
Hi Dutchy,
thank you for your detailed information. This shows me, other than the one from argentin, that you are serioulsly using WEA and try to isolate the failure. That you do not like the design of the BATxx is OK. Hard to develop something that fits all. I will buy one cause I like it. And I buy it not only to get rid of this patchlead... Which ever worked flawlessly for us from the beginning on our mx22,
--
Your log clearly shows that you did not lost the RF link to the model; the DV4* just got only short interrupted control signal (PPM) from the TX. Seems like there is something running out of sync over the operating time, so that the DV4* can not realiable digitize the PPM signal coming from the FX30. (Modulation [with failsafe-frames info] ?, FW ? ) So the patch lead can not be entirely defect, minimum the Vcc and GND lines are OK. Maybe the PPM-signal line has problem. But I do not think that. I guess that there this is a compatiblity problem between the FX30 and the DV4*. You symptom is not related to the one reported by argentin. Would be interesting to see the signal curve coming from the FX30 on an oszilloscope... Futaba is known for their special signaling format which can differ from TX to TX to different countries/country-codes. But as you can see, this really doesnt stop the chinese people from creating clone RX :-) ...but makes the life even harder for those who want to develop retrofit kits...
I am really interested in your expirience with that second FX30... please report. BTW, are you coming to holland glide ?
As Oli stated, Alan (here in this thread) is doing superb manufactured patch cables for interconnect the DV* with the TX adapter.
Maybe it is a good idea to PM him...
LG
Thomas
thank you for your detailed information. This shows me, other than the one from argentin, that you are serioulsly using WEA and try to isolate the failure. That you do not like the design of the BATxx is OK. Hard to develop something that fits all. I will buy one cause I like it. And I buy it not only to get rid of this patchlead... Which ever worked flawlessly for us from the beginning on our mx22,
--
Your log clearly shows that you did not lost the RF link to the model; the DV4* just got only short interrupted control signal (PPM) from the TX. Seems like there is something running out of sync over the operating time, so that the DV4* can not realiable digitize the PPM signal coming from the FX30. (Modulation [with failsafe-frames info] ?, FW ? ) So the patch lead can not be entirely defect, minimum the Vcc and GND lines are OK. Maybe the PPM-signal line has problem. But I do not think that. I guess that there this is a compatiblity problem between the FX30 and the DV4*. You symptom is not related to the one reported by argentin. Would be interesting to see the signal curve coming from the FX30 on an oszilloscope... Futaba is known for their special signaling format which can differ from TX to TX to different countries/country-codes. But as you can see, this really doesnt stop the chinese people from creating clone RX :-) ...but makes the life even harder for those who want to develop retrofit kits...
I am really interested in your expirience with that second FX30... please report. BTW, are you coming to holland glide ?
As Oli stated, Alan (here in this thread) is doing superb manufactured patch cables for interconnect the DV* with the TX adapter.
Maybe it is a good idea to PM him...
LG
Thomas
#2346
My Feedback: (13)
I hope they hurry up with the Bat 60. This weekend I was getting movement in the rudder when moving the elevator stick, similar to a programmable mix. There was no mix, just some kind on interference within my Futaba 12FG. I opened the Tx and re-connected the cabling from the stick to the PCB inside the TX and the interference when away. Evidently my radio is getting old. If it dies (hopefully not in the during flight) not many options to replace!
#2347
Junior Member
Join Date: Dec 2011
Location: Terneuzen, NETHERLANDS
Posts: 29
Likes: 0
Received 0 Likes
on
0 Posts
Hi guys,
Thanks for your replies.
I'll definitely PM Alan for those cables.
Like said, I do like the rest of the Weatronic gear, e.g. the LinkVario Duo with TEK and the multiple setup options of GC, but the cable issue in combination with that other problem really aggravated me past the boiling point sometimes.
I'll run some tests with both FX30's besides each other to draw a conclusion and let you know.
Had that once too. When I moved the elevator my rudder moved with it.
Looked like somesort of mix too but it was an easier fix. (Well fix, it showed where I F-ed up lol )
I had the elevator control rod running alongside the receiver.
It was a Micro10 with Gyro and at big throws the elevator pushrod pushed the receiver over a lil bit activating the gyro on the rudder.
Probably has nothing to do with your problem but was a nice story to tell.
I assume you fly mode 1 but if you hook your set up to GC it will most likely show the rudder throws making it easier to see what is actually happening.
Thanks for your replies.
I'll definitely PM Alan for those cables.
Like said, I do like the rest of the Weatronic gear, e.g. the LinkVario Duo with TEK and the multiple setup options of GC, but the cable issue in combination with that other problem really aggravated me past the boiling point sometimes.
I'll run some tests with both FX30's besides each other to draw a conclusion and let you know.
Looked like somesort of mix too but it was an easier fix. (Well fix, it showed where I F-ed up lol )
I had the elevator control rod running alongside the receiver.
It was a Micro10 with Gyro and at big throws the elevator pushrod pushed the receiver over a lil bit activating the gyro on the rudder.
Probably has nothing to do with your problem but was a nice story to tell.
I assume you fly mode 1 but if you hook your set up to GC it will most likely show the rudder throws making it easier to see what is actually happening.
#2348
Junior Member
Join Date: Dec 2011
Location: Terneuzen, NETHERLANDS
Posts: 29
Likes: 0
Received 0 Likes
on
0 Posts
As said, I'll pick that 2nd one up tomorrow and will run them alongside each other and place the findings here.
Would have loved to go to that F3J competition but unfortunately I'm not available that weekend.
BR.
Paul