Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- From: "TJC Support" <jvsREMOVE@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 7 Feb 2006 09:00:51 -0600
"Larry" <l@xxxxx> wrote in message news:43e8ab05$1@xxxxxxxxxxxxxxxxxxxxxxxxx
Sounds like you have an interesting job. Much more interesting than us
boring client/server business software writers! I'm quite interested to
know what tools to you use and how you communicate with these embedded
systems? And since we're on the topic, have you ever investigated talking
to these systems from the .NET framework?
There are two different systems that I work with. The first is the data
acquisition system, which is an in-house developed system. The data
collection part is a VME chassis with the CPU running VxWorks realtime
operating system (Unix derivative), and the code for that is written in C.
The piece of the system that I deal with most is the control & display unit,
which is a PC running Windows, and the software is written in Delphi.
Communication between the two is via ethernet, and software-wise it is
simple TCP/IP blocking sockets, with a proprietary communication protocol.
Not much likelihood of changing the communication methodology between the
two due to the difference in the two systems and the company's belief in the
"if it ain't broke, don't fix it" philosophy.
The other system is built into the airplane, and thus is governed by
extremely strict certification requirements from the FAA. The hardware is a
32 bit Intel CPU running a proprietary OS that is a Unix derivative. Code
is C or C++ depending on the age of the system. This system only
communicates with other parts of the airplane on a proprietary data bus.
The last app that I work with is a PC-based app that is written in Delphi
and allows the user to do aircraft performance calculations that are a part
of the required preflight planning. This app _could_ be reinvented as a
..NET app, but there's just no real reason at this point to do that,
especially since it doesn't communicate with anything else, other than to go
to the web and download and display weather graphics from NOAA (simple file
download). We expect to go through an FAA certification process with this
software in the near future, and that increases the likelihood that cert
requirements will force it to be more of a closed system than it currently
is. I did have thoughts of creating a Pocket PC version of the program, and
possibly use CF to do that, but the cert issue is going to kill that idea.
BTW, some days I'm bored to tears and have to go to the gym and shoot hoops
for a while to clear the cobwebs. :^)
Van
.
- References:
- Prev by Date: Re: MS Project Server
- Next by Date: Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- Previous by thread: Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- Next by thread: Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- Index(es):
Relevant Pages
|
Loading
