EZTouch panel

[DLTimmons]

HAs any one connect an EZTouch to a Do-More? Any pointers?

[BobO]

I assume it will be using DL protocols like KSequence. Just remember that all such comms go to DLX, DLY, DLC, and DLV...rather than X, Y, C, and V...and that if asked, a Do-more CPU will respond that it is actually a DL260. Other than that, it should just work.

[DLTimmons]

I must be doing something wrong when I try to export the tag data base to a cvs file the file does not contain the DLC or DLV that I created.

[b_carlton]

DLX, DLY, DLC, and DLV are the names for these areas as seen by the Do-More system. An external access (like from your EZ-Touch) will see them as just X, Y, C and V. It won't even know anything else exists.

[BobO]

As Bernie said, when you write to C memory from the EZTouch, it will show up in DLC in Do-more, rather than Do-more's C memory.

[DLTimmons]

Ok I can be a little slow Kept looking for the DL in the out put file.

Thanks

[BobO]

Ok I can be a little slow Kept looking for the DL in the out put file.

We're handling it in a somewhat unusual way and you're not the first to get tripped up. There are many reasons for doing it this way, but the two biggest are 1) DL and Modbus protocols are not secure, so we wanted to limit the access through them to quarantined memories, and 2) to simplify addressing, since Do-more memories are all decimal addressing and DL is octal, and to make Modbus addressing much easier than traditional maps.

It requires us to educate folks, but the benefit of doing it this way far exceeds the pain.

[DLTimmons]

I'm get A protocol error on the touch screen while using the K-sequence Rev H

[BobO]

I'm get A protocol error on the touch screen while using the K-sequence Rev H

I'll probably need a bit more to go on...but...one possibility is that the EZTouch is attempting to read some values in areas of memory that are above the default sizes of the DL blocks. You can increase the size of those blocks in the Memory Configuration.

Not sure what it is reading, but I'm speculating that it is accessing the area between V7400 and V7777.

[DLTimmons]

Right now I looking a 16 inputs x0-x15 mover to DLX0-DLX7 and DLX10-DLX17 and one c bit C0 to DLC0

I increase the v block to 8000 still getting the protocol error on the screen

Tried taking all the mover commands out and still getting the same error

[BobO]

I increase the v block to 8000 still getting the protocol error on the screen

Did you mean DLV?

[DLTimmons]

I did the V to 8000 Just now took the DLV to 8000 same thing

[DLTimmons]

Found it port settting on th eserial port