Messages

1

MODBUS / Re: MODBUS IP to serial (RTU) gateway

« on: May 17, 2012, 01:02:04 PM »

Hi Mark,

  Thanks for sending the password (again).

With the latest MODBUS files I've managed to get the Kinetis project compiling ok in the simulator (C++ 2010 Express) - I'm struggling to get the same project working on the 2009 version on a different PC but I'll upgrade to 2010 & see if that sorts it.

Thanks once again for your help with this - it really is appreciated.

I'll let you know when I've sorted it all.

Cheers,
    Jez

PS - I've just tried to get the MODBUS working in the simulator for the LPC1768 (Keil MCB17xx board) target to compare with the Kinetis but that's still reporting compile errors relating to stTIMER_INTERRUPT_SETUP as below

1>c:\downloads\utasker\utasker_lpc17xx_v1.4-1\utasker\modbus\modbus.c(1618): error C2039: 'timer_us_value' : is not a member of 'stTIMER_INTERRUPT_SETUP'
1>          c:\downloads\utasker\utasker_lpc17xx_v1.4-1\hardware\lpc17xx\lpc17xx.h(3661) : see declaration of 'stTIMER_INTERRUPT_SETUP'
1>c:\downloads\utasker\utasker_lpc17xx_v1.4-1\utasker\modbus\modbus.c(1619): error C2039: 'timer_us_value' : is not a member of 'stTIMER_INTERRUPT_SETUP'
1>          c:\downloads\utasker\utasker_lpc17xx_v1.4-1\hardware\lpc17xx\lpc17xx.h(3661) : see declaration of 'stTIMER_INTERRUPT_SETUP'
1>c:\downloads\utasker\utasker_lpc17xx_v1.4-1\utasker\modbus\modbus.c(1622): error C2039: 'timer_us_value' : is not a member of 'stTIMER_INTERRUPT_SETUP'
1>          c:\downloads\utasker\utasker_lpc17xx_v1.4-1\hardware\lpc17xx\lpc17xx.h(3661) : see declaration of 'stTIMER_INTERRUPT_SETUP'
1>c:\downloads\utasker\utasker_lpc17xx_v1.4-1\utasker\modbus\modbus.c(1623): error C2039: 'timer_us_value' : is not a member of 'stTIMER_INTERRUPT_SETUP'
1>          c:\downloads\utasker\utasker_lpc17xx_v1.4-1\hardware\lpc17xx\lpc17xx.h(3661) : see declaration of 'stTIMER_INTERRUPT_SETUP'
1>c:\downloads\utasker\utasker_lpc17xx_v1.4-1\utasker\modbus\modbus.c(1626): error C2039: 'timer_us_value' : is not a member of 'stTIMER_INTERRUPT_SETUP'
1>          c:\downloads\utasker\utasker_lpc17xx_v1.4-1\hardware\lpc17xx\lpc17xx.h(3661) : see declaration of 'stTIMER_INTERRUPT_SETUP'
1>c:\downloads\utasker\utasker_lpc17xx_v1.4-1\utasker\modbus\modbus.c(1627): error C2039: 'timer_us_value' : is not a member of 'stTIMER_INTERRUPT_SETUP'
1>          c:\downloads\utasker\utasker_lpc17xx_v1.4-1\hardware\lpc17xx\lpc17xx.h(3661) : see declaration of 'stTIMER_INTERRUPT_SETUP'
1>c:\downloads\utasker\utasker_lpc17xx_v1.4-1\utasker\modbus\modbus.c(1630): error C2039: 'timer_us_value' : is not a member of 'stTIMER_INTERRUPT_SETUP'
1>          c:\downloads\utasker\utasker_lpc17xx_v1.4-1\hardware\lpc17xx\lpc17xx.h(3661) : see declaration of 'stTIMER_INTERRUPT_SETUP'
1>c:\downloads\utasker\utasker_lpc17xx_v1.4-1\utasker\modbus\modbus.c(1631): error C2039: 'timer_us_value' : is not a member of 'stTIMER_INTERRUPT_SETUP'
1>          c:\downloads\utasker\utasker_lpc17xx_v1.4-1\hardware\lpc17xx\lpc17xx.h(3661) : see declaration of 'stTIMER_INTERRUPT_SETUP'
1>c:\downloads\utasker\utasker_lpc17xx_v1.4-1\utasker\modbus\modbus.c(1635): error C2039: 'timer_us_value' : is not a member of 'stTIMER_INTERRUPT_SETUP'
1>          c:\downloads\utasker\utasker_lpc17xx_v1.4-1\hardware\lpc17xx\lpc17xx.h(3661) : see declaration of 'stTIMER_INTERRUPT_SETUP'
1>c:\downloads\utasker\utasker_lpc17xx_v1.4-1\utasker\modbus\modbus.c(1636): error C2039: 'timer_us_value' : is not a member of 'stTIMER_INTERRUPT_SETUP'
1>          c:\downloads\utasker\utasker_lpc17xx_v1.4-1\hardware\lpc17xx\lpc17xx.h(3661) : see declaration of 'stTIMER_INTERRUPT_SETUP'
1>c:\downloads\utasker\utasker_lpc17xx_v1.4-1\utasker\modbus\modbus.c(1639): error C2039: 'timer_us_value' : is not a member of 'stTIMER_INTERRUPT_SETUP'
1>          c:\downloads\utasker\utasker_lpc17xx_v1.4-1\hardware\lpc17xx\lpc17xx.h(3661) : see declaration of 'stTIMER_INTERRUPT_SETUP'
1>c:\downloads\utasker\utasker_lpc17xx_v1.4-1\utasker\modbus\modbus.c(1640): error C2039: 'timer_us_value' : is not a member of 'stTIMER_INTERRUPT_SETUP'
1>          c:\downloads\utasker\utasker_lpc17xx_v1.4-1\hardware\lpc17xx\lpc17xx.h(3661) : see declaration of 'stTIMER_INTERRUPT_SETUP'
1>c:\downloads\utasker\utasker_lpc17xx_v1.4-1\utasker\modbus\modbus.c(1643): error C2039: 'timer_us_value' : is not a member of 'stTIMER_INTERRUPT_SETUP'
1>          c:\downloads\utasker\utasker_lpc17xx_v1.4-1\hardware\lpc17xx\lpc17xx.h(3661) : see declaration of 'stTIMER_INTERRUPT_SETUP'
1>c:\downloads\utasker\utasker_lpc17xx_v1.4-1\utasker\modbus\modbus.c(1644): error C2039: 'timer_us_value' : is not a member of 'stTIMER_INTERRUPT_SETUP'
1>          c:\downloads\utasker\utasker_lpc17xx_v1.4-1\hardware\lpc17xx\lpc17xx.h(3661) : see declaration of 'stTIMER_INTERRUPT_SETUP'
1>c:\downloads\utasker\utasker_lpc17xx_v1.4-1\utasker\modbus\modbus.c(1648): error C2039: 'timer_us_value' : is not a member of 'stTIMER_INTERRUPT_SETUP'
1>          c:\downloads\utasker\utasker_lpc17xx_v1.4-1\hardware\lpc17xx\lpc17xx.h(3661) : see declaration of 'stTIMER_INTERRUPT_SETUP'
1>c:\downloads\utasker\utasker_lpc17xx_v1.4-1\utasker\modbus\modbus.c(1649): error C2039: 'timer_us_value' : is not a member of 'stTIMER_INTERRUPT_SETUP'
1>          c:\downloads\utasker\utasker_lpc17xx_v1.4-1\hardware\lpc17xx\lpc17xx.h(3661) : see declaration of 'stTIMER_INTERRUPT_SETUP'

