Orion-XS on Globallink 520

This proves the Orion-XS clearly has a bluetooth issue with transmitting instant read-out data to a GlobalLink:

I edited slightly, since the GlobalLink is its own product, rather than a GX device.

I’m slightly impressed it worked at all, since the Orion XS is not on the GlobalLink’s product compatibility list -actually, it’s not there under BT or VE.Direct, but I’m not surprised it works over VE.Direct.

To be clear on your testing methods, these were at two different times, correct? As in, you tried connection over BT for a time and logged the graph, then disconnected BT and connected the unit over VE.Direct and logged that graph? Or was this at the same time and you had the unit connected to the GlobalLink via two different networks at once? If the latter, I’d think errors are to be expected in that case, and suggest running the test again but only using one connection method at a time.

Logged at the very same time period. But I have to disappoint you, when being connected with BT only, it had dropouts all the time. Sometimes the Orion wasn’t seen by the Globallink for months !

EDIT: The Orion-Tr I had before, though being clearly listed on the compatibility list, had the same issues. This list is just a desperate legal measure to exclude unreliable products. They all speak the same language, right? Protocol standard, is protocol standard.

Oh it’s no disappointment to me, again I’m happy to see it worked at all!

Hi @cstenger

From the logging on our server, it looks like the GlobalLink has lost the encryption key.
Have you perhaps changed the PIN code on the OrionXS? This will invalidate the encryption key on the OrionXS. The GlobalLink then detects that it has the wrong key and only sends basic information to the VRM server. You then need to connect with VictronConnect (which has been connected to the OrionXS after the PIN change) or connect the OrionXS to the GlobalLink via VE.Direct for a short period. It then receives the new encryption key and starts to send the battery and charging data again.

With kind regards,
Thiemo van Engelen

Sadly, none of that applies Thiemo.

I never changed the PIN, and as you can see, I’ve connected it with VE.direct in parallel, so it should’ve sent a new encryption key.

It simply loses connection out of the blue:

RED: Bluetooth

BLUE: wired