NI Home
Cart Cart | Help
Hello Events Academic NI Developer Zone Support Solutions Products & Services Contact NI MyNI
You are here: 
NI Home > NI Developer Zone > NI Discussion Forums


Reply
Member
SCADADog
Posts: 10
0 Kudos

Modbus Logical Data Member Status Not Logging

I am using several Modbus objects and have setup aliases for all of the Native Members that are being used.  For each alias, I checked the "Log to historical database" box.  None of the members/aliases that have not been setup as Alarm Conditions (i.e. checking "Generate logical alarm" box) seem to be logging to the database.  When I print Alarms and Events ot Event only reports, none of the non alarm events, other than button presses and Edit Mode On/Off events are in the reports.  What am I doing wrong?

Member
Bob_L
Posts: 35
0 Kudos

Re: Modbus Logical Data Member Status Not Logging

There are 2 databases. Alarms & Events are logged to Alarm/Event database.

 

The Modbus objects that you "Log to historical database" are logged as traces and saved in the citadel database. As logical members they will be logged as 1's or 0's. This data can be viewed with Measurement and Automation (MAX) or within Lookout using hypertrend objects.

 

Regards

Member
Jim_Besselman
Posts: 39
0 Kudos

Re: Modbus Logical Data Member Status Not Logging

It sounds like you want to use the "Event" object located in the Logger Folder. This will allow to to use the modbus alias as a trigger to record a non-alarm event to the event logger. When you check "Log to Historical Database" the Modbus item is logged as a trace to Citadel. 

By using this web site, you accept the Terms of Use for this web site. Please read these Terms of Use carefully before using any part of this site. Please go here for information on ni.com's copyright infringement policy.
My Profile | Privacy | Legal | Contact NI © 2011 National Instruments Corporation. All rights reserved.    |    E-Mail this Page E-Mail this Page