01-13-2024, 07:56 PM
(01-11-2024, 08:42 PM)IMAY2023 Wrote: Tanks for the info, I did not know that car actually opens the first session towards Orbit / VIDA using specific destination UDP port "13400" that Orbit listens to.
I checked the VIDA too, it listens to UDP 13400 and TCP 24200 + ( ANY TCP PORT from source 13400 tcp ) ports and creates the firewall rules during installation!
I guess, that's why Orbit worked for me from the beginning!
Yup, the DoIP standard, or at leas how Volvo does it, is the car broadcasts on the network, the tool listens for it, and then open up the packet, which has the IP of the car. That's how the tool finds the car without running a port scan for open 13400 on the huge subnet 169.254.0.0/16 which would take a lot of time ;-)
Did you notice if the Volvo firewall rule created allows "all" applications? That may be why people with VIDA installed are less likely to have issues. OrBit would already be able to listen. I did the firewall rule creation in the OrBit installation bound to only OrBitRun.exe executable, following "least privilege" security. I should check on TCP port 24200, I suspect that is for the "Shop WiFi" connection it makes sense TCP is needed for that.
(01-11-2024, 10:09 PM)SashaSolitaire Wrote: @Power6, did the following:
- Uninstalled Orbit app and deleted both the folders
- Downloaded and installed OrBit 0.9.7
- Checked in Windows Defender firewall that both inbound and outbound rules were set up for orbitrun.exe
- Connected the OBDII cable
- Faced the following two times:
Found car
Connecting to IP: 169.254.4.10
Gateway ECU: 0x1021
Waiting for the gateway to respond...
No cars found! Check cable, replug OBD connector, or check local firewall blocks OrBit from incoming connections
- The third time it connected to the car successfully, and I made a couple of config changes, wrote to the car, checked that the changes were applied and then reverted back the test changes I made
All in all, Ver 0.9.7 did the trick for me. Thanks!!!
Glad it's solved! I have seen the initial issue you see there...OrBit found the car, tries to connect and the gateway stops responding. It has eluded me as to why that happens sometimes. OrBit tries multiple times to connect when that happens to be sure the connection can't be made. Well I will figure that out someday but as long as you got through it and all is well for you now, all is well that ends well ;-)