GROOV Epic controller I/O will not enable

This is local IO for the Epic controller in Pac control. The local control sees the IO just fine and knows the states if changed. The IO in the strategy wont enable due to comm issue.


#, Code, Severity, Description, Chart, Block, Line, Object, Time, Date,
0, -539, Info, I/O error; performing retry, <system: _INIT_IO>, N/A, N/A, A2Controller type: 402008 , 08:08:41, 10/08/24,

< forums admin snip of the many many errors for readablity >

93, -69, Error, Invalid parameter (null pointer) passed to command., Comm, print.1, 15, (null), 08:08:53, 10/08/24,
94, -69, Error, Invalid parameter (null pointer) passed to command., Comm, print.1, 18, (null), 08:08:53, 10/08/24,

Have checked IPs, rebooted, Pac term connects and shows same errors with comm to IO down. This unit has been working before. Changed secondary IP and unchecked/checked local loopback. Think config issue but dont know where else to look

Hope you don’t mind, I took out a lot of the errors in your original post so that it is easier to read…

Can you provide a screenshot of the I/O unit in config mode please.

PAC Terminal is not really the right tool to look at I/O, its really only useful for the controller.

The screenshot Im wondering about is this one:


Yes on the errorsI started a couple pointers and haven’t finished till I resolve this issue with the IO comm

The controller is seeing the local IO when I check the IO status by applying 5v to digital inputs, the display displays the off or on condition also can ping laptop. Any ideals?

Ah, so local-host is working fine, the screenshot showing it offline is from another laptop on the second IP address subnet?

yes it on line on the second IP and it goes into debug, but will not enable IO ever if tell it to manually

that should say even when I enable it manually

Its been a while since I have used redundant networks… I assume you have read, and given this issue, re-read, the PAC Control users guide (Doc #1700) from about page 100 on wards?
The secondary address use is a PRO only feature, so I take it both your systems are running PAC Control Pro?
The secondary address needs to be in the same address space as the primary of the controller, so while you have localhost here, you need to review your subnet mask for the controllers IP address and make sure it works with the secondary IP address you have configured.
If the other computer needs to also be in the subnet.
If it is running with the Windows firewall, I’d test it for a moment with it switched off.

See how those checks go and if you are still having trouble, I’d next hit up our support group.
Please drop back and let us know what you found to close the loop on the thread.

I checked: the windows firewall is off, Subnet masks seem to have no issue. I am using Pac C Pro, so decided to set one Ip and see if the IO would talk .


and it still wont let IO enable

so, I’ll look over thee 1700 again, if you see anything here let me know, if not, is that product support?