Joe Tauser

Go the support@unitronics.com route and ask that it be forwarded to Israel, in which case the Creators will see it. Joe T.

Not an out-of-the-box solution. The closest thing we have right now is MQTT. Joe T.

Posting your code would be even better. Joe T.

This can be caused by noise gremlins getting into the CPU via the I/O module. Do you have any VFDs in the system? Joe T.

There are no system operands which contain this data. The MAC address method I've used returns the address of the PLC (contained in SDW 22 and 23) for router security configuration. Maybe the Creators know if a way to sniff the incoming TCP packets using the TCP_RAW protocol. The IP of the Master could be extracted from that. Joe T.

They're talking about Port 1 on the PLC, which the USB port on the PLC takes over when you connect a cable. Your PC has mapped the adapter to its COM 3. In other words, you're OK. Go for it. Joe T.

Make sure the OS is updated. There was one a while back that had a clock issue. Joe T.

I know nothing of the hardware activation. Can you elaborate? Otherwise, your points are well taken. We'll tickle some of the Creators to see that you are heard. Joe T.

This is a question for the Creators. Cut and paste your above post and send it to support@unitronics.com. This forum is not an official representation of the Unitronics staff, although they do weigh in from time to time. Joe T.

You've just repeated the PCOM protocol guidelines from the documentation. https://unitronicsplc.com/Download/SoftwareUtilities/Unitronics PCOM Protocol.pdf So this tells me you're trying to implement a PC program to talk to Unitronics. This protocol is published to be embedded in a higher language program. But there are other easier ways to communicate with the PLC - the OPC Server, Modbus, and the .Net driver. I don't have the sample program you're looking for as I don't code at that level. When I want to talk to Unitronics with a PC program I use Visual Basic and an embedded Modbus control I purchased for $259.00 US. Way easier. What is the rest of your story? Joe T.

This was bugging me so I asked support. Here is the response - So UniOPC does use PCOM. You would want to remove the Modbus logic if you're using UniOPC to a Unitronics PLC This is a muddy part of the Help. It is referring to an OPC server provided by somebody else (such as Kepserver) that uses Modbus as its protocol. Also known as a "Modbus OPC Server". This is not what UniOPC is. This is their way of telling us not to call Modbus continually from ladder logic if the Unitronics is the Master. The times are bases on the PLC model. Don't use 0.0 time. I can tell you from experience that you have to wait a bit between slave calls - I usually wait 0.1 seconds. Joe T.

I have never personally used the OPC server so I can't speak from direct experience, but I did look at the OPC manual. The OPC server is a program that has been around for a long time, and I don't think it uses Modbus. I didn't see anything in the manual about setting up the PLC as a Modbus slave. The OPC Server probably uses the Unitronics PCOM protocol, and by using the COM INIT block and Modbus Config in the ladder logic you blocked the port to PCOM commands. As an experiment, try deleting COM INIT and the Modbus Config block if you still want to try it. Joe T.

BTW, I bought an IoT light control for my bedroom to turn on in the morning to help get my night-owl butt out of bed- https://www.leviton.com/en/products/dw3hl-1bw It talks to my wireless router, and I set up the schedule with an app on my phone. It works properly 99% of the time. I THOUGHT it kept the schedule inside itself, but one morning when my Internet was down I learned that was not true. If it couldn't talk to the Levition Master in the Cloud, it just sat there. In other words, my light didn't go on that morning. I couldn't trigger it with my phone app, either. Yep. Anyone who tells you their Internet is up 100% of the time is lying. When Hurricane Sandy hit the east coast of the US, I could not communicate with my vendors in the New York / New Jersey area for over a week, because they couldn't get email and they had drank the Kool-Aid and converted their phone systems over to VoIP. Those who had copper land lines could still be reached. Anything connected to the Internet can be hacked, too. Joe T.

Or you could just buy an IO-DI16 and tack it on. Joe T.

30 channels of precise measurements is not going to be cheap. I'd look at a Keysight 34970a with a pair of 20 channel cards. You can talk to it with the PLC via RS232 or get yourself a copy of LabView. Do you need control or just data acquisition? Many moons ago I did a 48 channel hybrid system for Emerson Motor that combined a PC app talking to the above instrument and also talking to a V350 that performed UL life tests with temperature monitoring on new motor designs. Not cheap (about $25K). But good. Very good. There is a new family of UniStream Ethernet I/O that sports 16 bit four channel analog modules that may suit your needs. Ask your supplier about it. Joe T.

