RMS version for custom modules?
annuello
Junior Member
Gday all,
I've got a moderate number of modules which grow/change over time, and I'm finding it difficult to keep track of what is installed on my various masters. (50+, soon to become 150+, then 400+, then...). I have limited access to our classrooms, so some rooms tend to get "left behind" in the changes to my code as a result. To preserve my sanity, all my modules have a version number which can be obtained by:
I'm using RMS to monitor equipment in the rooms, and I see that my modules have a "version" in the NetLinx Device Information section. This version looks like a copy of the NetLinx firmware. What I'm wondering is: Is there a command that will allow me to override this version number so that it represents the version of my module?
Obviously I could create an additional parameter for every device to monitor, and register the module version as a parameter for the device. I just want to check if the previous idea is possible before heading down this path.
Yours,
Roger McLean
Swinburne University
I've got a moderate number of modules which grow/change over time, and I'm finding it difficult to keep track of what is installed on my various masters. (50+, soon to become 150+, then 400+, then...). I have limited access to our classrooms, so some rooms tend to get "left behind" in the changes to my code as a result. To preserve my sanity, all my modules have a version number which can be obtained by:
send_command vdvMyModule, 'VERSION?'This is okay for a "what version does this room have" approach, but doesn't scale well for planning & maintenance.
I'm using RMS to monitor equipment in the rooms, and I see that my modules have a "version" in the NetLinx Device Information section. This version looks like a copy of the NetLinx firmware. What I'm wondering is: Is there a command that will allow me to override this version number so that it represents the version of my module?
Obviously I could create an additional parameter for every device to monitor, and register the module version as a parameter for the device. I just want to check if the previous idea is possible before heading down this path.
Yours,
Roger McLean
Swinburne University
Comments
-
Hi Roger,
I looked into the "version" field you mentioned and unfortunately there is not a command to override the value that gets set here. When a device is regsitered the DPS that is passed in on the registration call gets passed thru a DEVICE_INFO call and the resulting DevInfo.VERSION is what is used to populate this "version" field.
For now, adding a PARAM to record your module version would probably be the best way to capture this information.
We will look at a better way in future versions to enable the user/programmer to have more flexibility and control over the information propogated to the RMS server.
Thanks,
Robert
Categories
- All Categories
- 2.5K AMX General Discussion
- 922 AMX Technical Discussion
- 514 AMX Hardware
- 502 AMX Control Products
- 3 AMX Video Distribution Products
- 9 AMX Networked AV (SVSI) Products
- AMX Workspace & Collaboration Products
- 3.4K AMX Software
- 151 AMX Resource Management Suite Software
- 386 AMX Design Tools
- 2.4K NetLinx Studio
- 135 Duet/Cafe Duet
- 248 NetLinx Modules & Duet Modules
- 57 AMX RPM Forum
- 228 MODPEDIA - The Public Repository of Modules for Everyone
- 943 AMX Specialty Forums
- 2.6K AMXForums Archive
- 2.6K AMXForums Archive Threads
- 1.5K AMX Hardware
- 432 AMX Applications and Solutions
- 249 Residential Forum
- 182 Tips and Tricks
- 146 AMX Website/Forums