Changing the target back to LPC1788 is still giving me the same errors.

Any ideas?

Cheers,
    Jez

2

MODBUS / Re: MODBUS IP to serial (RTU) gateway

« on: May 16, 2012, 05:14:27 PM »

Hi Mark,

Ok, thanks for confirming that is the problem. The next problem is for me to find the original password again...

I'll continue proving the ideas with the 52259 build until I can retrieve the password.

Thanks once again for your support!

Cheers,
    Jez

3

MODBUS / Re: MODBUS IP to serial (RTU) gateway

« on: May 16, 2012, 12:55:40 PM »

Hi Mark,

Thank you for the response - I've tried to make a start with the simulator for both Kinetis & LPC17xx families but both fail to compile when I include the 'real' MODBUS.c & .h files...

\utasker\modbus\modbus.c(1383): error C2039: 'timer_reference' : is not a member of 'stPIT_SETUP'
\hardware\kinetis\kinetis.h(5857) : see declaration of 'stPIT_SETUP'
\utasker\modbus\modbus.c(1383): error C2065: 'MODBUS0_TIMER_CHANNEL' : undeclared identifier


I've quickly tried the same with the 52259 DEMO board & that seems to build ok for the simulator & run.

Do I need a later version of MODBUS.c & modbus.h fiels to support Kinetis /LPC17xx/2xxx ?
Looking at the comment at the top of MODBUS.c I appear to have v1.06 (2/9/2009)...

