I’m undigging this post to know if there’s any vision of firmware 3.1 support inside an upcoming build any soon ?
We have 2 OSDOME Rev7 for an upcoming immersive space project and we can use them through modulopi and send player data to Touch, but i wish we could get the data directly inside Touch to avoid overflowing our local network.
I was just testing and the sensor is behaving greatly inside Ouster Studio.
And i can’t seem to get the legacy profile inside the device configuration interface (as it as been deprecated). I Tried the replacement UDP profile one the documentation here recommands Sensor Data — Ouster Sensor Docs documentation without success.
We’ve actually got a dev working on this right now and its very close to being ready. We are hoping to do some testing before merging it into our official release and could send you a preview copy if you’re interested in trying it.
We’ve updated the Ouster SDK to 0.15.0 on a separate branch. Please note that we weren’t able to test v3 firmware because our sensor model only supports up to v2.
If you would like to try it out, here’s a Dropbox link for the Windows installer. Let us know if you have any feedback.
@samuelgadenne I was wondering where you landed on the interoperability issue with the latest OSDome?
@robmc@daniel.k please share an update if you have any further info on v3.1 firmware in the conext of the rev7 OSDomes!
I’m searching for an IP67+ sensor(s) to gather positional data for a projection mapped courtyard and adjacent slim alleyway, if anyone knows of anything natively compatible with TouchDesigner similar to the OSDome or Hokuyo YLM-10LX. Giving a lot of weight towards sensors that support spatial filtering (for preciptiation) and can survive all 4 seasons while generating enough heat to melt snow and ice.
The Ouster update is now in the official release as of build 2025.32050, but I don’t believe we’ve heard any confirmation yet of anyone testing it with the new firmware.
According to the SDK documentation, the 0.15 version we’re using now should work with the OSDome and firmware up to 3.1.
Sorry for the late reply, i had no time ealier but I tested again the OSDOME rev7 v3.1.0 just now on the latest official build (2025.32050) and i’m happy to say i’m getting the expected data. Everything is configured on a local network, but the os-xxx.local adress was working fine :
Thanks a lot for the good work, we are opening an immersive and interactive space soon in Lille and this should simplify a lot our workflow rather than using other softwares on top of Touch.
