Re: [foxboro] FBM230 MODBUS RTU Mapping for Micro Motion Coriolis Transmitters
- From: Pablo Lioi <plioi@xxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Fri, 13 Mar 2015 23:03:38 +0000
Tom,
In our plant we have two CFM300 Coriolis flowmeters with 3700 transmitters
(exact model number is 3700A2B06DUEZNZ).
We are reading them with a PLC5 Prosoft Modbus Module, using Modbus RTU.
Mass Flow Rate is read from registers 246 and 247 with function code 03 (Read
Holding Registers). Both registers are then assembled into a floating point
register, with previous word swapping.
This means that:
1 - They are holding registers.
2 - As the Prosoft Module is 0-based, 246 would be 40247 and 247 would be
40248, in accordance with the manual.
3 - You should read using a RIN block. PNT_NO should be 40247:F4:Wx where "Wx"
is to be determined by trial and error, but I would start with W3, as this
swaps word pairs in the response message, as our configuration in the Prosoft
Module. If this doesn't work, you should try with W1 and W2. If nothing of this
works, you should repeat with register numbers 40246 and 40248.
I hope this helps. I will post another message with my conclusions so far as to
my "FBM230 slave response too fast" problem that may also be relevant to your
problem if nothing works.
Regards
Pablo Lioi
Total Austral S.A.
Tierra del Fuego
Argentina
> From: TVandewater.contractor@xxxxxxxxxxx
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] FBM230 MODBUS RTU Mapping for Micro Motion Coriolis
> Transmitters
> Date: Fri, 13 Mar 2015 19:55:13 +0000
>
> Matt,
>
> It is a CMF200 Coriolis with a 3700 (3000 MVD series) field mount
> transmitter.
> Are you communicating FBM230 MODBUS RTU with any Micro Motion Coriolis
> Transmitters?
>
> Thanks for any help you can give.
>
> Tom
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of Kinsinger, Matthew R
> Sent: Friday, March 13, 2015 9:48 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] FBM230 MODBUS RTU Mapping for Micro Motion Coriolis
> Transmitters
>
> Which micromotion model? They had some issues with some models, and stated
> communications capabilities and available registers, that were not truly
> available for non micro-motion device communication.
>
> Matt Kinsinger
> mkinsinger@xxxxxxx
> 330-825-1208 office
> 330-472-1454 ppg cell
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of Vandewater, Tom (HI Contractor)
> Sent: Friday, March 13, 2015 3:20 PM
> To: 'foxboro@xxxxxxxxxxxxx'
> Subject: [foxboro] FBM230 MODBUS RTU Mapping for Micro Motion Coriolis
> Transmitters
>
> To All,
> I read with interest responses to Pablo's FBM230 Modbus interface
> issues because I just inherited a failed attempt to interface a Micro Motion
> Coriolis Transmitter via Modbus RTU protocol and am trying to sort out if it
> is a problem with the FBM230 installation, the Modbus driver
> configuration/installation, or the way I am requesting data from the
> interface. (I suspect the data request because the interface shows that the
> DCI is "Ready" with no failure until I make my first/only data request from
> this device). I know this is Friday the 13th but am still hoping to resolve
> this issue on this fateful day if possible. All responses are appreciated.
> Don't hate me because it is early in the morning here in Hawaii and you may
> be dealing with a pile in snow near Foxboro, MA;<)
>
> My first question to the amazing repository of Foxboro info stored in all of
> your heads is this:
>
> Is anyone out there using an FBM230 and MODBUS RTU to communicate with Micro
> Motion Coriolis Transmitters?
>
> If so, can you tell me whether you use an "RIN" or "IIN" block and what is in
> your "Pnt_no" configuration for the Mass Flow Rate register polling?
>
> The Micro Motion manual I am looking at shows this for the Modbus address for
> the Mass Flow Rate:
>
> 0247 0248 RO Mass flow rate
>
> I am assuming that since there are two registers to read I probably need to
> issue a command that swaps words or even bits, (based on previous fun I've
> had), but there is not enough info in the manual for me to know. Since the
> leading number for the MODBUS register type has been omitted from the Micro
> Motion document it is also unclear if the data is being stored in MODBUS
> standard 30001-39999 input registers, or the 40001-49999 holding registers.
> I have put both 30247, and 40247 in the "Pnt_no" configuration with no
> success. Each time I try to issue a read request via either an RIN or IIN
> block, my "LPGFLW" MODBUS interface immediately indicates "Device Failed" in
> System Manager and I get a "W62 - UNRESOLVED CONNECTION" message on the RIN
> block detail display and everything turns CYAN. Even when I remove the read
> request from the IIN or RIN block by placing the block in SIMOPT and
> downloading which clears the block from CYAN and causes no data requests to
> the interface
> the "Device Failed" status remains in System Manager until I disable and
> enable the interface. It looks healthy until I make another read request
> from the interface.
>
> Any help here is greatly appreciated.
>
> Tom VandeWater
> Control Conversions, Inc.
>
>
>
> _______________________________________________________________________
> 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
>
>
>
> _______________________________________________________________________
> 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
>
>
>
> _______________________________________________________________________
> 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
>
_______________________________________________________________________
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:
