Custom Device Glyph Issue

[MileP]

As per the file "Building Custom Devices for NI VeriStand 2010.pdf" page 13, "default fpga category.png" results in "folder" symbol for sections and "default fpga channel.png" results in "dash" symbol for channels. 

I had two channels in the beginning with one input and one output, and "default fpga channel.png" worked as expected (dash symbol).

Later on, I added 1 more input channel and 2 more output channels, and used "default fgpa channel.png" in .xml file, but these newly added pages had "folder" symbol instead of "dash" symbol.

It might be a very simple issue, but i just have no idea what is wrong. Is there any GUID range for channel and section?

Thanks

[StephanieA]

MileP,

Can you post your XML file or a screenshot of the portion of code in question? It could be that it isn't quite set up correctly and viewing the XML can help me troubleshoot the issue.

I'm not sure if there a GUID range for channel and section. I'll look into that and let you know once I find out.

[MileP]

Please see the attachment zip file with xml and screenshoot from sdf.

BTW, it looks like this forum doesn't support xml format attachment.

[StephanieA]

MileP,

I took a look at the XML and everything does check out. I'm curious to know if the items that show up as folders (Connect, Command ID, Payload Address, and Serial Communication State) are they set up to be channels in the custom device? Can you map something to these items? If not, it may be the case that since they are not channels there may be some overriding feature that will cause the icon to default to the folder icon, regardless if you specify the image in the XML file.

If those items are channels, then it may be a GUI issue and I would ask that you rebuild your custom device and verify the GUID for each of the XML command packets.Let me know how it goes.

[MileP]

Stephanie,

Thank you for the reply.

Please ignore this question. I just found the cause. There is nothing wrong with Glyph. My appology. 

It was my mistake. I added those channels later but didn't generate new GUID for them. Instead, I copied section GUID from a trial version of custom device.

Since both custom device are built and exists under public data folder. VeriStand got confused.

I happened to go back to the trial version today and noticed this. What a funny mistake. I believe no one else would have this problem.

[StephanieA]

Thanks for letting me know that you figured out the problem! I'll be sure to make a note of this for others that may have the same issue.