These links will be dynamically renewed so those links will always work within the product. Its cases where images (or other files) URLs are pulled out of the product (like being added to an email chain) where you may see them expire after 24hr,
Question, I have multiple calipers connected to the U-wave R, is there a way I can distinguish one caliper from another?, normally the device output includes name and data, and this case only data and length measured.
I’ve worked a bit with the U-Wave-R device, hopefully I can help:
On Player (the PC), the Caliper driver unfortunately ignores this ‘name’ information. So, I do not believe it is possible to differentiate the different calipers with this driver. This may be a good feature request to add.
In Node-RED (on Edge Devices), the U-Wave-R shows up as a generic serial device. So, EIO/EMC will simply intake whatever the u-wave-r outputs - in this case, the name and the measurement. Then, in Node-RED, you can modify your flow to act on both data: for example, to either direct that data to a different Tulip Machine Node based on its name, or to simply include both data in the output and make decisions within your app.
Is CSV shown in the same way .pdf or .txt files? I run into an issue trying to visualize CSV file. In fact I’m not able to directly view the file in the table widget but the pop-up window asks to save it first. Is this behaviour expected? I need to visualize the file directly in the player in fact, can you suggest me a work around? Thanks!
M
It looks like the behavior you are seeing is what is expected. A potential workaround would be using a custom widget to visualize the CSV - maybe by using the custom widget to convert from CSV to object list, output the object list, and then visualize the object list as a Variable in the app.
If you’d like, you can create a Product Suggestion for this to become a native feature in the Tulip Platform!