Re: Emulate seriel communication

From: Roger Lascelles (r.o.g.e.r.l.a.s._at_optusnet.com.au.removedots)
Date: 10/31/03 

Date: Fri, 31 Oct 2003 14:23:53 +1100

I have met the same issue - even producing an entire complex project without
ever having access to the device on the other end of the RS232 line. I
prefer to put two computers on my desk, connect them with RS232, fire up
Delphi on both, but you can manage with one computer with a cable between
the serial ports.

One computer runs the emulation application, which in your case is the
"production computer". The other computer runs the app you are developing.
First start writing the emulation app. You have to get all the details
right - response time, reply to commands etc - whatever the protocol may
be. When you have enough built, you can start work on your main app. Both
ends will have bugs, but gradually the emulation app will settle down and
you can work mostly on the main app. I use iterative development, where I
get the basic comms structure working, then develop other layers as demanded
by the main app.

The emulation screen can display controls to let you setup for particular
situations. In an extreme case, the emulation app may need to be script
driven - or you can write the mods straight into the Delpi code, compile and
run. The emulation app must be able to create fault scenarios such as error
codes and no reply so you can test your main app error handling.

Roger

"Lasse" <lars.makiaho@kpwood.com> wrote in message
news:3fa17fce@newsgroups.borland.com...
> Hi,
> I am looking for something that can emulate series rs232 communication. I
am
> building a application that are going to communicate with a production
> computer using rs 232, the problem is that I dont have access to it. I
> wonder if there is such device that I can setup to emulate the production
> computer?
> Lasse
>
>

Relevant Pages

  • Re: The curse of constant fields
    ... production branch, EAR construction etc) for a reasonably important J2EE app I am pretty fanatic about sanitizing everything prior to an official build. ... our environment it would be unrealistic. ... Because a lot of time can be wasted if a tester reports that an error is still there, and then it's a question of is the error still there because the build is flawed, or because the developer who "fixed" it only fixed it for a different use case or in his own development environment. ...
    (comp.lang.java.programmer)
  • Re: Homegrown synchronization
    ... my launcher just copies the production backends as is. ... What you need is to have the synch app zip up the production ...
    (microsoft.public.access.replication)
  • Re: The curse of constant fields
    ... EAR construction etc) for a reasonably important J2EE ... No automated testing of the complete app through its web ... Also, presumably, before you deploy to production, you deploy to a staging ... or pre-production environment which replicates the production environment, ...
    (comp.lang.java.programmer)
  • Credentials being lost between servers - out of ideas!
    ... I have a webservice in production that is working great. ... I have a web app that works when it is on the same server as the web ... I have my app set up to impersonate, using windows authentication, and I ... The same error message is received. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • simple pro tools set-up for radio production???
    ... adopted by default as the defacto 'standard' for the most part - for ... to a simple straightforward broadcast production user interface. ... move to some computer based daw app. ... ProTools is filled with features i have no need for. ...
    (rec.audio.pro)