topic Re: CVT Client Communication (CCC) in Components

CVT Client Communication (CCC)

Doug_S — Thu, 20 Sep 2007 16:20:51 GMT

Post your questions or feedback on the CVT Client Communication (CCC) component here.

Re: CVT Client Communication (CCC)

JanJacob — Fri, 05 Jun 2009 11:56:59 GMT

Hi,

when running the MC Tank Demo HMI NavigationEngine Example, which uses the CCC I get the following error-message on the client side:

"Error -8701 occurred at CVT_Bool_TagList: Tag is not initialized.

This error code is undefined. No one has provided a description for this code, or you might have wired a number that is not an error code to the error code input."

Any ideas what's going wrong???

Kind Regards

Jan

Re: CVT Client Communication (CCC)

Christian_L — Fri, 05 Jun 2009 14:50:04 GMT

Jan,

Can you be more specific where this error is generated. This error is coming from the CVT (Current Value Table) and indicates that somewhere the application is trying to read or write a tag in the CVT which has not been initialized. (The CVT is used inside the CCC as well as the TAE and other VIs in this example.) All of the CVT tags are initialized in the main VI based on a list of tags read from the configuration file.

Can you dig into the VI a bit more and find where specifically the error is generated and what the name of the tag is that the application is trying to read?

One of the changes we are planning for the CVT to be published in a couple of months is to provide more detailed error information which will identify the missing tag name in this type of situation.

Re: CVT Client Communication (CCC)

JanJacob — Fri, 05 Jun 2009 17:41:25 GMT

Hi Christian,

Thank you for the quick reply. The error occurs within the CCC VI for reading tags on the client side when it tries to read the status of the heater in that example. I probed the Name of the Tag inside the CCC VI and inside the CVT_Binary_Tag_List.vi. Interestingly on some occasions the CCC side probe says "Heater Switch" while the CVT side, which receives this value, delivers only "Heater" in the probe... This creates the error. Some kind of strange...

Kind Regards,

Jan

Re: CVT Client Communication (CCC)

paperduck — Fri, 12 Jun 2009 16:10:31 GMT

Hi,

I'm using the CVT to read from Compact RIO modules and it works really well. However, I have not been successful writing to the output module. I suspect I'm making a simple mistake. Just to let you know, I have configured the AO-00 tags on both host and target in the tag editor to write and the AI-00 tags on host and target to read. Can someone spot my mistake and tell me what it is?

Here is a snippet of the code on the target:

I am using CVT double read on port AI0 to put the data into the tag AI-00. And CVT double write on AO0 from tag AO-00.

On the Host VI, I've got this:

CVT double read from CVT tag AI-00 to a double field on the front panel (numeric). CVT double write from double field on the front panel (numeric3) to the CVT tag AO-00.

Again, reading from AI works, writing to AO does not and I have configured the AO-00 tags on both host and target in the tag editor to write and the AI-00 tags on host and target to read. How can 1 work and not the other?

Re: CVT Client Communication (CCC) ERROR on CRIO plus TPC-2106T

ingpconci — Fri, 05 Mar 2010 10:20:54 GMT

I've tried to implement the architecture from the Sample Referecence Application: PackML MAchine control Reference Application.

I have got these system:

CRIO 9074

TPC-2106T

LabVIEW 2009 with RT,TOUCH and FPGA extension

The application don't work because there are problem with CCC library.

the communication work fine from TPC to cRIO ( write TAG) but it is impossible to read TAGS from CRIO

The TAG is configured in this fragment:

<hmi>
  <Name>TPC-2106T</Name>
  <Description></Description>
  <TagFolder>
    <Name>Machine Status</Name>
    <Description></Description>
    <NetworkTag>
      <Name>TemperatureSolution</Name>
      <Description></Description>
      <DataType>Float (Double)</DataType>
      <Default>0.000000</Default>
      <Log>False</Log>
      <BindToTag>CRIO-9074\Machine Status\TemperatureSolution</BindToTag>
      <ReadTWriteF>True</ReadTWriteF>
    </NetworkTag>
   </TagFolder>
</hmi>

The controller section in the xml file is:

<controller>
  <Name>CRIO-9074</Name>
  <Description></Description>
  <TagFolder>
    <Name>Machine Status</Name>
    <Description></Description>
    <LocalTag>
      <Name>TemperatureSolution</Name>
      <Description></Description>
      <DataType>Float (Double)</DataType>
      <Default>0.000000</Default>
      <Log>False</Log>
    </LocalTag>
  </TagFolder>
