pcmccartney1

Bob, this is how I'm checking lead times, as well as talking to my distributor. An Update on Our Global Supply Chain Lead Times | Rockwell Automation

Adding to Bob description, aliasing of inputs and outputs helps latter when an input or output point fails on a module.  You have a spare and can make one change to the alias and not affect any other logic.

Cross reference the Local:3:O.Data.4 to determine if something else is writing to it.  You are looking for destructive references.

Nope.  Go get the docs and read. All are still active, used and supported.  You would best be served by focusing on E/IP.  The others are relics and fading quickly.

The 1769 series of processors require a power supply.  Since you only have a processor and two IO modules, position the power supply anywhere.  The power supply is not assigned a slot.  I suggest you arrange PLC, Input, PS, Output, Right End Cap. Honestly, the L30 is way to much PLC for your process.  Probably an L16 or L18 could work as well for less cost.

We've done messages to inhibit and un-ihibit the scanner.  Done the same this to inhibit and un-inhibit individual nodes.  The issue comes that the scanner card must be idle or not enabled for scan.  Even through Networx, I think to modify a node requires the the PLC to be in Program Mode.  In Logix, the faulting of the card can be setup to fault the entire controller, but I don't think that's what you are looking for either. Not seeing a way for you to accomplish your task.

If concerned with maturity of Omron's IO Link devices, consider ifmEfector.  Been using them for several years successfully.  Not sure we've used them with Omron as yet.  But we use them with E/IP for Rockwell and Profinet with Siemens.  Omron talks E/IP, dependent upon processor, you might need to add a comms module.  Additionally, we use SMC valve banks via EX260 (IO Link) as a slave to the IO Link Master.

Might I also add for SLC and MLX, you should always have at least one service interrupt (SVC).  Usually, second to last rung.  This always for outside devices to have a time slice to talk to the SLC for devices like the SCADA, other PLCs and your PC. My last rung was always an unlatch of the math overflow error.  This gives you a chance of diagnosing the offending logic that's causing the processor to fault.

Yes.  And ridiculous lead times on standard items and only getting worse.

Can the PLC poll the Historian rather than the Historian pushing the heartbeat to the PLC? MSG instruction, fired periodically, to read the status of the Historian heartbeat?

I think you should post this in the GE Forum.  Steve Bailey is an expert.  If he doesn't know the answer, I'm sure he knows someone that does. Personally, I've done it thru the serial port of a Rockwell MicroLogix.  Add code to scan for characters in the buffer.  Confirm correct length.  Then move the data and store in another location for additional logic and eventual display on HMI.

Might I suggest you use a full string rather than 40.  It's lost the 176 at beginning of controller part number.

Possibly a company called Esitron in Germany?

VIPa and Speed 7 seem to be a German owed platform by Yaskawa.  Suggest you contact their technical support to figure out next steps.

Try posting them in the Allen-Bradley forum and someone will create a PDF for each ACD.