A little bug for me with the latest Futaba 18mz software update. 2.5.1 Anyone else?
 

Ok so last weekend I updated my 18mz to the latest 2.5.1

I also coincidentally had one of my CB-Elektronics FSS-460 Pitot Airspeed sensors start acting up.

It was zeroing out at 32 mph on start up and seemed like the air speeds were erroneously high.

So I swapped it out with one I had in another model ... same problem.

I went back to software 2.4.1 and it seemed to fix the problem. I will go flying tomorrow and see how it behaves in the air.

I was wondering if anyone else has updated and had any issues. Thanks!

I have updated 5 of them and we have not seen any issues yet on the telemetry side of things, but we are not running the sensor you are speaking of. We are running info directly off our FADEC so we don't need our handheld units for normal operations and then running different sensors for our airspeed (ASSI) and then our normal GPS from Futaba and voltage info from the PowerBox Royals. I do have a fellow pilot that has that system, we will see if we get the same results. But if you reverted back to the last update and that fixed it you will probably need to contact Futaba about that one. I'm pretty good with the Futaba systems ( I set up almost all of the ones in our club) but that one sounds like something that only they could answer... Maybe.

Steve,
I also see problems with the new firmware. I modified my ASSI device to use the "True airspeed" sensor type they added.
The values will not update on the "telemetry screen", I have to add the sensor to the "home 2" screen, then they will update. They also update if I press on the actual sensor on the "telemetry screen", otherwise not.
And then I can not understand why they did the JetCat sensor the way they did, using 14(!) slots for the data, and you can not disable those that you do not want to see !!
I don't care about many of the parameters, but they have to throw them all in my face :(
Again the "non-flexibility" of the telemetry shows its face.....

I would have to agree with Carsten. Futaba really needs to do some things with the telemetry for jet guys. I have been hardcore Futaba for years and have owned every top end radio, I hope they can fix these issues. Not all of us use JetCat. But with the Xicoy interface for the FADEC unit that doesn't really come into play. But, my readings are all in degrees, no user defined ability to change the degrees into what we need them to say. And then with PowerBox Royals, those guys have got everything lined up for us to get the gps data from the unit but Futaba is the one that needs to let us read the data. I will have to say, they are not leading the pack in the telemetry field, which sucks because I really like the 18MZ, and Futaba products.

Totally agree!
And there is no support for dual engine systems whether jetcat or other engine types.
Glad I have my Android telemetry system ;)

Carsten,

Talking of which, how are you going with the AMT interface?

Cheers,

Jan

Hi Jan,
(red ears here :D) I have been overwhelmed with work but the nice test system from AMT is on my desk starting monday evening :)
I'll get back once I have the stuff decoded

I have the PowerBox GPS II sensor and also reading 32 mph on my GPS speed. I read it as soon as I power on the radio. Today, I will power up GPS on the jet and when I receive a good GPS signal, will check it again. I may try to reset sensor and if that doesn't work, go back to 2.4.1

Hi guys,

try out for testing "Metric" instead of "Yard-Pound" in the SYSTEM UNIT menu.
See if you can observe more logical results.


BR
Dirk

Sounds like the same bug with a different sensor.

The fact that it reads 32 instead of 0 makes it seem like its some sort of unit of measure conversion bug. 32 degrees Farenheit = 0 degrees Celsius. I know its a speed measurement, not temperature but it seems like more than coincidence.

And I'm with the rest of you. Come on Futaba! If you want to stay the leader you have to lead! Love my 18mz best radio in my book but some of the 'others' are making quick progress on the telemetry front.

When I select Meters, speed indicates correctly (0 KM/H). In yards- pound mode, I also had set a maximum speed threshold of 160 mph (Type 4 alert) and that speed indicated 518mph when I switched it back to Yards-Pound. I attempted to reset it and I could only get to 124 mph. I had to arrow down to 0 and set it back to 160 mph. Obviously there is a conversion issue. Think I will go back to 2,4,1

Now that I think of it, I had to do the same thing, I had to go back to Metric, seems fuatba "0" is converted to 32 F. Seems they use metric a the "0" point. I totally missed that you were using the yard pound system instead of the metric system. All of this leads to the point that we cant put things in to speed reading instead of a temperature reading for our telemetry sensors. I did get the same results as you in the Yard pound system.

