openrcforums

Thanks for all the help jhsa. Upgraded the bootloader and firmware, managed to bind to a frsky EU LBT for the first time with the changes.

Balls. Just got home with my brand new SD card and it's the wrong size! I thought it was standard :'(... Waste of a tenner there.

What size is it supposed to be?

Edit - for anyone who needs to know it's micro SD.

Ok thanks for the help! I'll have a go tonight if I can get hold of an SD card by then.

I don't have an SD card in the radio. Do I have to have one?

Hey everyone. I'm looking at upgrading the firmware on my AR9x to the latest version. As it's been.. Well 2 years :( Unfortunately i'm on bootloader version 1.9, and cannot upgrade because the new firmware file is too big. I have tried out of curiosity but as expected it failed. I can't find anywher...

Just to update this thread. Everything was fine with the multiprotocol module and AR9X + ersky9x. Turned out the seller got frsky D stock and wasn't told. So when I finally give up and get a beecore to replace the old flight controller I take off the shell and there's a micro FrskyD receiver staring...

I'd be tempted to buy a OrangeRX DSM module to attempt it but everywhere seems to be sold out. It looks like HK is having serious problems with their Orange products FCC certification, or the lack/faking of it.. João Ahh that makes sense. To be honest I'm surprised it's took this long for them to s...

That's right. Solid until bind mode, flashes in bind mode, then solid after a few seconds - I assume that's because it's failed to bind.

On the quad end it just keeps flashing with no change or feedback.

And just to cover all bases - you mention that the mode should be reported on the binding screen - there's nothing appearing but the BINDING text.

It only seems to flash like it was attempting to bind normally on the multimodule as well.

It's best to check! I double checked the telemetry options when attempting AUTO bind mode this morning and again there was no luck binding to it, I also double checked that I have the correct option in the source for the multimodule commented out for telemetry inversion and I do. And yup I've been u...

Just tried it - still not working :(. It's hard for me to say that the quad's defective when I'm using such a strange hardware combination to try and communicate with it and no other DSM receivers to attempt to bind to. I'd be tempted to buy a OrangeRX DSM module to attempt it but everywhere seems t...

Thanks Mike, I'm glad I was confused about the rate. So far as I know Auto mode requires the receiver to have telemetry? I seem to remember reading that on the wiki. Is that not the case? And yes I've tried using 6 - 8 channels in the options recently ( strictly it's supposed to only work with 8 acc...

Hi, I'm trying to bind one of these: http://www.dronejunkie.co.uk/product/bnf-micro-fpv-racing-quad/ To my ar9x with the latest ersky9x firmware on it. The quad uses DSM2 / 22ms ( 1024 ). i I'm using a banggood multiprotocol module and I can't for the life of me get it to bind. I've triple checked t...

Finally have a little time to try and compile eepskye again. Mike I pulled the latest source and found another compiler error. In node.cpp it complains about ambiguous use of the abs function. To fix this - include <cmath> and change all instances of abs to fabs ( I'm assuming that they're floating ...

Mike if you want my board with the different cloned chip for proper testing you're welcome to it. All I've done to it is solder on a connection for firmware upgrades. I'm running behind with getting it flashed etc due to sorting out the Ar9x board, if you just want me to do it I'll get it done event...

Okay I'm making progress with building this from source, I'm attempting to build eepskye at the moment but I'll have a look at eepe as well. There seems to be a couple of things that need sorting from your end so far as eepskye goes though. 1. stamp-eepskye.h, have you forgotten to add this file to ...

This is my output from dpkg (don't like using it but it's a deb file) sudo dpkg -i eepe-i386.deb --snip for privacy-- dpkg: error processing archive eepe-i386.deb (--install): package architecture (i386) does not match system (amd64) Errors were encountered while processing: eepe-i386.deb So pretty ...

Thanks for that, there only seems to be a 32 bit version of the program on there though.

I'm not sure I'll have all the 32 bit libraries to successfully use it or not.

Edit - Yeah confirmed for not working on 64bit systems.

I'm finally at a point where I'm able to check whether this firmware works with the newer cloned chips, but I'm having a little problem. I can't for the life of me find eepe for 64bit linux, the site on google code (https://code.google.com/archive/p/eepe/) has dead links. Do I need to compile it mys...

Attached is a macro image of the microchip. Completely different from any others I've seen so far.

It'll maybe take me a day or two but sure I can do that. I have a couple of other jobs to do before I can commit to it.

I posted on the rcgroup forums about this. I got one of these chips in a FlySky transmitter, so it's not just Turnigy that are getting them. Mine is slightly different though. There's no Atmel markings at all, and it's a Green ED040502-H16D rather than Green ED040501-H16D. I haven't tried flashing a...