In the interest of getting off of the old ADI Ocelot plug-in from Michael McSharry I decided to move to this .NET plug-in. Several things seem to not work, and I don't know if there is something I am doing wrong. My gut tells me that if something really doesn't work, there is no hope of getting HST to fix it at this point. Here's the things I'm seeing:
Steve
- I have a watchdog CMAX snippet that does a periodic (every 10 minutes) handshake with HS. It sets a variable to 1, and I have an event that is triggered by that value. The event then sets the value to 9, which tells the Ocelot that HS is up and running. It will then set it back to 1 after 10 minutes. If after 10 minutes it doesn't see the 9, the Ocelot turns a relay ON and then back OFF that is connected to the reset button on the computer. I can see that the event properly sets the value of the device to 9, but as far as I can tell that value is never set to the Ocelot. I can't interpret the debug output from the plug-in.
- The debug log indicates that all 8 of my RLY8 relays are off. Well, actually it says that all the relays from '/9' through '/16' are OFF, and my relay devices that the plug-in created are actually '/1' through '/8', and two of them are almost always ON. Turning them ON and OFF from the HS status page seems to work, but the debug log would seem to indicate that the plug-in doesn't see the correct status from the Ocelot.
- I have a couple of scripts that used the cpuxa.SetVar() method. I added the stuff that the .NET plug-in requires to set the cpuxa object to point to the plug-in, but as far as I can tell it doesn't actually do anything.
Steve
Comment