Can anyone send me version 2.4.1 or on where to download from....stupid me deleted in on SD card :( From now on, I will keep all updates on my computer hard drive for cases like this....lesson learned!!
Seems futaba website only saves previous software update pdf files.

sent you a PM, I have it

I noticed the same 32mph GPS malfunction last weekend after updating to the latest software. I spoke to Futaba support on Monday and again yesterday. It's a bug with the new software update, don't know when they will have a fix but they know about the issue and are working on it.

Which Sensor gave you that problem?

I'm using the Futaba SPS 01G sensor. I tryied a new receiver, new sensor, new model, re-updating the software, etc. When I spoke to Futaba the first time, the guy had a freshly updated 18mz, he tried it and it was doing the same thing as mine.

In my opinion, Futaba is really dropping the ball on their $3K flagship transmitter. Updates are far and few between and most are little tweaks. You can request new features in the Futaba support forum where the mod sends them directly to Futaba. I've put in a few and although some may be jet related, others seemed to be universal like a talking timer. How many flyers would find that useful? Having been a Futaba user since day one, I would still recommend them to a newbie but if someone asked me today what brand of flagship radio they should buy, it would not be this radio specifically because either Futaba doesn't want to add new useful features or more than likely they didn't put that flexibility into it when it was in the design stage. Right now you can buy a Jeti 16 which seems to have way more useful features and telemetry for almost half the price of an 18 and have enough leftover to change out a good number of planes to Jeti Rx's. I really like the 18 but thought it was overpriced when I bought it a few years ago but now with the competition out there it is really not worth it. I hope Futaba can change my mind but I'm not holding my breath.

' I hope Futaba can change my mind but I'm not holding my breath.'

I'm right there with you afterburner.

Ok so the new update has a coding issue when in the US mode. Mine only working correctly when set to Metric. Any word from Futaba on a correction to the last update?

Anyone spoke directly to Futaba ?

Come on Futaba, can we get a bug fix or something?

I can't even get the 2.5 to install. says "update not compatible with this transmitter" anyone have any ideas on how I can get it to work. Guessing I am doing something wrong when I transfer the files off my pc, but this isn't rocket science... lol

I have a similar problem, mine says "Files not found" don't think I'll bother.

m

I am sure everyone has figured it out already... You need to use an empty SD-card, not forget to unzip the downloaded zip file properly, and above all do this download and unzipping with a WINDOWS computer (it does not unzip them all correctly on a Mac, resulting in the "not compatible" message... ask me how I know.... I lost today one hour on this). Note it is not 100% clear that the files are/were unzipped indeed

I am quite worried about the short note that for European transmitters in version V2.5.0 the transmission seems to be restricted to 100 mW. Some of my planes are all carbon fibre and I did not have any issues so far...

Is it worth it to upgrade to V2.5.0 or should I go back to V2.4.1 too ?

I dont suppose anyone knows if they fixed the issue with GPS sensors not working after the last update? Im still running an older version so I dont run into this with my Robbe gps sensor

Sorry if my post was not completely clear ; I was only talking about the issue how to upgrade the higher version(s), caused by using a Mac computer (resulting in the mentioned "some files are not compatible" error message during the installation process), and not about the telemetry bugs itself in the pertaining transmitter software.

I just Noticed Futaba has an August 5, 2015 date on this update.

Editor Version: 2.5 Encoder version: 2.2

But it is still calling it a 2.5.1 which is the version that didn't play well with the Airspeed Telemetry.

Has anyone updated with this version and is it any different than the one that was out in January?

Stevek

Hello Steve,

I´m stil wondering that you got a Version 2.5.1 already in January.

I got here from Robbe in Germany a non released (Beta) Version 2.5.1 in May. I tested it an gave Robbe Futaba a report back becaus of our FEPC and FSS products.
This version had not the known issues we know from 2.5.0 in respect to the IAS and GPS Speed Display.
I´m still using the Version 2.5.1 Beta with my test models.

Unfortunatly I lost my contact at Robbe because Robbe went into insolvency.

Ripmax the new German Futaba Distributor released aprox. two week ago a now official Version 2.5.1 for T18MZ.

I would suggest in your case pull the now official released 2.5.1 and install it.

BR
Dirk

I think it is Fixed !!!!!!!!!!!! Woo Hoo! :o

To be a little cautious I only tested this on 1 plane and on the bench.

Tested with the CB Elektronics 460.

Fired up in Yard-Pounds and zeroed out at 0 MPH. Switched over to Metic and zeroed out at 0 kph

I did NOT get the 32 mph error at start up. I think Futaba fixed the bug !!!

Happy Flying

SteveK

But Futaba still need to get all the display units fixed - so that we don't have use RPM for ml or temp for voltage etc. Surely all they have to do (for now) is to give us the option to change the display unit (not only the name of the sensor). Changing and updating verbal warnings to have the correct terminology, can come later.

Jan

I just updated the GPS II and the teleconvertor tonight to the most recent software updates and updated the 18MZ to editor 2.5.1, encoder 2.2. When set to "Yard/Pounds" unit measurement, I'm still getting 32 F for the temp reading. Switching to metric zeroes everything. I didn't have the success that Steve had. Any suggestions?

That's too bad Mike. The CB Elektronics 460 spoofs the Robbe GPS unit for speed. It doesn't convert it from temperature. I haven't tried it with my ASSI device planes, not sure what they will do.

I kept the copy of the earlier Update Folder on the SD card and renamed the folder Update.Prev in case I need to go back. I will try and do some testing in the air this weekend.

I posted this in the radio support forum nine months ago! I've given up hope on Futaba releasing any useful updates in general or any updates that will play nice with Xicoy.

http://www.rcuniverse.com/forum/futa...l#post11917056

Still beating your head against the wall?

Yeshttp://www.sherv.net/cm/emoticons/fi.../bash-head.gif, would you happen to have an icepack, Excedrin, and a Jeti DS-24?

Very Funny ! I want a talking timer too! Cmon Futaba, you've gotta keep up/catch up to the Germans !

Actually Jeti is Czech

Gents,

After hours of beating my head against a wall (having joined Marty), I have yet to have the PB teleconverter downlink data to my 18MZ. My installation is;

Futaba 18MZ Editor v2.5.1 Encoder 2.2
Futaba 7008SB receivers operating in dual. Telemetry is active and the teleconverter is plugged in the S-Bus 2 port of the primary receiver.
Powerbox GPS II v0.1.0 set to Royal SRS in Terminal.
Powerbox Teleconverter v0.3 set to T18MZ in Terminal.
Powerbox Royal SRS v9.3

I've registered and installed the teleconverter as per instructions included with the teleconverter as well as tips on the PB forum. The only telemetry data received at the transmitter is the battery voltage. No Powerbox data is being received. I am showing strong signal in the tx in the telemetry section. The GPS is acquiring satellites and the LED is solid green. Using the advice on the PB forum, I've performed the data reset (telemetry) and sensor reload. Still no Powerbox data received at the transmitter.

I've compared my transmitter settings with a successful teleconverter operator and they are identical.

Any suggestions on configuration changes that I've missed or is it possible that I've got a defective teleconverter?

Thanks!
Mike

Mike,

In case you didn't try it already I would suggest to re-bind both receivers when in dual configuration! The difficulty might be that there are now two receivers both believing they are "primary" ones. This causes telemetry conflict.

AND: make sure you really bind both separately: you must remove SRS cable from SRS Royal as otherwise you end up re-binding both receivers as "secondary" eventually. (as turning of receiver power from PowerBox will impact on both receivers ;)

Regards, Ilkka

Any news guys? Does 2.5.1 resolve the units conversion on speed or does it not? .. since we have conflicting reports here.

Also, does anyone have the 2.4.1 download zip files? I would like to get the CB FEPC working but I have only the 2.3 version on my radio and don't want to go to 2.5.x until the units bug is fixed. Apparently 2.4.1 has the Current sensor that I need for the FEPC (2.3 does not) and I see that only 2.5.1 is on Futaba's website here in the US.

Sigh...

Dave McQ