March 22, 2006:

We're using the EnerMatic Controller to operate three engine run-in test stands. Presently just a single engine is being run through the break-in period. The engines are driving 150 Amp, 24V alternators and after engine break-in they will be operating in remote locations with minmal service expected.

Monitoring the EnerMatic Controllers is a small server based on a VIA Technologies Mini-Itx board. A compact flash is used to hold the Linux operating system, and a second compact flash is used for data logging. No hard drive is needed. In fact, the system is running completely fanless because there are a lot of contaminants in the air which we don't want inside the server - the engines are operating in a corner of a steel fabricator with cut-off saws and welders going constantly..

Interface between the EnerMatic and server is over USB/serial adapters, and of course all communications is done using our Remote Access Protocol, RAP. The server is running Apache to provide web access. The presentation served to a browser is done with a custom set of programs written in-house.

Engines can be started and stopped from a browser. For obvious reasons the server is running with encryption and limited user access.

Data to be logged is easily set via a plain text file. Every five minutes plots of the logged data are made for web presentation. Each day log files are zipped up to reduce memory space, and of course files can be downloaded for preservation on another computer. There are actual data files which have been copied from the operating unit to this computer, and the plots from those log files can be viewed.

Besides the data set being logged, access is provided to all of the variables in the EnerMatic Controller. This is shown under a link to `Rap Control'. By typing in the name of a variable its value is returned. Try using b1v as a variable name. The return string is what comes directly from the EnerMatic and is all explained in our document for RAP.

There is also a facility that we call a sequencer. It allows RAP statements for be attached to a time and when that time expires the RAP statement is sent to the EnerMatic Controller. Oil needs to be changed after 50 hours of operation, but who wants to stay up at night to shut an engine down at 50 hours - let the sequencer to it.

Again for obvious reason we're not going to divulge the URL of the engine server, however, we have setup the same software here. The difference is the fact that there is no engine attached. Instead there is one EnerMatic and if it is connected to anything, it's a test jig that provides stimuli used for software testing. Nevertheless, you can get a feel for the EnerMatic/Server system and the monitoring and control capabilites we can provide.

Have fun playing with The EnerMatic and Server