[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: testing octave-instrument-control-toolbox, looking for a workaround
Re: testing octave-instrument-control-toolbox, looking for a workaround for "sorry, printing char matrices not implemented yet"
Thu, 29 Nov 2012 20:16:00 +0100
Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
Hugo Coolens wrote:
> I'm trying out the octave-instrument-control-toolbox. I guess it
> installed fine, but as you can see below, running the sample program
> pops up a "sorry, printing char matrices not implemented yet", is
> there a workaround for this in Octave 3.2.4 or how should the code be
> adapted to get the text identification string which is (hopefully)
> sent back?
> octave:10> readbytes = 10000;
> octave:11> fd = usbtmc_open("/dev/usbtmc1")
> fd = 4
> octave:12> usbtmc_write(fd,"*IDN?");
> octave:13> result = usbtmc_read(fd,readbytes)
> result =
> sorry, printing char matrices not implemented yet
> octave:14> usbtmc_close(fd);
I have answered Hugo already, but I forgot to include the mailing list.
For the actual master branch at github use
result = char(usbtmc_read(fd,readbytes))
to get the text string.
Meanwhile I ported usbtmc to be included to OF instrument control within
the port2forge branch. The syntax will change a little bit, but you
still have to use char(usbtmc_read(obj,readbytes)) to get the result as