Re: data import via USB interface
John Donoghue <[email protected]> Thu, 29 Feb 2024 07:52:09 -0500
| Newsgroups | gmane.comp.gnu.octave.general |
|---|---|
| Message-ID | <CAOJTVZDVVWXx_cCyETMJ2R40gRDNOGS+YS+4pi6cx=5YSm9wMg@mail.gmail.com> |
--===============0960212250842802288== Content-Type: multipart/alternative; boundary="000000000000dced25061284baaf" --000000000000dced25061284baaf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Feb 29, 2024 at 7:10=E2=80=AFAM Andreas Weber <[email protected]> = wrote: > Am 29.02.24 um 12:50 schrieb John Donoghue: > > Per the wiki for instrument-control [1], the usbtmc interface is not > > available in windows. You can also run 'instrhwinfo' from octave to see > > which interfaces have been built.. > > I saw that but because it says "Windows(native)" and not MXE and because > usbtmc.oct actually IS distributed with the installer I thought this > info is outdated. But I don't have a windoze installation to hand to > test it myself. > > -- Andy > the octave file is built for all modules, just it returns the unimplemented error is the functionality isnt available. There was a discussion years ago now where it was decided it was better to do that than just not have the module. instrhwinfo is the easiest way to see what functionality is available - as its set at configure time. --000000000000dced25061284baaf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Thu, Feb 29, 2024 at 7:10=E2=80=AF= AM Andreas Weber <<a href=3D"mailto:[email protected]">octave@josoansi.= de</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi= n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex= ">Am 29.02.24 um 12:50 schrieb John Donoghue:<br> >=C2=A0 =C2=A0Per the wiki for instrument-control [1], the usbtmc interf= ace is not <br> > available in windows. You can also run 'instrhwinfo' from octa= ve to see <br> > which interfaces have been built..<br> <br> I saw that but because it says "Windows(native)" and not MXE and = because <br> usbtmc.oct actually IS distributed with the installer I thought this <br> info is outdated. But I don't have a windoze installation to hand to <b= r> test it myself.<br> <br> -- Andy<br></blockquote><div><br></div><div>the octave file is built for al= l modules, just it returns the unimplemented=C2=A0error is the functionalit= y=C2=A0isnt=C2=A0available.</div><div><br></div><div>There was a discussion= =C2=A0years ago now where it was decided it was better to do=C2=A0that=C2= =A0than=C2=A0just not have the module.</div><div><br></div><div>instrhwinfo= is the easiest way to see what functionality is available - as its set at = configure time.</div><div>=C2=A0</div></div></div> --000000000000dced25061284baaf-- --===============0960212250842802288== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline Ci0tLS0tLS0tLS0KV2UgYXJlIHRyYW5zaXRpb25pbmcgdG8gYSB3ZWIgYmFzZWQgZm9ydW0KZm9y IGNvbW11bml0eSBoZWxwIGRpc2N1c3Npb25zIGF0Cmh0dHBzOi8vb2N0YXZlLmRpc2NvdXJzZS5n cm91cC9jL2hlbHAK --===============0960212250842802288==--