Orbbec TOP won't restart feed after connection drop over Ethernet

So I’m trying out the Orbbec Femto Mega and hoping to use it for an upcoming installation. From past experience with Azure Kinects I like building in the ability to power cycle the sensor if it stops outputting a video feed, preferably without having to restart both the PC and the sensor itself and aim to make this automatic where possible.

Whilst I reckon I can find a POE switch that I can toggle the port power on via some CLI method (also welcome to model suggestions if you happen to have them, currently testing with a managed POE switch without some CLI function but does allow me to switch port power through a web UI over HTTP), I’ve tested this with what i have and found that the Orbbec TOP won’t remake the connection, toggling active, specify ip, rentering the ip and even deleting and remaking the TOP won’t remake the connection, only thing that works is restarting the project, which i’m trying to avoid as this would cut the projection off during the restart and isn’t ideal for the installation.

Any work arounds? am I missing something, or is this a bug with the TOP? I imagine there might be a way of implementing something that works using python but not sure where to start with that and assuming its a dead end given i get the same problem if i remake the top manually in the same session of the Touchdesigner project, my laymans guess is this is to do with the code that carries out the POE connection only running once in a single session.

Spec:

Orbbec Femto Mega over ethernet
Zyxel GS1200-8hp v2
Windows 10 22h2
2023.12230
ASUS GA503Q (developing on this but will run on a custom desktop, haven’t currently got another machine to run it on but will be trying this)

Hi @Mshed,

thank you for reporting this, we are having a look.

cheers
Markus

Sorry you’re having trouble. You might want to try setting the environment variable TOUCH_TEXT_CONSOLE to 1 and then see what the console window outputs. The Orbbec library handles all of the network communication and will output errors to the console that might tell us what is happening.

I’ll try some power cycling with the Orbbec I have here as well and see if I can recreate any problems.

It might be worth checking the firmware version of your camera as well since that might affect the connection. It should be visible if you connect to the camera with the Orbbec viewer app

Hi Guys

I’ve run the console method a couple of times, once with a long delay between reconnection once with a smaller, but i’m not savy enough to tell if that is camera side or touch side.
Quick


Long

So Firmware version: 1.2.7, the latest is 1.3.0 so whilst i could update to this there is only the one note on 1.2.8 that might be something to do with this and also none of the updates past this are compatible with the sdk touch is displaying (1.10.8) based on the notes orbbec are displaying Release Release Femto Mega Firmware · orbbec/OrbbecFirmware · GitHub
Based on this i believe firmware is unlikely to be an issue.