The vxi-11 that you referred is still a python library. Wrapper or not.
there is a python file as an example on how to call it, but its not a python library. well, I guess in a sense it is, since any C library is callable from python.. or ruby.. or lua.. or perl..
hey, that makes yours, also a python library! cool no?
liblxi is a higher level abstraction which does away with some of the intricate details of the vxi11 C module.
how is it higher, how will it make my life better if I switch my code over? I mean, libvxi11 gives me all I need to communicate with a vxi/lxi device.... open, send/recv, close.. what intricate details does it do away with in libvxi11?
I'm trying to get you to explain why its better than the well known pre-existing library, but I need more than a vague 'intricate details' answer.
say we want to connect to rigol scope, grab its identifier string, send say 10 other commands to setup channel 1, turn it on whatever, some bunch of arbitrary calls then quit.
with libvxi11, I open device, send the commands, read data etc, close device. those are the core steps. as basic as it gets.
how would that change with yours? do I not need to open the device? send/recv? close?
just trying to find out what makes it better/easier?
(I mean, I have a large project using it as the core to talk ethernet over gpib, if its better, I'll switch in a heart beat!
https://www.eevblog.com/forum/projects/a-fancy-gpib-psu-front-end/) Im asking because I want to know, not because I want to be an ass about it