Is there a maximum latency before the cube app won’t successfully connect to a DMA?
Hi Philip,
There is no real maximum latency for Cube. We do also test against higher latency, and 500 to 700 ms should still work. I guess this range would typically be the maximum latency because e.g. going over satellite. The ‘DataMiner Agent did not respond in time’ message you mention in the comment of the other answer here, is probably caused by something else, because latency is typically 100s of milliseconds, and I only expect this message after many seconds…
The DataMiner Agent could be effectively not responding under certain circumstances, but then other clients should experience the same. Or it’s related to this client, maybe anti-virus or packet drops or something like that…
Bert
Hi Philip,
Did you have “unresponsive” messages reported you started a Cube session?
Cube can freeze and you have a workarround described in the documentation.
https://docs.dataminer.services/user-guide/Troubleshooting/Known_issues/KI_DataMiner_Cube_freeze_on_startup.html
We get the DataMiner Agent did not respond in time message, the user has full access to the internet and regular windows updates.
Thanks Bert.
They’re in the 200ms range, so should be fine then.
Cube shows a green tick when putting the DMA address into the multi-version app, and using test-netconnection 8004 is accessible, so just trying to narrow down the issue.
No one else is having access issues, just this one client.