Just updating this thread with the solution.

Turns out that it was a firmware issue. Beijer supplied me with an updated Runtime for the T12C. After updating the runtime, everything started working as expected.

It's a bit of a stretch, but could this problem be OS related? Is it possible to refresh/reload the Win7 OS in the field? Or does the unit need to be returned to Beijer?

I'm not certain if it's Win 7 or Win embedded.

I am connecting to a Panasonic FP-X PLC via RS-232. Communications appears to be successful, as I do not have any error messages. I am able to get the T12C to read the status of I/O and data registers. The button tags on the screen do not seem to be working. I've used the touch interface as well as ...

Just an update for anyone interested: Found the problem. The Modbus register bit in the Yaskawa machine controller had somehow been set to TRUE and got stuck in that condition. Interestingly, the condition persisted even after re-downloading the program in the Yaskawa and the Beijer T10A. I'm not su...

I have a machine in a remote location that is behaving strangely. Basically, the machine cycle is starting before the operator pushes the "start cycle" tag. I have the tag disabled until certain parameters are satisfied, but the cycle seems to start at the very instant the parameters come within tol...

Thanks Mark.

I will give this a try.

FWIW, I am using the Matsushita/MEWTOCOL driver.

I was just wondering if this is possible. If so, I could use some direction in setting this up. I use T7A/T10A screens with Panasonic PLC's. The PLC connects to the HMI via RS-232 through the COM1 port, typically at around 38,400 baud, but I'm flexible. I use an ethernet cable for programming the Tx...

Well, it turns out that it wasn't the CPU, which peaks at about 60% and idles at around 25%. However, I think I have found the root cause of the problems. It doesn't seem to be programming related at all. Just a noise issue on the cabling. Because COM3 and COM4 share a common connector, I used a sin...

Thanks, I'll try the CPU system tag and see if that's the issue. I've used this basic setup on another machine, but didn't have any issues. Difference was that machine only had 1 temperature loop to monitor versus 12 on my current project.

Thanks Mark. The scripting worked out really well. It turns out that Data Exchange is probably not the culprit here. Even after elimininating DE, I was still having a lot of Comm errors in my "real" program, not the barebones one I created for testing purposes. I played around with baud rates, but t...