</controller>

The problem is in the block CCCRead.

To verify the mechanism I tried to remove the block CCCWrite and the TAG in write mode didn't work.

I've tried to debug the application in TPC windows CE but the data read is alway null

Regards

Paolo

Re: CVT Client Communication (CCC) ERROR on CRIO plus TPC-2106T

paperduck — Fri, 05 Mar 2010 15:42:38 GMT

Hey ingpconci,

This sounds like the tags aren't configured properly. Download the tag configuration editor (TCE), open your tag configuration file and view your tag's properties on there. You must have an HMI version on the local PC, and a target version on the RIO side (separately saved in the TCE). Verify all the tag properties. Make sure you configure the tag with read for tags you will be reading from the target and write for tags you will be sending to the target.

Let me know if this helps,

Message Edited by paperduck on 03-05-2010 09:42 AM

Re: CVT Client Communication (CCC)

StevePVI — Wed, 10 Mar 2010 13:58:24 GMT

Hi Christian,

I had to modify the CCC Client Write.vi and CCC Client Read.vi to allow for a "forced init." The way was it was written it only initialized (sent the controller the list of indices) on first call. I allow for the controller to disconnect and reconnect while the HMI code stays running. So when the HMI reconnected with the cRIO it would not resend the list of indices.

Here is a screen shot of the change I made.

Regards,

Steve

Re: CVT Client Communication (CCC) ERROR on CRIO plus TPC-2106T

ingpconci — Wed, 10 Mar 2010 14:08:34 GMT

Hi PD

I've installed the TCE and I've verified the xml and I copied the file on Touch Panel and on cRIO 9074 but the problem persist.

So I leaved this framework for a simple implementation with network shared variable because I have to develop the prototype in some days.

I like the CCC architecture but in my opinion there is some problem on the pocket pc 5 platform for the HMI host.

Thanks

Re: CVT Client Communication (CCC)

rwunderl — Fri, 26 Aug 2011 18:51:01 GMT

I had to make the same modification as StevePVI did above, as I stated in the CVT forum post, but for different reasons. I was leaving the server running and restarting the CCC Client with a different set of tags (a different section of the Tag Configuration). This required a reinitialization of the CCC Client so that it would send all of the data properly. This change should definitely be implemented in any future revision.

Re: CVT Client Communication (CCC)

rwunderl — Wed, 07 Sep 2011 20:41:34 GMT

Another change I had to make to the CCC functionality was to the CCC Server (ccc_Server.vi) that runs on the cRIO system. When opening the TCP connection, you need to set the input "resolve remote address (T)" to False. There's no benefit to setting it to True that I have ever found, and if you try to connect directly to the cRIO (without going through an intermediate network), the system hangs for about 10 seconds or so until the request for address resolution times out. In the meantime, your app has probably given up internally and thrown an error or an impatient user has already Ctrl-Alt-Deleted and ended the program on the PC-side. Either way, it's no good.

This is a problem that I have encountered many times when developing TCP applications for the cRIO where you need the cRIO app to work both on a network and when connected directly to a computer.

So set resolve remote address to False, and the TCP connection can be made even when connecting directly to the cRIO. This is a nasty bug since you might not notice it until after you deploy your system for the first time.

Re: CVT Client Communication (CCC)

Branch_Support-NIC — Fri, 30 Nov 2012 23:25:16 GMT

Noticed a weird bug I received from some code.

The attached project uses a Status Tag4.xml for the Tag set. There is a unbound network tag under the HMI called tag.

Anyway if I don't watch for errors the CCC Client Write vi reports the error only once and the subsequent iterations return no errors. Of course the work around in watch for errors but it was quite hidden. This also affects data from being sent from the client to the server (using Sup Write to turn on ProcRead). Data sent from Server to Client works fine.

Thanks,
Kyle Hartley

Re: CVT Client Communication (CCC)

Etarkleson — Wed, 08 Jan 2014 18:18:20 GMT

Hello,

I am having issues with my CCC implementation. Here is the background

CRIO+EtherCAT+Desktop computer.

CRIO in hybrid mode

using CCC, CVT (vs3, modified), AMC, STM, etc. Pretty much the CRIO reference architecture.

I have no problems writing or reading tags on the CRIO but when I began to implement my engine on my HMI computer I am running into this error...