Is there any chance to get the updated files to allow me to use Kinetis or LPC targets please?
Or, if it's easier to just let me know what changes I need to add in to support one or other, that would be most helpful.

In the meantime I'll try and get some of the basic functionality/configuration sorted out with the 52259 ssimulation.

Cheers,
    Jez

4

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

5

µTasker general / Re: Simulating custom peripherals?

« on: December 13, 2011, 10:11:38 PM »

Hi Martin,

Hurrah! I've been struggling to find a good way to get virtual com ports working in 64 bit Win7 Pro (the old unsigned Com0Com wouldn't install except in test mode...).

I'll give that a try again!

Thanks for letting us know :-)

Cheers
Jez

6

NXP^TM LPC2XXX and LPC17XX / Re: LPC1788 Support added to LPC17XX project

« on: November 29, 2011, 10:52:26 PM »

Hi Mark,

Ok, I'll get the latest version & try it on the EA board over the weekend & hopefully report back on my progress.

IIRC the biggest difference with the SDRAM will be that the IAR board uses a pair of x16 SDRAM devices but there's only a single x32 SDRAM on the EA board.

I've got the 320x240 LCD at the moment & this is the same as the one on the LPC2478 dev kit (I think).

Thanks,

Jez

7

NXP^TM LPC2XXX and LPC17XX / Re: LPC1788 Support added to LPC17XX project

« on: November 28, 2011, 10:47:32 PM »

Hi Mark,

Yes, unfortunalely the schematics are part of the downloads only available after registering the product.

However, the NXP examples for the LPC1788 (which also seem to be their CMSIS libraries) are all written for the EA board (and many now support the IAR board too) & at least one of these covers setting up the SDRAM.

I'll try and dig out a bit more information about this if it would help?
I'd also be happy to try and prove that the port to the EA board works if that would help?

Cheers,
    Jez

8

NXP^TM LPC2XXX and LPC17XX / Re: LPC1788 Support added to LPC17XX project

« on: November 26, 2011, 10:31:00 PM »

Hi Mark,

That's great news! I've got the EA LPC1788 dev kit - are there any plans to support this as well? If not, I'll try and get something working on that board myself...

The EA board offers 320x240 as well as 480x272 & 800x480 display resolutions ;-)

I'm working on our own hardware based on the LPC1788 (upgrading from the LPC2478) at the moment so having the option to run it on the dev kit would be really helpful!

Cheers,

Jez

9

