Proper use of TCPLISTEN

[BobO]

Umm...<Big red ears> I don't remember why I did it, but I had the .Running bit for the program the the TCPLISTEN runs, inline as a NOT with the TCPLISTEN... Ooops.

I deleted it and things look much better.

Yeah...I put it the way you described. That is kinda ugly.

I wonder if the Memory Image Manager problem is getting tripped up by the same thing that locks up DataView when viewing long strings? Something in my computer maybe...

Any single element that is over 256 bytes (big strings, for instance) uses a different comm function that is optimized for long stuff. We did have a bug or two in that in some pre-release code, but looking back through the change log since DmD 1.0.2 to current, I don't find any relevant changes...which means either it ain't broke or it ain't fixed.

What port are you connected to the PLC with? Have you tried connecting through a different port, and is the result the same?

[plcnut]

I do everything over ethernet. Should I dig out my USB?

[BobO]

It's another lever to pull. I honestly don't expect it to make any difference, but it would eliminate at least one possible area of failure.

[plcnut]

I connected with USB, and so far it has been over 10 minutes, and several "communication while reading region" error messages, I click OK and it keeps going. Definitely needs a progress bar, because I'm not sure what it is actually doing. I just get the little round wait indicator that flickers...

[plcnut]

I just passed the 30 minute mark. Should it ever take this long?
(I have less than 3000 Bytes of data left in the PLC, so it is pretty full)

[BobO]

Full system took 18 seconds for me on USB.

What is your scan time? I'm guessing it is getting up there, and I'm guessing that it where some of your comm issues might be coming from...

[plcnut]

I've been real happy with scan time. Currently: Min: 2.1ms Avg:2.8 Max: 11.2ms
I have not reset it either, and have hit it pretty hard with data a couple of times today.

[BobO]

Well...that ain't it. I bumped mine to about 12ms and it went from 18 seconds to about a minute for a maxed out memory map.

It is possible that your comm server has crashed. Start Task Manager and make sure there is a process named CSMainDM.exe.

[plcnut]

I'll check in the morning.

[plcnut]

CSMainDM.exe is running, but no go on the Image.