Staopping and Starting the K8062

Hi,

in this thread “VM116–>K8062d.dll freezing issue” it is noted that there is a problem with the K8062 becoming unresponsive and requiring a restart (unplugging, and re-pluggin the DMX cables for example) “when using the StartDevice and StopDevice repeatedly.”

Do we have a more formal dexription of what constitutes “repeatedly”? Is it (as I suspect) a problem of interleaving concurrent start and stops, or is there a maximum number of start and stops a second, or some other limit? On a similar note is there a problem with starting the device and never stopping it?

I ask as I am controlling the device from a web application that will be running 24hrs a day 7 days a week, this application will go through periods of heavy usage of the device and periods of realtively low usage. If there is no problem with starting the device and never stopping it then I’ll just start the device when the webapp gets loaded and never bother stopping it. If this is not acceptable then I need to implement some sort of limiting on the device interface to prevent many webapp users from spaming the controls and potentially causing the device to become unresponsive as described in the thread above. I would need to know the actual limits though in order to code this limiting function correctly.

Thanks for any help you can provide,

Simon.

The StopDevice is meant to be used only when the application program is closed.
The main purpose of the StopDevice is to terminate the K8062e.exe program.
The K8062e.exe acts as a link between the K8062D.dll and the USB.

[quote]If there is no problem with starting the device and never stopping it then I’ll just start the device when the webapp gets loaded and never bother stopping it.[/quote]There is no problem if you keep the application running forever and never use the StopDevice.

Thanks for the clarification.

Are there any issues with calling startDevice several time without any intermediate stopDevice calls?