Ultrex Quest network issues

I cannot get my Quest to show up on the one boat network (in boat). I have a solix 12 and solix 15 both gen 3. The Quest is connected via ethernet to the hub.

I can connect my phone via bluetooth to the quest, and use the one boat network app, but I'd like to see it on the network in the boat to make use of the gps navigation controls from the solix units.

Side note: My Quest software version is 2.200. I have the new update downloaded but it will not transfer to the controller - fails after getting 95% complete on the status bar after numerous tries.

Both solix units are on the latest version of software, updated a couple days ago.

This is a NEW setup (new boat).

Double check your Quest ethernet connections both at control head and at the hub.

Agree with checking the connections. The connection at the trolling motor head can work loose. Had similar issues, but that connection was loose.

Connections good. Ethernet port blinking orange...

Post a screenshot of your OBN
Also, what's the software version on your Solix G3 units

Not currently at the boat but the OBN shows not indication or recognition of the Quest. Both solix units are on 5.120. The Quest is on 2.200, and I'm unable to update to 2.240 because the dang OBN app won't push it to the motor. It will start the transfer and after about 30 min, the transfer bar will be around 90% complete and it times out (no message that it failed to transfer).

I am wondering if the software mismatch (the Quest not being on the latest version) is the issue? If so, I don't know how to fix it because the package won't transfer.

Quote:

---

Originally Posted by KC_Bass_Fanatic

Not currently at the boat but the OBN shows not indication or recognition of the Quest. Both solix units are on 5.120. The Quest is on 2.200, and I'm unable to update to 2.240 because the dang OBN app won't push it to the motor. It will start the transfer and after about 30 min, the transfer bar will be around 90% complete and it times out (no message that it failed to transfer).

I am wondering if the software mismatch (the Quest not being on the latest version) is the issue? If so, I don't know how to fix it because the package won't transfer.

---

Update the motor via memory card in a display.

Quote:

---

Originally Posted by Wayne P.

Update the motor via memory card in a display.

---

Would love to but the displays don't show the motor on the network - as stated.

Quote:

---

Originally Posted by KC_Bass_Fanatic

Would love to but the displays don't show the motor on the network - as stated.

---

Fix your Ethernet connection and turn on the power to the trolling motor.

Quote:

---

Originally Posted by Wayne P.

Fix your Ethernet connection and turn on the power to the trolling motor.

---

Is this a serious reply? The ethernet connection is good, or at least indicates good with blinking amber light at the hub.

Quote:

---

Originally Posted by KC_Bass_Fanatic

Is this a serious reply? The ethernet connection is good, or at least indicates good with blinking amber light at the hub.

---

You could still have a weak Ethernet connection even though you get the communication indicated by the Switch. Swap some cables around to trouble shoot.

I had the same thing as Steve with the connection getting lose at the top of the motor due to the lock nut rubbing on the coiled cord. I put tape on it to prevent it from happening again. Everything "looked" good but wasn't.

Quote:

---

Originally Posted by Wayne P.

You could still have a weak Ethernet connection even though you get the communication indicated by the Switch. Swap some cables around to trouble shoot.

I had the same thing as Steve with the connection getting lose at the top of the motor due to the lock nut rubbing on the coiled cord. I put tape on it to prevent it from happening again. Everything "looked" good but wasn't.

---

Thanks Wayne I'll try all the connections

UPDATE: the ethernet connection at the Quest head needed to be re-seated. I was tight, and the amber light was blinking at the ethernet hub, but apparently one or more pins was not making good contact. I disconnected and reconnected it (shoving it together very ehem, firmly) and it started working.

thanks Wayne good call out my man