| Products > Test Equipment |
| Open source lxi-tools and liblxi v1.0 released for GNU/Linux |
| << < (32/67) > >> |
| lundmar:
Siglent Technologies has kindly lent me their new SDS1204X-E oscilloscope (200 MHz, 4 channels) to help the lxi-tools open source effort :-+ I hooked it up, calibrated the 4 included probes, and after enabling the network interface (DHCP) it was easily discovered with lxi-tools. It turns out that this is an absolutely blazingly fast scope, especially in terms of LXI/LAN SCPI command processing performance! With the benchmark feature I'm getting ~1100 requests/s via TCP/VXI11: --- Code: ---$ lxi benchmark --address 192.168.1.125 Benchmarking by sending 1000 ID requests. Please wait... Result: 1123.5 requests/second --- End code --- And I get ~600 requests/s via TCP/RAW: --- Code: ---$ lxi benchmark --raw --address 192.168.1.125 Benchmarking by sending 1000 ID requests. Please wait... Result: 1123.5 requests/second --- End code --- This is quite impressive. Compared, the performance of e.g. the Rigol DS1054Z is ~30 requests/s via TCP/VXI11 and ~160 requests/s via TCP/RAW. Of course, the faster performance is to be expected from a newly released scope which clearly uses a newer and faster chipset. However, fact still is, it is very fast and it is one of the first low cost scopes that makes it possible to easily implement a poor-mans data logger using LXI/LAN polling that can consistently sample data at e.g. 100 Hz or more. I also notice that Siglent uses standard LXI ports as defined here: http://www.lxistandard.org/About/LXI-Protocols.aspx That is, the available network ports for the SDS1204X-E are: --- Code: ---$ nmap -p- 192.168.1.125 Starting Nmap 7.60 ( [url]https://nmap.org[/url] ) at 2018-01-08 15:18 CET Nmap scan report for 192.168.1.125 Host is up (0.042s latency). Not shown: 65529 closed ports PORT STATE SERVICE 23/tcp open telnet 80/tcp open http 111/tcp open rpcbind 918/tcp open unknown 5024/tcp open scpi-telnet 5025/tcp open scpi-raw Nmap done: 1 IP address (1 host up) scanned in 40.14 seconds --- End code --- In particular, they use standard port 5025 for SCPI/RAW and port 5024 for SCPI/telnet. This is one of the odd things that Rigol fails to do for the DS1054Z (they place it on non-standard port 5555): --- Code: ---$ nmap -p- 192.168.1.210 Starting Nmap 7.60 ( [url]https://nmap.org[/url] ) at 2018-01-08 15:19 CET Nmap scan report for 192.168.1.210 Host is up (0.080s latency). Not shown: 65529 closed ports PORT STATE SERVICE 80/tcp open http 111/tcp open rpcbind 617/tcp open sco-dtmgr 618/tcp open dei-icda 619/tcp open compaq-evm 5555/tcp open freeciv Nmap done: 1 IP address (1 host up) scanned in 40.54 seconds --- End code --- Taking a screenshot with the SDS1204X-E is very fast too: --- Code: ---$ time lxi screenshot -a 192.168.1.125 Loaded siglent-sds screenshot plugin Saved screenshot image to screenshot_192.168.1.125_2018-01-08_15:37:22.bmp real 0m0,141s user 0m0,004s sys 0m0,024s --- End code --- Only ~0.14 second! It's also nice to see that the Siglent scope has a small and light form factor which feels solid. My first impressions are good - I'm looking forward to more testing with this instrument during the development of the GUI frontend for lxi-tools. It will also make a nice addition to the pool of instruments that I plan to use for lxi-tools performance and regression testing. |
| BloodyCactus:
just because, why not :P R&S HMO1202 (which seems surprisingly slow...) --- Code: ---[ sgeorge @ workstation ] - [ ~/git/rai1/c64_c128_plus4 ] (master*) [$]> lxi --version lxi v1.17 [ sgeorge @ workstation ] - [ ~/git/rai1/c64_c128_plus4 ] (master*) [$]> lxi benchmark --address scope.cactus Benchmarking by sending 100 ID requests. Please wait... Result: 13.9 requests/second [ sgeorge @ workstation ] - [ ~/git/rai1/c64_c128_plus4 ] (master*) [$]> lxi benchmark --raw --address scope.cactus Benchmarking by sending 100 ID requests. Please wait... Result: 12.6 requests/second [ sgeorge @ workstation ] - [ ~/git/rai1/c64_c128_plus4 ] (master*) [$]> nmap -p- scope.cactus Starting Nmap 7.01 ( https://nmap.org ) at 2018-01-08 20:39 EST Nmap scan report for scope.cactus (192.168.0.107) Host is up (0.0022s latency). Not shown: 65530 closed ports PORT STATE SERVICE 80/tcp open http 111/tcp open rpcbind 1024/tcp open kdm 1025/tcp open NFS-or-IIS 5025/tcp open unknown Nmap done: 1 IP address (1 host up) scanned in 11.73 seconds --- End code --- |
| lundmar:
--- Quote from: BloodyCactus on January 09, 2018, 01:46:53 am ---just because, why not :P R&S HMO1202 (which seems surprisingly slow...) --- End quote --- He he - that is truly slow! That must be the lowest benchmark scores I has seen so far. I'm not that surprised though - well established big company instrument manufacturers like R&S tend to over engineer things and this sometimes leads to over engineered cost reduction. Likely their instrument is featuring a low cost, low performance application/communication processor or their application/network stack is horribly inefficient - I think the former is probably the case. |
| ralphrmartin:
Another instrument for you: Keysight 34461A multimeter. Discovery works fine. Sending scpi commands seems OK (e.g. *IDN? returns the expected ID string). Trying to take a screenshot results in it trying to use the rigol-1000Z plugin, and thence timeout. Telling it to use the keysight-ivx plugin gave the same result. Doing a benchmark gave a result of 45.1 requests a second. |
| lundmar:
--- Quote from: ralphrmartin on January 09, 2018, 05:12:56 pm ---Another instrument for you: Keysight 34461A multimeter. Discovery works fine. Sending scpi commands seems OK (e.g. *IDN? returns the expected ID string). Trying to take a screenshot results in it trying to use the rigol-1000Z plugin, and thence timeout. Telling it to use the keysight-ivx plugin gave the same result. Doing a benchmark gave a result of 45.1 requests a second. --- End quote --- Thanks. If you share the ID string that this instrument returns then I can fix the plugin matching part. It looks like we need to create a new screenshot plugin for this instrument as it handles screenshots differently from the oscilloscopes. EDIT: I have added a new screenshot plugin "keysight-dmm" that should work with your 34461A multimeter. Let me know if it works for you. |
| Navigation |
| Message Index |
| Next page |
| Previous page |