24/7 system
Isaac
I am developing a medium system for a factory that work 24/7 so I need
to make sure my software did not crash or hangup by any mean so what is
the measures I should place in my software ?
any suggestion are welcome
Thanks
Krisztian Pinter
> I am developing a medium system for a factory that work 24/7 so I need
> to make sure my software did not crash or hangup by any mean so what is
> the measures I should place in my software ?
you find a property of TApplication named "NeverFail". set it to true.
Isaac
Thanks Krisztian, any advises are welcome
Ray Marron
news:op.t6w27bq6obk3tt@karwst_pint2...
You owe me a keyboard! :o)
--
Ray Marron
Isaac
> You owe me a keyboard! :o)
>
!!!! why ?? did your old keyboard is broken by me !!! :)
Ray Marron
news:47bf...@newsgroups.borland.com...
> Ray Marron wrote:
>> You owe me a keyboard! :o)
>>
>
> !!!! why ?? did your old keyboard is broken by me !!! :)
Your humorous reply caused me to spit coffee all over it!
--
Ray Marron
Isaac
coffee any more again , you choose :)
seriously: about my topic I suggest my customer to buy UPS to prevent
data loose is there something else I should do in my software to prevent
crash or hanging specially when I am connecting to RS232 com ports
Krisztian Pinter
> seriously: about my topic I suggest my customer to buy UPS to prevent
> data loose
UPS, raid system, failsafe power supply, and bluescreen-safe operating
system
are good. but they DON'T make your data safe. they only reduce the recovery
costs, simply with making data recovery a less frequent operation.
no matter how safe your hardware is, you need to have plans for data loss.
> is there something else I should do in my software to prevent crash or
> hanging specially when I am connecting to RS232 com ports
a lot. designing safety critical and mission critical software is a
complete
branch in computer science. should your application corrupt any of its
data,
run on an unexpected code-branch, leave one uninitialized variable, and the
behaviour is unpredictable. garbage can be communicated over the rs232, or
can be written in any files, logs, etc. hangs, or crashes can occur. there
is
no silver bullet against bugs. there are methods that can minimize and help
detect bugs. the entire software design phase should be done with safety
issues in mind.
more to that, windows is no real time OS. you never can guarantee that your
thread will get CPU time when needed.
Arthur Hoornweg
> Hello,
> I am developing a medium system for a factory that work 24/7 so I need
> to make sure my software did not crash or hangup by any mean so what is
> the measures I should place in my software ?
On the hardware side, a UPS and a software that cleanly shuts down the PC
if the battery goes empty to prevent HDD damage.
On the software side, implement a "watchdog" application. This watchdog
application should communicate with your main application in regular time
intervals to see if it is still alive. Use sockets or named pipes for the
communication.
If it finds that the main application doesn't answer, it can undertake
action
such as killing/restarting the task or even rebooting the PC.
A hardware watchdog, connected to a serial port, is even better.
--
Arthur Hoornweg
(In order to reply per e-mail, please just remove the ".net"
from my e-mail address. Leave the rest of the address intact
including the "antispam" part. I had to take this measure to
counteract unsollicited mail.)
DelphiUser
architecture.
I have a system running which has
DB-Server
Application-Server
40-60 Fat-Clients
Products are connected by serial-port or lan.
At the beginning the DB-Server and the Application-Server were located on
different machines.
To improve the situation we later installed both (DB-Server and Application
Server) on the same machine.
"Isaac" <as...@fsdf.com> wrote in message
news:47bd...@newsgroups.borland.com...