My application receives and displays Heart sounds and ECG's in real time.
This data comes from a proprietary USB 2.0 device. Unlike most USB devices,
this data comes in short bursts of about 24 bytes. These bursts could come
as fast as every millisecond.
The display of the sound and ECG traces is similar to an oscilloscope
display except a blank space of about 5 pixels is shown as it sweeps across
the screen. This means that not only is six horizontal lines drawn for each
trace, for each data burst, but the next six existing horizontal lines have
to be blanked.
The above equates to around 300 Heart Beats per Minute (BPM). This is easily
handled by my VB6 application.
Using VB2005 Pro I have attempted to convert this VB6 app. As of now I use
shared memory, an in process thread to capture data from the USB and an
ActiveX thread to interface with the USB. I have attempted to do the drawing
with GDI, DirectX, etc.
The best I can get is a 15 BPM heart rate.
I am contemplating doing the drawing in my ActiveX thread. The idea being
that all of the data capture and drawing is, in effect, being done via VB6.
But if I do this then the VB2005 portion becomes one of just showing forms
with Command buttons and Text boxes etc. But my VB6 app already does this.
So my question is, what's the benefit of converting this app to VB.NET?
Apparently I can use the Interop Toolkit on my VB6 app instead of converting
to VB2005. What's the benefit in doing that?
As an aside, 99% of the customers have us buy a computer and install the
software at the factory. Then the computer is shipped to them. So no
installation problems.
I would appreciate any comments pro or con.
Thanks
Galen
This data comes from a proprietary USB 2.0 device. Unlike most USB devices,
this data comes in short bursts of about 24 bytes. These bursts could come
as fast as every millisecond.
The display of the sound and ECG traces is similar to an oscilloscope
display except a blank space of about 5 pixels is shown as it sweeps across
the screen. This means that not only is six horizontal lines drawn for each
trace, for each data burst, but the next six existing horizontal lines have
to be blanked.
The above equates to around 300 Heart Beats per Minute (BPM). This is easily
handled by my VB6 application.
Using VB2005 Pro I have attempted to convert this VB6 app. As of now I use
shared memory, an in process thread to capture data from the USB and an
ActiveX thread to interface with the USB. I have attempted to do the drawing
with GDI, DirectX, etc.
The best I can get is a 15 BPM heart rate.
I am contemplating doing the drawing in my ActiveX thread. The idea being
that all of the data capture and drawing is, in effect, being done via VB6.
But if I do this then the VB2005 portion becomes one of just showing forms
with Command buttons and Text boxes etc. But my VB6 app already does this.
So my question is, what's the benefit of converting this app to VB.NET?
Apparently I can use the Interop Toolkit on my VB6 app instead of converting
to VB2005. What's the benefit in doing that?
As an aside, 99% of the customers have us buy a computer and install the
software at the factory. Then the computer is shipped to them. So no
installation problems.
I would appreciate any comments pro or con.
Thanks
Galen
Comment