Any Crestron Experts?

[CDC]

We installed an M1G w/an EXP module. The Crestron installer said he couldn't use ethernat to connect to the Elk but needed the serial port. What is involved in having a Crestron system communicate over the LAN rather than through the serial port on the M1 board. Thanks. CDC

 

[Neurorad]

I'm sorry, I don't know the answer to your question.

But I'm curious - what's wrong with serial communication?

 

[WayneW]

But I'm curious - what's wrong with serial communication?

If Creston takes the Elk serial port, then the XEP cannot be used. This limits access to the M1 via Elk-RP, Elk-RM, etc.

 

[Neurorad]

The answer can't be this easy:

"The M1 Gold and M1EZ8 support up to 7 M1XSPs" -Elk

Please explain, Wayne or someone else. Aren't multiple serial ports possible? I'm guessing it has something to do with the location of the XEP on the board.

 

[WayneW]

Multiple serial ports are possible (via XSPs) for special purposes, but the on-board serial port 0 is better/different than the other serial ports. Serial port 0 is the only one that broadcasts all the status messages. The XEP requires use of serial port 0. I am assuming that Crestron also require serial port 0 (rather than XSP) since every full-featured HA package I have heard of also requires serial port 0 or an XEP.

 

[Neurorad]

Hmmm...maybe this is something that should be addressed in the M1 Platinum, or M2. There should be an M2 dedicated wish list thread...the closest I could find was 'Future of Elk M1', started Jan '09 and not very focused.

 

[opie]

I think Wayne is on the right track here. I'm not a Crestron installer so I can't say for certain but it may be that there isn't an IP Crestron module for the ELK.

 

[WayneW]

Hmmm...maybe this is something that should be addressed in the M1 Platinum, or M2.

Possibly, but the reason it is that way now is that the serial port 0 is pretty chatty and to add all that chatty traffic to the Elk data bus and expose all the XSPs to it would add a lot of traffic, which could require more horsepower in the hardware.

IMHO, all HA software (and HW like the Crestron) should be able to talk to the Elk via IP. The XSPs should be for dedicated, low traffic devices (thermostats, lighting controllers, etc). Maybe the M2 could have 2 chatty full-featured serial ports on the main board as a compromise.

 

[icellama21]

Correct me if I am wrong, the M1XEP doesn't care if it is talking to Crestron or Bob the plumber. It is just an ASCII protocol. If you have a serial interface from your crestron system, hook it up to an IP-RS232 bridge that is designed to automatically reconnect to the M1XEP. Most are capable of this. Should work pretty well. May take some tinkering to make sure it is reliable, but for someone that programs and installs crestron, this seems like a minor issue.

 

[signal15]

I have successfully used "socat" running on a linux box to make the serial port on that box operate as if it was Serial0 on the ELK. You would use a command like this, replacing it with your ELK IP:

socat /dev/ttyS0,raw,b9600,crnl TCP:10.1.1.40:2101

 

[Neurorad]

Any updates on Crestron Elk modules? I heard of a rumor of an IP module.

 

[electron]

http://www.cocoontech.com/portal/articles/news/31-software/493-elk-m1-driver-now-available-for-amx-and-crestron

 

[Neurorad]

A very kind soul has explained to me that the native Elk module (c. 2006) can be used over the IP network. It doesn't need an Elk serial port.

But I will definitely check out the ModuleDepot's offering. Thanks, electron.

Maybe the ModuleDepot programmer will post here, with a comparison of functions. That is, why use theirs, instead of the standard?

 

[Spanky]

Eric Lee's ModuleDepot's AMX and Crestron driver uses the M1XEP Ethernet interface to the M1. This allows other equipment that wants to talk to the M1 to be able to share the connection. The RS-232 interface only allows one connection.

Also I understand the the ModuleDepot's driver reads up all the names that are programmed in the M1 and displays them at the appropriate locations on the touchscreens. That way you do not have to double load them in the M1 and onto the screens. The driver will also maintain a constant connection to the M1. If the connection drops, it will reconnect automatically. Plus there are many more features to vast to mention here.

 

[Neurorad]

David, thank you so much.

But, I think the 'native' Crestron Elk module also can use the M1XEP Ethernet interface. At least, that's what I've been told by an alarm installer who commonly integrates with Crestron.

I will speak with Mr. Lee, when it comes time to decide. Price, unfortunately, will be a factor. 'The Best' is often not affordable.