From: Mathias G. <mg...@za...> - 2013-11-02 20:15:14
|
Hi Martin, Martin Ling writes: > On Fri, Nov 01, 2013 at 08:36:53PM +0100, Mathias Grimmberger wrote: > > > > What I implemented now is to recognize whether the scope is already > > stopped and decide from that. We don't have the capability to completely > > configure the thing anyway, so may as well take some hints from how the > > user has set up the device. Complete configurability should wait for the > > LibreVISA version, there are just so many options I don't think it's > > worth implementing everything twice. > > The change to using librevisa isn't going to affect the driver code > much, it's just the transport. Basically rigol_ds_send will switch to > using librevisa to send its messages and the serial_read calls will be > replaced with some other librevisa call. But the content of the protocol > will be the same, so things implemented now will not be wasted. Ah, OK, didn't understand that. > > AFAIK the software uses the NIVISA runtime. NIVISA should come with a > > nifty tool called "nispy.exe" or similar - it does what the name > > suggests. > > It I think that will show the higher level queries made to the driver, > I'd be more interested in what it's actually sending on the wire to the > device. But I may give it a try at some point. Yes, it will show the VISA calls. To see the wire stuff you could sniff USB, Wireshark on Linux can do this AFAIK, should work with the Windows SW inside something like VMware Player. For RS232 I don't know, but certainly some way must exist. MGri |