[Jhinta]

what happend to oplink , its connected but cant change anything

gcs (git master)
gcsas cordinator
drone as slave witch has id of master

[TheOtherCliff]

If it is an OpLInk, you probably just need to flash matching firmware on the OpLink.

Also, you must change OpLink settings with that OpLink connected with USB.  You can't change Revo OpLink or other remote OpLink with RF.  That causes a problem.  You can't save and restore settings properly across OpLink.  You always get the ground OpLink in the settings and not the air OpLink.  I don't know if that has been reported as a bug yet.

[Brian]

That's not a bug.  The OPLink explicitly removes the OPLinkSettings UAVO from the UAVTalk stream coming from the connected device.

It could be debated how that should work, but IMO it would be confusing and somewhat error prone to support re-configuring the radio link over the radio link.

In any case, the OPs problem is likely mismatched firmware.

[TheOtherCliff]

It used to be that you could save settings over the RF and you would get the air oplink settings, now you get the ground oplink settings.  That's a bug if you ask me.

Take settings you saved over RF and restore them over USB and your oplink is messed up.

I haven't tried to find out what happens the other way around (settings from USB restored over RF).  Does it mess up the ground oplink or just not write the settings at all?

[Brian]

I don't know when it would have showed the remote settings.  I'm pretty sure that was not the way it worked when I originally wrote it, and I haven't modified that recently, so it would have to have flip-flopped at some point.

I don't generally save and restore settings, so I didn't know about that aspect.  That does sound like a bug.

The functionality could probably be changed by removing a couple of lines in the oplink firmware.

Edit:  Looking at the code reminded me of some of the issues involved.  One of the problems is with saving OPLinkSettings.  The modem doesn't know if an FC is connected or not, so how does it decide if a OPLinkSetting save command should be passed on or executed locally?

In any case, this discussion has derailed this topic.  We can discuss it in a but report if you want.  It sounds like there is at least one bug in the way things work now that should be addressed at some point.

[Jhinta]

compiled mater and flashed oplink and revo ,

what i used to get doesnt work anymore, cant change anything i just get some data stats & shows log replay 
i'm not talking about setting of the oplink , setting of the quad !

i can change with usb , drone side setting
i can change oplink side usb connectted -> setting
CANT ! do anything when oplink is active as virtual usb

[f5soh]

Set the "Air Data Rate" in both sides to 100000 or more

Sorry... are you using master or next ?

[Jhinta]

see

[Jhinta]

Set the "Air Data Rate" in both sides to 100000 or more

Sorry... are you using master or next ?

sorry correct answer , next

[f5soh]

Its working here. Air Data Rate to 57600 do not work.

You need 100000 at least while using next (that's equal to old 57600)

[Jhinta]

Its working here. Air Data Rate to 57600 do not work.

You need 100000 at least

Air Data Rate = bit ratespeed ?
why the change as it was working with lower speeds even.

[f5soh]

Simply set 100000 using Next is the same as 57600 using 16.09

You quoted the same post 3 times... maybe not needed ?

[TheOtherCliff]

assuming you want the oplink to do just data
now that you have revo, oplink, and gcs on the same version

power Revo and Oplink off
plug oplink into usb and configure it (protocol=OpLinkCoordinator, LinkType=Data, MaxPower, and ComSpeed) copy "Device ID" number onto paper
save
unplug
plug Revo into usb and configure it (protocol=OpLinkReceiver, LinkType=Data, CoordinatorId=WhatYouCopiedFromOplink MaxPower, and ComSpeed same as oplink)
save
unplug

[Jhinta]

have it working on 128  tnx
retested 100 also working (maby i was to fast) somtimes it works

[f5soh]

assuming you want the oplink to do just data

Cliff, no need to redo config for something already connected.
Just a too slow baudrate.