I agree the sensor control and recording should be in a service.
The service communicates to the sensors through activeX. The GUI needs to know nothing about that.
My initial thought seeing as this is not that intensive is you use a table in the database for communicating with the GUI.
The service reads it's configuration from the db and control signals, may be stop/start/restart/ config change.
The gui reads and writes from the config and control tables and does the reports.
Not only complete separation, you have the potential to control the service from any DB-aware application.
If you don't like the db idea, you could use the registry with a polling method in the service, or even couple of files. Event based you are at RPC calls (uggh) or windows messages.
GUI, writes to config and control service reads.
service writes to status and GUI reads
The other thing you need to cope with is there is nothing to stop anyone running the GUI more than once, so you'll need some way of either using a token for control so, only one GUI at at time can do it, or potentially dealing with conflicting commands from several GUIS.
The token idea is nice but you need to deal with it being left set erroneously locking out all subsequent GUIS. If you use a DB, you could easily queue a set of commands for the service, or simply get the GUI to put a lock on the record and then execute or or an inactivity timer drops it.
A few ideas anyway.
Keep the actions the GUI can take as atomic as possible if you go for multiple GUIs, that way there's less chance of a livelock.
Hmmm also if you use the DB for command and control, you can run the GUI from any machine that can access the database, which might be useful.
HTH