dua anjing

Some HMI's are capable of "backfilling" their trend data (I believe Citect is capable, ClearSCADA is another that can backfill but i think it is protocol dependant ie DNP3 is capable but I don't know about others) try checking with supplier of the particular HMI that you intend to use. What you are describibng is something that is reasonable popular amongst RTU's where the data is stored locally and retrieved infrequently. Yo may need to get creatinve in the search terms you are usning. Maybe there is a way in Panelview that you can put your data into it's (panelviews) trend file via a backdoor

It also needs to be capable of running in "spanned" or "streched" mode this is where the windows task bar run accross ALL monitors. Not all multimonitor grrphics cards can do this. According to Citect it can be done the other way but it is not very clear how to. we used NVIDIA GEFORCE 7300 SE

I use Ghost 12.0. It works fine with laptops/desktops

I THINK that the 9300, 9330 and the 9350 are OEM meters form a company called ION (formerly Power Measurement). Check their web-site I am pretty sure that they are the ION 7300, 7330 and 7350 meters if so the 7350/9350 supports metermail. Most of ION's meters will , if they have an ethernet port, have access to their parameters via tcp. Soory can't help with the price I just use 'em.. Funny thing is ION are now owned by Schneider and they are making Power Meters to sell to Siemens..strange bed-fellows ?

Muli_monitors_with_citect.zip This file is a zip file of a word document I found on Citect's web-site when I was setting a system up to work with multi-monitors maybe it will help.

I am not familiar with ver 7. But in previous versions of Citect #COM indicates that Citect cannot communicate with the IO Device. If you can communicate between your OPC server and another OPC Client as Adriel suggests and it is OK. Then check the Citect.ini parameters related to OPC. I 'm sorry this is a bit vague but I havn't used version 7 and I believe that it is very different (as far as OPC is concerned) to previous versions. We have a large project in version 6.1, intially we had #COM errors displayed but we found that if we changed some INI settings we could get the system to respond. These settings are below [OPC] FailOnBadData=0 FailOnUncertain=0 GoOfflineForBadTag=0 CAUTION !!! As I said earlier these settings worked for OUR project in version 6.1. They may not even be available (or may not be required) in version 7.

I copied this snippet from your original code.. FUNCTION Tryckrulle1() THIS LINE IS THE BEGINNING OF THE FUNCTION. SOMEWHERE ELSE IN YOUR PROJECT THIS FUNCTION WILL BE CALLED. TRY SEARCHING FOR "Tryckrulle1()" . ONCE THIS FUNCTION HAS BEEN CALLED IT WILL RUN ONCE ONLY. Minvärde_Old = LS_sw_press_roll_1_min; //Läser in "gamla" Minvärdet. Maxvärde_Old = LS_sw_press_roll_1_max; //Läser in "gamla" Maxvärdet. Nollvärde_Old = strToInt(Z_pressure_roll_1); //Läser in "gamla" Nollvärdet. Börvärde_Old = SP_pressure_roll_1; //Läser in "gamla" Nollvärdet. Maxvärde_Temp = Maxvärde_Old - Nollvärde_Old; //Beräknar skillnad mellan 0 och Max. Minvärde_Temp = Nollvärde_Old - Minvärde_Old; //Beräknar skillnad mellan Min och 0. Nollvärde_New = PV_pressure_roll_1; //Läser in nya 0-värde från ÄR-värdet. Maxvärde_New = Maxvärde_Temp + Nollvärde_New; //Beräknar nya Maxvärdet LS_sw_press_roll_1_max = Maxvärde_New; //Läser ut det nya Maxvärdet till PLCn. Minvärde_New = Nollvärde_New - Minvärde_Temp; //Beräknar nya Minvärdet LS_sw_press_roll_1_min = Minvärde_New; //Läser ut det nya Minvärdet till PLCn. // Börvärde_New = Börvärde_Old + (Nollvärde_New - Nollvärde_Old);//Beräknar nya Börvärdet // SP_pressure_roll_1 = Börvärde_New; //Läser ut det nya Börvärdet till PLCn. Z_pressure_roll_1 = IntToStr(Nollvärde_New); Status = 0; DevFirst(hRiktverk); THE DEVICE HAS BEEN OPENED ELSEWHERE ,LOOK FOR "DevOpen(hRiktverk)" .THIS LINE ENSURES THAT WE ARE AT THE FIRST RECORD IN THE DEVICE WHILE Status = 0 DO Recept_Börvärde_Old = strToInt(DevGetField(hRiktverk, "U")); Recept_Börvärde_New = Recept_Börvärde_Old + (Nollvärde_New - Nollvärde_Old); DevSetField(hRiktverk, "U", IntToStr(Recept_Börvärde_New)); Status = DevNext(hRiktverk); ONLY WHEN WE HAVE REACHED THE LAST RECORD WILL Status <> 0 THEN WE WILL JUMP OUT OF THE LOOP END END THIS LINE IS THE END OF THE FUNCTION. ANYTHING BELOW HERE IS MOST LIKELY ANOTHER FUNCTION AND WILL ONLY BE EXCUTED WHEN THAT FUNCTION IS CALLED . I hope this explains some of what your are looking for. I have had a quick look thru your code. If you have access to Citect's Example project have a look thru their recipe demonstartion it uses similar cicode to what you have posted here . If your English is good it may help .

