Re: Geo SCADA Import Points

sbeadle

The CSImport spreadsheet needs the correct system name (defined in your Configure Connections tool) and a username/password of a real user. See in row 1/2 columns B to D System Username Password Local FredBloggs rafdsafdsaf Note that column A of the main table is a command, e.g. Create or Update. See the page 'Example' which shows what you put in the other columns. (The descriptions in bold are ignored as there's no command on those rows). The 'Update' command is a series of fieldname and value pairs. To get field names, use the schema browser (localhost/schema) or click the fields on object forms in ViewX.

adamwoodland

Yes, the irony, it is CAlarm. I think one of the problems is the table length is limited (a joy when writing DDKs) hence why some are C... and some are CDB...

adamwoodland

Two possible options spring to mind: 1. If using OPC, check out search keys with the tag option enabled. They provide an alternative reference for objects. Search keys are a special kinda of metadata field, and if you need some more generic way of addressing objects the standard metadata fields could be used 2. If only for alarming (i.e. for showing on the alarm banner), check out the Alarm Source field under the Alarm tab

rlao

Thanks bevan, I feared this might have been the case. Looks like I'll just have to script a user form myself

Hardin4019

I had to modify it some to get seconds since the alarm came in. The original formula was coming up with a result of / 86400 of a day as the final answer (I think). IIF ( (TIME('NOW') - ".Point.StateChangeTime")*86400 > 86400, FORMATVAL('0.# days', ((TIME('NOW')-".Point.StateChangeTime")*86400)/86400), IIF( (TIME('NOW') - ".Point.StateChangeTime")*86400 > 3600, FORMATVAL('0.# hours', ((TIME('NOW')-".Point.StateChangeTime")*86400)/3600), IIF( (TIME('NOW') - ".Point.StateChangeTime")*86400 > 60, FORMATVAL( '0.# minutes', ((TIME('NOW')-".Point.StateChangeTime")*86400)/60.0), FORMATVAL( '0.# seconds', ((TIME('NOW')-".Point.StateChangeTime")*86400)) ) ) ) I trimmed this down and made it a Minutes and Seconds count down timer, where the 1200 is a constant = 20 minutes, and in mine I am using a Variable that is the current time instead of TIME('NOW') : IIF( (1200-(TIME('NOW') - ".Point.StateChangeTime")*86400) > 60, FORMATVAL( '0.# minutes', (1200-(("...Time"-".Point.StateChangeTime")*86400))/60.0), FORMATVAL( '0 seconds', (1200-(("...Time"-".Point.StateChangeTime")*86400))) ) (Final Result) To clean it up further and prevent going less than 0 Seconds while counting down, and to prevent count down after the alarm has cleared : IIF( "Point.AlarmState" >= 2, IIF( ("...Time" - ".Point.StateChangeTime")*86400) <= 1200, IIF( (1200-("...Time" - ".Point.StateChangeTime")*86400) > 60, FORMATVAL( '0.# minutes', (1200-(("...Time"-".Point.StateChangeTime")*86400))/60.0), FORMATVAL( '0 seconds', (1200-(("...Time"-".Point.StateChangeTime")*86400))) ), '0 Seconds'), 'Not in Alarm')

sbeadle

More detail is needed on the nature of the data retrieval. The Geo SCADA ODBC Driver (the telemetry device driver, not the ODBC server) can be used in many ways to get data from a source database. However, more custom applications for data retrieval will require the Driver Dev Kit (DDK): https://tprojects.schneider-electric.com/telemetry/display/CS/Driver+Development+Kit+%28DDK%29

BevanWeiss

Does eDNA support Web Service? The last time I looked at it, eDNA had an ODBC (SQL) type of connector to it, and that was about it. If so, then you could use the ODBC Driver from Geo SCADA Export to retrieve data from eDNA. Otherwise if the EcoStruxure Web Service stuff is now available out of eDNA then you could use that (if it's available, then it's probably the best option). Configuration side in GeoSCADA Expert should be quite straight forward, how to configure this in eDNA is a different story... and you might have to beat it to death with its own shoe.

BevanWeiss

Have you read the manual? https://download.schneider-electric.com/files?p_enDocType=User+guide&p_File_Name=33002535_K01_000_15.pdf&p_Doc_Ref=33002535K01000 The link that you provide does not appear to be from a Schneider website, so I don't think you'll get much support from that. The buffer doesn't need for you to do anything special with it. Just create it of a suitable size for the delay you want to compensate for, and provide the reference for it to the IMC EFB.

BevanWeiss

@Jimi The Tune Limits is a built in capability of the SCADAPack DNP3 Points, but restricting which limits can be tuned is not. And there is not a way to restrict what the values for the tune limits can be (apart from being within Underrange/Overrange). I think what the OP is after is a way to restrict the High Tuned Limit to be within some range (such as 150-250) whilst the Low Tuned Limit could only be in another range (like 25-50).. with the Underrange and Overrange still set as required at 0 and 1000.

Johnny07

Jimi, Thanks for your additional testing and posting your results. We do some tests with the POI popup, else we need to use the right click menu. Thanks, Johnny

Online Status	Offline
Date Last Visited	Monday

Schneider Electric Exchange Community

Re: Geo SCADA Import Points

Re: ODBC/SQL to get Alarm List (Mimic Alarm Banner)

Re: Geo SCADA Dual Tag Possibilities

Re: Call built-in Interval Control as a user Pick Action

Re: Mimic Animation rudimentary alarm countdown timer

Re: Geo SCADA Web Services

Re: Geo SCADA Web Services

Re: IMC Example

Re: ClearSCADA - GeoSCADA Tune Limit function

Re: Geo Map object left mouse click

Support

FAQ

About