DanW

The SIOU A/O modules on the right leads me to believe that it might be Bedrock Automation hardware. They were based in San Jose, CA and made a big splash about cyber-secure control hardware/firmware a decade ago. For an overview see https://www.piprocessinstrumentation.com/process-control-automation/company/21136469/bedrock-automation According to this Reddit thread, Bedrock Automation died 3 years ago. https://www.reddit.com/r/PLC/comments/yz2mt6/bedrock_automation_defunct/ There are various Google hits for SIOU I/O. I'm just guessing it's Bedrock automation because of the SIOU I/O module. Could be something else. Best of Luck.

Is the analog output passive (does not supply DC power for a loop-powered field instrument, like the majority of analog inputs) or is it active (supplies 18-24Vdc for powering loop powered field instruments)? The analog input module manual does not explicitly say, as far as I can tell, even though it is the length of an encyclopedia. There are comments how to connect device power supplies on page 75-76 but I'm not familiar with Omron hardware. But the document does not contain the word "loop", "active" or "passive" and nowhere (in a quick scan) implies that DC power is provided on any of the input terminals. I would therefore conclude that the AI is passive and does supply DC power to the field device. On page 95, it shows a 3-wire voltage output field device that uses DC power to power the transmitter. But the next diagram down shows the 4204 module as not supplying DC power. I think you need to grab 24Vdc to power the transmitter.

You provided the same number for the sensor as for the cordset. Need a link to the sensor installation guide.

I assume you can post articles on your own company's website and your question is asking whether this site allows posting of product articles. Most forum policies do not allow product posting because it is advertising and it rapidly gets out of hand. The most extreme example was LinkedIn which used to have topical "Groups" and the I abandoned all the automation/control/instrumentation groups because they were not technical forums for problem solving, they were just one press release or ad after another. I'm not sure LinkedIn had sufficient moderator rights to address what I thought was a problem, but whatever, it was just a flood of ads and press releases. It might still be; I haven't looked in several years. I honestly do not know what this forum's formal policy is, but on another forum where I moderate, I delete product announcements. I do allow mention of products that can solve a specific problem for a given thread's topic if there is an explanation of why the product will solve the problem.

Back in the late 1990's when OPC DA was gaining steam, the hotel meeting room seminars by the OPC Foundation provided an overview on use and applicability, but the nitty gritty details about the protocol were available by membership, typically corporate membership, given the market. That appears to be the case for OPC UA, reading the last line on the Developer Tools page on their web site: https://opcfoundation.org/developer-tools/

There is an established market for disposable thermocouples used for measuring molten metal. I've seen the noble metal (platinum) thermocouples Types R and S used on a lance. 40 years ago the guy using the lance had an analog indicator on the end of the lance, but nowadays, you can connect the thermocouple extension wires to any wired or wireless temperature transmitter to get a temperature signal back to a PLC or whatever you envision as a 'broadcast' system. Google disposable thermocouples for molten steel

Functionally, what is a Qj71C24N? Links to the manuals of these devices?

I have scanned paper manuals from late 1980's and 1990's equipment and in one case even OCR'd the scanned document. But one has to have access to a paper manual from that pre-pdf era.

As long as the specs say that they'll support Modbus RTU, which has very specific timing requirements that can be a problem for generic serial-to-Ethernet converters.

If heating increased the temperature from a negative 130 Deg C to a positive 19 Deg C, then the thermocouple must be connected in the correct polarity, because when a thermocouple is connected with reverse polarity the indicated temperature drives in the wrong direction, i.e. a reverse connection drives the temperature down, not up, when heat is applied. The interesting thing is that a 149 Deg C temperature, as determined with a non-contact IR handheld is 149 Deg C above freezing point of water (0.0 DegC). Somehow this AI card/CPU thinks that freezing point of water is -139 Deg C, not 0 deg C. The mV conversion for the span of the temperature above freezing is correct, 149 DegC, but the freezing point of water is not 0.0 DegC , it is -139 Deg C. I suspect that whatever program/configuration the PLC is running was lost or altered during storage, possible battery back-up failure, and the program/configuration is now wrong. In 20+ years of web forum troubleshooting temperature problems, this is a first.

Shine a light beam through the bottle. The liquid should refract the beam. Weigh the bottle.

Ironic that I just deleted my Scanbus folder for this app this morning. Someone was looking for a Modbus Master/scanner app and when I checked the former URL it 404'd so I deleted the folder. Glad to see the app is still supported.

