On Sat, 2012-02-11 at 19:20 +0000, andy pugh wrote: > On 11 February 2012 16:31, Kirk Wallace <kwall...@wallacecompany.com> wrote: > > > What I am thinking about is to have two sets of components, one set for > > Modbus slaves such as for VFD's, PLC's, pendants, etcetera, then a set ... snip
This is what I have worked out so far. My original plan has changed. The attached file shows an overview. I think I can use normal u32 HAL pins. The connections between the muxes will just be named something like block0, block1, block3, etcetera. The top byte of the first block will have the slave ID, the next byte will have the function, the next two will have the address, the next byte, in block1, the number of registers involved with the function. The port component will break the bytes out of the u32's and create the data needed to fill in the function calls to libmodbus. An issue I haven't worked out yet is how to control the muxes. The plan is to have each slave component send a query in a regular order. Each slave query will finish when a reply comes back, so each slave transaction will be a separate process. I'll need to have enough HAL u32's to handle the largest planned packet but with four bytes per u32 and multiplexing the number should not be too large.
<<attachment: Screenshot-11.png>>
------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
