About RobertSanders

RobertSanders

Additional to Richard's comments, the DspAnGetPos() function returns the X and Y position of the animation point in question, relative to the top-left corner of the window (remember multiple screens can be present). Every object on a Citect page has an Animation Point and some objects can have many depending upon whether multiple objects have been grouped into a single object etc.. This function is one of the few functions within Citect that returns both X and Y positions at the same time. Example: FUNCTION AnXYPos(INT hAn) INT iXPos; INT iYpos; DspAnGetPos(hAn, iXpos, iYpos); When the function is run iXpos & iYpos will contain the X, Y coordinates to the AN passed Regards Rob

RobertSanders

You are correct with your assumption the function AlarmSetInfo will overwrite other filters set by AlarmSetInfo. Its better to use the Alarm Filter Functions The following is a copy from the help for AlarmFilterEditSet function iHndl = AlarmFilterEditOpen(iAN); iRet = AlarmFilterEditSet(iHndl,"Tag=Dig*;Category=1;Area=1;"); iRet = AlarmFilterEditAppend(iHndl, "Priority<20"); sRet = AlarmFilterEditFirst(iHndl); // Tag=Dig*; sRet = AlarmFilterEditNext(iHndl); // Category=1; sRet = AlarmFilterEditLast(iHndl); // Priority<20; sRet = AlarmFilterEditPrev(iHndl); // Area=1; iRet = AlarmFilterEditClose(iHndl); Regards Rob

RobertSanders · ‎2020-03-25

Also check the Master.dbf, which is found in the User location, it contains the project name and project location, ensure that the folder locations for each project are correct. I have attached an example screenshot. NOTE do not change the column widths Regards Rob

RobertSanders · ‎2020-03-25

Its worth double checking the Citect.ini file, In the section [CtEdit] ensure all the paths are correct, pay particular attention to Bin: folder which should point to the Citect installation folder location, it has Citect32.exe User: which has all the Citect projects, see the attached screenshot The following is a example INI setting for Citect SCADA 2018, [CtEdit] Bin = C:\Program Files (x86)\Schneider Electric\Citect SCADA 2018\Bin Config =C:\ProgramData\Schneider Electric\Citect SCADA 2018\Config Data =C:\ProgramData\Schneider Electric\Citect SCADA 2018\Data Logs =C:\ProgramData\Schneider Electric\Citect SCADA 2018\Logs User =C:\ProgramData\Schneider Electric\Citect SCADA 2018\User Regards Rob

RobertSanders · ‎2020-03-13

I do not have a MiCOM P127 and are therefore unable to test with Citect. Citect SCADA has approximately 20 different Protocol configurations for Modbus Eg, Modbus1, Modbus20 in which the major parameters are hard coded into the Driver. Check that the Citect I/O Device Protocol is set to Modbus, not Eg Modbus20, this means the parameter changes in the INI file will have an effect, unfortunately it’s a matter of trying different parameter combinations. It may also be worth plugging the MiCOM directly into the PC using a USB to Serial converter and using a utility like ModScan to validate the readings. Regards Rob

RobertSanders · ‎2020-03-12

Hi Below is an extract from the Modbus help (attached), try the following parameters using the Setup Editor, ensure the change is made on the IOServer. Note: This parameter is not applicable if you are using the protocol variant MODBUS20 or MODBUS30 to communicate with a device. Under these circumstances, a value of 3 will be hardcoded for this parameter in the driver. [MODBUS]LongDataType In the Modbus protocol, LONG data types defaultto a simplified implementation, with a shortened range of 0 to 99,999,999 - mode 0. Mode 2 has the samerange as mode 0, but with the register order swapped. Mode 1 supports thecomplete LONG range of -2,147,483,648 to +2,147,483,647. Mode 3 has the samerange as mode 1, but with the register order swapped. Allowable Values: 0 to 3, where: 0 = 10000 x low register + high register 1 = 65536 x low register + high register 2 = 10000 x high register + low register 3 = 65536 x high register + low register Default Value: 3 With this parameter, you can set different values for specific I/O devices or groups of I/O devices. See Device/group-specific parameters. If this doesn't work we will need more information Eg what controller are you using? Regards Rob

RobertSanders · ‎2019-08-29

Hi Samir Unfortunately, I don’t have a M221 and therefore unable to test, however there are still a few things we can try. There is a difference between how the OFS Client connects and how Citect connects to the OFS Server. Citect will create several groups, three are used for items subscriptions and two are used for status. Citect will also subscribe to all variable tags defined in its database. I would suggest that you change the existing M221 IODevice to Memory and create a new test IODevice that only has one variable tag defined and displayed on a page. With Citect stopped, Open the OPC Server Diagnostic window and clear all messages, start Citect. You should see Groups added and an Item added messages. I hope that these messages may give some indication to the underlying problem. Another test worth trying is to change the newly create IODevice from OFS to OPC. This will simplify how Citect connect to OFS and it force Citect to communicate as just a normal OPC Client. Regards Rob

RobertSanders · ‎2019-08-28

Hi We would require more information about your configuration to give a detailed answer, however, the following should give you something to investigate: - It is recommended that both the Citect IOServer and OFS Server are running on the same PC, this removes any DCOM security issues. Using an OPC Client connect to the OFS server on the same PC that the Citect IO Server is running on and ensure you can read some Items (Items is the OPC name for variable tags). If you can read items using an OPC Client, then double check the communication setting in Citect and ensure you have the correct Alias name and variable names. The OFS Server while running has a diagnostic popup, watch this while starting Citect and you should see groups and items being added. I have attached a white paper which may give you an insight into the communication method between Citect and OFS, it’s based on a M580 and NOT a M221. Therefore only read the information regarding Citect to OFS. Regards Rob

RobertSanders · ‎2019-03-13

Hi The following link is to the Citect 2016 Online help for Kernel commands https://www.citect.schneider-electric.com/webhelp/citect800/#Kernel_Commands_Reference.html?Highlight=kernel The main Kernel command for Citect Runtime information is the PageTable, which can be found https://www.citect.schneider-electric.com/webhelp/citect800/#Page_Table.html Regards Rob

Online Status	Offline
Date Last Visited	2 weeks ago

About RobertSanders

Re: SCADA

Re: Citect Cicode Function DspAnGetPos

Re: Cicode Function AlarmSetInfo

Re: Citect V7.40 SP1 Installation on Win 10

Re: Citect V7.40 SP1 Installation on Win 10

Re: Vijeo Cİtect V7.3 Modbus Communication Problem

Re: Vijeo Cİtect V7.3 Modbus Communication Problem

Re: communication CITECT SCADA M221 through OFS

Re: communication CITECT SCADA M221 through OFS

Re: Help file on kernel tables on Citect

Support

FAQ

About