Weatronic 2.4 RF diagnostic tool
#2676
Thread Starter
To further troubleshoot your system, I would suggest that you run the engine at idle and shut down the Tx to trigger a failsafe condition. Check what the engine does.
BUT you need first to download the content of the ECU memory so that the log is not being stacked behind new data. That way it will be a lot easier to analyze the point of shutdown during the flight.
BUT you need first to download the content of the ECU memory so that the log is not being stacked behind new data. That way it will be a lot easier to analyze the point of shutdown during the flight.
#2677
All very interesting.
I have a question also: if You use the 12-22/DV4, would there be difference in the readout of the telemetry file? (which are also stored in the 12-22).
To be honest, I never compared them.
Also, I have studied the JetCat ECU's own fail safe system and long time ago I decided not to use it. I forgot why,but at the time I thought is was more confusing than it would bring more safety. I fly big gasoline engined tugs which don't carry an own failsafe and I trust the WEA failsafe fully.
We actually check it every year at the beginning of the towing season or after any engine/throttle servo change .
I have a question also: if You use the 12-22/DV4, would there be difference in the readout of the telemetry file? (which are also stored in the 12-22).
To be honest, I never compared them.
Also, I have studied the JetCat ECU's own fail safe system and long time ago I decided not to use it. I forgot why,but at the time I thought is was more confusing than it would bring more safety. I fly big gasoline engined tugs which don't carry an own failsafe and I trust the WEA failsafe fully.
We actually check it every year at the beginning of the towing season or after any engine/throttle servo change .
#2678
Thread Starter
Yes. The on-board sd card records everything from the receiver side. It will record all the data even if the telemetry return is lost.
#2679
My Feedback: (13)
At this stage, it is not guaranteed that the engine got shut down in flight due to an invalid ECU signal, as this could have been triggered on the ground.
The problem is that the failsafe signal seen by the ECU could have been after the crash! As Roger points out, once Tx frames go to zero, the log recording is meaningless as it is taken from the DV4!
You need to check the ECU memory and try to get a time stamp at the beginning of the flight that coincides with the DV4 log to see if the ECU shut down signal was in flight or on the ground after the crash.
Could you also send me your micro 12 config file so I can see how the failsafe was programmed?
The problem is that the failsafe signal seen by the ECU could have been after the crash! As Roger points out, once Tx frames go to zero, the log recording is meaningless as it is taken from the DV4!
You need to check the ECU memory and try to get a time stamp at the beginning of the flight that coincides with the DV4 log to see if the ECU shut down signal was in flight or on the ground after the crash.
Could you also send me your micro 12 config file so I can see how the failsafe was programmed?
Thanks for the support here. I'm going to check the ECU log. Note that the crash occurred because there was no thrust (turbine shut down in flight), not because there was lack of control of the flying surfaces. The only scenario that I can imagine that could fit the theory of the engine shutting down in the ground would be that the turbine went to idle (failsafe, not logged because the loss of telemetry), the pilot pulled the stick to idle and then never raised again assuming that the turbine was off. Although the plane was not too far, the idel sound may not have carried.
I did a range check prior to this flight and confirmed that the fail-safe was set to sent the turbine idle by turning off the transmitter.
I will send the config file.
Thanks!
#2680
Thread Starter
The only scenario that I can imagine that could fit the theory of the engine shutting down in the ground would be that the turbine went to idle (failsafe, not logged because the loss of telemetry), the pilot pulled the stick to idle and then never raised again assuming that the turbine was off.
The position of the throttle channel is recorded without interruption from the DV4 module.
The channel value sent by the DV4 is in green on the diagram above. The ECU output from the Rx is in red.
The stick was pretty much at full thrust all the time after the loss of frames, till on the ground.
Last edited by olnico; 08-31-2015 at 11:07 PM.
#2681
Hello all,
I haven't posted for a very long time and was seeking some advice.
I'm currently flying with a JR10X and JR12X, both with DV3 modules. Although not the most current equipment now, they are all very reliable and I am happy with the performance of both transmitters, running firmware 2.33 amd 2.56 respectively. Consideirng that the DV3 has now been superseded, what is the latest firmware I can run these transmitters on? I have the following receivers, a clever 6, a micro 8, a few micro 12's, and a 12-30 gyro III + GPS. Updating to DV4 modules or a BAT60 for that matter is not an option at the moment. I simply wish to retain my current gear and use the most recent firmware that the DV3 will allow.
I apologise if this question has been asked previously!
Thanks in advance guys,
Best Regards, Frank
I haven't posted for a very long time and was seeking some advice.
I'm currently flying with a JR10X and JR12X, both with DV3 modules. Although not the most current equipment now, they are all very reliable and I am happy with the performance of both transmitters, running firmware 2.33 amd 2.56 respectively. Consideirng that the DV3 has now been superseded, what is the latest firmware I can run these transmitters on? I have the following receivers, a clever 6, a micro 8, a few micro 12's, and a 12-30 gyro III + GPS. Updating to DV4 modules or a BAT60 for that matter is not an option at the moment. I simply wish to retain my current gear and use the most recent firmware that the DV3 will allow.
I apologise if this question has been asked previously!
Thanks in advance guys,
Best Regards, Frank
#2682
Senior Member
Join Date: Dec 2011
Location: , GERMANY
Posts: 190
Likes: 0
Received 0 Likes
on
0 Posts
Hi Frank,
for the DV3, user Firmware v2.62, which is the most recent one. There will be no updates in the future, just bugfixes if applicable...
for the whole line-up of the receivers, use version 2.63 respectively.
best regards and always good flights with Weatronic
Thomas
for the DV3, user Firmware v2.62, which is the most recent one. There will be no updates in the future, just bugfixes if applicable...
for the whole line-up of the receivers, use version 2.63 respectively.
best regards and always good flights with Weatronic
Thomas
#2683
My Feedback: (40)
Hi Frank,
for the DV3, user Firmware v2.62, which is the most recent one. There will be no updates in the future, just bugfixes if applicable...
for the whole line-up of the receivers, use version 2.63 respectively.
best regards and always good flights with Weatronic
Thomas
for the DV3, user Firmware v2.62, which is the most recent one. There will be no updates in the future, just bugfixes if applicable...
for the whole line-up of the receivers, use version 2.63 respectively.
best regards and always good flights with Weatronic
Thomas
On a related note, I am upgrading my JR10X/DV module to a BAT60 transmitter. Will I need to totally reprogram the 12-22R receiver in my MIBO A-10 or is there a suggested method when switching to a BAT transmitter?
Thanks,
Craig
#2684
Craig
After switching transmitters from a Futaba FC28/DV3(only 8 channels) to an FX30/DV4 (12 channels), I have found that a complete reprogramming is necessary when making a big switch like that.
With the FC28/DV3 I still hung to using the Tx's programming possibilities, only used the Weatronic features offered through Giga when the TX did not offer it, however not completely consequent with all my models.
When I moved to the FX30/DV4 I ONLY used the TX programming if it could not do it with Wea/Giga, like switchable mixers. And consequently with ALL my models. Most programming however I normally keep track of in a document so I could rebuild the settings in Giga.
The whole reprogramming of a lot of (complex) models was time consuming, also taking into account new test flights to get all the fine tuning and return Your self confidence/trust in the new setup. Luckily the Look&Feel of the FX30 was pretty much like the old FC28.
But the whole exercise was worth it, the models were more consequently programmed, found better setups and ironed out some older shortcomings that had crept in over the years. The FX30's 12+ channels offered more flexilbility than the limited 8 of the FC28.
With BAT60/64 this will have to be done again, because now most programming is once back again at the Tx side, unless You use it as a "dumb" Tx and not use all of its splendid features. But hey, why buy a new Tx then? And end up in a chaotic scenario with partly programming the Tx trying to keep the old programming on the Rx.
Before You begin, measure all the control surface deflections and important settings using the old system, and start all over again.....Take Yr time, especially in a complex and expensive model like the A-10....
After switching transmitters from a Futaba FC28/DV3(only 8 channels) to an FX30/DV4 (12 channels), I have found that a complete reprogramming is necessary when making a big switch like that.
With the FC28/DV3 I still hung to using the Tx's programming possibilities, only used the Weatronic features offered through Giga when the TX did not offer it, however not completely consequent with all my models.
When I moved to the FX30/DV4 I ONLY used the TX programming if it could not do it with Wea/Giga, like switchable mixers. And consequently with ALL my models. Most programming however I normally keep track of in a document so I could rebuild the settings in Giga.
The whole reprogramming of a lot of (complex) models was time consuming, also taking into account new test flights to get all the fine tuning and return Your self confidence/trust in the new setup. Luckily the Look&Feel of the FX30 was pretty much like the old FC28.
But the whole exercise was worth it, the models were more consequently programmed, found better setups and ironed out some older shortcomings that had crept in over the years. The FX30's 12+ channels offered more flexilbility than the limited 8 of the FC28.
With BAT60/64 this will have to be done again, because now most programming is once back again at the Tx side, unless You use it as a "dumb" Tx and not use all of its splendid features. But hey, why buy a new Tx then? And end up in a chaotic scenario with partly programming the Tx trying to keep the old programming on the Rx.
Before You begin, measure all the control surface deflections and important settings using the old system, and start all over again.....Take Yr time, especially in a complex and expensive model like the A-10....
#2685
My Feedback: (40)
Thanks for your observations! I guess I still don't fully understand exactly what is being programmed in the BAT transmitter vs the receiver itself. With my previous Weatronic setup, a LOT of the programming was in the receiver. It seems likely that starting over may be the best option as you suggest. Probably a good way to get familiar with the BAT anyway.
Thanks,
Craig
#2687
Thread Starter
With BAT60/64 this will have to be done again, because now most programming is once back again at the Tx side, unless You use it as a "dumb" Tx and not use all of its splendid features. But hey, why buy a new Tx then? And end up in a chaotic scenario with partly programming the Tx trying to keep the old programming on the Rx.
#2688
Thread Starter
I brought 5 transmitters and a model to a primary school for the first school week on Tuesday and had a demo session on why programming is important for kids.
I had the kids program a simple model with the Wizard within 30 minutes without any aero knowledge. They loved it ( but lost interest after playing with the flight controls for 5 minutes ). All to say that it will not take you a lot of time to get used to the radio and to program the A-10, especially following my programming guide:
http://www.geohei.lu/olin/data/model...%20rev%206.pdf
Now I can also offer you the BAT-60 program for my Mibo A-10 in mode 1. You will not be able to use it as is on a mode 2 radio, but it will give you a good idea of how to do things.
Last edited by olnico; 09-02-2015 at 10:39 PM.
#2689
Thread Starter
#2690
Senior Member
Join Date: Dec 2011
Location: , GERMANY
Posts: 190
Likes: 0
Received 0 Likes
on
0 Posts
Hi Craig,
Richard and Oli said it already. You have to do a new setup with the BAT6x, but it makes a lot of fun with its interface; so the time being consumed by the programming does not really feel long.
Keep in mind, that there is a new, more powerful firmware running on the receivers when using the BAT6x. The curves, and also new with v6.06, the sequencer data, is stored inside the receiver (like with GC/DV4). Maybe it is a good approach to imagine that Gigacontrol now runs on the BAT6x (or a browser, it contains a web server) instead of a Win-PC. You do the setup there and it is transmitted in real time to the RX config memory. You can spread functions with their corresponding servo outputs/ports (formely "channels") across up to three receivers, and this receivers can be of different type, i.e. a 12-22, a micro and a Tiny or any other combination. All these improvements justify the necessary reprogramming work.
best regards and much fun with the BAT6x
Thomas
PS: In a Weatronic Multi-RX setup, there are no cable links required between the (up to three) receivers. All three can send back telemetry data from the RX-internal sensors, but only one can send back telemetry data from connected external telemetry equipment, like GPS (Pro), Link Vario and so on...
Richard and Oli said it already. You have to do a new setup with the BAT6x, but it makes a lot of fun with its interface; so the time being consumed by the programming does not really feel long.
Keep in mind, that there is a new, more powerful firmware running on the receivers when using the BAT6x. The curves, and also new with v6.06, the sequencer data, is stored inside the receiver (like with GC/DV4). Maybe it is a good approach to imagine that Gigacontrol now runs on the BAT6x (or a browser, it contains a web server) instead of a Win-PC. You do the setup there and it is transmitted in real time to the RX config memory. You can spread functions with their corresponding servo outputs/ports (formely "channels") across up to three receivers, and this receivers can be of different type, i.e. a 12-22, a micro and a Tiny or any other combination. All these improvements justify the necessary reprogramming work.
best regards and much fun with the BAT6x
Thomas
PS: In a Weatronic Multi-RX setup, there are no cable links required between the (up to three) receivers. All three can send back telemetry data from the RX-internal sensors, but only one can send back telemetry data from connected external telemetry equipment, like GPS (Pro), Link Vario and so on...
Last edited by tms-ger; 09-03-2015 at 02:44 AM. Reason: added some information
#2691
Hello Thomas/all,
Thank you for the prompt reply and clarification regarding firmware types. Will there be any compatability issues with Gigacontrol or should I simply use the most latest?
Thank you for the prompt reply and clarification regarding firmware types. Will there be any compatability issues with Gigacontrol or should I simply use the most latest?
#2694
Hi guys, forgot to ask another question....
One of my micro 12's has a damaged antenna where it exits the receiver case. How do I replace without damaging the receiver case? I cannot see any screws so I assume the case can come appart?
Thanks again and best regards,
Frank
One of my micro 12's has a damaged antenna where it exits the receiver case. How do I replace without damaging the receiver case? I cannot see any screws so I assume the case can come appart?
Thanks again and best regards,
Frank
#2695
My Feedback: (40)
Thanks for those explanations and clarifications. I can't wait for my BAT 60 to arrive so I can start using it's remarkable capabilities. It will be a pleasure re-programming my A-10 with so many options available and so much easier than when I only had 9 effective control channels.
Thanks again,
Craig
#2696
Senior Member
Join Date: Dec 2011
Location: , GERMANY
Posts: 190
Likes: 0
Received 0 Likes
on
0 Posts
Hi Frank,
unlike the other Weatronic receiver-cases, the ones from the MICRO line-up are glued together. There are several describtions here in RCU on the topic on how to open them. When I remember them correctly, they used to use pliers in reverse way (open the mouth) to "crack" the case open at the plug side, alternating from left to right side. Since it is glued with CA, it then pops off immediately and after you did the antenna replacement, you can glue them together same way as it was done by weatronic.
Hope that helps
Thomas
unlike the other Weatronic receiver-cases, the ones from the MICRO line-up are glued together. There are several describtions here in RCU on the topic on how to open them. When I remember them correctly, they used to use pliers in reverse way (open the mouth) to "crack" the case open at the plug side, alternating from left to right side. Since it is glued with CA, it then pops off immediately and after you did the antenna replacement, you can glue them together same way as it was done by weatronic.
Hope that helps
Thomas
#2697
Hello Thomas,
I really appreciate your help on these matters, thank you - looks like I might have to read up on this thread and get up to date!
Best regards, Frank
I really appreciate your help on these matters, thank you - looks like I might have to read up on this thread and get up to date!
Best regards, Frank
#2698
Senior Member
Join Date: Dec 2011
Location: , GERMANY
Posts: 190
Likes: 0
Received 0 Likes
on
0 Posts
you are welcome
take this shortcut for opening the MICRO case...
http://www.rcuniverse.com/forum/rc-j...l#post11720859
best whishes
Thomas
take this shortcut for opening the MICRO case...
http://www.rcuniverse.com/forum/rc-j...l#post11720859
best whishes
Thomas
#2700
Thread Starter
For the PC time stamp, this is retained only as long as the module is powered by the coin cell.