Reqeust for RTEMS applications was Re: RTEMS : Development areas

Paul Whitfield paulw at microsol.iinet.net.au
Thu Nov 14 01:10:08 UTC 2002


Joel Sherrill wrote:
>>eigu,
>>    I'm not experienced in RTEMS, but a google search on the topic also resulted in vain. But it seems that you are not the only one having this doubt. See,
>>http://www.rtems.com/rtems/maillistArchives/rtems-snapshots/1999/august/msg00094.html . Joel Sherill has posted the same question to the list, and no
>>response to that too.. But there's no reason that I should believe a 3+ years old RTOS has no commercial users. Let's wait for the feedback from others.
> 
> 
> That's not true at all.  There are lots of systems unfortunately, people
> don't always step forward every time someone asks this question.  I have
> a web page with a list of the systems people tell me about, are willing
> to let it out publicly that they are using RTEMS, and have some info on
> the web.  I am not the best at keeping this up to date as I have not
> updated it to reflect the Philips critical care patient monitor or 
> the Australian FedSat program.  There are also a number of networking
> products that use RTEMS but don't want to discuss it.  RTEMS seems to
> have become popular in the satellite community.
> 
> This is the short list of applications that have told me they want
> to be on the list (http://www.oarcorp.com/~joel/rtems/apps.html)
> and have published enough info to be interesting.  You can also
> tell from published papers
> (http://www.oarcorp.com/~joel/rtems/refs.html)
> which includes a number of systems which we wouldn't know about
> otherwise.

For the record, Microsol Ltd, an international company with offices in 
Ireland and Australia, is using RTEMS as a base for our next generation 
of products.

These products as Remote Terminal Units that are used mainly by the
Electrical Utility Sector to control Electricity Networks.

Our products need to communicate using multiple standards based and
proprietary protocols.

Some of the reasons for choosing RTEMS were (in no particular order):

- Cost (including development tools and network stack)
( especially avoiding on-going royalties )
- "Compatibility" with existing RTOS
- Availability of source code of the kernel
- Good support of the Coldfire Processor (5307)
- The ability to put together a package that will enable
third parties to develop for our product

Joel Feel free to add this information to your application collection if 
you like (note: the main corporate web site makes no mention of RTEMS, yet!)

Best regards


Paul Whitfield




More information about the users mailing list