Host Engineering Forum

General Category => Do-more CPUs and Do-more Designer Software => Topic started by: mhw on March 10, 2016, 03:12:37 PM

Title: Operation time out
Post by: mhw on March 10, 2016, 03:12:37 PM
I have a domore reading and writing to two Ethernet clicks. I keep having time outs with them. Each one is setup as a separate device. I have put the timeout to 500ms and it still throws an error. There are no exception responses. Any ideas on how I should troubleshoot this problem?
Title: Re: Operation time out
Post by: franji1 on March 10, 2016, 03:18:54 PM
Make sure the Ethernet Ports for the Do-more and all your Clicks are configured properly:
They all have the same subnet mask, and on the same subnet itself, no duplicates
(e.g. all are 192.168.x.x w/subnet 255.255.0.0, and all the x.x values are unique across ALL TCP/IP devices not just PLCs (no network printer, etc.))
Title: Re: Operation time out
Post by: BobO on March 10, 2016, 04:52:41 PM
I have a domore reading and writing to two Ethernet clicks. I keep having time outs with them. Each one is setup as a separate device. I have put the timeout to 500ms and it still throws an error. There are no exception responses. Any ideas on how I should troubleshoot this problem?

The easiest solution I could come up with is to replace the Clicks with other Do-mores. ;)
Title: Re: Operation time out
Post by: mhw on March 10, 2016, 04:59:25 PM
I do not see any address conflicts but I do not see any errors when I am not connected to the office LAN.
Quote
[/
The easiest solution I could come up with is to replace the Clicks with other Do-mores. Winkquote]
This would not of been necessary if the T1H had serial options.
Title: Re: Operation time out
Post by: MikeS on March 11, 2016, 08:37:43 AM
how often are you executing the MRX instructions? could it be that you are getting into a mode where the Click is replying to one request when you are sending it another one ?
Title: Re: Operation time out
Post by: mhw on March 11, 2016, 09:17:36 AM
I am hitting them as fast as I can.
I disconnected a wireless router that was connected to the network. The errors stopped after disconnecting it.