Announcement

**Michael McSharry** · November 10, 2005, 03:16 PM

I run mine behind an IP/Serial converter so I'm communicating via LAN rather than directly to a port. When I get a chance I'll connect it directly to a port to see if I get the same behavior as you.

**drodegeb** · November 10, 2005, 07:15 PM

What kind of network serial port are you using? Lantronix?

**Michael McSharry** · November 10, 2005, 08:03 PM

Yes, in this case it is an EPS4, but any network interface that will pass raw data should work. I've got two hub locations with EPS12 and EPS4 and several remote pieces of equipment with EPS1

**Michael McSharry** · November 11, 2005, 01:10 AM

I tried the xapmcsADIOcelot directly to COM port and it behaved just as with the direct IP connection. I have some startup error messages related to the scripting support that is ony partially implemented but the basic variable and SECU updates are seen and the variables are being polled at 2000 milliseconds per the setup.

What polling rate are you using? You can enable the low level communications log from the setup page and take a look at the serial traffic.

Here is my startup log

mcs.AdiOcelot.MCS5 2005-11-10 22:17:15 | xapmcsAdiOcelot | Using xAP port 32775
mcs.AdiOcelot.MCS5 2005-11-10 22:17:16 | xapmcsAdiOcelot | InitFilterDictionary Line 30 Object variable or With block variable not set
mcs.AdiOcelot.MCS5 2005-11-10 22:17:16 | xapmcsAdiOcelot | InitDeviceDictionary Line 30 Object variable or With block variable not set
mcs.AdiOcelot.MCS5 2005-11-10 22:17:16 | xapmcsAdiOcelot | InitScriptControl -2147024809 Line 60 The object cannot be nothing.
mcs.AdiOcelot.MCS5 2005-11-10 22:17:17 | xapmcsAdiOcelot | Version 2.0.25 Registered with Setup
mcs.AdiOcelot.MCS5 2005-11-10 22:17:17 | xapmcsAdiOcelot | Initializing X10 Interface on port 8
mcs.AdiOcelot.MCS5 2005-11-10 22:17:19 | xapmcsAdiOcelot | Using Comm Port 8
mcs.AdiOcelot.MCS5 2005-11-10 22:17:19 | xapmcsAdiOcelot | Found CPU-XA/Ocelot
mcs.AdiOcelot.MCS5 2005-11-10 22:17:20 | xapmcsAdiOcelot | Ocelot IR size: 1024
mcs.AdiOcelot.MCS5 2005-11-10 22:17:22 | xapmcsAdiOcelot | Unit found: SECU16 Addr: 1

**drodegeb** · January 25, 2006, 02:28 PM

I have been given a xyplex MaxServer 1600 Terminal Server. Any ideas if it will work with the xap ADIOcelot?

**drodegeb** · January 25, 2006, 11:13 PM

Well I almost got it working through the terminal server. It identifies the modules, and seems to communicate. Except..

In the log I get:

1/25/2006 11:34:24 PM TCPCOMM
1/25/2006 11:34:24 PM 2A 00 00 A9 1B 00 2F C3 2C 17 CD 24 13 3A 35 A0 B7 20 05 21 35 A0 36 01 3A 35 A0 6F E5 3A 34 A0 4F 3A 33 A0 C3 FD 17 2A 1B A0 36 00 CD BA 27 26 00 22 13 A0 3A 22 A3 5F CD 4B 43 3A 23 A3 5F CD 4B 43 3A 13 A0 5F CD 4B 43 C3 2C 17 CD 24 13 ED 5B 39 A0 C3 82 17 CD 24 13 3A 35 A0 32 1E A6 2A 39 A0 22 2E A3 C3 2C 17 CD 24 13 2A 3B A0 E5 3A 34 A0 4F 3A 33 A0 5F C3 6F 17 CD 24 13 21 00 00 18 EC CD 24 13 01
1/25/2006 11:34:24 PM Waiting for IO info from Ocelot
1/25/2006 11:34:24 PM TCPCOMM

