Closed prt-prt closed 2 months ago
The error message "Could not connect to ws://10.0.0.20:3330/" is about the connection to the Scape X Engine running on the Scape Tangible Display. Can you reach the User Interface of the Scape X Engine at http://10.0.0.20
?
Yes, I can reach the Touch & Object Assistent over http at 10.0.0.20. I think the issue seems to be within the SxmBridge Node. One thing also worth mentioning is that the log messages continue to fire even when i stop the vvvv runtime, so I am not sure where excactly this error is coming from.
The bridge keeps trying to connect. This is independent of anything. Which version of the ScapeXMqttDeviceBridge
do you use and what version is your Scape X Engine?
The Version of the Scape X Engine is 6.1.3 and the SxmBridge references MQTTnet Version 4.3.6.1152 (shown in the screenshot above).. is this what you mean by ScapeXMgttDeviceBridge
?
Ah, my mistake. There is only one version of the SxmBridge
node and it should work with 6.1.3 of the Scape X Engine.
If you can connect to the Touch & Object Assistant via http://10.0.0.20
and touches and objects work there then the only thing I can imagine why "Could not connect to ws://10.0.0.20:3330/" happens is a firewall.
The MQTT connection is established when the connection to ws://10.0.0.20:3330/
is established, because you can configure the mqtt broker in the Touch & Object Assistant.
I think the issue here is the websocket port. We have two hardcoded websocket ports. 3333
for tuio 1.1 and 3343
for tuio 2.0. for scape x mobile we use tuio 2.0 so try to connect with 3343
. I just tried the Scape X Mobile.vl
help patch and everything worked as expected.
Regarding the missing mqtt dll I will have a look how to properly link it to the package.
UPDATE: Temporary fixes for both issues mentioned in this thread:
The FileNotFoundException
can be resolved by opening the patch menu, navigating to Dependencies > .NET Nugets > MQTTNet
and toggling the small rectangle next to the package name to be on with a rightclick.
The websocket connection issue can be resolved by going into the Touch and Object Assistent
, toggling Show Expert Options
and making sure that the Scape X Mobile Server
field contains the URL of the MQTT broker without the port number. Including the port number in the URL apparently causes parsing issues. This workaround should help get the connection running until the issue is permanently fixed.
Big Thanks to @eqbic for figuring this out!
Hi there,
I am having issues getting the Scape X Mobile patch to run on my machine. It seems that the reference for the .NET MQTTnet dependency is faulty, as it throws a FileNotFoundException even though the dependency on the SxmMqttBridge.dll file provided in the repo doesn’t show any issues.
I have tried referencing the NuGet package at the following path:
C:\Users\myUser\AppData\Local\vvvv\gamma\nugets\MQTTnet.4.3.6.1152
This resolved the exception but did not fix the behavior of the patch.
Additionally, I am getting numerous log messages indicating that the WebsocketClient cannot establish a connection. This issue persists even after resolving the FileNotFoundException.
Please let me know if you find a fix for this, any workarounds, or if you have any ideas that could point me in the right direction!