On Tue, Nov 27, 2012 at 4:47 PM, Stefan Mahr <dac...@gmx.de> wrote: >>>> For those wanting an open source (GNU) alternative to NI closed >>>> source code here is a VXI11 set of source code by Steve D. >>>> Sharples. The linux package can be compiled on Cygwin/Windows. >>>> Hopefully this can be of use to someone. >>> >>> Did you read the start of this thread? >>> >>> As you can see at >>> >>> https://github.com/dac922/octave-instrument-control-toolbox/blob/master/vxi11_tb/build.sh >>> >>> I use this package for my octave VXI11 toolbox. >> >> Is this exclusively the only package you use? Does your code link to >> non-free libraries? If it does link to non-free libraries, please take >> it down, as this is a GPL violation. >> > > vxi11_tb uses source code from Steve D. Sharples VXI11 library. Except of > vxi11.x (which has it's own open source license) all GPL. > > gpib_tb uses linux-gpib (GPLv2) > > usbtmc_tb and tcp_tb uses libc > > dummy visa_tb uses openvisa (GPLv2) > > >>>> It would be more useful if you could add your code to the existing >>>> instrument-control package in OF and merge your instrument-control >>>> with the one that Andrius Sutas wrote for SOCIS. >>>> >>>> Do you have the time and interest to do so? >>> >>> I have ported the TCP and USBTMC part. Could you take a look, >>> please? >> >> Andrius Sutas or Juan Pablo Carabajal may be better qualified than I >> to judge this contribution. I am CC'ing them here. > > OK > >> As an aside, it's not "GNU/Octave". There should be no slash there. >> The slash in "GNU/Linux" is meant to indicate that the operating >> system is a combination of GNU with the Linux kernel. "GNU Octave" >> isn't an operating system of which Octave is a kernel; it is merely a >> GNU package. > > done > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > _______________________________________________ > Octave-dev mailing list > Octave-dev@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/octave-dev
(I edited the topic to move out of the previous thread) Hi Stefan, This is so great! I do not have a card to test around (old INES DAQ, but never got them to work under linux), I will take a look at the tcp part. I suggest the following plan: 1.- Integrate your code to the current instrument-control package (Andrius and Stefan, are you ok with this?) a. I suggest we use the sub-package structure that, for example, geometry has (http://sourceforge.net/p/octave/code/11459/tree/trunk/octave-forge/main/geometry/inst/). b. We will need to update the makefile in the top folder to deal with the new subfolders. 2.- Update the wiki with Stefan contribution http://wiki.octave.org/Instrument_control_package (Stefan, do you think you can complete the box just at the beginning? Maybe add a new color for "Testing") a. Ideal here is to have tutorials/demos (like the ones in the wiki or this one for serial http://youtu.be/d1If8XOL73c). Stefan, have you ever look at comedi? They used to support many NI cards, where there also using proprietary libraries? Is there we can scavenge something from that project (it has been abandoned for a long while)? We are on the move! ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
