Date: Sun, 24 Jul 2016 10:51:34 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Gary Jennejohn <gljennjohn@gmail.com> Cc: Ian Lepore <ian@freebsd.org>, freebsd-usb@freebsd.org, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: Digi Watchport/T temperature sensor as /dev/ttyU Message-ID: <20160724105134.184f0b7f.ohartman@zedat.fu-berlin.de> In-Reply-To: <20160724083859.4c0dd392@ernst.home> References: <20160722183556.2fc39fd7.ohartman@zedat.fu-berlin.de> <1469206374.84197.14.camel@freebsd.org> <20160723220430.34ce02fe.ohartman@zedat.fu-berlin.de> <1469306951.84197.31.camel@freebsd.org> <20160724080330.3a27e875.ohartman@zedat.fu-berlin.de> <20160724083859.4c0dd392@ernst.home>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/o/t_pXrOJINiBb9lbfwGo_J Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Sun, 24 Jul 2016 08:38:59 +0200 Gary Jennejohn <gljennjohn@gmail.com> schrieb: > On Sun, 24 Jul 2016 08:03:30 +0200 > "O. Hartmann" <ohartman@zedat.fu-berlin.de> wrote: >=20 > > Am Sat, 23 Jul 2016 14:49:11 -0600 > > Ian Lepore <ian@freebsd.org> schrieb: > > =20 > > > On Sat, 2016-07-23 at 22:04 +0200, O. Hartmann wrote: =20 > > > > Am Fri, 22 Jul 2016 10:52:54 -0600 > > > > Ian Lepore <ian@freebsd.org> schrieb: > > > > =20 > > > > > On Fri, 2016-07-22 at 18:35 +0200, O. Hartmann wrote: =20 > > > > > > For temperature monitoring, we have a bunch of Digi Watchport/T > > > > > > sensors:=20 > > > > > >=20 > > > > > > http://ftp1.digi.com/support/documentation/90000406_H.pdf > > > > > >=20 > > > > > > =20 > > > > > [...] > > > > >=20 > > > > > I think the attached patch will make it show up as a ttyU*/cuaU* > > > > > device > > > > > for you. (You should probably use the /dev/cuaU* flavor, to avoid > > > > > problems with tty layer and modem control signals). > > > > >=20 > > > > > I keep wishing we had a mechanism, like a sysctl that could be set > > > > > or > > > > > something, that would let you supply a vendor/product pair and ha= ve > > > > > the > > > > > ugensa driver attach to that device, for quick testing of this so= rt > > > > > of > > > > > thing. > > > > >=20 > > > > > -- Ian =20 > > > >=20 > > > > No, it doesn't change anything. I applied the patch to most recent > > > > CURRENT and it is > > > > still the same. But thanks anyway. > > > >=20 > > > > Kind regards, > > > >=20 > > > > oh =20 > > >=20 > > > Oh, my bad, I forgot to mention: You'll have to manually "kldload > > > ugensa" before plugging in the device (or load it from your > > > loader.conf). > > >=20 > > > When the change gets committed (assuming it works), the devd usb > > > scripts will get regenerated, and that's what handles the auto-load of > > > the driver. > > >=20 > > > -- Ian =20 > > man ugensa doesn't exist! As I wrote earlier, I tried everything to loa= d what I could > > find. It seems, the patch and the hint about ugensa.ko did the magic ;-= ) Thank you > > very much! Could the patch be made permanent to FreeBSD CURRENT? > >=20 > > And also important: where is the man page for ugensa? Can the the modul= e be compiled > > staitcally into the kernel or are there pitfalls? > > =20 >=20 > Even the most complete man page found in the internet, the one from > Dragonfly, doesn't list your Digi International device as being one > of those supported. Yes. That is a pity. But Linux seems to operate this serial device. I have = to check next time I get hands on a Linux box, what driver is attached to the sensor. >=20 > Still, having the man page under FreeBSD would at least provide a hint > that the driver even exists. Agreed. >=20 > I added device ugensa to my config file and the kernel was generated > without an error. Me, too. >=20 > > root@localhost: [src] kldload ugensa > >=20 > > ugen2.7: <Digi International> at usbus2 > > ugensa0: <Digi International WatchportT, rev 1.10/1.00, addr 7> on usbu= s2 > > ugensa0: Found 1 interfaces. > > root@thor: [src] man ugensa > > No manual entry for ugensa > > root@localhost: [src] ll /dev/cuaU0* > > 203 crw-rw---- 1 uucp dialer - 0xcb Jul 24 07:51 /dev/cuaU0 > > 204 crw-rw---- 1 uucp dialer - 0xcc Jul 24 07:51 /dev/cuaU0.init > > 205 crw-rw---- 1 uucp dialer - 0xcd Jul 24 07:51 /dev/cuaU0.lock > >=20 > >=20 > > I'll try now to get informations out of the device, I let you know whet= her that is a > > success. But anyway, again, thank you for helping making the device vis= ible and > > available.=20 >=20 I had no luck with retrieving informations out of the device by the Perl5 s= cript provided by Nagios.org. A prerequisite for the Perl script is the FreeBSD port comms/p5-Device-SerialPort Patching the script is trivial, but I do not know whether the backend, comms/p5-Device-SerialPort, works a sexpected. So the first, dirty, trial e= nded up in nothing - since the information gained from the sensor is an empty string/n= othing. I'm not familiar with serial devices, so far, so probably there is somethin= g trivial missing. --Sig_/o/t_pXrOJINiBb9lbfwGo_J Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXlIGWAAoJEOgBcD7A/5N8CmoH/jUYDAovA8em7YRtAs64/QDV FdApj+GEjpeMfQIRbsFrqu65U5thA5stFYRCRNrRY1cbiocjm3hiYBw3yscGPhxy tZec1bmb9CLQ1GeRuZTd0cGVujPeEFOqRzr819ghupWcPhqK7MFEoaL4JJkewv8Q GNizxOnCiq5g2uHe0Q3QGUDR5GD9WCwpnXOaRRd/RoAceE1EIgFHmtlZiG6k9LKS 7BVIN3DgTq07t//P5sw3jnMKpQr0AD/EjewiZ2cc7GV1vy4tegGNFaWADp7ehhBl SlLxCyMyShoTFfLuDd51GaMF/0D6EHHeElwPU+hOR1/2EeRp5aUx25HyXdAqVec= =12BX -----END PGP SIGNATURE----- --Sig_/o/t_pXrOJINiBb9lbfwGo_J--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160724105134.184f0b7f.ohartman>