Error 537164 occurred at Group Memory.vi

Possible reason(s):

A group was not found in the CVT.
Group 'CCC_Client Write Group_169.254.181.155:54444'

First off, I am not using any groups right now, but I am wondering if this has something to do with connecting to the server? I see where the error is getting generated but since the CCC doesnt appear to use groups when updating the CVT across the network Im not sure what this error means.

Has anyone seen this error before? I have included my "connection manager" for the HMI side that inits the tags and refreshes the table.

Re: CVT Client Communication (CCC)

paperduck — Wed, 08 Jan 2014 18:25:59 GMT

Etarkleson,

I don't recall that particular error but have you defined the variables you are using with the appropriate read/write permissions on *both* the cRIO and the HMI computer?

Re: CVT Client Communication (CCC)

Etarkleson — Wed, 08 Jan 2014 18:33:57 GMT

Hello paperduck, thanks for the quick response.

I think I am properly defining the read write permissions on the HMI here. the direction should define whether it is "read from RT" or "Write to HMI". However I am not sure about this on the RT side. I thought there were no read write permissions on the server side.

What to you think?

Re: CVT Client Communication (CCC)

Etarkleson — Wed, 08 Jan 2014 18:39:41 GMT

Here is the same section on the server side. When you set up and define the tags properties there is no direction as far as I can see.

Also for clarity in this post and the last one the section of code I am referring to is the for loops where tag information is split from the tag editor file and built into the proper cluster for CCC and CVT.

Eric

Re: CVT Client Communication (CCC)

CMal — Wed, 08 Jan 2014 19:18:09 GMT

Etarkleson,

The CCC uses groups to access the CVT more efficiently. The group name in the error message refers to the group on the client side that contains the tags sent from client to server. The group name contains the server's IP address and the remote port it uses, so make sure "169.254.181.155" is the correct IP address of the server. Would you consider sharing the file that gets read by "Init Tags HMI.vi"? I can take a look at the tags to see if I get the same error with them. Can you identify when the error happens? For example, is it happening when you first call Client Init.vi, or is it inside the loop when you call Client Synchronize Data.vi, and which iteration?

You also mentioned that you are using a modified version of the CVT. Can you elaborate on the modifications you made and which CVT version you started with? Also, which version of CCC are you using?

Chris M

Re: CVT Client Communication (CCC)

Etarkleson — Wed, 08 Jan 2014 20:03:51 GMT

Thanks Cmal,

"so make sure "169.254.181.155" is the correct IP address of the server."

Yes I have drilled in and see that the FG Client Configurations.vi reads the server ID and if the variant is empty fills it up with the correct group names. Do I have to set up or init these groups somewhere? I dont see where that happens so I am starting to think this is why. However even after the first pass through on this VI it seems that the variant stays empty. Since its an FG its a little hard to troubleshoot since I dont know what VI is writing to it.

"Would you consider sharing the file that gets read by "Init Tags HMI.vi"?"

I have included the binary file I read the tags from. I will also include the tag editor that I use to write the file.

"Can you identify when the error happens?"

The error happens after everything is init'd and starts refreshing the CCC, Both the CCC Client Read and Write VIs throw the error because the groups dont seem to have ever been set up. Where would the groups be set up at? I cant find anywhere this happens. It will throw the error everytime. I also have used the client synchronize data.vi and it behaves the same.

So I guess I could write a VI that goes after the Init CCC and reads through the tags again to create the two groups, or maybe I should put it in the init tags HMI.vi... I suppose I just dont fully understand whats happening under the hood yet.

"You also mentioned that you are using a modified version of the CVT"

I guess I should say I rewrote a tag editor since it wasnt available for the new CVT 3.0, instead of modifying the CCC I am only using the old supported datatypes and am using the "information" column to share scaling information and write new tags for each scaled value.

I am using CCC 3.0.0.3, CVT 3.3.0.13

Re: CVT Client Communication (CCC)

Etarkleson — Wed, 08 Jan 2014 20:05:01 GMT

Here are the tag files. I couldnt directly attach them since they dont have a proper file extension.

Re: CVT Client Communication (CCC)

Etarkleson — Wed, 08 Jan 2014 20:27:44 GMT

Ok, I was able to manually create the groups and get the error to go away. I am not 100% sure everything is working perfect but now I move forward.

Thanks for helping me work through this.

Eric