Elk M1G and elan G! with IP232 Questions

[cnacht]

This is probably one for Spanky, but if anybody has input, it would be appreciated.
My elan G! controller is supposed to hook directly to the COM 0 port. Because of this, I am not able to connect my M1XEP to use RP over the network. From prior posts it may be possible to hook up my M1XEP on COM 0 and use an IP232 to connect my M1G to my Elan G! controller. I have tried this and can't seem to get it to work. I am not sure what ports I should use and how to set them up.
Thanks in advance,
Chad

 

[Del91574]

Why not use an XSP for the XEP?

 

[cnacht]

Why not use an XSP for the XEP?

Can I connect to the M1G with RP through an XSP? If so then I can hook the G! Controller to com 0 then run RP through the XSP. If you meant run G! Through an XSP, I am not sure if that would work because the instructions specifically state it needs to be hooked to com 0.

 

[Jwbarrett]

Don't know if this helps but i use the IP232 to connect ECS to the m1 thru the M1XEP. I just assigned it a static addess 115200 baud rate and kept the incoming port at 2401. Clicked the new button at the bottom right and added the ip address of the m1 and and port 2101 TCP. Clicked next and selected > following power up or reboot stay connected indefinitly. Also the IP232 expect to be pluged into a modem type interface if it going into a pc type interface you will need a null modem cable (DTE/DCE)

 

[tmbrown97]

Going purely from memory, you're supposed to be able to do most things the same regardless of which port you use; the main difference is that all the regular status updates are only transmitted through Com 0 (which the Elan probably needs to keep up). The idea of tricking the Elan into thinking it's connected serially but going through the XEP seems like a great way to go if it's reliable!

 

[cnacht]

Don't know if this helps but i use the IP232 to connect ECS to the m1 thru the M1XEP. I just assigned it a static addess 115200 baud rate and kept the incoming port at 2401. Clicked the new button at the bottom right and added the ip address of the m1 and and port 2101 TCP. Clicked next and selected > following power up or reboot stay connected indefinitly. Also the IP232 expect to be pluged into a modem type interface if it going into a pc type interface you will need a null modem cable (DTE/DCE)

Where do you get port 2101? The secure port is usually 2601 on the M1XEP. Are you setting it up to communicate with the non-secure port with that number? Also, do you do anything with the "incoming UDP packet data" box.
Thanks,
Chad

 

[Jwbarrett]

Yes i'm using the unsecured port and you need to enable it in the M1EXP setup I did not use the "incoming UDP packet data" box

 

[cnacht]

A follow up to see if this helps anyone. I have the M1XEP hooked up to my router and the XEP is connected to the M1G's com 0. I have an Elk ip232 connected to my HC 6 and to my router. I set my ip232 to act a client using the XEP's IP address and non secure port 2101. I set up the M1G in G tools to communicate using the lantronics driver and it worked. On the driver setup I used the XEP's ip address and non secure port number. Don't know how reliable this is, but it has been up a day without problems. This allows me to program my M1G over the network using ElkRP yet still communicate with G!. I will report back if any further problems. If anybody sees any long term problems with this solution, please let me know.
Thanks,
Chad

 

[fcwilt]

A follow up to see if this helps anyone. I have the M1XEP hooked up to my router and the XEP is connected to the M1G's com 0. I have an Elk ip232 connected to my HC 6 and to my router. I set my ip232 to act a client using the XEP's IP address and non secure port 2101. I set up the M1G in G tools to communicate using the lantronics driver and it worked. On the driver setup I used the XEP's ip address and non secure port number. Don't know how reliable this is, but it has been up a day without problems. This allows me to program my M1G over the network using ElkRP yet still communicate with G!. I will report back if any further problems. If anybody sees any long term problems with this solution, please let me know.
Thanks,
Chad

I didn't try using the lantronics driver. I was using a HomeLogic SerialBrick connected to the serial port on the IP232. Your approach is cleaner and perhaps that is why it is working. I will have to give this a try and see how it works for me.

 

[fcwilt]

I set up the M1G in G tools to communicate using the lantronics driver and it worked. On the driver setup I used the XEP's ip address and non secure port number.
Chad

I was re-visiting this issue and there is something I don't understand in your setup. Above you say "On the driver setup..." - are talking about the G! driver?.

If so where does the IP232 unit come into play? It sounds as if you have the G! system connecting directly to the XEP.

 

[cnacht]

Yes, by driver I mean the G! driver. When you go to create a security communication device and have to pick a driver, I selected the Lantronics driver. When it asks me to put in an IP address, I put the XEP's ip address and port 2101.
The connections are: G! to elan to RJ-45 to DB9 Male connector to gender changer to IP232 to router to XEP.
I set my ip232 to act a client using the XEP's IP address and non secure port 2101 and always connect.
It continues to work since I last posted as well.
Chad