Are you handling zone or partition snapshot messages? I bet I have all of the transition messages enabled and the NX is broadcasting status info that is being updated in your scripts. Do you know if the NAK issue is specific to the NX-584 implementation or if the problem exists on the NX-8e as well? I'm using an 8e myself. I wasn't aware of the NAK problems and haven't seen those (that I know of). In the end the packets are the same (byte stuffing does suck though) with binary being much faster to broadcast transition info and a touch quicker on responses.

I've found that the binary mode is more reliable than ascii but a bit trickier to implement. I've been working on a native com event server for the Caddx (not vb based to avoid com port issues and I prefer Delphi) so I am more familiar with the Caddx protocols and fletcher checksums than I care to admit.

I wonder if there is a specific version or even a simple registry change that would get the MsComm control on track.

HS won't send any script commands to the higher comports but doesn't error out either. I have a couple of apps (most notably HomeSeer) that cannot get to the ports. The only thing that seems to have a problem is older versions of MsComm that cannot see past com 4,5 or 6 (depending on version and particular implementation). It acts 'native' (in fact the drivers are on the Win2K cd) to everything I've tried it with so far. I am using a Stallion multiport board and expander for the extra serial ports. Great! I'll take a look at the new version.

Caddx nx8