LibrePilot Forum

Development => Hardware => Topic started by: lowz on January 31, 2016, 02:56:18 pm

Title: op link binding problem
Post by: lowz on January 31, 2016, 02:56:18 pm
After following the guide on how to pair two op link boards, I am still not able to get them to pair. I Have tried using both as coordinator.

Im using the revo board and a op link mini.

op link mini as the coordinator and connected to computer.
The orange tx diode flashes wildly after startup
rx diode does not flash, but in the system tab -> GCSTelemetryStatus RxBytes is counting.
OPLinkStatus RXseq is not counting
Resets is counting.

Any pointers? any more info needed?
Title: Re: op link binding problem
Post by: f5soh on January 31, 2016, 03:14:20 pm
Hi,

Post Oplink tab screenshot with oplm1 and oplm2
Title: Re: op link binding problem
Post by: lowz on January 31, 2016, 03:31:47 pm
I see here that the non-coordinator does not seem to send or recieve anything. I tried switching roles on them, the behavior was the same on both cards.
Title: Re: op link binding problem
Post by: f5soh on January 31, 2016, 04:16:43 pm
Try with baudrate set to 57600

Set bigger range maybe 25 - 50 for channels ?

Edit: Tried using the same setup like you and it works here.
Title: Re: op link binding problem
Post by: lowz on January 31, 2016, 05:37:06 pm
no difference unfortunately.
Title: Re: op link binding problem
Post by: lowz on January 31, 2016, 05:40:16 pm
I also tried updating the boot loader on the revo board. And installing new firmware on both of them.
extrnal battery or 5V trough usb for the external card makes no difference.
Is not sending any packages (TX seq no = 0) expected behavour for the non-coordinator board? Or does it say so because it sends telemetry trough USB instead when connected?
And the amount of resets? is that normal?
Title: Re: op link binding problem
Post by: f5soh on January 31, 2016, 06:07:42 pm
The coordinator do Tx every time with channel hopping.

The no-coordinator wait on first channel, when a coordinator is received and matches the CoordID field, it do Tx (Coordinator do Rx blink) and jump to next channel same time as coordinator.

The reset on Revo looks like nothing is received from coordinator.

If you have a UHF receiver you can check if Oplink coordinator really do Tx.
Title: Re: op link binding problem
Post by: lowz on January 31, 2016, 11:42:32 pm
I don't have access to a UHF reciver atm. Is there any other way to debug the handshake?
They switch behavour when assigning the revo role as coordinator.
Title: Re: op link binding problem
Post by: f5soh on February 01, 2016, 12:14:21 am
If you set the Revo as Coordinator you should see the non-coordinator Rx led blinking+Brief Tx led blinking.

Also find another Oplink so you can detect which side do not work.
Title: Re: op link binding problem
Post by: lowz on February 01, 2016, 08:05:34 pm
Does it log anything?
Is there any more equipment i need to really start to find out what is going on in the board, will order it aswell if im going to get a new oplink.
Title: Re: op link binding problem
Post by: f5soh on February 01, 2016, 08:30:45 pm
With a new oplink you can test the first oplink and your revo,  and finally find which side don't work.

Did you inspect the RFM22b module ? Maybe post some macro pictures ?

Title: Re: op link binding problem
Post by: armond on March 10, 2016, 04:18:08 pm
Hello,
Maybe there are any news from you guys in this topic? I have the same binding issue and can not figure out how to make it work.
Title: Re: op link binding problem
Post by: hwh on March 10, 2016, 04:34:35 pm
There was another similar thread a few days ago and the solution was he forgot to hook up an antenna on one of the boards.  The thread is at https://forum.librepilot.org/index.php?topic=1015.msg7322#msg7322

We all overlook the obvious sometimes.
Title: Re: op link binding problem
Post by: jtrout19 on March 10, 2016, 10:23:09 pm
LOL ;D I love being the example. But yes damn antennas! I left it unplugged.
Title: Re: op link binding problem
Post by: armond on March 13, 2016, 07:36:18 pm
Thanks for reference. The problem is a bit different. The telemetry works perfect (I get data from revo to oplink which is connected to pc). However, I am not able to make PPM Vehicle Control Link to work. Everything is connected to frsky taranis as here: http://opwiki.readthedocs.org/en/latest/user_manual/oplink/control.html but not working. Any ideas what could be wrong?  :)
Title: Re: op link binding problem
Post by: f5soh on March 13, 2016, 07:40:05 pm
Post screenshots of booth sides
Title: Re: op link binding problem
Post by: armond on March 14, 2016, 06:10:52 pm
Sure. Here the one which is selected as coordinator is oplink connected to frsky taranis.
The problem occurs during the Input channel configuration, when I replicate movements on the controller. It seems like it doesn't send any signal.
Title: Re: op link binding problem
Post by: f5soh on March 14, 2016, 06:25:16 pm
OPLink connected to taranis : Set flexiport to PPM, the one used for PPM input

On Revo : Check the PPM check box

If the link is already active, nothing more to do. Reboot all and go to Transmitter wizard.
Title: Re: op link binding problem
Post by: armond on March 14, 2016, 06:47:56 pm
Do you mean to check PPM only? In this way the telemetry will be disabled, right?
And when in Transmitter wizard.. should the Revo or OPLink be connected via usb?
Title: Re: op link binding problem
Post by: f5soh on March 14, 2016, 06:49:29 pm
No, there is "PPM only" and "PPM" while revo is connected.

You need "PPM" checked !
Title: Re: op link binding problem
Post by: armond on March 14, 2016, 06:58:39 pm
Thanks, dude! This made it work! Brilliant  :)
Title: Re: op link binding problem
Post by: jtrout19 on March 17, 2016, 05:00:21 am
How is the control when sent through the Oplink. I am currently using a Frsky Module. Why did you choose to go with the Oplink. Are there any pros or cons to going with an Oplink over a regular TX/RX or vis versa?