PNI800 License Key Issue
We just upgraded to the new S+ Ops 3.2 and S+ Eng 2.2. As part of this upgrade we also converted to a PN800 network using PNI800s as the interface. We got the license keys for the PNI800s from ABB using the MAC IDs read from the PNI800 using the HAPI utility. However, once we applied the license key 2 of 3 PNI800s seemed to stop working. The ICI Status utility can't seem to get status on the PNI800s either. We double checked the MAC ID vs the license key to ensure the right key was entered (in fact if you enter the right key the PNI800 rejects it anyway) and it seems correct. Has anyone encountered this issue or know of a work around?
Asked 1 year ago
Answers
This question has not yet been answered.
by
Hi,
Have you tried setting the license directly at the PNI? I usually just set the IP and license directly on PNI/IET and the host normally connects without issue.
Cheers,
Alan
by adatta Rank: 1692 on 12/8/2019 5:58:13 AM | Like (0) | Report
Alan thanks for the suggestion. However, it seems with the A8 firmware the main menu via the diagnostic port doesn't seem to give any option to do that. Or at least it's not clear how you can.
by
Hi,
I think that the old menu is still there but you have to set the dipswitches via the S+ menu first and this might get complicated. What about looking at the working PNI switch settings and comparing with the units that don't work. Confirm the IP address settings and dipswitches/battery jumper are correct before attempting to load the license.
Alan
by adatta Rank: 1692 on 12/9/2019 11:47:05 AM | Like (0) | Report
You're right Alan. The old menu is still there, but you have to set the dip switches (virtual) in the correct position before it becomes available. However, we were able to enter the keys via the software finally.
by
Good news, BTW was there a reason for licenses being accepted finally or is it a mystery?
by adatta Rank: 1692 on 12/10/2019 10:07:04 AM | Like (0) | Report
No concrete reason. While the keys were not installed we found that the PNIs restart/disconnect very frequently (as per design when not licensed). It could have been that in that first instance we were trying to apply the key during a restart sequence.
Add new comment