Somewhere in your 11 pages there will be a DevOpen() this function opens a Citect device that you should be able to find in the Project Editor. The DevOpen will have a returned a handle for this device this handle is stored in hRiktverk. DevNext(hRiktverk) will step to next record in the Device. if it is successful it will return a 0 into the variable Status and will therefore remain in the loop. If it is not successfull it will return an error number and this will drop the code out of the loop. Most likely cause for it to be unsuccessful is that it reaches the end of the device BUT there could be other reasons. have a look through Citec's documentaion on error numbers.

Have you tried using Tools, Goto Object in the drawing editor ? I think you can set up your hardware alarms just like any other category , ie you can display them on your alarm summary page, can't remeber exactly how so you may need to read up on it. Hopefully you can set up the summary to display the pagename that triggers the alarm. If not go thru your pages when project is running and determine which page(s) cause the hardware alarm this should give you a hint as to where to look. If you can norrow it down to a page the create a copy of that page. You can then puul the page apart without worrying about destroying a required page.

Good Morning All. I am currently working on adding a UPS to our SCADA system. SCADA is Citect and UPS is EATON Powerware. I am using SNMP protocol and have managed to successfully access most of the data available from UPS. The problem I have is in accessing Alarm data. According to UPS manufacturer (and Citect) the Alarm data is stored in a table, if there are no Alarms present then this table doesn't exist however when an alarm becomes active then the UPS creates this table and puts current Alarm data into it. I can access the "Number of Alarms Active" and can read the number of current Alarms. My problem is that even if I have Alarms present I cannot read the table to display any data. Anyone have any experience with SNMP ? Or possibly an example of how to format this Alarm table so that it can be displayed by SCADA (even if SCADA not Citect maybe enough of a clue to help). Thanks.

try "Ed for Windows" it's a programming editor which supports colour syntax highlighting, back before Citect v5 , Citect themselves recommended using "Ed" for exactly that reason. I think the company is called "Soft as it gets"

Search Citect on-line Help for a function called "LoginForm()" This function will display apop-up that will allow a user to enter their name and password. It will return a 0 if login is OK.

I'm with TW Controls my current laptop doesn't have a serial port. I use a Belkin usb to serial adapter , it's actually called a PDA adapter. It works fine with RSLinx. The only issue that I have is that I cannot "talk" to SLC 503 series using a PIC.

I noticed Open Office in the list but I also have PortableOpenOffice runs from a usb stick and dosen't need to be installed I find it incredibly useful actually had it given to me by another programmer but if you search for "PortableOpenOffice" you should be able to find it..

You could do it in excel. Let's say that you already have the instantaneous value display in a spreadsheet . You would need to write some code (Visual basic) that would move that value to another location at a regular time interval, next time interval repeat the process , putting the data into the "next" cell. Over time you will have lots of cells with "snapshots" of the data. The problem is though, you need to make sure that excell (or whatever you choose) is running all the time.. thats where going to a commercial datalogger starts to make sense.