The replacement meter does not provide a shunt, the customer provides the shunt. The wires on the terminal strip labeled 86 and 87 are shown on the original diagram as 501 and 502 that run to an exterior shunt. Follow 86 and 87 to wherever the shunt is and measure the resistance of the shunt or see how it is marked or identified.

Thanks for the heads-up on the email log-in, instead of user name. My old email address hasn't been valid for maybe 8-10 years now. I would've been locked out at the log-in change having a non-existent email address. Dan

It appears that most if not all of the spam finally got cleaned out. Thanks for effort. Dan

What a recovery ! ! I thought the site was in hospice for quite a while there. Nice job on the upgrade.

Presumably the reason for two pressure transmitters is that the tank is a closed vessel and there's pressure in the vapor space above the liquid. If you subtract the vapor pressure measured by the upper transmitter from the pressure measured by the lower transmitter (units have to be the same), convert the pressure value to a distance value (inches/feet,mm/m) and then divide the distance value by the Specific Gravity you will get physical level value. The problem with using two pressure transmitters instead a single differential pressure (DP) transmitter is that the combined error of both transmitters can be significant. Convention calls for using a single DP transmitter.

Thanks for the comments. I have no exposure to robots and wondered what the real story was.

Does the valve/actuator assembly have a positioner?

Serial comm is always a project, it is rarely plug-and-play. You might need to make an adapter cable for the connection between the adapter in the field the RTU field device. You need to ring out the programming cable that you have to see which RS-232 function is on which pin, going from the laptop to the 'working' end and make a drawing of which pin goes where. Make sure that the laptop's function match the adapter's functions on each pin. Things can get reversed going from male to female, or counting from the wrong end. When I've done stuff like that I always had a print-out of the make DB9 pinout numbering and the female DB9 pinout numbering. Then you need to match up the pinout on the other end to the RTU that is the field device so that the pin functions end up on the needed pins. You have noted that you need to use CAT 5 cable that is runs point-to-point between the two adapters. This is NOT Ethernet and you can't connect the CAT cable to a switch, hub or router.

The 50 feet limitation comes from the EIA specification. It doesn't mean that the signal dies at 50 feet, but that one should expect reliable communications for installations 50 feet and under. Performance beyond the stated limit can be compromised. I know of two installations that when I arrived the RS-232 'cable' had already been installed, in one case about 65 feet, in the other about 75 feet away. The 65 foot run was not even shielded, twisted pair, but it worked at 9600 baud and to my knowledge is still running today (commissioned in the early 2000's). On a similar note, Ethernet is rated to 100m. A local town fair ran a CAT 5 cable 500 feet to get an internet connection that ran fine at 10Mb, back in the day before Wi-fi was everywhere (early 2000's). The signal doesn't 'die' at the limit, but extending beyond the limit affects performance. My suggestion is to try comm with shielded twisted pair cables, at least 18g, 16g if you've got it to reduce any voltage drop. As to converters, USB is more limited that RS-232,short cables only. There are scads of 232/Ethernet converters. There are Bluetooth/RS-232 converters but I have no experience at all with them.

If the Modbus maps for the old unit and the new unit match identically, same register addresses, same data formats, and the serial settings on the replacement unit match the old unit, then the Modbus Master/Client should encounter not difference in either reading or writing data to/from new unit. The assumption is that the operation of the new unit does not vary from the old unit, the commands work the same way, which is usually the case for updates over time because vendors want the replacment business and having functional compatibility between old and new Modbus comm tends to make people stay with the same brand.

I'd guess V_SP" the setpoint with warm-up ramp with a value of 58? Just guessing.

If the "RTD" in the part number of that input module means that that particular AI card is for direct connection of RTD's then the answer is most likely, "No, you cannot wire Infrared sensors directly to that card". Nor are you able to take signal from the temperature controller because there is no known commercial temperature controller than outputs a resistance vs temperature signal. The re-transmitting output of temperature controller is normally 4-20mA, sometimes a high level voltage, like 0-5V. 4-20mA and 0-5V is incompatible with a RTD input. The infrared sensor market has models that output 4-20mA over a specified temperature range and then there are models that output a non-linear thermocouple mV output over a temperature range. The thermocouple output is designed to be compatible with thermocouple inputs but it is not compatible with an RTD input card. You need a different analog input card to handle an infrared sensor signal.

You might try control.com and Plcs.net forums with this problem.