OPLink Mini - the continuing saga
« on: August 25, 2018, 05:14:47 pm »
After another several month hiatus of building/flying/crashing/rebuilding multiple other aircraft and other projects, I'm once again back to homebuilt multi-rotors and am trying to configure/calibrate my latest.  The current challenge is getting my OPLink working again as it was when I last used it. 
Upon connecting it to my laptop and trying to check the configuration and/or configure it to my new quad, Librepilot couldn't find it, despite all the LED's blinking happily and Windows announcing that it was connected and configured.  Device Manager also reassures me that it's "working correctly".
 I've tried the procedure for "Rescue" and "Upgrade and Erase" several times.  In all cases, it appears that the firmware loads, but it hangs and times out during rebooting.
 I've read all 7 pages of the Forum that come up with a search for OPLink Mini, and it appears I should reload the bootloader, but, before I mess something else up, I'd like to get some expert advice about:
1. Is this the proper procedure?
 2. What's the appropriate bootloader file?

Thanks everybody

f5soh

  • *****
  • 4416
    • LibrePilot
Re: OPLink Mini - the continuing saga
« Reply #1 on: August 25, 2018, 05:44:49 pm »
Normal procedure is a Manual update, this mean hit the Upgrade&Erase button before connecting the OPLink.

Bootloader for OPLink is here

How are the telemetry led status (in bottom/right corner) after you connect the OPLink ?

Re: OPLink Mini - the continuing saga
« Reply #2 on: August 25, 2018, 11:17:34 pm »
After flashing those bootloaders, you must then flash the firmware, since flashing bootloader erases firmware.  After that you should have a working OpLink.

There is a very small chance that you have a bad USB cable that connects power, but does not connect signal.

Re: OPLink Mini - the continuing saga
« Reply #3 on: August 26, 2018, 02:02:50 am »
Still no joy. 
For what it's worth, the firmware tag "On Device" is 16.09 and the "Loaded" is Next.
My Librepilot version is 16.09.
Does that make any difference?

f5soh

  • *****
  • 4416
    • LibrePilot
Re: OPLink Mini - the continuing saga
« Reply #4 on: August 26, 2018, 02:54:44 am »
Between next and 16.09 if the Oplink firmware do not match the GCS you cannot see Oplink connected.

When you do the Upgrade&Erase (Manual) from 16.09, still the Next version into the Oplink ?
« Last Edit: August 26, 2018, 03:00:56 am by f5soh »

