04-15-2010 07:11 PM
Hi unclebump,
now i see. i did'nt know this before. im so grateful for your very crystal cleared explanation about this matter.
I believe, in my OPC modbus setting, i already done almost all possibilities except the one you had mentioned: setting Poll value. i really dont know that its necessary to set this parameter.
so i cannot escape showing my ignorance in this part. i badly needed to know how to set this. should i just type "TRUE" in its column like shown below? or a TRUE value (i.e. 1), or some algorithms as shown in OPC help topic?, because when i right-click this parameter, the expression editor shows, that is why i did'nt put any value here before to avoid mistakes. please clarify me with this matter. I will do this setting right now and update you the results.
a trillion thanks for the time!
Ivel
04-15-2010 07:27 PM
04-15-2010 07:54 PM
not succeeded... i tried the "TRUE", "true", and paste some simple expression but still did'nt work. i even tried the number "1" but is invalid input.
i think i may try different OPC software trial version. btw, i am looking for kepware OPC trial ver., do i need to create a new account to avail that? do you have the link to get me there directly? i will try using kepware OPC to investigate this problem...
04-15-2010 07:59 PM
04-15-2010 08:26 PM
04-16-2010 12:59 AM
hi unclebump,
i tried the kepware OPC & get good values when reading the system data but when i create a new tag to read particular output registers, the value returns bad for that particular address, but the system data of my device still in good values. i tried to attached the kepware files but have no zip software in my computer (not permitted in our company), only .rar software (.rar files cannot attached). I am starting to think that the my power meter devices is not following the Modbus standard.
in my LabVIEW program using MB library, hexadecimal address (i.e. 005E, 005F, etc.) can recognized by the device, so i can read and write data to registers.
in my OPC program using both IA OPC & kepware OPC, the register address (i.e. 40001 - 49999, or 40001 - 499999) cannot recognized by the device. it shows value bad always.
04-16-2010 09:53 AM
Have you tried MatrikonOPC's Server for Scada Modbus? Even if your meters' are not conformed to the Modbus Standard, MatrikonOPC's Server for Scada Modbus supports many different function calls for the read or write operation. I recommend trying it:
http://www.matrikonopc.com/opc-drivers/302/base-driver-details.aspx
Consult the user manual to find out what is the item sytax that you need to use for a specific function call to complete the operation.
Let me know if you have any questions and i will be happy to help.
Wassim Daoud
Global Solutions Architect
04-16-2010 02:14 PM
04-20-2010 08:02 PM
Hi unclebump,
In tag properties, do i need to modify the scaling also to choose the data type in scaling data range?
or the data properties only in the general tab?
i attached the two tag setting window.
sorry for late updates, i'm working w/ other important things these recent days. im also trying to add 1 to the device ip address (i.e. 10.37.125.13.1 to 10.37.125.13.2).
thanks
04-20-2010 08:53 PM
follow-up,
the powermeters system reading is good.
the tag i created, 400258 for reading adress of device, reading is bad.
in this situation, i tried almost all possibilities of data type and the tag i created never turns good value. i also do add 1 to the unit ID of device (i.e. from 10.37.125.13.1 to 10.37.125.2) but still bad value.
one thing is quite interesting here to me is that the system reading of device also turns good. what is the meaning of this unclebump? is this mean i can
communicate to my device and i just create a wrong settings in the tag?
i attached the result of my reading. maybe, it will more express my current situation...