News:

  • December 06, 2022, 04:34:31 AM

Login with username, password and session length

Recent Posts

Pages: [1] 2 3 ... 10
1
Do-more CPUs and Do-more Designer Software / Re: Vertical Red/Blue Lines in Trend View
« Last post by franji1 on December 05, 2022, 03:54:34 PM »
I'm guessing that seeing Transport Protocol Errors (appearing "randomly" and for very brief periods of time <1/2 second) could be a sign of potential network traffic issues.
Could be Noise (more likely), Runtime Edit, Firmware update.  Unless you have some kind of broadcast or bandwidth issues, noise is a potential comm issue.
Here's some general help on Ethernet, Panels, and Noise:
https://hosteng.com/FAQFiles/ECOM.htm#FAQ0045

Quote
I'm also guessing that seeing a timeout for a sufficiently long period of time would also indicate that the same network conditions causing the timeout of the link would cause issues with the MRX/MWX functions.
Network traffic, noise, runtime edit, firmware update - yes.

Realize also that there may be issues on the Designer/Modbus Client side, not necessarily the PLC side, so Modbus may be fine but Designer is not (or vice versa).  But if it is PLC side, it can affect all areas of Communication.
2
Until the implicit EIP scanner functionality is added to the Do-More platform, you might have some issues. Most of the equipment that is designed to operate with RA products use implicit EIP where the PLC is the scanner. At present time, Do-More can only be used as an adapter. Some of the devices designed to work with implicit EIP can be used with explicit EIP which can be done in the Do-More. If the device offers Modbus, this might be a better option.

There is a section with local Modbus reads/writes in the ConveyLogix software they use. I'll look more into that.
3
Until the implicit EIP scanner functionality is added to the Do-More platform, you might have some issues. Most of the equipment that is designed to operate with RA products use implicit EIP where the PLC is the scanner. At present time, Do-More can only be used as an adapter. Some of the devices designed to work with implicit EIP can be used with explicit EIP which can be done in the Do-More. If the device offers Modbus, this might be a better option. 
4
Hello,

We are implementing ConveyLinx controllers from Pulse Roller to be controlled by our Do-More plc. We have not done this before so I'm looking for some information to point me in the right direction from the Do-More side. In the ConveyLinx documentation they show how to connect to Rockwell and Siemens PLCs via Eth/IP or profinet. I'm not looking for a full breakdown on how to get the systems to interact, but maybe some general advice on what instructions I should look at to get me started connecting the systems and talking back and forth.

I've talked with the ConveyLinx manufacture and got some information from them too including manuals and examples from their software.

Thanks.
5
Do-more CPUs and Do-more Designer Software / Re: Vertical Red/Blue Lines in Trend View
« Last post by RBPLC on December 05, 2022, 02:21:37 PM »
I'm guessing that seeing Transport Protocol Errors (appearing "randomly" and for very brief periods of time <1/2 second) could be a sign of potential network traffic issues. I'm also guessing that seeing a timeout for a sufficiently long period of time would also indicate that the same network conditions causing the timeout of the link would cause issues with the MRX/MWX functions. Are these true statements? 
6
Do-more CPUs and Do-more Designer Software / Re: IO Reinitialization
« Last post by BobO on December 05, 2022, 02:13:18 PM »
That is very interesting. I see 15 TCP sessions suddenly get closed, but you said .ActiveSessions was 0. That shouldn't be.
7
Do-more CPUs and Do-more Designer Software / Re: Vertical Red/Blue Lines in Trend View
« Last post by franji1 on December 05, 2022, 02:10:05 PM »
To see Comm Link log details, open up the Link Info dialog either by clicking on the Link name in the Status Bar or under PLC->Link Info menu item.

8
Do-more CPUs and Do-more Designer Software / Re: Vertical Red/Blue Lines in Trend View
« Last post by franji1 on December 05, 2022, 01:02:05 PM »
They are Comm Link status, including status going on and off, which can happen during Program Writes, firmware updates, changes to the System/Memory Configuration.

Blue:
Link Error CLEARED
Link UNPAUSED (after editing a Comm Link)
Link ACTIVE (check/uncheck Link Active in Link Editor)
Status ON

Yellow:
Status OFF

Red:
Link INACTIVE
Link PAUSED (editing Comm Link)
Link ERROR (comm error)
9
Do-more CPUs and Do-more Designer Software / Re: IO Reinitialization
« Last post by ryanastiefes on December 05, 2022, 12:17:22 PM »
BobO,
I have a Wireshark trace that I emailed you.
The Wireshark capture's both TCP port 502 and UDP port 28784.
Note that towards the end of the capture I Re-Initialize I/O in order to bring Modbus Comms back up.
10
Do-more CPUs and Do-more Designer Software / Vertical Red/Blue Lines in Trend View
« Last post by RBPLC on December 05, 2022, 11:21:24 AM »
What do the vertical red/blue lines in a trend view mean? For a while, I've assumed that these indicated comms issues between the PC running DmD and the PLC. I'm seeing these now in a trend view where I suspect comms to be good between the PC and the PLC but all values shown on the trend view are coming from remote Modbus devices and I'm getting periodic MRX/MWX failures. I believe the network infrastructure from the PLC to the Modbus devices to be less than ideal.   
Pages: [1] 2 3 ... 10