Topics

1

Feature Request / An option to clear strings in the CLX driver

« on: November 21, 2016, 03:54:16 AM »

Righ now, sending an empty string to the CLX results in the driver just doing nothing.
In my project I have to clear strings from time to time frequently.
As a workaround, I send a string like "empty" to let the CLX clear the Tag.

By the way.
Is there an easy way to handle UDTs? Maybe let the driver just read the number of bytes a UDT member has.
I know I can copy them into Bytearrays in the CLX and read that.
But it happens that I can't change the logic of the maschine.

2

Open Discussion / STAND-ALONE CONTROLLOGIX/COMPACTLOGIX COMMUNICATION DRIVER

« on: October 09, 2016, 12:08:21 PM »

Hello
I saw on the product page, that this driver is available for purchase.
But there is no information about it's capabillity, or any documentation.
Just one little axample.

I assume now, that this driver has similar functionality and syntax as the one bundled with newer versions of advancedHMI.
Is that true?
When buying the driver at this early stage, am I than entitled for updates?

What about PLC5 communications (through 1756 backplane i.e.)? Is there a second driver needed?

Thanks for all the support in this forum!
Thomas

3

Open Discussion / Is there a datasubscriber2 fails on >500 bytes fix?

« on: April 27, 2016, 01:13:46 PM »

I tried to read an array of 300 real values with Datasubscriber2 (CLXoverIP and 399d).
But the data received event never got fired.
I remember reading some thread here that the transfer is limited to 500 bytes (Can't find again :-().
So I set the number of elements down to 124 to test. Working. Doing 125 elements = not working.

I wonder if there is already a  fix for this.
I have to read that package of data at once for some tag update reasons.
Doing multiple reads might mess it up.

Thanks

4

Open Discussion / Problem when setting IP by code

« on: March 29, 2016, 11:22:20 AM »

Good Morning

I have a question/problem with changing the IP adress of the driver when starting an application. I am using 3.99d and EtehrnetIPforCLXcom.

To be able to have one application for different machines, I read a setup file and try to change the IP of the driver in the form.open routine.
I am using this code in a called subroutine.

 Private Sub Set_System(ByVal ID As String, Val As String) 'Use incoming values to set the system.
        If ID = UCase("IP1") Then                                              'Set SystemIP for Driver
            IP1 = Val                                                                     'Public String to use this IP on other pages too.
            EthernetIPforCLXCom2.IPAddress = IP1            'Reconfigure Driver.

As soon as I have the last shown line active, the driver won't connect to my CLX. Even overwriting the .IPaddress with its preconfigured value will stop the driver from working. I checked the string that is writen to the diver, and it is fine.
Is there something like a driver/communication restart I have to add, or is this the wrong way of doing things anyway?

Best Regards
Thomas