Well, I'm working with this ABB plc project, and It's been a learning experience coming from Allen Bradley. The project can't be changed to an AB unit, even though it would be easier to service for my whole office.
Where I'm getting weird issues is with the HMI not having solid communications with the PLC.
It's communicating through Ethernet, Modbus TCP/IP. I've had the communications working fine more than once, but it seems intermittent. Sometimes on startup I won't get any kind of modbus comm error on the hmi, but tags and values don't update properly. I can disconnect the cable, see a modbus comm error show up, and plug back in and still nothing.
Other times it will work flawlessly, all buttons and feedback work. I can see analog in values and write to the registers. What might be going on with this? or is it just a weird communication problem with modbus and beijer or ac500 issues?
Where I'm getting weird issues is with the HMI not having solid communications with the PLC.
It's communicating through Ethernet, Modbus TCP/IP. I've had the communications working fine more than once, but it seems intermittent. Sometimes on startup I won't get any kind of modbus comm error on the hmi, but tags and values don't update properly. I can disconnect the cable, see a modbus comm error show up, and plug back in and still nothing.
Other times it will work flawlessly, all buttons and feedback work. I can see analog in values and write to the registers. What might be going on with this? or is it just a weird communication problem with modbus and beijer or ac500 issues?