-
Notifications
You must be signed in to change notification settings - Fork 21
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
Opcode unknow #18
Comments
This comment was marked as duplicate.
This comment was marked as duplicate.
Something went wrong with uploading the images. |
Thank you very much for answering, here I paste the information of the 4 packages. those from ip 2.0.0.1 are from the app. those from ip 2.0.0.2 are hardware. As I was saying, if you look at the ports they are intertwined, I think the app acts as a bridge. and there is the OpCode: Unknown (0x1005) which I think is what starts the app Ip 2.0.0.1 software User Datagram Protocol, Src Port: 6455, Dst Port: 6454 Art-Net, Opcode: ArtPollReply (0x2100) User Datagram Protocol, Src Port: 6455, Dst Port: 6454 Art-Net, Opcode: ArtPoll (0x2000) Ip 2.0.0.2 hardware User Datagram Protocol, Src Port: 6454, Dst Port: 6455 Art-Net, Opcode: ArtPollReply (0x2100) User Datagram Protocol, Src Port: 6455, Dst Port: 6455 Art-Net, Opcode: Unknown (0x1005) |
The first 3 packets looks like normal device discovery. The last packet is an unusual frame. Normal Art-Net traffic is on port 6454, but this one is on 6455 (Src and Dst) only. Can you capture the response from the last packet, from the original hardware? And please include the full data part. The partial data looks like a repetition of For now, my lib can only run on port 6454, as normal Art-Net devices do. But lets see what the real device replies, and maybe I can come up with a solution. |
i managed to make it work. from what i could find out the software bridges receive on 6454 and sends node to 6455. that's why the node only works with this software. copy these packets the standard and the unknown and forward them to port 6455. the app recognized a node. As I thought, that package is the one who does the magic. Now it remains to do it with the esp8266. there is no response to that packet what it sends and receives is what I sent. I am not in the office anymore but tomorrow I will send you the complete code |
full data fa2e00c6cec9beb4bcf99fc7fa2e00c6cec9beb4bcf99fc7fa2e00c6cec9beb4bcf99fc7f74418f94025f74418f94025f74418f94025f3ff |
I don't understand the bridging? There are only two parts (device and app), what must be bridged? Normally a device (node) responds with Your somewhat Art-Net node does presumably two things for
Am I right? |
if you're right. the app acts as a bridge between other apps and has an artnetominator-type display without this app turned on, the node does not work. I need to send Unknown (0x1005) with datafa2e00c6... I don't know how to modify the library to send that data or if it would be easier to send the package in some way without modifying the library |
Try this (it's beta, not tested on hardware and I don't know the exact frame format!): I have also tweaked the library a bit to make it work, so check out the latest revision. For
And for the special sauce:
|
Hi, I love your project. i have an unbranded chinese node that uses its own app to work. I am trying to build another one with your library. but the software does not detect it. I clone all the data I found mac, name, manufacturer, etc but still not detected and looking at the traffic I found an unknown opcode that doesn't follow artnet rules, besides port changes. I believe that the data of this opcode is what enables it to be recognized. I can add that response somehow?, create that opcode?. the photos with ip 0.1 are the software packages and those with ip 0.2 are those of my node
The text was updated successfully, but these errors were encountered: