EUID Decode Errors - E1.20 RDM (Remote Device Management) Protocol Forums

tharron · September 23rd, 2014

Thanks sblair,

I made certain to leave the Break and MAB out of my DUB response.

My original timing issue was due to how the original code responds to regular DMX packets. I wouldn't respond for something like 6ms, but I updated the routine to respond more promptly. I don't have scope shots handy, but the UART started sending out data something like ~200uS after the controller finished.

I have had zero success in it discovering me, but it does follow the tree all the way down to my UID before finally giving up. I think I'm sending it something like two dozen "I'm here!" responses, and according to the sniffer every single one has a decode error on the EUID. That's not surprising as it should be the exact same packet each time.

I don't know if it will help, but here are the raw contents of a response packet from the sniffer:

FEh FEh FEh FEh FEh FEh FEh AAh EAh 5Dh EFh 55h AAh 55h AAh 55h AAh 57h EEh 75h AEh 57h EFh FDh

My UID is currently hard-coded as 0x48 0x45 0x00 0x00 0x02 0x64 (MSB to LSB).

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Switch to Hybrid Mode Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Errors and Sub Device All Call	SeanSill	RDM General Implementation Discussion	2	July 19th, 2013 01:48 PM
errors when testing discovery	redwind	RDM General Implementation Discussion	1	July 20th, 2011 12:05 PM

September 23rd, 2014	#3
tharron Junior Member Join Date: Sep 2014 Posts: 10	Thanks sblair, I made certain to leave the Break and MAB out of my DUB response. My original timing issue was due to how the original code responds to regular DMX packets. I wouldn't respond for something like 6ms, but I updated the routine to respond more promptly. I don't have scope shots handy, but the UART started sending out data something like ~200uS after the controller finished. I have had zero success in it discovering me, but it does follow the tree all the way down to my UID before finally giving up. I think I'm sending it something like two dozen "I'm here!" responses, and according to the sniffer every single one has a decode error on the EUID. That's not surprising as it should be the exact same packet each time. I don't know if it will help, but here are the raw contents of a response packet from the sniffer: FEh FEh FEh FEh FEh FEh FEh AAh EAh 5Dh EFh 55h AAh 55h AAh 55h AAh 57h EEh 75h AEh 57h EFh FDh My UID is currently hard-coded as 0x48 0x45 0x00 0x00 0x02 0x64 (MSB to LSB).