Re: [foxboro] Fbm230 fdsi driver modbus rtu
- From: Yonca Yesilipek <yonca@xxxxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Wed, 28 Jul 2010 19:25:10 +0300
Today , I have replaced FBM230 with FBM224 before reading suggestions
about new version of FDSI driver.
I have done all transaction configurations, ECB's etc. Now the system is
working .
Thanks to everybody.
Brannagan, Martin wrote:
> Hi
> A colleague informed me of this thread and mailing list so I joined up
> especially to offer my knowledge!
>
> You are all somewhat correct in that the early versions of the modbus driver
> requested continuous blocks of data so in the example Yonca gave the modbus
> request would be for 10 words starting at address 850. I think this is down
> to a balance of the additional overheads created by requesting two individual
> addresses over requesting a block of data including both of the addresses.
>
> With the recent release of Modbus driver V2.0 it allows the creation of an
> additional XML file with a 'custom memory map ' which allows you to dictate
> to the FDSI which addresses are valid to request from the slave device - any
> addresses that aren't included in that XML file are flagged as invalid and
> will never be requested by the FDSI, thus forcing a split in the read
> requests in the way you desire.
>
> This XML file also lets you dictate individual scantimes for memory areas, so
> is effectively a complete replacement for the MDSCAN functionality.
>
> This procedure used to be available in a custom version of the modbus FDSI
> driver but has now been incorporated into the full release V2.0
>
> Foxdoc B0700BG rev F gives full information on the full functionality of this
> driver
>
> I have used this driver successfully using Modbus RS485 to communicate with
> an Omron PLC which caused communication failure with the older driver.
>
> The main downside that I have experienced unless you are clever setting up
> your memory map configuration upfront is that to add any new addresses later
> in time you have to modify the memory map and perform an XML download which
> will temporarily take all of your existing working comms off-line as well,
> though this is usually only a quick download, reset FDSI and everything is
> working again.
>
> I am on the technical side of things so not sure how you would obtain this
> driver, I guess get in touch with your local sales representative to see if
> you can get an upgrade from the driver you obviously already have
>
> Regards
> Martin Brannagan
> Lead Engineer
> Invensys Operations Management
> 13a & 15 The Genesis Centre
> Birchwood, Warrington, WA3 7BH, UK
>
>
>
> Hi all,
>
> I'm using an FBM230 with modbus RTU FDSI driver (serial).
>
>
>
> I'm trying to communicate with a modbus device which parameter address
>
> list is not in order. I mean that it has an adress #850 and then #860 ,(
>
> #851 or #852 does not exist.. )
>
>
>
> When I configure fdsi device configurator with these two address ,
>
> FBM230 sends a query to device for the all addresses between #850 and
>
> #860 total 10 and I lost the the communication.
>
> How is it possible to send separate queries for each different address
>
> on modbus device.
>
> It was possible with MOD30 and MDSCAN block before. I thought that it
>
> should be possible with FDSI also.
>
>
>
> Could anyone help me
>
> Thanks
>
> Yonca
>
>
> Martin Brannagan
> Lead Engineer
>
> [cid:image002.jpg@01CB2E40.FF6AB900]<http://www.invensys.com/aboutus/default.asp?top_nav_id=1&nav_id4&prev_id)>
>
> 13a & 15 The Genesis Centre
> Birchwood, Warrington, WA3 7BH, UK
> T: +44 (0)1925 859823
> M: +44 (0)7500 765971
> E: martin.brannagan@xxxxxxxxxxxx<mailto:martin.brannagan@xxxxxxxxxxxx>
>
>
>
> *** 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_idw&nav_idEUR&prev_idw. You
> may contact Invensys plc on +44 (0)20 7821 3848 or e-mail
> inet.hqhelpdesk@xxxxxxxxxxxxx This e-mail and an
> y 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
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature
> database 5318 (20100727) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5318 (20100727) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
_______________________________________________________________________
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:
