Testing Tira 2.1

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Testing Tira 2.1

Craig Treleaven
Hi:

The good folks at Home Electronics have lent me a Tira 2.1 IR receiver to test with Lirc under Mac OS X.  

https://www.home-electro.com

https://www.home-electro.com/products/tira-21

Unfortunately, I don’t know what to put in lirc_options.conf.  I’ve put in driver = tira.  I think I need to specify something for the device setting but I dont’ know what.  (I’ve previously only ever used udp where device was the port to listen to.)

I know that the device has been recognized by the operating system:

CT-MBP11:usbids craigtreleaven$ lsusb
Bus 253 Device 004: ID 0403:fa78 Future Technology Devices International, Ltd
Bus 250 Device 004: ID 05ac:0252 Apple, Inc. Internal Keyboard/Trackpad (ANSI)
Bus 250 Device 002: ID 0424:2513 Standard Microsystems Corp. 2.0 Hub
Bus 253 Device 002: ID 0424:2513 Standard Microsystems Corp. 2.0 Hub
Bus 253 Device 001: ID 05ac:8006 Apple, Inc. EHCI Root Hub Simulation
Bus 250 Device 001: ID 05ac:8006 Apple, Inc. EHCI Root Hub Simulation

The Tira is the "Future Technology Devices International, Ltd” device.

I’ve tried using the Bus # (253) as the device with no joy.  The following is the lircd log:

Jan 24 07:02:26.073397 CT-MBP11.local lircd: Notice: caught signal
Jan 24 07:02:26.443442 CT-MBP11.local lircd: Info: lircd:  Opening log, level: Info
Jan 24 07:02:26.628576 CT-MBP11.local lircd: Info: Initial device: 253
Jan 24 07:02:26.628640 CT-MBP11.local lircd: Info: Initial device: 253
Jan 24 07:02:26.628697 CT-MBP11.local lircd: Debug: lircd:  Opening log, level: Debug
Jan 24 07:02:26.673160 CT-MBP11.local lircd: Notice: Running as user _lirc
Jan 24 07:02:26.673210 CT-MBP11.local lircd: Debug: Groups: [501]: 501 12 61 100
Jan 24 07:02:26.724494 CT-MBP11.local lircd: Info: Using remote: Sony_RMT-V402A-VIDEO.
Jan 24 07:02:26.724770 CT-MBP11.local lircd: Info: Using remote: Sony_RMT-V402A-SHUTTLE.
Jan 24 07:02:26.725139 CT-MBP11.local lircd: Info: Using remote: Sony_RMT-V402A-TV.
Jan 24 07:02:26.775853 CT-MBP11.local lircd: Info: Using remote: veq2249.
Jan 24 07:02:26.810989 CT-MBP11.local lircd: Notice: lircd(tira) ready, using /opt/local/var/run/lirc/lircd
Jan 24 07:02:29.313009 CT-MBP11.local lircd: Notice: accepted new client on /opt/local/var/run/lirc/lircd
Jan 24 07:02:29.313160 CT-MBP11.local lircd: Warning: Failed to initialize hardware
Jan 24 07:02:48.873192 CT-MBP11.local lircd: Info: removed client

Oh, BTW, the lirc-setup script isn’t working for me.  (This may be my fault—I may have an incomplete X environment at the moment.)  Will test on another machine and try to narrow down the issue.

Craig
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Testing Tira 2.1

Alec Leamas


On 24/01/17 13:07, Craig Treleaven wrote:

> Hi:
>
> The good folks at Home Electronics have lent me a Tira 2.1 IR receiver to test with Lirc under Mac OS X.
>
> https://www.home-electro.com
>
> https://www.home-electro.com/products/tira-21
>
> Unfortunately, I don’t know what to put in lirc_options.conf.  I’ve put in driver = tira.  I think I need to specify something for the device setting but I dont’ know what.  (I’ve previously only ever used udp where device was the port to listen to.)
>
> I know that the device has been recognized by the operating system:

You have read the tira section in the plugin docs, right?

That said, looking at the source it seems that the tira device should be
visible as /dev/ttyUSB?, typically /dev/ttyUSB0 which then is the device
to use.

In current master there is 'mode2 --driver tira --list-devices' which is
what's really needed here. But not 0.9.4d.


Cheers!

-alec


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Testing Tira 2.1

Craig Treleaven
> On Jan 24, 2017, at 7:32 AM, Alec Leamas <[hidden email]> wrote:
>
> On 24/01/17 13:07, Craig Treleaven wrote:
>> The good folks at Home Electronics have lent me a Tira 2.1 IR receiver to test with Lirc under Mac OS X.
>>
>> https://www.home-electro.com
>>
>> https://www.home-electro.com/products/tira-21
>>
>> Unfortunately, I don’t know what to put in lirc_options.conf.  I’ve put in driver = tira.  I think I need to specify something for the device setting but I dont’ know what.  (I’ve previously only ever used udp where device was the port to listen to.)
>>
>> I know that the device has been recognized by the operating system:
>
> You have read the tira section in the plugin docs, right?
>
> That said, looking at the source it seems that the tira device should be
> visible as /dev/ttyUSB?, typically /dev/ttyUSB0 which then is the device
> to use.
>
> In current master there is 'mode2 --driver tira --list-devices' which is
> what's really needed here. But not 0.9.4d.

I’ve compared the results of ‘sudo ls -al /dev’ before and after connecting to USB:

$ diff "Tira not attached.txt" "Tira attached.txt"
28,30c28,30
< crw-rw-rw-   1 root            wheel      14,  17 23 Jan 20:03 io8log
< cr--r--r--   1 root            wheel      14,  13 23 Jan 20:02 io8logmt
< crw-rw-rw-   1 root            wheel      14,  16 24 Jan 13:00 io8logtemp
---
> crw-rw-rw-   1 root            wheel      14,  13 23 Jan 20:03 io8log
> cr--r--r--   1 root            wheel      14,  16 23 Jan 20:02 io8logmt
> crw-rw-rw-   1 root            wheel      14,  15 24 Jan 13:00 io8logtemp
40c40
< crw-rw-rw-   1 root            tty        15,   2 24 Jan 13:05 ptmx
---
> crw-rw-rw-   1 root            tty        15,   2 24 Jan 13:06 ptmx
231c231
< crw--w----   1 craigtreleaven  tty        16,   0 24 Jan 13:05 ttys000
---
> crw--w----   1 craigtreleaven  tty        16,   0 24 Jan 13:06 ttys000

I though /dev/ttys000 looked promising but I get the same error when I run irw:

Jan 24 13:07:41.685789 CT-MBP11.local lircd: Warning: Failed to initialize hardware

Also tried /dev/ttys001 and /dev/ptmx with the same result.  

AFAICT, OS X does not mount character-based USB devices as Linux does.  See:

http://stackoverflow.com/questions/36523760/find-mount-point-of-an-usb-device-in-osx

It seems that plugins/osx_usbraw.c uses a very different approach to accessing the Sony IR receiver.  It may be that this just isn’t going to work.

Craig



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Testing Tira 2.1

Bengt Martensson-2
On 01/24/17 19:24, Craig Treleaven wrote:
>> On Jan 24, 2017, at 7:32 AM, Alec Leamas <[hidden email]> wrote:
>>
>> On 24/01/17 13:07, Craig Treleaven wrote:
>>> The good folks at Home Electronics have lent me a Tira 2.1 IR receiver to test with Lirc under Mac OS X.
...
>> That said, looking at the source it seems that the tira device should be
>> visible as /dev/ttyUSB?, typically /dev/ttyUSB0 which then is the device
>> to use.

Correct; the TIRA does serial-over-USB emulation, like FTDI, and many of
our favorite devices, like Arduino, USB-uirt, CommandFusion, IrToy, but
unlike commandIR, Iguana,.. As Alec says, with Linux it shows up as
/dev/ttyUSBn (n = 0,1,2,...). On my Mac (Mac Mini "early 2009", MacOS
10.11.6) it shows up as /dev/tty.usbserial-HE00001 as well as
/dev/cu.usbserial-HE00001. (These two differs in how they treat some
modem control lines; on Solaris it was /dev/tty* for dial-in and cu for
dial-out, IIRC.)

So it should work, using one of these devices.

BTW, it appears as your goal is to get as many "things" as possible to
work with MacOS. Have you tried my baby: the Girs driver and (e.g.) an
Arduino like this: http://www.harctoolbox.org/arduino_nano.html ? It
"should" work.

Greetz,

Bengt


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Testing Tira 2.1

Alec Leamas
In reply to this post by Craig Treleaven


On 24/01/17 19:24, Craig Treleaven wrote:

>
> It seems that plugins/osx_usbraw.c uses a very different approach to accessing the Sony IR receiver.  It may be that this just isn’t going to work.

Yes... With the new enumerating support in place it's "probably"
straight-forward to make a patch avoiding the linux devices completely.
The key thing is that it seems like libusb (both 0.12 and 1.0) exists on
MacOS as it also does on linux.

The sketch:
     - Rewrite the enumeration code to use the libusb enumeration instead.
     - Represent the usb address in the UI as a string together with
other info, notably productId and vendorId.
     - User selects one  string and uses it as "device" to --device.
     - Driver reconstructs the libusb_device from the string and uses it.

This should be perfectly acceptable also on linux, although using the
/dev devices has some edge there. #ifdef?

Looking further, drv_enum_usb() in drv_enum.c is one key piece. It
actually enumerates using libusb mechanisms, but encodes the result as
linux /dev paths. If it instead used OS-agnostic strings one would have
to teach the corresponding drivers to use that to feed libusb_open()
somehow, but that's basically that. Perfectly doable.

That is not to say I'm about to do it. But, a patch would be welcomed...


Cheers!

--alec



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Testing Tira 2.1

Craig Treleaven
In reply to this post by Bengt Martensson-2
> On Jan 24, 2017, at 2:22 PM, Bengt Martensson <[hidden email]> wrote:
>
> On 01/24/17 19:24, Craig Treleaven wrote:
>>> On Jan 24, 2017, at 7:32 AM, Alec Leamas <[hidden email]> wrote:
>>>
>>> On 24/01/17 13:07, Craig Treleaven wrote:
>>>> The good folks at Home Electronics have lent me a Tira 2.1 IR receiver to test with Lirc under Mac OS X.
> ...
>>> That said, looking at the source it seems that the tira device should be
>>> visible as /dev/ttyUSB?, typically /dev/ttyUSB0 which then is the device
>>> to use.
>
> Correct; the TIRA does serial-over-USB emulation, like FTDI, and many of
> our favorite devices, like Arduino, USB-uirt, CommandFusion, IrToy, but
> unlike commandIR, Iguana,.. As Alec says, with Linux it shows up as
> /dev/ttyUSBn (n = 0,1,2,...). On my Mac (Mac Mini "early 2009", MacOS
> 10.11.6) it shows up as /dev/tty.usbserial-HE00001 as well as
> /dev/cu.usbserial-HE00001. (These two differs in how they treat some
> modem control lines; on Solaris it was /dev/tty* for dial-in and cu for
> dial-out, IIRC.)
>
> So it should work, using one of these devices.
>
Oh, but if I only _had_ those devices!  I don’t know why but I have nothing like that.

$ sudo ls -al /dev/tty.*
crw-rw-rw-  1 root  wheel   17,   0 23 Jan 20:03 /dev/tty.Bluetooth-Incoming-Port
crw-rw-rw-  1 root  wheel   17,   2 23 Jan 20:03 /dev/tty.Bluetooth-Modem

I’m on a MacBook Pro (2011) running 10.10.5.  I can’t imagine that this was
something added in 10.11.  

I will try connecting the Tira to my other Macs.

> BTW, it appears as your goal is to get as many "things" as possible to
> work with MacOS. Have you tried my baby: the Girs driver and (e.g.) an
> Arduino like this: http://www.harctoolbox.org/arduino_nano.html ? It
> "should" work.

My main interest is MythTV on Mac.  I created a standalone all-in-one installer
that makes it easy to run a complete Myth system on OS X.  However, remote
control remains a problem for some people.  The ‘gum stick’ remote works (with certain
Mac models but isn’t very full-featured.  I’ve used Lirc for 8 or 9 years with a
SiliconDust HDHomerun forwarding IR over udp.  Works great for me but new
models don’t have that feature.

In fact, Lirc was my introduction to the MacPorts project.  The fellow that was
maintaining our port at that time worked with me to get udp functioning.  I think the
IguanaIR was the only hardware known to work at that time.  Later, I began contributing
to MacPorts and eventually took over as maintainer for the Lirc port.

I was hoping that if the Tira ‘just worked’, it would bode well for some of the other
USB devices.  Thanks for your explanation about serial-over-USB; that helps me
understand a bit better.

I’ve seen mention of Girs a couple of times.  If you have a Mac, have you not tested Lirc
there?  It is easy enough with MacPorts but that really doesn’t give you a good environment
for Lirc development.  MacPorts is oriented towards reliable, repeatable builds.

Craig
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Device enumerations

Bengt Martensson-2
In reply to this post by Alec Leamas
[Changed subject; this is not Tira anymore]

On 01/24/17 20:36, Alec Leamas wrote:

>
>
> On 24/01/17 19:24, Craig Treleaven wrote:
>
>>
>> It seems that plugins/osx_usbraw.c uses a very different approach to accessing the Sony IR receiver.  It may be that this just isn’t going to work.
>
> Yes... With the new enumerating support in place it's "probably"
> straight-forward to make a patch avoiding the linux devices completely.
> The key thing is that it seems like libusb (both 0.12 and 1.0) exists on
> MacOS as it also does on linux.

I do not claim that I understand the low-level stuff as Alec does, but
here is what I envision (at least for serial-over-USB devices):
Something that delivers a map of human readable descriptions (Vendor,
serialID, etc) to device names. This should both be available as a
command line program, delivering an output like

IrToy -> /dev/ttyACM0
Arduino Uno, serial 12345 -> /dev/ttyACM1

callable both from C and other languages (Python, Java (delivering a
Map<String,File>), ...)

lircd can then just regexp-match the user's device against the keys in
this list. The plugins just contains a regexp that is used if the user's
device is missing. Thus the enumeration code can be taken out of the
plugins, at least for serial-over-USB devices.

I can surely use it in IrScrutinizer too.

Hard do image that something like this does not exist already...???

Greetz,

Bengt


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Testing Tira 2.1

Bengt Martensson-2
In reply to this post by Craig Treleaven
On 01/24/17 23:02, Craig Treleaven wrote:

>> On Jan 24, 2017, at 2:22 PM, Bengt Martensson <[hidden email]> wrote:
>>
>> On 01/24/17 19:24, Craig Treleaven wrote:
>>>> On Jan 24, 2017, at 7:32 AM, Alec Leamas <[hidden email]> wrote:
>>>>
>>>> On 24/01/17 13:07, Craig Treleaven wrote:
>>>>> The good folks at Home Electronics have lent me a Tira 2.1 IR receiver to test with Lirc under Mac OS X.
>> ...
>>>> That said, looking at the source it seems that the tira device should be
>>>> visible as /dev/ttyUSB?, typically /dev/ttyUSB0 which then is the device
>>>> to use.
>>
>> Correct; the TIRA does serial-over-USB emulation, like FTDI, and many of
>> our favorite devices, like Arduino, USB-uirt, CommandFusion, IrToy, but
>> unlike commandIR, Iguana,.. As Alec says, with Linux it shows up as
>> /dev/ttyUSBn (n = 0,1,2,...). On my Mac (Mac Mini "early 2009", MacOS
>> 10.11.6) it shows up as /dev/tty.usbserial-HE00001 as well as
>> /dev/cu.usbserial-HE00001. (These two differs in how they treat some
>> modem control lines; on Solaris it was /dev/tty* for dial-in and cu for
>> dial-out, IIRC.)
>>
>> So it should work, using one of these devices.
>>
> Oh, but if I only _had_ those devices!  I don’t know why but I have nothing like that.

Then THAT, and nothing else is the problem: The OS does not recognize
the device. I think I have even adjusted some EEPROM parameter on the
Mac to have them recognized, but I cannot remember... It may have
something to do with "signed drivers" or such. Search the Internet. This
may be a start:
http://kig.re/2014/12/31/how-to-use-arduino-nano-mini-pro-with-CH340G-on-mac-osx-yosemite.html

Be sure to report the solution when you have found it.

 > I’ve seen mention of Girs a couple of times.  If you have a Mac, have
you not tested Lirc there?

It should "just work", if the device is recognized.

Greetz,

Bengt



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Device enumerations

Alec Leamas
In reply to this post by Bengt Martensson-2


On 25/01/17 09:56, Bengt Martensson wrote:
> [Changed subject; this is not Tira anymore]
>
> On 01/24/17 20:36, Alec Leamas wrote:
>>
>>
>> On 24/01/17 19:24, Craig Treleaven wrote:

>
> I do not claim that I understand the low-level stuff as Alec does, but
> here is what I envision (at least for serial-over-USB devices):
> Something that delivers a map of human readable descriptions (Vendor,
> serialID, etc) to device names. This should both be available as a
> command line program, delivering an output like
>
> IrToy -> /dev/ttyACM0
> Arduino Uno, serial 12345 -> /dev/ttyACM1

The command is mode2 --driver=... --list-devices. The output is a single
line for each device. First word is the 'device', acceptable as argument
to --device for actual driver. The rest is basically free format info,
for use in UI. If present, a string like [1234:5678] is the usb
vendorId:productId. With a linux kernel the info comes from udev in most
cases, even if the enumeration might be based on other sources.

The code is in lib/drv_enum.c and drv.enum.h. There are routines to
enumerate based on glob patterns and libudev enumeration.

Note that in general, devices not always have a name. On linux, the /dev
link is the unique identifier required. MacOS perhaps blurs this picture
(?), but it's possible to adapt as I described.

> Hard do image that something like this does not exist already...???

Indeed. But in master almost all drivers now support it

A *big* exception is drivers using serial connections /dev/tty*. These
are as of now handled by lirc-setuo, and it might be the only reasonable
way since it involves  modprobe settings for irq etc.


Cheers!

--alec

PS Next version 0.9.5 is dead. Long live 0.10.0!  DS

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Testing Tira 2.1

Craig Treleaven
In reply to this post by Bengt Martensson-2
> On Jan 25, 2017, at 4:10 AM, Bengt Martensson <[hidden email]> wrote:
>
> On 01/24/17 23:02, Craig Treleaven wrote:
>>> On Jan 24, 2017, at 2:22 PM, Bengt Martensson <[hidden email]> wrote:
>>>
>>> On 01/24/17 19:24, Craig Treleaven wrote:
>>>>> On Jan 24, 2017, at 7:32 AM, Alec Leamas <[hidden email]> wrote:
>>>>>
>>>>> On 24/01/17 13:07, Craig Treleaven wrote:
>>>>>> The good folks at Home Electronics have lent me a Tira 2.1 IR receiver to test with Lirc under Mac OS X.
>>> ...
>>>>> That said, looking at the source it seems that the tira device should be
>>>>> visible as /dev/ttyUSB?, typically /dev/ttyUSB0 which then is the device
>>>>> to use.
>>>
>>> Correct; the TIRA does serial-over-USB emulation, like FTDI, and many of
>>> our favorite devices, like Arduino, USB-uirt, CommandFusion, IrToy, but
>>> unlike commandIR, Iguana,.. As Alec says, with Linux it shows up as
>>> /dev/ttyUSBn (n = 0,1,2,...). On my Mac (Mac Mini "early 2009", MacOS
>>> 10.11.6) it shows up as /dev/tty.usbserial-HE00001 as well as
>>> /dev/cu.usbserial-HE00001. (These two differs in how they treat some
>>> modem control lines; on Solaris it was /dev/tty* for dial-in and cu for
>>> dial-out, IIRC.)
>>>
>>> So it should work, using one of these devices.
>>>
>> Oh, but if I only _had_ those devices!  I don’t know why but I have nothing like that.
>
> Then THAT, and nothing else is the problem: The OS does not recognize
> the device. I think I have even adjusted some EEPROM parameter on the
> Mac to have them recognized, but I cannot remember... It may have
> something to do with "signed drivers" or such. Search the Internet. This
> may be a start:
> http://kig.re/2014/12/31/how-to-use-arduino-nano-mini-pro-with-CH340G-on-mac-osx-yosemite.html
>
> Be sure to report the solution when you have found it.

Um, the instructions on that page are pretty extreme:  unloading Apple kernal extensions (kext, aka
“drivers”), changing NVRAM settings to boot into kext development mode, etc.  Installing binaries
that came from Chinese and Russian sources. ...

Anyway, on your Mac, Tira mounts a /dev/tty.usbserial-HE00001 device and mine does not.  Either
your software is different…or your Tira is not the same.

The ioreg command can give details of certain objects.  Use the the full name of the device ala
“-n Tira-2@fd120000”.

Details from my setup are:

CT-MBP11:lirc craigtreleaven$ ioreg -w0 -p IOUSB -nTira-2@fd120000
+-o Root  <class IORegistryEntry, id 0x100000100, retain 10>
  +-o EHCI Root Hub Simulation@1D,7  <class IOUSBRootHubDevice, id 0x100000227, registered, matched, active, busy 0 (15 ms), retain 13>
  | +-o HubDevice@fd100000  <class IOUSBHubDevice, id 0x100000290, registered, matched, active, busy 0 (6 ms), retain 15>
  |   +-o IR Receiver@fd110000  <class IOUSBDevice, id 0x1000002a0, registered, matched, active, busy 0 (51 ms), retain 12>
  |   +-o Tira-2@fd120000  <class IOUSBDevice, id 0x100000a58, registered, matched, active, busy 0 (695 ms), retain 11>
  |       {
  |         "sessionID" = 18681502702885
  |         "idProduct" = 64120
  |         "bNumConfigurations" = 1
  |         "iManufacturer" = 1
  |         "bcdDevice" = 1536
  |         "Bus Power Available" = 250
  |         "bMaxPacketSize0" = 8
  |         "USB Product Name" = "Tira-2"
  |         "iProduct" = 2
  |         "iSerialNumber" = 0
  |         "USB Address" = 4
  |         "IOUserClientClass" = "IOUSBDeviceUserClientV2"
  |         "bDeviceSubClass" = 0
  |         "bDeviceClass" = 0
  |         "bcdUSB" = 512
  |         "locationID" = 18446744073660399616
  |         "PortNum" = 2
  |         "IOCFPlugInTypes" = {"9dc7b780-9ec0-11d4-a54f-000a27052861"="IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle"}
  |         "bDeviceProtocol" = 0
  |         "USB Vendor Name" = "Home Electronics"
  |         "Device Speed" = 1
  |         "idVendor" = 1027
  |         "Requested Power" = 55
  |         "IOGeneralInterest" = "IOCommand is not serializable"
  |         "Low Power Displayed" = No
  |       }
  |      
  +-o EHCI Root Hub Simulation@1A,7  <class IOUSBRootHubDevice, id 0x10000022e, registered, matched, active, busy 0 (13 ms), retain 15>
    +-o HubDevice@fa100000  <class IOUSBHubDevice, id 0x10000028f, registered, matched, active, busy 0 (5 ms), retain 17>
    | +-o BRCM2070 Hub@fa110000  <class IOUSBHubDevice, id 0x1000002a6, registered, matched, active, busy 0 (4 ms), retain 13>
    | | +-o Bluetooth USB Host Controller@fa113000  <class IOUSBDevice, id 0x1000002bc, registered, matched, active, busy 0 (60 ms), retain 14>
    | +-o Apple Internal Keyboard / Trackpad@fa120000  <class IOUSBDevice, id 0x1000002aa, registered, matched, active, busy 0 (508 ms), retain 16>
    | +-o USB-PS/2 Optical Mouse@fa130000  <class IOUSBDevice, id 0x1000002b9, registered, matched, active, busy 0 (98 ms), retain 12>
    +-o FaceTime HD Camera (Built-in)@fa200000  <class IOUSBDevice, id 0x10000029a, registered, matched, active, busy 0 (74 ms), retain 15>


Notice the “IOCFPlugInTypes" — I believe this means that the standard Apple USB kext has
got (exclusive?) access to the device.

Bengt, if you run a similar command, what kext is handling your device?  Is your’s a “Tira-2”?  
Any indication that I’ve got a different hardware rev?

Thanks for the help,

Craig



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Testing Tira 2.1

Bengt Martensson-2
On 01/25/17 15:04, Craig Treleaven wrote:
>> On Jan 25, 2017, at 4:10 AM, Bengt Martensson <[hidden email]> wrote:
...

>>>> So it should work, using one of these devices.
>>>>
>>> Oh, but if I only _had_ those devices!  I don’t know why but I have nothing like that.
>>
>> Then THAT, and nothing else is the problem: The OS does not recognize
>> the device. I think I have even adjusted some EEPROM parameter on the
>> Mac to have them recognized, but I cannot remember... It may have
>> something to do with "signed drivers" or such. Search the Internet. This
>> may be a start:
>> http://kig.re/2014/12/31/how-to-use-arduino-nano-mini-pro-with-CH340G-on-mac-osx-yosemite.html
>>
>> Be sure to report the solution when you have found it.
>
> Um, the instructions on that page are pretty extreme:  unloading Apple kernal extensions (kext, aka
> “drivers”), changing NVRAM settings to boot into kext development mode, etc.  Installing binaries
> that came from Chinese and Russian sources. ...

I have boot-args kext-dev-mode=1 in nvram, possibly that makes the
difference. Since with Linux the device shows up for lsusb as FTDI, you
may try to install the FTDI Mac drivers, or follow FTDI's instructions, see
http://www.ftdichip.com/Support/Documents/InstallGuides/Mac_OS_X_Installation_Guide.pdf


>
> Anyway, on your Mac, Tira mounts a /dev/tty.usbserial-HE00001 device and mine does not.  Either
> your software is different…or your Tira is not the same.
>
> The ioreg command can give details of certain objects.  Use the the full name of the device ala
> “-n Tira-2@fd120000”.
>

Mine is not that different:

+-o Root  <class IORegistryEntry, id 0x100000100, retain 13>
   +-o Root Hub Simulation Simulation@04000000  <class
AppleUSBRootHubDevice, id 0x10000025f, registered, matched, active, busy
0 (3 ms), retain 7>
   | +-o IR Receiver@04500000  <class AppleUSBDevice, id 0x100000260,
registered, matched, active, busy 0 (70 ms), retain 14>
   +-o Root Hub Simulation Simulation@06000000  <class
AppleUSBRootHubDevice, id 0x10000026e, registered, matched, active, busy
0 (3 ms), retain 8>
     +-o BRCM2046 Hub@06100000  <class AppleUSBDevice, id 0x10000026f,
registered, matched, active, busy 0 (1 ms), retain 12>
     | +-o Bluetooth USB Host Controller@06110000  <class
AppleUSBDevice, id 0x100000283, registered, matched, active, busy 0 (2
ms), retain 17>
     +-o Tira-2@06400000  <class AppleUSBDevice, id 0x10000055c,
registered, matched, active, busy 0 (4601 ms), retain 14>
         {
           "sessionID" = 8461543888030
           "iManufacturer" = 1
           "bNumConfigurations" = 1
           "idProduct" = 64120
           "bcdDevice" = 1024
           "Bus Power Available" = 500
           "USB Address" = 3
           "bMaxPacketSize0" = 8
           "iProduct" = 2
           "iSerialNumber" = 3
           "bDeviceClass" = 0
           "Built-In" = No
           "locationID" = 104857600
           "bDeviceSubClass" = 0
           "bcdUSB" = 272
           "USB Product Name" = "Tira-2"
           "PortNum" = 4
           "non-removable" = "no"
           "IOCFPlugInTypes" =
{"9dc7b780-9ec0-11d4-a54f-000a27052861"="IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle"}
           "bDeviceProtocol" = 0
           "IOUserClientClass" = "IOUSBDeviceUserClientV2"
           "IOPowerManagement" =
{"ChildrenPowerState"=4,"DevicePowerState"=0,"CurrentPowerState"=4,"CapabilityFlags"=32768,"MaxPowerState"=4,"DriverPowerState"=4}
           "Device Speed" = 1
           "USB Vendor Name" = "Home Electronics"
           "idVendor" = 1027
           "IOGeneralInterest" = "IOCommand is not serializable"
           "USB Serial Number" = "HE000001"
           "IOClassNameOverride" = "IOUSBDevice"
         }


If this does not help, I suggest you seek help from Mac experts.

Greetz,

Bengt

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Loading...