Re: OPLink Mini - the continuing saga
« Reply #5 on: September 01, 2018, 11:16:06 pm »
I'll try to include as much info as possible to try to enable diagnosing and solving my OPLink maladies.
When I plug the unit into the USB port on my computer, what appears to be 2 blue LEDs illuminate for about 5 seconds then go out and are replaced by a red (or orange or yellow, since I'm somewhat color blind)  LED and the blue LEDs start blinking about once a second. 
Upon connection, Windows gives its "connect" tones.
The Tx and Rx at the lower right of the Configuration screen remain dark until Windows gives "disconnect" tones, at which time, the Tx and Rx indicators fill briefly before showing a Tx number of 24 and Rx of 238. 
Librepilot's Configuration/Hardware screen shows no device connected.
When I do a Manual update in accordance with the instructions, connecting the OPLink AFTER selecting Rescue and Upgrade and Erase, the progress bar shows the Uploading firmware to board to get to 100%, followed by Rebooting and erasing board, please wait, followed by Board updated successfully, Press OK to finish.  When I press OK, the message window says Detecting first board and, after several seconds "Could not enter DFU mode".
Plugging in the OPLink after clicking Rescue brings up Device 0 Information:
OPLinkMini
Device ID 301
HW Revison 1
Flash Access RW
BL Version 4
Max Code Size 102300
The Firmware On Device window shows
Board Name OPLink Mini
Firmware Tag 16.09
Firmware date 2016-12-12 23:37
Git Commit Hash 4859aa59
CRC 2838426457
When I Open the bootloader file linked in f5soh's first response to my first post (which I downloaded), it "Loads" the "Next" version, with the other parameters being:
Date 2013-05-28 10:01
GCH f1684453
CRC 3766705501
To me, it appears that the bootloader "On Device" matches the firmware (version 16.09), but Librepilot still can't recognize tne board.
What am I missing?



 



f5soh

  • *****
  • 4416
    • LibrePilot
Re: OPLink Mini - the continuing saga
« Reply #6 on: September 01, 2018, 11:40:09 pm »
After updating the bootloader, the "next" description you see is normal.
Bootloader is tagged as next, alone, without firmware.

After a Upgrade&Erase the version is 16.09, as expected.

Seems a windows issue because the disconnect sound.

Try uninstalling the driver like here.

Re: OPLink Mini - the continuing saga
« Reply #7 on: September 02, 2018, 06:43:21 am »
You should be aware that GCS doesn't show much when just an OpLink is connected.  The only Configuration page that will show anything is Configuration->OpLink.  The others show data for the Revo, etc. that is talking to the OpLink.

Re: OPLink Mini - the continuing saga
« Reply #8 on: September 05, 2018, 10:34:17 pm »
I just went through the procedure referenced by f5soh to reinstall the driver.  According to Windows, the driver reinstalled. 
I'm still getting the same result with the Manual upgrade process.  The Configuration/Hardware window states that the panel will be updated once the device is connected and running. 
Device Manager shows in both the COM and LPT Port and the USB Controller windows that the USB Serial Device on COM3 is working properly and the Event window shows that the device was configured and started. 
Since I've acquired 3 or 4 OPLink Minis over this odyssey, I pulled another from my parts box and tried the same procedures, with the same result.  It's possible that I may have connected the device to my computer without an antenna attached, which I know is fatal for the FC, but I've tried to be compulsive about having one installed every time I've worked with it.  Is it very likely that I've had a succession of faulty products.  I've ordered them from Hobby King.

Thanks again for your suggestions.     

f5soh

  • *****
  • 4416
    • LibrePilot
Re: OPLink Mini - the continuing saga
« Reply #9 on: September 05, 2018, 11:37:22 pm »
LPT port has nothing related with oplink and the Com port (if any) will show Oplink in his name.
The driver to be reinstalled is a USB composite device.

If the connected status fails with all others OPLink devices you should try using another USB cable.
Connecting a Oplink without antenna do not cause USB issues and after a Upgrade&Erase the modem do not transmit at all by default.

Re: OPLink Mini - the continuing saga
« Reply #10 on: September 06, 2018, 07:57:52 am »
Still no joy. 
For what it's worth, the firmware tag "On Device" is 16.09 and the "Loaded" is Next.
My Librepilot version is 16.09.
Does that make any difference?

This says you are running some "next" version GCS and not 16.09 version.  (unless you got this when flashing the bootloader)

First of all, decide what version you want to run, then make sure the GCS you are running is that version.  It would be a good idea to re-install the GCS version that you want, just to be sure.

Then flash the bootloader that @f5soh linked to, then flash the firmware.  Use manual update method for both flashings.  That requires you to press the GCS button before plugging the OpLink in to USB for both flashings.

All software / firmware versions must match: GCS, OpLink(s), FC(s).  All bootloaders must be flashed with recent (e.g. year 2016 or later or so) version.  Basically you should check the bootloader version for every board you buy, and update it if necessary.

Remember that if only the OpLink is active (OpLink plugged in, but not connected to RF to model) that the only page that shows anything is the OpLink page (OK, System page too...).  Firmware page does not show OpLink is plugged in unless you are doing the Manual Update method (press GCS button before plugging in the OpLink).

I have accidentally run an OpLink without antenna for extended periods at 50mw without damaging it, so don't assume that your OpLink is damaged unless you can prove that.  Also, even if you did damage it, it would very probably continue to boot up and run and show the counters counting (at least the Tx Seq No:) on the OpLink page.  But a damaged OpLink would just always pretend that the model was not powered on, or the RF would have very reduced range.

After doing the updates, and restarting the GCS, and re-plugging in the OpLink USB (with no model powered on) and waiting 10 seconds (more not needed) does:
- the GCS Connections box (lower right) show grayed out "USB OpLink"
- the GCS Tx and Rx bar (lower center) show short green bars
- the GCS OpLink page "Tx Seq No:" counts up
if so, the OpLink is running correctly and the next thing is to get it talking to your model (which must be running firmware version that matches the GCS version).
« Last Edit: September 06, 2018, 05:27:25 pm by TheOtherCliff »