回應： Re: 回應： Re: large monitoring system: MB lib, NI-OPC server, or DSC?

[ivelson]

haha.. copycat.. so they (maybe) adopt the NI-OPC server from kepware tech. but i think that's a good move from NI to stay foot in fast rising/changing technology. anyway, we have IA OPC server (5.1 version) and as far as i knew its from NI also. i don't know what's among the two is the latest (your post version vs mine). see attached picture file.

[Billingsley]

IA OPC is old and will not update anymore. ( from NI sales guys )

NI-OPC is a replacement of IA OPC and supports many new PLCs.

[ivelson]

thanks for info charles.

anyway, i will communicate thru modbus (powermeter devices and not PLC devices) and i hope IA OPC server was good enough for this kinda system. i will test the IA OPC servers' reliability by nextweek and feedback my results.

im so grateful to hear comments/suggestions from you guys...

[ivelson]

hello again,

Now im trying to work with IA-OPC server 5.1 and i cannot read good values from the server explorer... the value appears "XXX" and "value bad". i've attached some files to clarify my situation. I think the settings is quite simple to have mistakes. i've already used the IA OPC server in omron PLC and i can communicate w/out a problem.. does anyone know what's problem with this???

my device (server) is ADTEK power meters which is not included in the supported device list in this link http://zone.ni.com/devzone/cda/tut/p/id/6417 but it uses MODBUS protocol so i guess there's no problem communicating to it (since NI said IA OPC server can communicate w/ almost all modbus devices).

thanks for support...

[ivelson]

Hi to all,

anyone using IA OPC server 5.1 here?? anyone can relate with my present problem (my last msg)?

thanks for the help..!

[Billingsley]

I don't know, either.

Plz see attatched file.

[unclebump]

We will need more info from you on how things are connected. The power meters are ethernet or RS485 serial? Sounds like they are serial ports from your first post. Does your ethernet to serial converter support an RS485 network or just a single device?? Does it support ethernet encapsulation? http://www.kepware.com/Support_Center/doc_ethernet_encapsulation.asp and http://www.kepware.com/Support_Center/app-digi-oneSP.asp Does the IA OPC server support ethernet encapsulation??

It will make a difference as to how you configure the opc server software. You might need a unique ip address for each rs485 device, you might need to create an address table inside the ethernet/serial converter for each rs485 device.

Part numbers and manuals for each of the devices would help.

[ivelson]

hi unclebump,

let me answer your questions:

Q: We will need more info from you on how things are connected. The power meters are ethernet or RS485 serial?

A: power meters uses RS485 serial port

Q: Does your ethernet to serial converter support an RS485 network or just a single device??

A: in the serial to ethernet converter setting, there is are selection "multiple connection support". is it this the same as what you've ask?

Q: Does it support ethernet encapsulation? Does the IA OPC server support ethernet encapsulation??

A: i may need time to read your link (a day or two) to answer this.

Q: You might need a unique ip address for each rs485 device, you might need to create an address table inside the ethernet/serial converter for each rs485 device.

A: im afraid there is no such setting as address table in my ethernet/serial converter device, but i will double-check again. but i have two ethernet/serial converters so i can create a unique ip address for each rs-485 device.

but then before i failed connecting using OPC server, the Modbus drivers i created using LabVIEW (8.5.1) works in this layout. i got the data of power meter devices using only single IP address for two power meter devices (because they differ in device id).

Q: Part numbers and manuals for each of the devices would help.

A: the attached file pertains to 3 devices: MWH-10 powermeter, CPM50 power meter, PL Snet serial/ethernet converter.

million thanks for the help!

regards,

Ivel

[unclebump]

From the pc view as a modbus master, it needs to talk to slave devices 10.37.125.13.1 and 10.37.125.13.10. The .1 and .10 on the end are the ethernet encapsulation. Sometimes this is done in the opc software config on the pc, or it can be done inside the ethernet/serial device.

I found my old IA opc 5.1 disk and loaded it. You need to create Multiple objects inside the IA software for each plant floor device. Select modbus, Ethernet communication, your ip address, and then the identifier field is where you put each individual slave id for the 485 network. You also need to set the Poll value to True to get the sampling to start.

One word of advice as far as naming your devices, set it up for worst case and room for expansion first. Then you won't have to keep modifying the names everytime you add devices. It also makes working with the info inside excel and csv files much easier. Try things like CPM50_001 if you plan on having more than 100 of them in total.

Read this pdf file for some info about number of tcp sockets and serial device communication.

http://www.advindsys.com/ApNotes/CorsairModbusEthernettoSerial.pdf