开云体育

ctrl + shift + ? for shortcuts
© 2025 Groups.io

OT - Opinion on System setup


 

Guys,

?I am wondering the best way to do this.....

5 rooms with AV3's , we have 3 A/V Carts with DMPS-200 and they want to be able to share each cart in any of the rooms.

So can the DMPS-200 run as a eSlave like we normally do with the other control processors?? Or do i need a tech page to select which cart will be in which room?

?If all systems are on the network a simple IP table would point to each system and i dont think that will work... they will not know which system to talk to?


 

You could create some tech page code that would change the IP table in the DMPS200 (and reboot) to allow it to EISC across the network to the desired AV3.? I think the only potential hiccup would be if you accidentally set two carts to connect to the same AV3.

? - Chip


 

开云体育

You cannot eslave any product with OOTBF, the DMPS-X00 included.

?

One alternative if wiring is possible would be to use 232 instead of Ethernet between the room processor and the cart – this way you (or rather, your users) don’t need to concern themselves with what cart is where & remembering to change the configuration [or sitting through the interminable reboot of a DMPS]

?

--

Lincoln King-Cliby, CTS, DMC-E/T/D

Commercial Market Director

Sr. Systems Architect | Crestron Certified Master Programmer (Silver)

V: 440.449.1100 x1107 F: 440-449-1106 I:

Crestron Services Provider

?

From: Crestron@... [mailto:Crestron@...] On Behalf Of dedicatedsystems@...
Sent: Tuesday, February 25, 2014 10:56 AM
To: Crestron@...
Subject: [Crestron] OT - Opinion on System setup

?



Guys,

?I am wondering the best way to do this.....

5 rooms with AV3's , we have 3 A/V Carts with DMPS-200 and they want to be able to share each cart in any of the rooms.

So can the DMPS-200 run as a eSlave like we normally do with the other control processors?? Or do i need a tech page to select which cart will be in which room?

?If all systems are on the network a simple IP table would point to each system and i dont think that will work... they will not know which system to talk to?



 

Agree with Lincoln on this one.? I would set it up to control the DMPS units with rs232 like an external device, rather than an internal device.

You could make a simple program for the DMPS that get's loaded into all of them, that has a custom rs232 protocol implemented to perform local actions on the DMPS unit, and then sends feedback back out the rs232 port (if you need status feedback or anything).

Then your main controller in each room, would just send out commands based on your implemented protocol to a single rs232 port on the AV3, and it wouldn't matter which DMPS was plugged in, as the DMPS would receive the RS232 command and the local DMPS program would perform the requested action locally and send any necessary feedback back to the AV3.

This would be simple especially if your only controlling switching on the DMPS.? But would still work even if your controlling IR devices locally on the DMPS as well, just a bit more protocol to implement.

Jason Mussetter
www.mpsav.com


 

Actually, now that I think about it, I don't think you would even have to implement a custom protocol.? I haven't used them in a while, but there used to be symbols that worked like EISC's that would work over serial com ports, back when master-to-master communication had to be performed over com ports like this.? If you used something like that, it would work similar to a regular EISC symbol, with digitals/analogs/serials, and it just packs it in and sends over com port to a receiving symbol on the far side.? No custom protocol required.

Jason Mussetter
www.mpsav.com


 

开云体育

Exactly… speedkey XSIG. Also includes mechanisms for “resyncing” the connection (\xFD, IIRC) for when the cart is first plugged in.

?

Lincoln

?

--

Lincoln King-Cliby, CTS, DMC-E/T/D

Commercial Market Director

Sr. Systems Architect | Crestron Certified Master Programmer (Silver)

V: 440.449.1100 x1107 F: 440-449-1106 I:

Crestron Services Provider

?

From: Crestron@... [mailto:Crestron@...] On Behalf Of jasonmussetter@...
Sent: Tuesday, February 25, 2014 1:16 PM
To: Crestron@...
Subject: [Crestron] RE: OT - Opinion on System setup

?



Actually, now that I think about it, I don't think you would even have to implement a custom protocol.? I haven't used them in a while, but there used to be symbols that worked like EISC's that would work over serial com ports, back when master-to-master communication had to be performed over com ports like this.? If you used something like that, it would work similar to a regular EISC symbol, with digitals/analogs/serials, and it just packs it in and sends over com port to a receiving symbol on the far side.? No custom protocol required.

Jason Mussetter




Eric Williams
 

开云体育

Couldn't you have an EISC from each "room program" connected to the program on the dmps.? Run each local room logic through some cross points.? Then simply use the front panel of the dmps to select the room its in.? This way everything is always online, and the logic is essentially the same across the board.

You could definitely even automate the crosspoint selection based on some system event...? When you plug dmps into XYZ its internal program reacts, or the rooms program sends a digital signal through the EISC telling the crosspoint to route.? A latched signal will even react when the dmps first starts, even if its not fully booted when the AV3 local program detects the connection.?

A simple shorted cable from cart to AV3 digital io would do the trick.? If there only one cart they are effectively already interlocked, can't be plugged into more than one room at once.


From: jasonmussetter@...
Sent: ?2/?25/?2014 1:21 PM
To: Crestron@...
Subject: [Crestron] RE: OT - Opinion on System setup

?

Agree with Lincoln on this one.? I would set it up to control the DMPS units with rs232 like an external device, rather than an internal device.

You could make a simple program for the DMPS that get's loaded into all of them, that has a custom rs232 protocol implemented to perform local actions on the DMPS unit, and then sends feedback back out the rs232 port (if you need status feedback or anything).

Then your main controller in each room, would just send out commands based on your implemented protocol to a single rs232 port on the AV3, and it wouldn't matter which DMPS was plugged in, as the DMPS would receive the RS232 command and the local DMPS program would perform the requested action locally and send any necessary feedback back to the AV3.

This would be simple especially if your only controlling switching on the DMPS.? But would still work even if your controlling IR devices locally on the DMPS as well, just a bit more protocol to implement.

Jason Mussetter
www.mpsav.com


 

I like your way of going with this. Each cart could have a different relay latched or group latched, or you could use analogs that get set on boot particular to each cart and look for that value in the EISC when the cart came online with the av3's. Make the logic work after that.


 

we have done a project like that in the past and we solved our problem. each room have it's own vlan. if the shared mobile cart change location it kept the setting and talk to the correct processor

{Paf}

Le 25 févr. 2014 10:56, <dedicatedsystems@...> a écrit :

?

Guys,

?I am wondering the best way to do this.....

5 rooms with AV3's , we have 3 A/V Carts with DMPS-200 and they want to be able to share each cart in any of the rooms.

So can the DMPS-200 run as a eSlave like we normally do with the other control processors?? Or do i need a tech page to select which cart will be in which room?

?If all systems are on the network a simple IP table would point to each system and i dont think that will work... they will not know which system to talk to?


 

Why not setup your EISCs to communicate by host name, and put the carts on the control subnet of the AV3 rather than in the main network. That way it's isolated to the room like Lincoln suggested, but using Ethernet rather than rs-232. This presents you with 2 options- assuming both carts are identical, you can set the host names the same in each DMPS and use a single EISC to talk regardless of which is connected. Or set each to a unique host name and rather than relays, you can use the online event for the EISC to tell which is connected. - chris