Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Unable to connect to 2019 S60 T6
#1
Hi all. I have tried everything I can think of. 


Purchased a OCHIKI 7 ft VOE OBD to Ethernet cable and a TP-Link USB to Ethernet adapter as my laptop does not have an Ethernet in. 

You can see the error in the attached picture. 

I have been putting a charger on the battery, holding the on switch long enough to start everything (engine off) and have tried with Windows Defender on and off. 

Any tips?


Attached Files Thumbnail(s)
   
Reply
#2
Anyone?
Reply
#3
First check if you can connect to internet via  TP-Link USB to Ethernet adapter, this would make sure that you do not have any driver problems. 
Then, check the inbound firewall rules,  (windows defender with Advanced security) 
You should have 4 inbound rules. 
Local Address > ANY
Remote Address > ANY
Profile> (public, private and domain) 
Protocol > TCP;  LOCAL Port >ANY;  Remote Port > 13400
Protocol > TCP;  LOCAL Port >24200;  Remote Port > ANY

Protocol > UDP;  LOCAL Port >13400;  Remote Port > any
Protocol > UDP;  LOCAL Port >24200;  Remote Port > ANY


Outbound rules:
Usually Firewall does not block any out pound TCP and UDP ports but it can block executables "OrbitRun.exe"  You can add a outbound rule and allow the orbit. 


connect the VOE adaptor to the car, turn the ignition on pos 2 without engine is running. Make sure on the  TP-Link USB to Ethernet adapter you have the link lights on.
Launch the Orbit and try again.  
Reply
#4
(11-18-2024, 08:21 PM)IMAY2023 Wrote: First check if you can connect to internet via  TP-Link USB to Ethernet adapter, this would make sure that you do not have any driver problems. 


Then, check the inbound firewall rules,  (windows defender with Advanced security) 
You should have 4 inbound rules. 
Local Address > ANY
Remote Address > ANY
Profile> (public, private and domain) 
Protocol > TCP;  LOCAL Port >ANY;  Remote Port > 13400
Protocol > TCP;  LOCAL Port >24200;  Remote Port > ANY

Protocol > UDP;  LOCAL Port >13400;  Remote Port > any
Protocol > UDP;  LOCAL Port >24200;  Remote Port > ANY


Outbound rules:
Usually Firewall does not block any out pound TCP and UDP ports but it can block executables "OrbitRun.exe"  You can add a outbound rule and allow the orbit. 


connect the VOE adaptor to the car, turn the ignition on pos 2 without engine is running. Make sure on the  TP-Link USB to Ethernet adapter you have the link lights on.
Launch the Orbit and try again.  

Thank you- yes I do have access to internet through the adapter, so that is good.  

I have never worked in defender with advanced before, so this is new.  I have a couple of Orbit rules, but I just added one for the exe, maybe that helps.  I attached a snap after I added the rule. It only had 2 rules total prior to my add.  

Fixed it- thank you!!


Attached Files Thumbnail(s)
   
Reply
#5
Hi!

I have v60 T8 2021 and same issue.
Was able to connect without problems few months ago and now it does not connect.
"Requesting connect
Waiting for connection...
Found car
Connecting to IP: 169.254.1.113
Gateway ECU: 0x1001
Waiting for the gateway to respond...
No cars found! Check cable, replug OBD connector, or check local firewall blocks OrBit from incoming connections
Error Reason: timeout
OrBit Disconnected" 

I checked my firewall rules, added 2 more inbound rules(had only two rules before) as described above and also .exe rule. Tried - ignition on, car running, door open, door closed - no success to connect to the car.

Any ideas?

Edit: using Enet cable
Reply
#6
Seems that the problem was related to my laptops or recent Orbit update. I have Orbit on two different laptops, both of them had the same issue. 
Installed Orbit to a new laptop and everything works fine.
(11-26-2024, 04:17 PM)Preparaator Wrote: Hi!
I have v60 T8 2021 and same issue.
Was able to connect without problems few months ago and now it does not connect.
"Requesting connect
Waiting for connection...
Found car
Connecting to IP: 169.254.1.113
Gateway ECU: 0x1001
Waiting for the gateway to respond...
No cars found! Check cable, replug OBD connector, or check local firewall blocks OrBit from incoming connections
Error Reason: timeout
OrBit Disconnected" 
I checked my firewall rules, added 2 more inbound rules(had only two rules before) as described above and also .exe rule. Tried - ignition on, car running, door open, door closed - no success to connect to the car.
Any ideas?
Edit: using Enet cable
Reply


Forum Jump:


Users browsing this thread: 3 Guest(s)