1
MODBUS / MODBUS IP to serial (RTU) gateway
« on: April 29, 2012, 08:53:57 PM »
Hi Mark,
I've been asked to look into providing a simple MODBUS gateway to allow serial (RTU) devices (RS232 & RS485 but not necessarily both at the same time) to be connected via Ethernet (MODBUS IP).
Having had a read of the documentation, this looks to be a pretty simple application for the uTasker MODBUS implementation.
I have a pretty wide range of devices to choose from (ColdFire Kirin3/Kinetis, NXP LPC2xxx/LPC17xx, STM32, TI) though the preference for development tools/compiler would be to use IAR (for ARM or ColdFire).
Can you suggest what the relative benefits/drawbacks of the various platforms are for the uTasker/MODBUS combination? I'd imagine that most would be capable of supporting the simple case above but any indication on which dev kits would be suitable for initial prototype development would be a great help.
Initial minimum project features are for MODBUS IP (IP v4 though the option for IP v6 would be good) & either RS232 or RS485 (possibly as two hardware builds) purely as a gateway.
Next phase would be to add in some simple web server applications & possibly support more than one serial connection at once (e.g. RS232 & RS485).
Then we'd be looking to add in USB Host functionality (we have our own flavour of MODBUS over USB bulk transfers we'd like to support)
We may also be wanting to offer a plain (non-MODBUS) Ethernet to serial gateway (but so far the options for providing a virtual serial port on the PC is looking problematic for this)
We'd like to be able to support this within a family of processors (maybe scaling the memory/package sizes as the complexity rises) rather than mixing solutions across the different vendors.
Any thoughts or suggestions (from you or your other MODBUS customers) would help
Cheers,
Jez
I've been asked to look into providing a simple MODBUS gateway to allow serial (RTU) devices (RS232 & RS485 but not necessarily both at the same time) to be connected via Ethernet (MODBUS IP).
Having had a read of the documentation, this looks to be a pretty simple application for the uTasker MODBUS implementation.
I have a pretty wide range of devices to choose from (ColdFire Kirin3/Kinetis, NXP LPC2xxx/LPC17xx, STM32, TI) though the preference for development tools/compiler would be to use IAR (for ARM or ColdFire).
Can you suggest what the relative benefits/drawbacks of the various platforms are for the uTasker/MODBUS combination? I'd imagine that most would be capable of supporting the simple case above but any indication on which dev kits would be suitable for initial prototype development would be a great help.
Initial minimum project features are for MODBUS IP (IP v4 though the option for IP v6 would be good) & either RS232 or RS485 (possibly as two hardware builds) purely as a gateway.
Next phase would be to add in some simple web server applications & possibly support more than one serial connection at once (e.g. RS232 & RS485).
Then we'd be looking to add in USB Host functionality (we have our own flavour of MODBUS over USB bulk transfers we'd like to support)
We may also be wanting to offer a plain (non-MODBUS) Ethernet to serial gateway (but so far the options for providing a virtual serial port on the PC is looking problematic for this)
We'd like to be able to support this within a family of processors (maybe scaling the memory/package sizes as the complexity rises) rather than mixing solutions across the different vendors.
Any thoughts or suggestions (from you or your other MODBUS customers) would help
Cheers,
Jez