I'm confused about what you're trying to do here. You have a data tag called AAL10516 but it appears that you're trying to map a tag with the same name to it? You have the Source set to PLC10 which would be an external device, so the text in the source field should be in the address format of that device. What you have there doesn't look like an Allen-Bradley PLC address to me.
The driver type is Allen-Bradley Native Tag Addressing, the tags names are the same in the PLC and it is working on their existing Crimson 3.1 application and it gives the same error message.
Just wondering why it tells me I'm not linking the Crimson Flag tag to a Bit/Bool in the PLC when I am? Maybe it's looking at the address and thinks "FSL40020" is not a bit type address. So when you work with a PLC that can use tags you get this error?
It is kind of odd that I have to create the PLC tag or address when I link it. Is there no setting to just pass it through to the PLC using the existing Crimson tag name and type?
Just a bug I guess. Working on the app again today and the same thing happens when adding a new flag tag and linking it to a bit in the PLC.
Just hope it works.
________________________________________
Lame... Ok, it looks like it just changes the icon from a Numeric tag to a Flag tag if you use a discrete source. ???
It seems the only way to tell is the error message you get when changing the source and if you create a new flag tag and look at the different options shown on the data tab. A numeric tag changed into a flag tag has the data scaling section and so on.
Now I'm not sure if I need to recreate all the flag tags that show a flag tag icon but have numeric properties.