But do you really need to care? Think it through. You're really not amplifying error, you're reducing sensitivity. Your circuit would be calibrated for a fixed input anyway, and once the divider was installed it would not change its response appreciably. The accuracy on a 10V input module is 0.3%, which is not as good as a modern multimeter. Your uncertainty (call it error if you want) is 30 mV. If you set up your divider to measure 20 VDC then your uncertainty is 60 mV. Pretty crappy. Here's a DC "differential amplifier": https://www.acromag.com/catalog/875/signal-conditioners-converters/signal-converters-transmitters/dc-voltage-current-input $185.00 each. Accuracy - 0.05% of span This will improve your uncertainty but you're still stuck with the PLC's relatively sloppy 30 mV. Bottom line - a PLC analog input is NOT a multimeter. I have tried to make electrical measurements like this in the past and did not have good long term results, thanks to the uncompensated thermal drift of all components involved creating slightly different readings every other day for the same calibration signal. If all you're trying to do is get a close-ish measurement the PLC is fine. But your initial comment about error tells me you want something better. You need to get a real voltage measuring instrument that talks Modbus and let it do the work. Or get an Agilent 34401 and use the Message composer to talk to it with SCPI commands over the RS 232 port. I have a customer who has done this. Joe T.

That looks amazingly like the Example program Kikis posted for you. You're having trouble modifying the code because you didn't write it and you don't know how it works. The problem with a Set/Reset and Contact type program (A.K.A. "A Bit-Banger") is they are very difficult to insert new steps in after they've been written to perform a certain task. Fear not, young Padawan. There is a better way, but you must study the Ways of the Force. You are trying to program a sequence, which can easily be defined using a flow chart. Read the following post three times: Then download my State Machine example program and study how it works. Then list the steps of your sequence. On paper. Use circles and arrows. A paragraph on the back is optional. From your written steps, see if you can implement the State Machine. You should be able to do it in four networks with three timers, based on your previous posts and this new information. Upload what you come up with, even if it doesn't work right. We'll worry about the analog output for the speed after the output coils are working. Joe T.

The statements expressed here are my own opinion and do not necessarily comprise a definition. Short answer - an IIoT device is an IoT device that's located in a factory with a lot more people that have an opinion about it. I found these- https://www.computradetech.com/blog/iot-vs-iiot/ https://www.leverege.com/blogpost/difference-between-iot-and-iiot https://www.iotforall.com/iot-vs-industrial-iot-differences-that-matter/ https://us.profinet.com/iot-vs-iiot/ You'll find in reading these that there is no clear definition of IIoT - just some thoughts on what it should be. What I have experienced is every company and every location has different expectations, requirements, paranoia, and regulations. Most of the time we put the controls on their own network and manually connect a line if we need to get in. There are other products that act as bridges through a secure website. And so on. Other input is certainly welcome. Joe T.

If you're rolling your own Modbus, you can use something like this (assuming a .NET environment)- https://sourceforge.net/projects/easymodbustcp/ Also look on the software page of this website at "Programming Tools for Developers" for the Unitronics PCOM protocol driver and documentation. Joe T.

Need to know what on the PC will be creating the Modbus requests. Joe T.

You need to be much more specific in your request. What data? What program on the PC receives the data? Is there a file format you need? Is this for a program you've written yourself or SCADA software? Unitronics has a Utility called DataXport that may meet your needs. Joe T.

You don't need a crossover cable. You can plug a regular cable from your computer to the PLC. Or have the PLC and the computer plugged into the same switch. My point is to remove all other components of the network. To Gabriel's point - do you have another PLC or Ethernet card you can try? These units are built by men - they are not without occasional fault. Joe T.

I didn't have any problem downloading from the above link. What exactly are you looking for? Joe T.

After you've looked through the sample projects and watched some videos try your hand at creating a project and upload it here. We will be happy to review it and make it do what you want. We are very helpful people, but we don't write other people's code from scratch. You have to go first. Joe T.

As Flex says, you've already got SB 168 to set on power-up. You don't need the coil in your logic. Socket 1 defaults to TCP 20256 slave, so you don't need that, either. I'd get rid of the powerup value in SI 104, too. Set SI 104 to 0. At 100, the PLC will wait 10 seconds before it unhooks from a "Connect" that has gone awry, and you're just muddying the water at this phase. You mentioned you are connected via wireless. Is the PLC on the same physical network as your wireless access point or is it at another site? Are there managed switches in the loop somewhere? There may be some latency in packet transfers - I've run into this with corporate networks and remote cellular systems. To eliminate the network connection question, connect to the PLC with an Ethernet cable from your computer. You need to do this test- I have not had problems with Ethernet-enabled PLCs going offline with a local hard pipe connection. And I've done a lot of them. You can set the TCP Retries timeout (SI 101) higher to something like 10 to see if it helps your wireless problem. The units on that register is also 100 ms. Also, there's no rule that you have to use only SB2 to init your Ethernet card. I always add a second self-resetting bit that allows me to edit the Init block or any other Ethernet stuff going on. If you set the bit from a button, PLC logic, or from Visilogic you will loose connection but will be immediately able to re-establish it with the new parameters you've set. Beats cycling power on the PLC every time. Joe T.