[MultiBen]

A question for the 'next' branch.

I ordered and received my OpLink Mini Ground & Air for the Chinese mini revo.

They both had OP 15.5 loaded.

Plugged Ground unit into USB for GCS 'next' version - it connects and shows up as USB: OpLink as a device and autoconnects to it but I am not able to Upgrade.  Button(s) stay grayed out in Firmware Tab.  no OpLink tab shows up for me to see the version.  Terminal that i ran GCS from is showing a bunch of UAVObject errors which makes sense as it is a version missmatch.

Plugged Ground unit into USB for GCS '15.09' version - it connects and I can flash to 15.09 and any other branch besides 'next' ( ie, I can use autotune branch, etc ).  This is where I get OP 15.05 version from.

Now flashed with 15.09 I plug Ground unit into USB for GCS 'next' version - still the same results.  It connects and shows up as USB: OpLink as a device and autoconnects to it but I am not able to Upgrade.  Button(s) stay grayed out in Firmware Tab.  No OpLink tab shows up for me to see the version.

Cable works correctly for mini revo - I can upgrade/downgrade to all versions.

Thoughts?

Ben

[hwh]

Long question, short answer 

Click upgrade and erase with the oplink NOT connected.  Connect it when it tells you to.  Oplinks don't do the usual warnings about firmware version mismatches and have to be upgraded with the disconnected method.

[MultiBen]

I'm with ya Hank!  But the buttons are all grayed out?  I did that to get to 15.09 but 'next' is showing only grayed buttons.

Ben

[MultiBen]

Fixed in latest pull

Sorry to waste time, should have made sure I was updated before posting.

Ben

[hwh]

I didn't know it was broken in any of the next versions. I have seen that upgrade buttons disabled  before but I don't remember what combination of things get you to that point.

As long as it's working for you in the current next it's all good.

[f5soh]

Looks normal, using the last version from next branch the Uavo used for Oplink changed.
This means the device is connected but the only Uavo needed for Oplink  is not readable.

So you cannot use current Oplink "next" firmware with previous versions.

[MultiBen]

Thanks for the replies.

The problem I had was at a certain pull ( 15.09 + r630 ) the buttons disabled and the mini wouldn't upgrade from OP 15.05 or 15.09 release. I updated last night and rebuilt and it is working fine. 

It was my error for not being current.

Ben

[f5soh]

Disabled buttons only reflect a uavo mistake.

In fact those buttons can't be used while Oplink is connected because Oplink do not support automatic update/reboot.

[MultiBen]

Exactly! The first screen shot of the buttons grayed out is after just starting the binary, with out connecting the mini oplink.  There was no way to Upgrade and then connect.

Ben

[TheOtherCliff]

Both the Upgrade buttons will be grayed out if you built the code yourself and did not build the opfw_resource

In that case you can use "rescue" and navigate to the *.opfw file that you want to flash.

[hwh]

Both the Upgrade buttons will be grayed out if you built the code yourself and did not build the opfw_resource
In that case you can use "rescue" and navigate to the *.opfw file that you want to flash.

That's it, I knew I had done something once that caused that but I couldn't remember what.

[MultiBen]

Cliff, I'm betting that is exactly what I did, built the revo specific fw I needed and not oplink, when I did a pull, I rebuilt everything and then probably had the fw available for oplink.

Ben

[cddmflyer]

Hi,
Not sure if this is correct place to post, but I am having trouble with Oplink ground and Revolution. I think this maybe confusion over firmware as I seem to have both oplinks functioning, inbuilt on revolution and oplink mini.
I have BL V6 and 15.09 on Revolution and have downloaded latest version of oplink mini from site and loaded that on to my mini, BL 4, this will not bind. I have also done an upgrade and erase, with mini first unplugged and I seem to get firmware tagged 15.09, but still no bind.
I have checked and rechecked all the other settings power channels, device name etc and these all seem correct.
I get solid blue and semi steady yellow on ground oplink connected with usb, and the revolution when powered up idenpendently gives me full green and alternating blue and yellow leds' but no bind.
At a loss what to try next, any suggestions would be of use.

[f5soh]

Hi, welcome.

Just for test, can you try setting the max com speed on both sides ? (115200bauds)

[cddmflyer]

Brilliant that fixed it with both set to 115200, I got them to bind and have communication between Revolution and oplink mini.
OK not what I was doing wrong I why that should fix it but happy that it did.
Thanks very much for that, any explanation to what I was doing wrong would be appreciated.
Now need to tackle GPS, seems to overwrite back to nema once plugged in after changing to UBLOX in mustation.
Thanks Again