Below is a beginning of a first pass at writing an EMC Modbus RTU interface spec. Any comments are welcome.
" EMC should talk to Modbus RTU devices through a Modbus RTU component. Each device, hence Modbus address, would have a Modbus component instance, modbus-rtu.0, modbus-rtu.1, etc. For example, a spindle or tool change signal might have an HAL link of "net motion.spindle-on modbus.0.coil001" and "net iocontrol.0.tool-change modbus.1.coil003". If a device meets modbus standards, no device dependant driver would be needed. Each modbus instance would need parameters set for; serial port number, address number, baud rate, parity, number of stop bits, latency time, response time-out, etc., to match the characteristics of the device being attached. " -- Kirk Wallace (California, USA http://www.wallacecompany.com/machine_shop/ Hardinge HNC lathe, Bridgeport mill conversion, doing XY now, Zubal lathe conversion pending) ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
