pturmel

Yes, for RSLinx.  Or change the CMore station number for itself (The Panel Station number--see image) that happens to match the (adjustable) default station number for RSLinx.  All of the devices own station numbers must be unique.  

When multiple devices are connected, they each need to take a different node.  Try changing your RSLinx node in the driver setup.

Try \\ipaddress\printername or \\hostname\printername  

It isn't an error, just an artifact of binary fractions.  Similar to some fractions yielding repeating decimals (anything that has any factor other than 2 or 5 in the denominator).  In binary, if the fraction's denominator isn't a power of two, it will repeat. Your HMI should round it for you.  You see the real thing in the PLC.

If the printer doesn't support the windows printing protocols, then you need a windows PC and set up the printer from it, and make it sharable.  Then that product can use the printer on the PC.

UNC indicates a Windows-compatible named printer.

Please share when you get it figured out.  For future clones of you with this problem. (:

Bad cable is quite possible.  Packet dropouts due to a bad cable will cause extreme delays due to TCP retries.  Similar behavior if the SLC's ethernet port itself has become flaky.  No fix for the latter, naturally. Another possibility is that your SLC has been set to throttle external messages.  See this: https://forum.inductiveautomation.com/t/typical-performance-between-ignition-and-ab-slc-5-05/17262/3?u=pturmel

Write a sample program with one process loop with the features you need and all of the necessary overhead code. Compile it and note how much memory it uses.  Use the instruction documentation to estimate the execution time.  Place this into a spreadsheet as your "baseline" with x=1.  Copy the code and data elements to make it support 10 process loops.  Compile it and note how much memory it uses.  Examine the code to estimate execution time.  Add this into your spreadsheet with x=10.  Repeat a couple times with various values of x. Extrapolate from there.  Add engineering margin to both CPU time and memory usage to account for user interface code and data.  (+100% would not be unreasonable.)

I don't think there's a magic wand to remembering PLC part numbers.  You'll learn some, you'll look up others.  Have user manuals or product manuals available to do the lookup.  A pile of various Manual PDFs organized in folders by brand is a big help, especially when in the field away from the internet.

DCS platforms have relatively rigid configuration structures for large numbers of process loops at relatively slow update rates (1 second and 10 second, typically).  With such a background, and if the user sticks to it, a spreadsheet is not unreasonable for forecasting. Totally useless with devices as flexible as PLCs.

Rockwell simply lists "AuditValue" and "ChangesToDetect" as GSV/SSV values for the Controller Object.  The contents are not further documented, to my knowledge.  You will want to talk to Rockwell for assistance.

Depends what duties that CPU is doing in your system.  It is common for the duties to be critical, so total production stoppage is normal for CPU stop.

That happens if you don't have the EDS files in your install.

I think you'll find that standardized processes won't work without standardized content and functionality, too.  Which means you need to pre-build content and functionality that covers all of your potential client needs.  Hmmmm. Good luck!

An RS232 connection can't handle very many tags at a 1-second interval.  Try changing the baud rate, but also consider making your screens less busy (fewer tags).

The SecToDt instruction, when given a zero input, will set the DT variable to Jan 1 1970 00:00:00.

Go for it.  Clients always appreciate reducing cost/schedule uncertainties.  As long as you meet functionality and performance expectations.  Of course, that's the kicker.  If it was easy, it would already be on the market. The fundamental issue it sounds like you wish to solve is financial risk.  SCADA integrators (like me, an Ignition integrator) generally will offer fixed prices on well-specified scopes.  I do, for a majority of my projects.  A well-specified scope contains the risk for the integrator while the client knows what they will get. The problem is that many potential clients do not know enough about the possibilities of SCADA platforms to generate a good scope document.  Someone has to take the time to learn and then do this, and time is not free.  A middle ground can be hiring an integrator on an hourly basis to produce a scope document, from which fixed bids can then be procured.  I sometimes do this.  The specifying integrator naturally has an advantage in the bidding, which may or may not be unfortunate. (: When scope is too vague for agreement, the only way forward is for the client to purchase incremental development.  All the risk is on the client.  If you can solve this, you will win.

Long before the math fails to add entirely, it begins losing low-order fragments of the amounts added.  The customer I reworked the logic for noticed when the waste water totals were smaller than expected, not that they stopped adding.

Modern logix protocol buffers top out at 4000 bytes.  You'll need to use two messages (same socket).

I know a couple of the Ignition integrators over there.  Send me a PM if you'd like a referral.

Yes.  Wastewater long-term totalizing.  I solved by using integers to count whole numbers and the float to handle fractions only.  Every scan, any amount in the float >= 1 would be added to the lowest-precision integer, then that integer portion removed from the float.  Applicable to modern systems, too.

Sounds like your noise is about ±0.1. Make the hysteresis deadband larger until it doesn't flicker.  Like I suggested above.  That will tell you the peak-to-peak magnitude of your noise. Then you can pursue mitigations.  I recommend starting with electrical and physical so you maintain maximum responsiveness.  Like I suggested above.  Only then would I move to software solutions.  You can add digital filtering to the algorithm options (which would permit a smaller deadband, but add latency). If you don't feel confident writing histogram code, see if your PLC can do internal high speed recordings into a buffer.  Studying captured full-speed data can help (Fourier transformed, perhaps).

You ignored the part where panic mode said to modify the HTML to include dynamic positioning.  And where he said you'd need software from the robot vendor or similar 3rd party to read the dynamic values for you to put in the right places in your webserver. No, this isn't simple.  And you are unlikely to get a magic wand from us to solve this.

Any USB3 ethernet adapter should do.