HP 5335A GPIB readout [Solved] - Page 1
Forum section: electronics / testgear

author: davorin
author_rank: Unknown
timestamp: October 09, 2014, 12:27:12 pm
content: Afternoon (o;I'm trying to read out via GPIB the frequency measurement from my HP 5335A counter....according to the manual I can just send the initialize command "IN" and it would reply with the data...but nothing is returned...Is there something missing in the handshake/GPIB mode?I'm using the "ibterm" console application with the F82357 USB adapter under Linux...

author: MarkPalmer
author_rank: Regular Contributor
timestamp: October 09, 2014, 01:30:35 pm
content: "IN" is only the initialize command. I don't know how it works with Linux systems or ?, but the context to receive a frequency measurement would normally be:OUTPUT XXX; (where xxx is the 5335A's HPIB address) "FN1" (FN1 is the mnemonic for channel A frequency)-Mark-

author: davorin
author_rank: Unknown
timestamp: October 09, 2014, 02:04:45 pm
content: Just makes the display going blank (o;Code:me@nuc:~$ ibterm -d 10Attempting to open /dev/gpib0pad = 10, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000ibterm>fn1ibterm>ibterm>

author: MarkPalmer
author_rank: Regular Contributor
timestamp: October 09, 2014, 02:21:57 pm
content: Does the adapter establish a handshake with the counter using the IN command where the remote light on the counter comes on?-Mark-

author: MarkL
author_rank: Unknown
timestamp: October 09, 2014, 02:46:12 pm
content: I would try sending simple operation commands that don't need a response to see if that works ok first. That's half the battle. For instance, try turning the display on and off with DR0 and DR1. And as MarkPalmer says, the remote light should come on with these too.Some of the older GPIB equipment can be pretty finicky with what it will accept. I have a couple of old HP devices (8116A, 5006A) that need reos set.I've also found that ibterm doesn't work reliably for me. Perhaps give the C or Perl library a try.

author: davorin
author_rank: Unknown
timestamp: October 09, 2014, 05:20:50 pm
content: Well it reacts on re and in turning remote LED on...dr1 and dr0 turn remote LED on and off...after those command no in and re is working...No luck with python gpib library either...might a firmware update to 1.1 help?btw...what happened tohttp://www.ko4bb.com?Code:ping: unknown host [url=http://www.ko4bb.com]www.ko4bb.com

author: MarkPalmer
author_rank: Regular Contributor
timestamp: October 09, 2014, 05:30:02 pm
content: I read K04BB has been moving over to a different server so some parts of the site are inactive. I'm not sure why your GPIB won't respond to the standard output commands, maybe someone more familiar with Linux will chime in.-Mark-

author: MarkL
author_rank: Unknown
timestamp: October 09, 2014, 05:51:25 pm
content: This was posted to the tekscopes yahoo list:Manuals at KO4BB.comMon Sep 29, 2014 4:41 am (PDT) . Posted by: didier_jugesThis is a public service announcement.My Host provider (1and1) has in formed me that traffic on ko4bb.com has consistently and grossly exceeded the unlimited bandwidth allocation specified by contract(!!!) They have also turned off my service a few times this month to emphasize the message. I have been a customer for about 10 years but apparently nowadays that does not count for much.This must be the new math, 2TB/month > infinite, or maybe unlimited is not the same as infinite...It turns out that many providers have responded the same way when asked if 2TB/month was less than the unlimited promise of shared hosting. Therefore I have to upgrade to a better class of service.As expected, there is a big price gap between services that offer unlimited bandwidth (they are all cheap shared hosts) and those that offer "only" 2TB/month (typically virtual private systems or managed servers). The cost goes up by a factor of about 10 or more.I have identified a new service provider: MyHosting.com and I am in the process of migrating everything, including the 65GB or so of manuals and related files (and the other 60GB of other stuff).The new service is now a Virtual Private Server, as opposed to a shared host. That means I have my own private virtual machine and full access to the OS, which is a blessing and a curse, as I can do anything I want (pretty much) but I have to do everything else too myself (like software maintenance). The price has gone up significantly, but MyHosting.com has a nice setup where you can pretty much rent as much CPU/memory/hard drive and bandwidth as you need, and it is easy to change on the fly.I am in the process of setting up the new server. I will make an announcement when it is online, probably in a couple of weeks. There may be a short interruption while the DNS caches are flushed. Be assured that none of the manuals are lost, but there were a large number of manuals uploaded this month and they are going to be in temporary storage (unsorted in the Stuff Not Sorted folder) for a little while.Also, I will ask everyone to postpone making large uploads until I have moved to the new server. I will turn off uploads a few days before the switch.I may have to turn off downloads on the current site if 1and1 gives me too much of a hard time. Please be patient.Thank you for your patience and your support.Didier KO4BB

author: MarkL
author_rank: Unknown
timestamp: October 09, 2014, 06:00:21 pm
content: But back to the 5335A...Quote from: davorin on October 09, 2014, 05:20:50 pmI don't have a 5335A, so I'm going by the manual.DR0 and DR1 are supposed to turn the whole *numeric display* on/off. Did it do that successfully?Another thing you could try for verification is "DI12345". That should make 12345 appear in the display. And then try "DI45678" and see if 45678 appears. Sometimes the GPIB logic gets caught in a funny state because of incorrect command termination and won't accept two commands in a row properly.On other libraries: You tried it with the same result, or you were unsuccessful in using those libraries?Not sure what firmware 1.1 refers to?

author: davorin
author_rank: Unknown
timestamp: October 09, 2014, 06:16:57 pm
content: Actually both DR0 and DR1 turned the display dark...one of them turning off the remote LED but activating the Listen LED...Gonna try tomorrow some more...maybe also with other libraries than Python...BTW: With the Python GPIB library it just timed out even with the "IN" command...Maybe linux-gpib isn't that supported much anymore...as for example the php library won't even run anymore...FOr the firmware...I've seen that most devices have a 1.0 ROM version...and some 1.1....difference is that it displays a dot when showing the GPIB address (no dot = 1.0)...

author: MarkL
author_rank: Unknown
timestamp: October 09, 2014, 06:18:57 pm
content: I think bingo600 is onto something with the EOI.But another thing I've noticed about ibterm is that it does a read immediately after every command. Some of my equipment is too slow to have a response that quickly.Try this: ibterm -d10 -e10 -r1 -N -i -xAfter entering a command, hit RETURN at the next prompt to explicitly read the response from the counter.(Edit: Fix ambiguity.)

author: MarkL
author_rank: Unknown
timestamp: October 09, 2014, 06:40:57 pm
content: On linux-gpib libraries: I can vouch that the perl and C libraries work (v3.2.20). I've used the perl library for almost everything GPIB for at least the last 7 or 8 years."IN" may be timing out because the host is not waiting long enough. You can try increasing the timeout for pad 10 in /etc/gpib.conf. Try T3s, or even T10s. Are you trying to read a result from "IN"? I'm not seeing that it returns a result.And that's not the expected behavior for DR0 and DR1 ("Display Remote"). DR1 is supposed to blank the display and put it in remote mode. DR0 is normal.From before, in order for DI12345 to work, the display has to be in remote mode, so a more complete example would be: "DR1,DI12345" (straight from the manual).And I'm also reading that you shouldn't use "IN" when the display is in remote mode "DR1". Not sure why, but that's what the manual says.

author: bingo600
author_rank: Super Contributor
timestamp: October 09, 2014, 06:46:49 pm
content: Whoopz my edit of the post above went bad ...I deleted it ... SorryWell i think Mark caught the EOI / EOT issueI've been using python fine with linux-gpib , but used the "named open" ... Meaning the name from the gpib.conf.That's because then eoi/eot is taken from the instrument def's in gpib.conf../Bingo

author: davorin
author_rank: Unknown
timestamp: October 10, 2014, 04:51:53 pm
content: What eoi/eot settings do you have in your gpib.conf file?Hmm..trying now with ibtest command:Code:: wenter a string to send to your device: FN1sending string: FN1gpib status is:ibsta = 0x2100 < END CMPL >iberr= 0ibcnt = 4But doing then a read gets:Code:: renter maximum number of bytes to read :trying to read 1024 bytes from device...received string: ''Number of bytes read: 0gpib status is:ibsta = 0xc100 < ERR TIMO CMPL >iberr= 6EABO 6: Operation abortedibcnt = 0

author: MarkL
author_rank: Unknown
timestamp: October 10, 2014, 05:18:13 pm
content: Quote from: davorin on October 10, 2014, 04:51:53 pmHere's mine with the board section and some of the devices:Code:***********************************************************************GPIB.CONF IEEE488 library config file-------------------copyright : (C) 2002 by Frank Mori Hess(C) 1994 by C.Schroeteremail : fmhess@users.sourceforge.net***************************************************************************//***************************************************************************** Syntax:** interface { ... } starts new interface board section* device {...} device configuration****************************************************************************//* Timeouts: T1s, T3s, T10s, T30s, T100s, T300s, T1000s *//* This section configures the configurable driver characteristics* for an interface board, such as board address, and interrupt level.* minor = 0 configures /dev/gpib0, minor = 1 configures /dev/gpib1, etc.*/interface {minor = 0 /* board index, minor = 0 uses /dev/gpib0, minor = 1 uses /dev/gpib1, etc. */board_type = "ni_pci" /* type of interface board being used */name = "violet" /* optional name, allows you to get a board descriptor using ibfind() */pad = 0 /* primary address of interface */sad = 0 /* secondary address of interface */timeout = T3s /* timeout for commands */eos = 0x0a /* EOS Byte, 0xa is newline and 0xd is carriage return */set-reos = yes /* Terminate read if EOS */set-bin = no /* Compare EOS 8-bit */set-xeos = no /* Assert EOI whenever EOS byte is sent */set-eot = yes /* Assert EOI with last byte on writes *//* pci_bus and pci_slot can be used to distinguish two pci boards supported by the same driver *//* pci_bus = 0 *//* pci_slot = 7 */master = yes /* interface board is system controller */}/* Now the device sections define the device characteristics for each device.* These are only used if you want to open the device using ibfind() (instead* of ibdev() )*//* Tektronix TDS3054 */device {name = scopeminor = 0pad = 1sad = 0eos = 0x0atimeout = T10s /* needed for slow print response */}/* Racal-Dana 1992 */device {name = counterminor = 0pad = 4sad = 0eos = 0x0aset-reos = yes /* required */}/* HP 8116A */device {name = fgenminor = 0pad = 16eos = 0x0aset-reos = yes /* required */}/* HP 8595E */device {name = spminor = 0pad = 18eos = 0x0atimeout = T30s /* needed for slow print response */}

author: olepr01@gmail.com
author_rank: Contributor
timestamp: October 10, 2014, 05:41:25 pm
content: I dont have a 5335, but I've spent some time getting data from a 5334b, which is about the same vintage. The "secret" in my case was to enable "terminate read on End of String", and set End of String-character = 0x0A. Now I get whatever reading shows up on the counter also through GPIB.

author: davorin
author_rank: Unknown
timestamp: October 10, 2014, 05:48:25 pm
content: With what application are you reading out?

author: olepr01@gmail.com
author_rank: Contributor
timestamp: October 10, 2014, 06:06:30 pm
content: At the moment some custom c# code I wrote - very simple, just reads whatever the 5334b sends across the gpib-bus and outputs it to the console. The "important bits" areCode:using NationalInstruments.NI4882;namespace _5334B_NI488._2 {class Program {static void Main(string[] args) {// ...Device dev = new Device((byte)board, (byte)addr, 0);dev.EndOfStringCharacter = 0x0A;dev.TerminateReadOnEndOfString = true;dev.IOTimeout = TimeoutValue.T3s;dev.Clear();while (true) {try {Console.WriteLine(dev.ReadString().Trim());} catch (NationalInstruments.NI4882.GpibException e){}Edit:That said, the c# libraries as far as I can tell map pretty much directly to NI 488 drivers, so the actual language should not matter much; you'll find the those settings somewhere. Reading from an Agilent USB-adapter is pretty much the same thing, using a different API ofcourse, but the Terminate on End of String and End of String character was the trick there also. With an Agilent adapter I think i had to use 0x040A for End of String character, theres a flag in there if I recall. I can probably dig out the code if needed, but the Agilent 488 support died when I installed the NI drivers, and I've been too lazy to fix it.

author: MarkL
author_rank: Unknown
timestamp: October 10, 2014, 06:55:18 pm
content: davorin: Did the "ibterm -d10 -e10 -r1 -N -i -x" not work? This sets the same EOI conditions that olepr01 is mentioning.Something like this:$ ibterm -d10 -e10 -r1 -N -i -xAttempting to open /dev/gpib0pad = 10, sad = 0, timeout = 10, send_eoi = 0, eos_mode = 0x040aibterm>FN1ibterm>(wait a second, hit a RETURN, should get a response...)Perhaps try the command "PQ" that doesn't depend on a measurement result. PQ returns a 30-byte binary "learn string", which is probably going to look like garbage, but it shouldn't time out under any conditions.

author: davorin
author_rank: Unknown
timestamp: October 10, 2014, 07:00:52 pm
content: Nope....Code:me@nuc:~$ ibterm -d10 -e10 -r1 -N -i -xAttempting to open /dev/gpib0pad = 10, sad = 0, timeout = 10, send_eoi = 0, eos_mode = 0x040aibterm>FN1ibterm>libgpib: IBEOS ioctl failedibterm>...but PQ worked...though also with error message:Code:me@nuc:~$ ibterm -d10 -e10 -r1 -N -i -xAttempting to open /dev/gpib0pad = 10, sad = 0, timeout = 10, send_eoi = 0, eos_mode = 0x040aibterm>PQibterm>libgpib: IBEOS ioctl failed00000000 | 01 00 00 00 10 10 00 00 | 00 00 00 00 00 00 00 10 |00000010 | 00 00 00 00 00 00 00 10 | 00 00 00 00 00 00 |

author: olepr01@gmail.com
author_rank: Contributor
timestamp: October 10, 2014, 07:53:10 pm
content: Perhaps a stupid question, but you DO have something connected to measure? If I try to measure frequency without anything connected, the gpib times out..

author: davorin
author_rank: Unknown
timestamp: October 10, 2014, 08:06:07 pm
content: Not a stupid question at all....sure a signal source is connected...a HP 8904A with external GPSDO...set to 100kHz sine wave and 2V......though I would expect to return just "0" when no frequency is measured (o;

author: MarkL
author_rank: Unknown
timestamp: October 10, 2014, 08:22:58 pm
content: "libgpib: IBEOS ioctl failed" Hmmm... should probably find out why that's happening. Maybe ibterm is doing something wrong, or it could be a driver issue. IBEOS is supposed to set the end-of-string modes, and we already suspect an issue in that area with the 5335A.But ibterm did return 30 bytes on PQ, and that's at least the correct byte count. Odd.

author: MarkL
author_rank: Unknown
timestamp: October 11, 2014, 06:55:15 pm
content: Quote from: davorin on October 09, 2014, 12:27:12 pmAfter a little walk through the linux-gpib code, it appears that the EOS mode is passed to the 82357 adapter for further processing. See agilent_82357a_read() in ./drivers/gpib/agilent_82357a/agilent_82357a.c.Before doing anything else I would check to make sure you have the latest firmware from Beiming. There are a couple of mentions of EOI improvements on their web page but not enough detail to know if it's your problem. And it may be worthwhile to contact their technical support. By the looks of it they're informal and likely responsive.http://bmjd.biz/index.php?m=content&c=index&a=lists&catid=17

author: davorin
author_rank: Unknown
timestamp: October 11, 2014, 06:59:31 pm
content: I'm sure I'm on the latest version of the F82357 adapter...for the S82357 I'm not sure....though the firmware can be interchanged between them (o;

author: bingo600
author_rank: Super Contributor
timestamp: October 11, 2014, 08:24:30 pm
content: I seem to remember , that there is a note about Beiming/Agilent USB adapters , that they can only do 8-bit (EOS & other) compares.Their firmwares doesn't support 7-bit compare.Herehttp://linux-gpib.sourceforge.net/doc_html/x259.html#AGILENT-82357AAs LF (0x0d) is only 7-bit i can't see any problem with a 7-bit compare , but as a "longshot" maybe try to set the BIN flag along with REOS.http://linux-gpib.sourceforge.net/doc_html/r1392.htmlEdit:Ohh and a lsusb -v vill show the fw-vers of the beiming like this (the bcdDevice field) ... Mine is an FIf you use sudo in front it will also show the manufacturer info (model & Serial)Code:Bus 001 Device 007: ID 0957:0718 Agilent Technologies, Inc.Couldn't open device, some information will be missingDevice Descriptor:bLength 18bDescriptorType 1bcdUSB 2.00bDeviceClass 0 (Defined at Interface level)bDeviceSubClass 0bDeviceProtocol 0bMaxPacketSize0 64idVendor 0x0957 Agilent Technologies, Inc.idProduct 0x0718bcdDevice 1.10/Bingo

author: davorin
author_rank: Unknown
timestamp: October 11, 2014, 08:28:53 pm
content: Hmm..interesting....thought though I already tried set-bin already...Gonna try tomorrow with a Prologix clone if it behaves the same...

author: bingo600
author_rank: Super Contributor
timestamp: October 11, 2014, 08:52:12 pm
content: I'd say you need send_eoi = 1 , and "eos" on LF (maybe binary)Try : ibterm -d10 -e10 -r1 -i1 -b1 -t12-t12 extend timeout to 3 sec 13 = 10 sec) , 300ms could be to fast if the trigger on the cntr is high or cpu slowhttp://linux-gpib.sourceforge.net/doc_html/r2190.html-i1 is default , but set it anyway to indicate it's there/Bingo

author: davorin
author_rank: Unknown
timestamp: October 12, 2014, 09:18:58 am
content: Haaaah....Code:me@nuc:~$ ibterm -d10 -e10 -r1 -i1 -b1 -t12Attempting to open /dev/gpib0pad = 10, sad = 0, timeout = 12, send_eoi = 1, eos_mode = 0x140aibterm>F +100.001773E+03ibterm>F +100.001788E+03ibterm>F +100.001789E+03ibterm>F +100.001789E+03ibterm>You're the best :-)

author: bingo600
author_rank: Super Contributor
timestamp: October 12, 2014, 12:03:23 pm
content: Super ...If you set those parameters for "HP5335A" in gpib.conf , you should be able to use the counter via python.Use gpib.find like below/BingoPs: I liked fpga.chCode:#!/usr/bin/python# -*- coding: utf-8 -*-import gpibimport serialimport timeimport datetimefrom time import gmtime, strftimedef query(handle, command, numbytes=100):gpib.write(handle,command)time.sleep(0.1)response = gpib.read(handle,numbytes)response = response.rstrip("\r\n")return responsedef command(handle, command):gpib.write(handle,command)time.sleep(0.1)def gread(handle, numbytes=100):response = gpib.read(handle,numbytes)time.sleep(0.1)response = response.rstrip("\r\n")return responsedef tread(sensor):ser.write(sensor)time.sleep(0.5) #give the serial port sometime to receive the datadata = ser.readline().rstrip() # read data from serialif data == "125.0000":print "*** Error Reading ***"return datadef getdate():fdate = strftime("%Y-%m-%d")return fdatedef openfile(date):#csvfilename = "dmm-"+strftime("%Y-%m-%d_%H.%M.%S")+".csv"filename = "dmm-"+date+'_'+strftime("%H.%M.%S")+".csv"handle = open(filename,'at')# append,text modereturn handlecsvdelim = ';'# CSV delimitermeastime = 5# Sec between print on screenlogevery = 12# Every 'th measurement should go itnto the logfileHP3457= gpib.find("HP3457A") # defined in /etc/gpib.conf - HP SVR-TK2015= gpib.find("KEITHLEY2015") # defined in /etc/gpib.conf - K SVRgpib.clear(HP3457)gpib.clear(K2015)command(HP3457,"END ALWAYS")# Force EOI on end of data (Default off)print query(HP3457,"ID?")print query(K2015,"*IDN?")command(HP3457,"DCV3,,;NPLC 100;TRIG HOLD")# DCvolt 3v range , 100NPLC (max) , Manual TRIGcommand(K2015,":Sens:Func 'Volt:DC'")# DCvoltcommand(K2015,":SENS:VOLT:DC:AVER:STAT OFF")# No statistics (def. 10 pt moving average)command(K2015,":SENSe:VOLTage:DC:RANGe 10:NPLC 10")# DCvolt 10v range , 10NPLC (max)

author: MarkL
author_rank: Unknown
timestamp: October 13, 2014, 12:22:54 pm
content: Quote from: davorin on October 12, 2014, 09:18:58 amSo, which parameters from "ibterm -d10 -e10 -r1 -i1 -b1 -t12" made it work? Was it the timeout or the "-i1"?I'm also noting that just using "-i" from the prior attempts does NOT set the flag. You need "-i1". Nice parser.

author: davorin
author_rank: Unknown
timestamp: October 13, 2014, 12:59:14 pm
content: The important flag is "-b1".....but then not always a result is returned..but with "-t12" it is returned with every press of enter key...Interesting though...sending "FN1" in advance turns the display dark and no values can be read....have to send "IN" first...

author: MarkL
author_rank: Unknown
timestamp: October 13, 2014, 01:26:06 pm
content: That's interesting that it's "-b1". I wouldn't have expected that. Setting bin mode should be more restrictive since it's supposed to be comparing all 8 bits instead of just the lower 7 for the EOS byte.Like the other EOS option bits, bin mode is also passed to the adapter so it's up to the adapter to interpret it. I wonder if Beiming is doing something unexpected with it.I always like to know why something is working as much as why it isn't working, but oh well. Can't argue with success. Glad you got it!On the "FN1", maybe try "-x1".

author: MarkL
author_rank: Unknown
timestamp: October 13, 2014, 01:29:42 pm
content: Just read this in the linux-gpib manual (3.2.20):QuoteTo me that says it doesn't matter if you set binary mode or not, but maybe the implementation is not what I think.

author: davorin
author_rank: Unknown
timestamp: October 13, 2014, 01:33:05 pm
content: The readout works without "-b1" flag..but always with an error message:Code:me@nuc:~$ ibterm -d10 -e10 -r1 -i1 -t12Attempting to open /dev/gpib0pad = 10, sad = 0, timeout = 12, send_eoi = 1, eos_mode = 0x040aibterm>libgpib: IBEOS ioctl failedF +100.001830E+03ibterm>libgpib: IBEOS ioctl failedF +100.001831E+03ibterm>

author: MarkL
author_rank: Unknown
timestamp: October 13, 2014, 01:42:21 pm
content: Ok, how about this for an explanation:The Beiming is rejecting all (maybe some?) of the mode setting ioctl because it knows it can't handle bin-mode=0.So, to successfully change anything else you need to include bin-mode=1.

author: davorin
author_rank: Unknown
timestamp: October 13, 2014, 03:32:32 pm
content: Is there a gpib.read function that reads until EOL?Well..for the 5335A it is always 21 chars including LF/CRThis snippet works now...but sending "FN1" in advance locks the device...Code:#!/usr/bin/pythonimport gpibHP5335A = gpib.find("5335")gpib.clear(HP5335A)print gpib.read(HP5335A,21)

author: MarkL
author_rank: Unknown
timestamp: October 13, 2014, 06:28:14 pm
content: Quote from: davorin on October 13, 2014, 03:32:32 pmThere's no special function in the regular library (I'm assuming python is no different). They all read until the number of bytes specified, or until: (from the manual)QuoteWhen I do reads from perl I pass ibrd() 100000 for the number of bytes. (It should really be written to be a little more robust and read until EOI, but I don't have anything at the moment that sends near that many bytes.)What does your /etc/gpib.conf look like?Quote from: davorin on October 13, 2014, 03:32:32 pmWhat do you mean by "in advance"? You mean sending FN1 and then trying a read?Perhaps you need "set-xeos = yes" or "set-eot = yes" in gpib.conf?(Sorry this is being less than scientific by just poking at different things. If you had a logic analyzer to slap on the GPIB we could probably get to the bottom of it pretty quickly.)

author: davorin
author_rank: Unknown
timestamp: October 13, 2014, 06:53:19 pm
content: Probably best with an analyzer....I even installed the 9918 GPIB chip in my Philips PM 3585 but there is no software support for it..or never was...Guess we can close this thread (o;

author: MarkL
author_rank: Unknown
timestamp: October 13, 2014, 07:21:02 pm
content: Your call. Good luck!

author: davorin
author_rank: Unknown
timestamp: October 14, 2014, 08:55:24 pm
content: Quote from: bingo600 on October 12, 2014, 12:03:23 pmHmm...almost didn't notice your comment (o;But that's a long time ago this site was active....when I was living and working in Finland (o;But just acquired recently some new FPGA boards...and Lattice promised to give me their software and cores for the once $99 introductory price (o; (Xilinx I didn't bother as they even give any feedback ;o)Project ideas are endless, but not time (o;

author: bingo600
author_rank: Super Contributor
timestamp: October 15, 2014, 08:40:25 pm
content: I think i learned about the "cheap" Altera config chips at your place/Bingo

author: doktor pyta
author_rank: Frequent Contributor
timestamp: October 17, 2014, 06:37:36 am
content: I just did similar thing in RF Scientific GPIB Data Logger v1.0I'm sending one time:++clrINFN1GA2CY3And every time i need to read new result i'm sending:CY3Below print screen with the commands.