-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device not found #5
Comments
Hi Thanks for the quick response. I'll try that later today. KR |
If you search ebay, amazon or aliexpress for usb dmx or udmx you'll see plenty. Some examples:-
|
Hi Thanks, for the links. |
😿 the end... |
how do i change the udmx.js? |
Dear @NickvanZon ,
|
Are you using this under Linux? Maybe try the lsusb command to find the id of your device? |
there is a log output: node-red-log |
FWIW, I'm getting close to an answer for this running in Docker at https://www.reddit.com/r/AlpineLinux/comments/165t1th/running_mdev_s_to_scan_for_devices_on_container/ I'm wondering if a config box could be created to allow for input of the device/vendor ID in future as many of the USB dongles from Amazon etc appear to be the Better yet, the ability to select from a drop-down of plugged-in USB devices would be fantastic! |
The USB Dongle you are using (Manufacturer: FTDI) is not compatible with the uDMX driver. Try the https://github.com/node-dmx/dmx package, especially the enttec-open-usb-dmx.js driver.
(Replace I am not aware of any node-red node that supports the OpenDMX driver out of the box. You could use the code above to get started and write your own. |
Amazing, thanks @christophengelmayer ! |
FWIW I worked around this by switching from Docker to a raspberry Pi, installing OLA from the standard APT repositories, enabling USB FTDI in the OLA config and then using NodeRed OLA to send messages to the OLA server. This isn't as "nice" as being able to talk directly to my cheap chinese USB DMX dongle, but it is working well, so I figured I'd put this here in case someone who also has a cheap chinese dongle tries to use nodered uDMX. |
@proffalken Thanks for your update. How is the "performance" using OLA with the USB FTDI Stick? My solution works but it is only capable of updating DMX values at about 30 times/second. I'm wondering if the 30Hz limit comes from the FTDI-Stick or the driver? |
@christophengelmayer - I only got it working this morning, and haven't tried more than alternating colours once a second so far. I'll try the gradient stuff later on today if I get a chance - my goal is to use this to react to messages on an MQTT bus and change the lights accordingly for an Escape Room-style setup. |
@christophengelmayer try the below, there's a delay of just 5ms between steps and my cheap chinese light seems to fade up without jitter: [
{
"id": "9c99abb435339285",
"type": "tab",
"label": "Flow 1",
"disabled": false,
"info": "",
"env": []
},
{
"id": "78cb4b068737cc2c",
"type": "function",
"z": "9c99abb435339285",
"name": "Fade",
"func": "var colour = [0,0,0];\nvar brightness = 0;\nvar total_fade_length = 1;\nvar step_size = 1;\n\nfunction sleep(ms) {\n return new Promise(resolve => setTimeout(resolve, ms));\n}\n\nif (msg.payload.total_fade_length){\n total_fade_length = msg.payload.total_fade_length;\n node.warn(\"Fade length set to \" + total_fade_length + \"based on message\");\n}\n\nif (msg.payload.colour){\n colour = msg.payload.colour;\n}\n\nstep_size = 255 / total_fade_length;\n\nnode.warn(step_size);\n\nfor (let seconds_passed = 0; seconds_passed < total_fade_length; seconds_passed++) {\n brightness = brightness + step_size;\n msg.payload = {\n \"channels\":[ {\n \"channel\": 13,\n \"value\": brightness,\n },\n {\n \"channel\": 14,\n \"value\": colour[0],\n },\n {\n \"channel\": 15,\n \"value\": colour[1],\n },\n {\n \"channel\": 16,\n \"value\": colour[2],\n }\n ]\n };\n node.send(msg);\n await sleep(5);\n}\nreturn;",
"outputs": 1,
"timeout": 0,
"noerr": 0,
"initialize": "",
"finalize": "",
"libs": [],
"x": 990,
"y": 500,
"wires": [
[
"93075025a6189a9a",
"360b821f24d7d0df"
]
]
},
{
"id": "93075025a6189a9a",
"type": "debug",
"z": "9c99abb435339285",
"name": "Payload",
"active": true,
"tosidebar": true,
"console": false,
"tostatus": false,
"complete": "payload",
"targetType": "msg",
"statusVal": "",
"statusType": "auto",
"x": 1380,
"y": 420,
"wires": []
},
{
"id": "637d47e8196ba65e",
"type": "inject",
"z": "9c99abb435339285",
"name": "",
"props": [
{
"p": "payload"
},
{
"p": "topic",
"vt": "str"
}
],
"repeat": "",
"crontab": "",
"once": false,
"onceDelay": 0.1,
"topic": "",
"payload": "{\"colour\":[123,0,123],\"total_fade_length\":255}",
"payloadType": "json",
"x": 750,
"y": 500,
"wires": [
[
"78cb4b068737cc2c"
]
]
},
{
"id": "360b821f24d7d0df",
"type": "ola",
"z": "9c99abb435339285",
"name": "",
"host": "127.0.0.1",
"port": 9090,
"universe": 1,
"size": 512,
"x": 1370,
"y": 520,
"wires": []
}
] |
Hi
I'm using this usb - dmx cable : https://www.steinigke.de/en/mpn51860118-eurolite-usb-dmx512-interface-update-adaptor.html
First I had troubles installing the node, but after folowing the instructions on https://github.com/tessel/node-usb#readme
I was able to install the node.
But now, I've tried restaring node-red, and also my raspberry pi, but node-red doesn't find my device, is there maybe something I still have to do?
Thanks in advance for the help.
The text was updated successfully, but these errors were encountered: