AdvancedHMI Software

General Category => Support Questions => Topic started by: astroman on January 28, 2015, 05:49:56 PM

Title: EthernetIPforCLXCom1 "Invalid Tag"
Post by: astroman on January 28, 2015, 05:49:56 PM
Hi Archie (and everyone). I've just begun a project in 3.97e using the EthernetIPforCLXCom1 driver, but suddenly my components are showing an "Invalid Tag" error. I'm using the format Program:MainProgram.On_Off_Pump
I've tried the tag in v3.97d, and everything is fine. Has there been a change to the tag structure? Thank you!
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: Archie on January 28, 2015, 09:32:20 PM
There was a change to fix a problem of UDT arrays not working. That change could have created the problem you are having. I will check into it.

Do Controller scope tags work?
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: Archie on January 28, 2015, 09:46:32 PM
It was a problem created when using program scope tags.

- Download and extract the attached patch
- Replace the file in \AdvancedHMIDrivers\Support
- Open the project in VS
- Clean All
- Rebuild All


PATCH REMOVED - See update below
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: jsorah on January 29, 2015, 09:08:01 AM
Applied the patched dll and I am still getting the same error as before, but the packets no longer display as malformed in wireshark.
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: Archie on January 29, 2015, 01:55:06 PM
I was able to test this and found the problem. Try this patch to see if it works
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: jsorah on January 29, 2015, 02:04:10 PM
The most recent patch appears to have resolved the problem, thanks Archie.
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: astroman on January 31, 2015, 08:58:39 AM
That did it. Thank you very much Archie.
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: Darrell on February 01, 2015, 09:02:33 PM
Since updating my HMI from 97D to 97e my buttons and indicator on a control Logix driver get this error , and no longer work , tried adding you patch and I still have the error.

The particular item referenced (usually instance) could not be found
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: Archie on February 01, 2015, 09:20:17 PM
Since updating my HMI from 97D to 97e my buttons and indicator on a control Logix driver get this error , and no longer work , tried adding you patch and I still have the error.

The particular item referenced (usually instance) could not be found
Are you using Program Scope tags?
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: Darrell on February 01, 2015, 10:21:10 PM
all controller tags  , base tags , bool
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: Darrell on February 02, 2015, 10:43:01 PM
Also noticed in 3.97D it will not let you force a value into a timer preset , DINT , I will try adding the patch to 3.97e to see if it cures  the above problem.

Darrell
Sorry
My mistake value was being over written somewhere else
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: Archie on February 03, 2015, 08:04:38 PM
Since updating my HMI from 97D to 97e my buttons and indicator on a control Logix driver get this error , and no longer work , tried adding you patch and I still have the error.

The particular item referenced (usually instance) could not be found
I added a BasicButton and set PLCAddressClick to a controller scope Bool, then set OutputType to Toggle. I also added a BasicIndicator and set PLCAddressSelectColor2 to the same bit. It worked as expected for me.

Am I testing the same way?
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: Randy on February 05, 2015, 06:27:36 PM
I am porting a project from 3.70 to 3.97e
I have downloaded and installed the latest dll above but still have a problem.

I have a UDT name HMI with a REAL[800]

With version 3.70 I could read the entire array

With version 3.97e I can only read the first 65 elements.

Below is code.  Click the button until N = 66



 Public C As New AdvancedHMIDrivers.EthernetIPforCLXCom

    Private Sub Button1_Click(sender As System.Object, e As System.EventArgs) Handles Button1.Click

        Static N As Integer = 60

        If C.IPAddress <> "192.168.1.6" Then
            C.DisableSubscriptions = True
            C.IPAddress = "192.168.1.6"
        End If

        Dim Tag1 = "HMI.REAL[0]"

        Dim S() As String = C.Read(Tag1, N)
        MsgBox(N & "  " & S(N - 1))
        N += 1
    End Sub

Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: Randy on February 05, 2015, 06:47:28 PM
I also found I had version 2.94.  It has the same problem of not being able to read more than 65 elements of an array as 2.97e
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: Darrell on February 07, 2015, 11:31:40 PM
has the patch been added to 3.97e the posted version for download , I may be  adding the patch incorrectly and the maybe part of my problem in my post listed above.

Darrell
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: nickbri on March 28, 2015, 03:36:55 PM
I'm having the same issue with the "invalid tag" using program scope tags when trying to use v3.98c. Controller scope tags work just fine. Format is correct, it worked in earlier versions v3.84 for example.

I've tried the patch from above, it does not work and instead gives a new error. I have to put the old .DDL file back in to get the project to load at all. Any Advice?
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: Archie on March 28, 2015, 04:12:33 PM
What are you using in for PLCAddress?
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: Archie on March 28, 2015, 05:35:00 PM
Try this patch for 3.98c
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: Darrell on March 31, 2015, 09:14:55 AM
This patch seemed to have cured a few problems
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: Archie on March 31, 2015, 12:40:00 PM
The latest version of 3.98d should fix all of these issues
Title: Re: EthernetIPforCLXCom1 "Invalid Tag"
Post by: nickbri on April 01, 2015, 07:30:59 AM
The patch fixed all the issues with the program scope tags, working well now. Thanks!