E1.20 RDM (Remote Device Management) Protocol Forums  

Go Back   E1.20 RDM (Remote Device Management) Protocol Forums > RDM Developer Forums > RDM Physical Layer/Hardware Discussion
Register FAQ Community Calendar Today's Posts Search

RDM Physical Layer/Hardware Discussion Discussion and questions relating to the physical or hardware layer of RDM.

 
 
Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
Old March 26th, 2015   #14
ericthegeek
Task Group Member
 
Join Date: Aug 2008
Posts: 390
Default

Quote:
Originally Posted by StephenYim View Post
Sorry to bother you again, but I have two question waiting for your answer.
No need to apologize. This forum was created to help developers like you.

Quote:
Originally Posted by StephenYim View Post
1.Get-Command:DEVICE_INFO:
The controller get all the device-info except Sensor count, no matter how many Sensor I set in my firmware, the controller always display:Sensor count:0x00.
Can you post a HEX Dump of your GET_RESPONSE to the DEVICE_INFO?

Quote:
Originally Posted by StephenYim View Post
2. Set-Command:IDENTIFY_DEVICE:
After the communication channel is setted up(Discovery process has completed),the controller send out this command periodic:
...
CC 01 19 09 0C 00 00 01 3C 00 00 00 00 00 00 13 01 00 FF FF 30 10 00 01 00 03 8B

I search the RDM protocol E1.20, but find nothing about these requirement,is it different between different RDM-Controller?
The standard doesn't define how controllers must behave. Each manufacturer will develop their controller to behave in a way that makes the most sense for their customers. Simple controllers will only send RDM when the uses asks for it, others will do a great deal of polling and monitoring in the background.

Having said that, periodically sending a "Sub-Device All Call" SET IDENTIFY_DEVICE on/off doesn't make any sense to me. You'd have to ask the manufacturer why they do that, and how to disable it.

Also, I notice that the controller's source UID is all zeros ( 00 00 00 00 00 00 ), this is not a valid RDM UID so you may want to ask the manufacturer to correct it.
ericthegeek is offline   Reply With Quote
 

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
RS485 networking tracyu RDM Physical Layer/Hardware Discussion 0 June 11th, 2008 05:54 PM


All times are GMT -6. The time now is 03:56 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2026, vBulletin Solutions, Inc.