ST^TM STM32 and STR91XF / Re: STM32 F4 Cortex M4 devices

« on: November 08, 2011, 11:09:41 AM »

Hi Mark,

That sounds like very good progress - from memory the pinouts between F2 and F4 are very similar, there's an RFU pin on some of the F2 parts that needs to be tied to Vdd on the F4 parts but other than that all should be the same.

I've historically found some of the ST peripherals to be a bit limited compared to other vendors offerings though they do seem to be working to address this - at last!

With the Ti and NXP M4 parts sampling soon (some NXP flashless parts are available now in BGA packages) it's certainly hotting up in the M4 arena. It's almost like we're spoilt for choice once more :-)

Cheers,
Jez

10

ST^TM STM32 and STR91XF / Re: STM32 F4 Cortex M4 devices

« on: November 07, 2011, 10:34:44 PM »

Hi Mark,

Thanks for the update - I've got several different F1/F2 dev boards already but only the discovery board for the F4 so far...

We've used the F1 parts for several years already (but only the F103/F105 parts i.e. no ethernet) & generally found them to be a good workhorse for jobs with low I/O requirements & features. So we're very keen to compare the newer parts to our other higher-end parts (NXP/Freescale etc).

When do you hope to have a full release (or even a reasonably complete beta)?

Cheers,
Jez

11

Luminary Micro ^TM LM3SXXXX / Re: Using The Serial Port in uTasker

« on: November 07, 2011, 11:08:17 AM »

Hi Mark,

Thank you for such a prompt & informative response - I will try that (and probably prove the RTS/TS operation first, then move onto teh RS485) and ask if/when I get stuck!

Cheers,
    Jez

12

Luminary Micro ^TM LM3SXXXX / Re: Using The Srial Port in uTasker

« on: November 02, 2011, 11:34:11 PM »

Hi Martin / Mark,

I'm trying to get the UARTs on the LM3S6432 going with
1) RS232 hardware flow control (RTS/CTS in particular)
2) RS485 half-duplex

As far as I can tell, there's no direct support in the UART block for either of these features (unlike many other parts from other vendors) so if either of you can give me some pointers on how best(?) to manage this, I'd be very grateful.

I think there's some code available from Ti to show one form of RTS/CTS control using GPIO pins which I'll try to implement for the first point, but I've not yet found anything to help me with the RS485 direction control.

Cheers,
    Jez

13

ST^TM STM32 and STR91XF / STM32 F4 Cortex M4 devices

« on: September 29, 2011, 10:57:58 AM »

Hi Mark,

ST have (finally) launched their Cortex-M4 range - I'm hoping to get a dev kit soon & see how compatible all the peripherals etc are.

Obviously the core will run Cortex-M3 code directly but I'm not sure how easy t will be to change the simulator over to use the new device.

Is there any information on this please?

Cheers,
    Jez

14

Luminary Micro ^TM LM3SXXXX / Re: What devices & eval boards are supported

« on: September 22, 2011, 10:21:14 AM »

Hi Mark,

That's great - thanks for the update.

Maybe it's worth pinning this info to the top of the Luminary Micro forum for ease of reference?

I'll apply for an eval license for this project & see how I get on with using it on the dev kit.

Cheers,
    Jez

15

Luminary Micro ^TM LM3SXXXX / What devices & eval boards are supported

« on: September 21, 2011, 01:01:16 PM »

Hi Mark,

I've been using / comparing uTasker on a variety of processor families in the past (generally very impressed with it all) but have now been asked to consider some of the TI Stellaris parts (partly due to the integrated PHY and impending availability with Cortex-M4 cores).

I've got a few boards available - newest ones I've been presented with are the LM3S9B96 dev board & LM3S9B90 eval kits - but wasn't sure what was supported or not.

Most of your other supported families have the info pinned to the top of the forum but not this one...

Sorry if I've missed the info in another post!

Cheers,
    Jez