[12many]

I upgraded my Revo board to r901 of the 'next' development branch and that went ok.  However, when I updated the OPLink using GCR r901,  I can't seem to bind to the flight controller.  It looks like the procedure has changed or something and it's not clear what to do.

To update the OPLink I followed the standard procedure:  With OPLink unplugged, go to Firmware & hit 'Upgrade & Erase', then plug-in the OPLink and the firmware updated successfully.  Unplug, plug-in.

The OPLinkMini device is detected in GCS, so I went to Configuration / OPLink and set Max Power = 3.16 and checked the Coordinator box, leaving other parameters at their default values.  Hit Save, wait for Rx/Tx to settle, unplug & plug-in, return to Configuration / OPLink page.

I expected to see a hexadecimal number displayed in Device ID, but instead it says "AutoGen" and is greyed out.

How do I obtain the Device ID for the flight controller to bind to if it's not displayed?

Hovering over the field displays help text saying 'Enter your custom Device ID for this device [...] Leave blank to use autogenerated Device ID".  However the Device ID appears to be read-only and only displays "AutoGen".

Is OPLink telemetry working in build r901?  If so am I doing something wrong or has the procedure changed?

[nitromethane]

Device ID should be displayed in the appropriate field in the Status section under the configuration section on the OPLink config page.

Copy that number and paste it the Coordinator ID box on the remote end, reboot OPLink, it should now work.

Never actually tried to set up a custom Device ID but the box seems to be writable for me.

[f5soh]

Procedure is the same.

Like the step 4 says:

4. Disconnect / Reconnect your OPlink mini modem, this enables modem and show Device ID.

https://librepilot.atlassian.net/wiki/display/LPDOC/OPLink+Configuration#OPLinkConfiguration-Binding
This mean remove all power from OPLink to obtain a effective reboot.

I expected to see a hexadecimal number displayed in Device ID, but instead it says "AutoGen" and is greyed out.

If you didn't input a custom deviceID, the deviceID still auto generated like always and current deviceID in use is displayed in Status section below.
The custom deviceId field uses a Hexadecimal mask, you should start typing from the left if you want to set the deviceID yourself.

[12many]

Ok, I figured out the problem.  There are two 'Device ID' fields on the Configuration / OPLink page:  one in the Configuration panel and one in the Status panel.  The Device ID in Configuration caught my eye because the one in Status is somewhat less visible being black-on-gray and listed among several other fields.

This might be confusing UX for new users;  having two Device ID fields on the same page is a bit ambiguous at best.  Perhaps change the "Device ID" label in Configuration to "Set Device ID" or something to clarify it's a write field and distinguish it from the corresponding read-only Status field below?

I'm no UX designer, but I also noted that my misunderstanding with the editable Device ID & Coordinator ID fields was because there appears to be an invisible region where clicking outside that area and typing keystrokes aren't accepted.  Example, click on the editable textbox to the right of the 'AutoGen' and type - nothing happens.  Once I selected all text in the textbox it became what's happening.

Thanks for the help.