Unable to view Citadel data, even though it is there.

[Brian_Beal]

I cannot view the traces with any method other that exporting them.  Historical and Real-time trends give an error:  Error 1.  Invalid Data Type to Trend.  The traces don't graph in MAX, but I don't get an error.  I recently upgraded to version 8.2.1.  This is an XP system.  I detached and reattached the database.  I registered the computer with the database.  I can't think of what else to do.  Help!

[Coal_Man]

Brian,

How are you storing the data to the Citadel database?  Are you using the DSC Write Trace VI or are you enabling logging on your shared variables?  Either way, what type of data is being stored into the database?  Doubles, strings, U8s?

Secondly, what type of data are you attempting to read from the database?  Also, how and to what are you exporting the traces? 

If we know what type of data is being stored and what type you are expecting to receive from the trace, that would be helpful.

[Brian_Beal]

I have opened a support request for this, but I will explain more here.  It is related to one library, which was created before I did the upgrade.  Data is not being logged.  The data in the text files is old.  I can create a new library and shared variable and have it bound to the same OPC item, and that works fine.  I am using the logging option in the shared variable properties.

So, the bottom line is it is not a general problem with the DSC module, but with a specific library, or maybe just a few of the variables.  I need to see if recently added variables are getting logged.

[Coal_Man]

Hi Brian,

I talked with Adnan about this issue since you spoke with him.  We are going to escalate the issue and see if R&D has any insight to the problem.

[Brian_Beal]

I got it working.  I had to change the numeric type from single to double.   When it was single, I also couldn't configure alarms(other than status) or scaling.

I should start another thread but I have one more question.  Can I bind the alarm setpoints to a shared variable?

[Coal_Man]

Brian,

While there is no way to actually bind the level of your alarm to a shared variable, you can change the level programatically.

The first way to do so would be to create a value change event on the variable that is storing the alarm levels.  When this event occurs, you can then write the alarm level into a property node that references the variable that the alarm is enabled on.  Thus the alarm level will change whenever the level variable is changed.

The second way would be to compare the two shared variables and set a user alarm instead of an alarm on the variable itself.  I hope this helps.