And I get many xap messages with the following body
Event.Log
{
Time=1/25/2006 11:35:54 PM
Type=Warning
Data=Ocelot Plug-in, Checksum error reading io points: 2130 4864
}

Any ideas what I should check?

**Michael McSharry** · January 26, 2006, 04:37 PM

The problem is low level communications where the checksum in the RS232 message is not correct. It seems odd that it is only with IO and not variables unless you are not polling variables. If it is only with IO then I would look at this wiring interconnect.

I did not attempt to decode the bytestream you posted. This level of operation will more likely have better answers on the ADI message board. I could add some debug if you can provide some guidance as to what.

I did post my current version that I am running, but it will likely not make any difference to what you are seeing

**drodegeb** · January 26, 2006, 07:40 PM

I made a few changes and seemed to correct things, but was still getting checksum errors when telling xap Ocelot to go through IP directly. I downloaded a virtual driver for windows that communicates with IP, when using that driver and setting it up as COM5, then telling the xap Ocelot module to use COM5 I don't get any errors with checksum.

**Michael McSharry** · January 26, 2006, 07:49 PM

When using TCP it needs to be setup with a presistant connection. I have my Lantronix units setup in raw data mode and the connection cannot be broken unless explicitly done.

**madmax** · June 25, 2006, 09:08 AM

Not Working

I cannot get this program to detect my ocelot at all. It just times out. I know that the ocelot is working fine because it can be detected in both CMAX and the Homeseer plugin when I enable it. Is anyone using this program with a directly attached comm port?

Using xAP port 32771
Initializing X10 Interface on port 7
Version 2.0.42 Registered with Setup
Using Comm Port 7
Ocelot Plug-in Error, Timeout looking for CPU-XA/Ocelot

**Michael McSharry** · June 25, 2006, 11:13 AM

xapmcsADIOcelot looks for a period in the IP text box to determine if it should use IP or COM. If you leave the IP field blank then it should try to use the COM port number entered.

xapmcsADIOcelot.exe is an ActiveX and should be registered. I think registration of .exe's is done by launching the application with /regserver added on the command line.

**madmax** · June 26, 2006, 09:08 AM

I treied registering the EXE and verified that there was nothinf in the SerialIP line of the ini. Can anyone else confirm that they have this working without a lantronix but directly comm port attached?

**madmax** · July 10, 2006, 04:56 PM

I was never able to get this xAP node to detect my ocelot or other Secu modules. it simply timed out when polling COM 7. This seems strange since I am able to get it to work with ADIOCelot HS plugin and also stand-alone with CMAX.

**Michael McSharry** · July 12, 2006, 04:56 PM

I toggled between direct IP and COM8 via the Redirector driver and had success with both configurations. I'm running V2.0.44. My log is below that shows the startup feedback where it finds the ocelot and an SECU16. When I configure for COM8 I put the IP to blank the 8 for the port.

If you give me the exact message produced on your timeout then I can add some debug info that might help.

**madmax** · July 13, 2006, 02:16 PM

Thanks for looking into this problem.

This is the body of each xAP message I see after starting the Ocelot plugin:

time=7/13/2006 3:05:57 PM
type=xapmcsAdiOcelot
data=Using xAP port 32768

time=7/13/2006 3:05:57 PM
type=xapmcsAdiOcelot
data=Version 2.0.42 Registered with Setup

time=7/13/2006 3:05:57 PM
type=xapmcsAdiOcelot
data=Initializing X10 Interface on port 7

time=7/13/2006 3:05:59 PM
type=xapmcsAdiOcelot
data=Using Comm Port 7

time=7/13/2006 3:06:03 PM
type=xapmcsAdiOcelot
data=Ocelot Plug-in Error, Timeout looking for CPU-XA/Ocelot

time=7/13/2006 3:06:06 PM
type=xapmcsAdiOcelot
data=Ocelot Plug-in Error, Timeout looking for CPU-XA/Ocelot

Announcement

xapmcsADIOcelot - ADIOcelot xAP Node

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment