hi, i need [mpusbapi.dll] to use in c# project.
but i can’t find this file or is incorrect file.
can you help me to find this file?
You can find it in velleman.be/downloads/files/ … ftware.zip
Dont know for what card you need it. K8061? i use k8061_C.dll (with k8061)
Write separate class library (to re-use it 
) with:
[code]using System.Runtime.InteropServices;
…
[DllImport(“mpusbapi.dll”)]
private static extern unsafe UInt32 OpenDevice();
… (and all the other methods you use)[/code]
dont forget to put dll in the projectname\bin\Debug folder of your project by adding a reference to your new class library.
for contacting within mobil & pc, i need that.
thank you my friend,thank you so much 
Hi
Just wondering if anyone might be interested in doing a small paid project. Simply an implementation of the sample in the k8055dll_rev3_0_2 download, available here velleman.be/be/en/download/files/
Any offers welcome.
Thanks in advance.
Hi Sashah,
do you mean the heavy dialog?
By the way - I guess we have a solution about our .NET implementation.
I’ll contact you by email later this week (or latest on weekend).
Regards
Manfred
Please let me know of any news on your .NET implentation too. I’d gladly beta test, and buy the resulting code if it works ok.
The reason I’m asking is that I’m running two K8055 cards in a multithreaded app in VB.net 2008. Each card is called by a separate class, but each class obviously loads the K8055D.DLL in its implentation. I’m guessing from the posts here that therefore only one instance of K8055D.DLL is actually open.
I’m getting some strange intermittent errors (such as random digital outputs momentarily triggering) which is a serious problem. Looking at previous posts, this looks like a problem caused by two threads accessing the same DLL at the same time and causing clashes I expect. I could do what’s suggested in an earlier post and create multiple copies of the DLL, but will this solve the problem?
I’d obviously be very interested in a fully fledged .NET assemlby instead that supports multithreading. So again, please let me know if this comes to fruition…
Phil
I know I this may be slightly offtopic, but Manfred, after reading this thread I must tell you it is a breath of fresh air to see such an obviously intelligent person taking the time to provide informative useful and even innovative details on a subject that for most of us has been thrust upon us by the stupid desire to hook ‘something’ up to our PC’s.
I have only just learned how to access the K8055D’s native dll using C++ in the Devcpp ide on a Vista OS. My mother always told me that my eyes were bigger than my stomach, but even as I am only just now creating learning apps for interacting with K8055D board, I have considered how will I progress in my quest for a more ‘machine’ level interaction with a board that obviously has (albeit minor) attempts to frustrate people going beyond the supplied dll interaction. This thread has given me real examples, and even more motivation to interact with the K8055D on this more intimate level.
your grasshopper,
Colin
I might be getting too technical here but,
The MPUSBOpen function of the mpusbapi DLL returns a handle to a device. This is either a kernel object or a pointer to a structure that identifies the device you just opened. This is quite common in Win32 programming; for example: if you open a file, you get a handle to that specific file which you can then use to perform read/write operations.
The K8061 probably keeps an array with all the handles you opened, to shield you from having to worry about them, eg. you only pass the array index.
If i remember correctly it is possible to find the source code for the mpusbapi dll (mpusbapi.h and mpusbapi.c) on the internet. Try Google or Google Code.
Hi,
a long time passsed - but too finalize this thread I want to let you know that we finally decided to sell the component.
The reason why it took some time was that microsoft released Expression 3 a great WPF tool which enables to bind data to controls via “drag and drop”.
And we wanted our component to support those new features - which took some time for development and testing.
And so it looks:
Furhter 64bit support and windows 7 support took some time.
Although we have been ready with the windows 7 CTP - we wanted to wait for the RTM to finish our tests.
I’ll be back with closer information in the next days.
Regards
Manfred
