| 01:31.45 | *** join/#qi-hardware archang (~archang@123.150.208.141) |
| 02:17.10 | *** join/#qi-hardware xiangfu (~xiangfu@101.36.77.37) |
| 02:36.14 | *** join/#qi-hardware rejon (~rejon@230.sub-70-195-69.myvzw.com) |
| 02:38.35 | *** join/#qi-hardware atommann (~atommann@116.24.8.165) |
| 03:26.59 | *** join/#qi-hardware atommann (~atommann@113.87.143.74) |
| 04:46.52 | *** join/#qi-hardware wpwrak (~werner@154-164-231-201.fibertel.com.ar) |
| 05:17.33 | *** join/#qi-hardware jekhor (~jek@nat-minsk-pool-46-53-200-14.telecom.by) |
| 06:43.30 | *** join/#qi-hardware FDCX (~fdcx@2a02:2f0a:a02f:ffff::54e8:d28c) |
| 07:38.35 | *** join/#qi-hardware FDCX (~fdcx@2a02:2f0a:a01f:ffff::5679:1df2) |
| 07:49.55 | *** join/#qi-hardware jekhor (~jek@nat-minsk-pool-46-53-200-14.telecom.by) |
| 08:07.36 | *** join/#qi-hardware FDCX (~fdcx@2a02:2f0a:a02f:ffff::bc1a:af31) |
| 08:25.56 | *** join/#qi-hardware wolfspraul (~wolfsprau@brln-4d0732be.pool.mediaWays.net) |
| 08:28.47 | *** join/#qi-hardware jekhor (~jek@nat-minsk-pool-46-53-200-14.telecom.by) |
| 08:32.11 | *** join/#qi-hardware xiangfu (~xiangfu@114.54.18.141) |
| 08:46.05 | *** join/#qi-hardware xiangfu (~xiangfu@106.38.205.45) |
| 08:51.33 | *** join/#qi-hardware atommann (~atommann@58.250.80.106) |
| 09:01.06 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 09:26.45 | *** join/#qi-hardware jluis (~jpddb@83.247.136.72) |
| 09:30.10 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 10:40.40 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 10:49.54 | *** join/#qi-hardware jluis (~jpddb@83.247.136.72) |
| 10:54.59 | *** join/#qi-hardware jekhor (~jek@port-61-adslby-pool38.infonet.by) |
| 11:01.24 | *** join/#qi-hardware jluis (~jpddb@83.247.136.72) |
| 11:29.08 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 11:44.14 | *** join/#qi-hardware jluis (~jpddb@83.247.136.72) |
| 12:05.12 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 18:51.15 | *** join/#qi-hardware infobot (ibot@rikers.org) |
| 18:51.16 | *** topic/#qi-hardware is Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware |
| 18:51.16 | *** mode/#qi-hardware [+v infobot] by ChanServ |
| 18:51.55 | DocScrutinizer05 | wpwrak: in LXI / SCPI how do you handle waiting for device to be ready? how do you check if a command succeeded? do you really check status / error after each command? |
| 18:52.09 | DocScrutinizer05 | :SYST:ERR? |
| 18:57.21 | *** join/#qi-hardware methril (~methril@200.49.35.42) |
| 19:01.46 | DocScrutinizer05 | http://privatepaste.com/13788725d8 |
| 19:03.16 | DocScrutinizer05 | this is particularly nasty since wav:start and wav:end don't change to invalid values, and this a wav:data? will simply succeed using the previous values for start and end |
| 19:04.30 | DocScrutinizer05 | jr@saturn:~> send_cmd ':ACQuire:MDEPth?' |
| 19:04.32 | DocScrutinizer05 | AUTO |
| 19:04.35 | DocScrutinizer05 | :-/ |
| 19:05.18 | DocScrutinizer05 | I guess I need some other way to determine the buffer size (2.40M) |
| 20:36.11 | wpwrak | hmm, with my scope, i ended up having to guess the right timing. it would just overflow and lose (part of) commands. but i guess this has since improved a bit |
| 20:36.53 | wpwrak | if yours can buffer a command while another is executing, just try sending a command that does produce output. this will synchronize you. |
| 21:11.02 | *** join/#qi-hardware valhalla (~valhalla@149-71-158-249.v4.ngi.it) |
| 21:58.51 | DocScrutinizer05 | nope, same issue as yours |
| 22:42.23 | *** join/#qi-hardware Textmode (~boneidle@adsl-1-au-2-174.ozonline.com.au) |