Once installed, when using a ut71c and a ut-do4 usb cable you can then run the program by: cd 'buildfolder'./sigrok-meter -d uni-t-ut71c-ser:conn=1a86.e008 -continuous or -frames 5 is you are using a different cable ut-do2 plus r232 to usb, locate the usb device in question by: lsusb and replace 1a86.e008 with the right adress.
Posted by3 years ago
Archived
I am embarking in writing a library to enable communication with a number of different medical devices which mostly speak some serial protocol and some USB. The main aim is:
Flexibility, making the library as cross platform as possible.
Encourage contribution to the code base without tie the library to some specific high level language (read Java,Perl,Python).
Release the code under the terms of some Free Software license
My choice of programming language to implement such a thing would be C , mainly because of point 2 above. Point 1 would be achieved with the help of libserialport and libusb, which effectively provide a plaftform agnostic layer for device communication.
Given that I haven't previous experience in developing a C cross platform library, I'd like to hear some pro/cons of this approach. My prevision is that following this path I'll be safe from much of the problems/work necessary to keep in sync the subtleties of the various platforms simply by taking advantage of those communication libraries. Am I missing/forgiving something about the cross-platform intricacies in this case?
I'm also particularly interested in hearing some experience on how much work it takes to build relative wrappers libraries, in particular the Java case seen that one of the main program to make use of the library will be written in Java (JNI?). I've heard of SWIG but I have no experience at all with it or with similar tools
Any valuable suggestions and experience are very welcome on these points.