Re: [foxboro] Device Integrator 30 manual
- From: "Wilson, Brad" <brad.wilson@xxxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 8 Mar 2010 08:55:02 -0500
Pablo,
I think the manuals you want are DI700AJ v1.16 (Modbus master) and DI700AK
v1.13 (Modbus slave). Both are dated Dec 1999.
The B0193RH-C manual is a generic hardware manual, but as others have said,
does not address the specifics of the protocol.
As you probably know, the Modbus FC3 message layout is:
master query = <slave address><FC><start register 2 bytes><register count 2
bytes><CRC 2 bytes>
slave response = <slave address><FC><byte count><1st register value 2
bytes><2nd register value 2 bytes>etc<CRC 2 bytes>
The query message is built in the FDMSGx parameters of the FDSCAN (master).
The FDIDMS block tells the input blocks (FDRIN, etc) where to find their values
within the response message.
Hope this helps.
Brad Wilson
-----Original Message-----
We have DI30B's on both sides of the communication, using the Modbus RTU
Protocol.
The "onshore" DI30 acts as master and the "offshore" acts as "slave", but they
are not using custom images, as far as I know.
According to the ds_stasict command, we have v651v344.186 OS1FDB.GDT.
The ECB20's of both ports are configured for RTU protocol.
On the "master" side, pollings are implemented using FDSCAN and response
messages are handled by FDIDMS and FDIIN blocks.
On the "slave" side, querys are handled by FDIDMS, FDMSBL and FDIOUT blocks.
The system was delivered with no documentation and the people who programmed it
are no longer available.
Originally, the system was working partially, with PERF error counters for the
ports in Sysmon increasing all the time, due to configuration errors.
Using the manual, I was able to correct the errors, but now I would like to
have a deeper understanding of the system.
Just to give you an example, I don't understand how a FDIDMS block on the
"master" side identifies a response message for FC 03.The response for FC 03
does not include the starting register number, so all responses from a given
slave, with the same number of registers, look identical to the FDIDMS blocks.
Yet, the FDIDMS blocks do include the starting register number, and in some way
the data gets routed to the right place. Well, I didn't find any explanation
for that in the manual.
Regards,
Pablo
*** Confidentiality Notice: This e-mail, including any associated or attached
files, is intended solely for the individual or entity to which it is
addressed. This e-mail is confidential and may well also be legally privileged.
If you have received it in error, you are on notice of its status. Please
notify the sender immediately by reply e-mail and then delete this message from
your system. Please do not copy it or use it for any purposes, or disclose its
contents to any other person. This email comes from a division of the Invensys
Group, owned by Invensys plc, which is a company registered in England and
Wales with its registered office at Portland House, Bressenden Place, London,
SW1E 5BF (Registered number 166023). For a list of European legal entities
within the Invensys Group, please go to
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77.
You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail
inet.hqhelpdesk@xxxxxxxxxxxxx This e-mail and any attachments thereto may be
subject to the terms of any agreements between Invensys (and/or its
subsidiaries and affiliates) and the recipient (and/or its subsidiaries and
affiliates).
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
