Products > Test Equipment
Open source lxi-tools and liblxi v1.0 released for GNU/Linux
lundmar:
--- Quote from: PeDre on December 10, 2017, 05:38:50 pm ---Hello Martin (lundmar),
just for your information.
The Rigol DM3068 only works without a waitlock flag. The flag may be set automatically when the VXI connection is established. The waitlock flag is used by many VXI functions as a parameter, e. g. device_read, see parameter Device_Flags.
The DM3058 may not work because of this. I have not received any feedback from anyone about this device and my program.
My VXI-simulator ignores this flag. The Rigol DS6000 and DG4000 with old firmware are also affected.
Peter
Edit:
What I wrote can't be the mistake. The IDN is received by the Rigol DM3058,
so the waitlock flag isn't the problem.
--- End quote ---
Ahh right, yes - the DM was the one you simulated. Either way, I've disabled any locking requests during establishment of the VXI-11 connection. It might fix the issue.
lundmar:
--- Quote from: crispus on December 10, 2017, 05:57:03 pm ---If helps, I updated the firmware to the latest version and same error (timeout).
On MSO1104Z-S, DG4062 and DSA815 screenshot works with no problem.
--- End quote ---
Ok. I've updated liblxi so that the lxi_connect() function does not try to set up any locking during establishment of the VXI-11 connection. Please update and try it out.
In case you don't want to bother with manual compilation the snap version should already be available on the edge channel.
Snap build status can be monitored here: https://build.snapcraft.io/user/lxi-tools/lxi-tools.snapcraft
lundmar:
Doh!
I've just studied the documentation for DM3058 and DM3068.
It seems that the SCPI command that we use to request screenshot data ":display:data?" is actually not supported on these instruments.
It might be an undocumented feature but it does not seem to be the case.
Looks like we will have to remove the rigol-dm3000 plugin.
@PeDre , you agree?
lundmar:
--- Quote from: lundmar on November 09, 2017, 10:55:11 am ---
--- Quote from: dpenev on November 09, 2017, 08:39:41 am ---lxi screenshot -a 192.168.1.59 -m rigol-2000 #Works fine now
1. Can there be a option for png instead of bmp? png are smaller.
--- End quote ---
The image format depends on which formats the instrument supports. PNG is certainly the preferred format but not all instruments support it. The Rigol 2000 series supports PNG for internal storage of screenshots but it is not documented whether it is possible to retrieve PNG remotely. Please try out the '"rigol_2000_png" branch and let me know if it creates a proper PNG for you. If not I'm afraid it is not possible unless the lxi tool itself starts doing BMP->PNG conversion but I think that is a bad idea. I would rather provide the raw material straight from the instrument and then the user can do as they please.
--- End quote ---
Update: The screenshot command now supports redirecting the screenshot image data to stdout. To do so simply use '-' as the output filename. This means it is now possible to pass on the captured image to external tools for image processing, such as converting it to a different image format. For example, to convert to .jpg using imagemagicks convert tool:
--- Code: ---$ lxi screenshot --address 10.0.0.42 - | convert - screenshot.jpg
--- End code ---
This feature will be included in the upcoming release. It is already available in the snap edge channel.
lundmar:
--- Quote from: PeDre on December 11, 2017, 06:41:09 am ---
--- Quote from: lundmar on December 10, 2017, 08:15:08 pm ---Looks like we will have to remove the rigol-dm3000 plugin.
@PeDre , you agree?
--- End quote ---
I have received feedback from two users that the Rigol DM3068 (Firmware 01.01.00.01.08.00.01 and 01.01.00.01.09.00) with the SCPI command ":DISP:DATA?" and my program works. This applies to the LAN and USB connection.
Peter
--- End quote ---
Ok good - so it is just an undocumented feature.
--- Quote from: PeDre on December 11, 2017, 08:49:36 am ---I found Wireshark protocols in my records.
The error was the timeout when creating the connection (CREATE_LINK). The timeout could then be used for write or read commands.
Peter
--- End quote ---
Ok, then my latest changes should hopefully solve the issue.
Thanks for the helpful input Peter :-+
@crispus, Please test latest git or snap and let us know if works or fails. Also, thank you for testing :-+
Man, I wish I had more instruments so I could create a small lab with various instruments for regression and feature testing.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version