Extruder line. ControlLogix 1756-L61 with a 1756-CNB in slot 2, ControlNet out to three 1794-ACN15 Flex racks and two PowerFlex 700 with the CNet card. RSLogix 5000 v20.
The CNB died Friday, OK LED red, no comms at all. I put the shelf spare in, node switches at 01 the same as the old one, and it's green now, but every rack under it has the yellow triangle and 16#0204 or 16#0203 depending which one you click. The drives too. I power cycled the whole chassis and swapped the tap for a known good one, no difference.
Went online with RSNetWorx and it's complaining about the keeper, something about a signature mismatch. Is the spare bad, or does it need something loaded into it? Does a new CNB need that signature loading into it before the racks come back, and is that something I do from RSNetWorx?
The spare's fine, it's empty. ControlNet has a keeper, one module on the network holds the schedule and the network parameters, and on a line that age the keeper was the old CNB, because when it was built the CNB was the only thing that could do it. Yours has never seen this network. Which RSNetWorx version? About screen.
RSNetWorx for ControlNet 11.00 off the About screen. So the schedule was sitting in the module that died, brilliant. The Flex racks and the drives are all still set up in the L61 project, that hasn't changed. Do I have to build the whole network again from scratch?
No. The schedule lived in the keeper, but what you need to rebuild it is in the .xc file from commissioning and in the controller. Go online in RSNetWorx, Network, Keeper Status, and if I remember right that dialog lists every keeper capable node and its state. The new CNB shows invalid or mismatch, the wording changes with the version. Select it, Update Keeper, so it takes the signature off a valid one. Then Network, Online, tick Edits Enabled, Save, pick Optimize and re-write schedule for all connections. Controllers in Program for the re-write. The 16#0203 and 16#0204 clear once the schedule's back. And node 01 is the CNB, the L61 isn't a node.
Keeper Status shows the new CNB as Invalid. The drives' CNet cards and the ACN15s all say something like Not keeper capable, so the only keeper on there was the dead one. Update Keeper is greyed out. Edits Enabled, Save with Optimize, and it stops with a message that the keeper is invalid and it won't write. extruder's still down and we're running a hand batch, so I'm not sure what else to poke at.
Greyed out because there's no valid keeper to copy off, as far as I can tell. Different route. Open the contractor's .xc file offline, go online from that file rather than from a browse, Edits Enabled, Save with the re-write. A save from a project that already has a schedule writes the keeper, it doesn't need a valid one to copy from. If the .xc is gone, let RSNetWorx browse and build a new file, then set the connection parameters again from the L61 project. Find the .xc first, the drive connections are in there.
Found the contractor's .xc on the old laptop in the office, Extruder_CNet_2012.xc. Opened it, went online from it, Edits Enabled, Save, Optimize and re-write schedule for all connections, L61 in Program. It wrote the keeper into the new CNB, Keeper Status went to Valid, and every rack and both drives went green the second the L61 went back to Run. Got a full shift out of it yesterday.
So the keeper was the dead CNB the whole time and the spare had nothing in it, and re-writing the schedule from the commissioning file put it all back. Nothing wrong with the spare.
Still don't know why Update Keeper was greyed out, maybe it wants a second keeper capable node. Thanks rsdave, louk.
Copy that .xc somewhere that is not the old laptop.