0810alpha2 USB-UIRT, HA-22 ZWave stick not detected

[qball4]

I'm having the same problem on the latest 0810 build with the MCV Z-Wave dongle and the UIRT. If I add the MCV dongle manually in the webadmin it works fine, but I'm stuck on the UIRT for now. I'm reinstalling 0810 for the third time tonight and if it still doesn't work I'll post some the syslog.

:Matt

[rodercot]

 Hey J,
 
 So I reinstalled the latest 8.10 with the same issues as the first time. I also plugged in my fiire chief this time and it does not work properly either, mapping is off, none of the functions work, vol, media, transport controls etc. 

 USBuirt - I have tried modifying the device template for the uirt with no luc , I try to pull up a log "errors or tail" and the log does not exist, It does detect and register the device when I tail dmesg.

 Mine is on /dev/ttyUSB0 and I try forcing that address in the webadmin or via the template but ofcourse it defaults back to the pci string, which if I recall for my TV (sharp aquos) was a problem, I am trying to find notes on how I fixed that.

 BUT hey I have my mce remote working I have not tried and transmits with it yet and DVD playback is working - YEH!!!

 Dave

[tschak909]

The Fiire Remote will not work, until HIDRemote.cpp in Orbiter gets a major rewrite.

The 8.10 kernel has facilities for parsing raw HID packets, which are now interfering with the libusb calls that Orbiter needs to make to control and bind to the remote. I am looking for a solution, but as of now, priority of adding support for the GYR3101US and a Generic kernel input device decoder takes precedent.

-Thom

[rodercot]

The Fiire Remote will not work, until HIDRemote.cpp in Orbiter gets a major rewrite.

The 8.10 kernel has facilities for parsing raw HID packets, which are now interfering with the libusb calls that Orbiter needs to make to control and bind to the remote. I am looking for a solution, but as of now, priority of adding support for the GYR3101US and a Generic kernel input device decoder takes precedent.

 -Thom

 Thom,

 Thanks for the update on the Fiire Remote. You know one thing, I found interesting is as soon as I plugged in the dongle, lmce ofcourse installed it right away, BUT also downloaded perl libft and id-my-disc without failing this time, not sure if this is related to the latest update or plugging in the fiire - stranger things have happened.

 Dave

[rodercot]

 USBUirt is now responding to mce remote commands, again I am not sure if this from the update of a couple days ago as I did not have it plugged in at the time. I just setup the device manually, then in the USBuirt core/hybrid tree I set the device to the pci bus and saved it and then in the USB UIRT 0038 device template I changed the comm method to usb from please select and then regen the orbiter, at first I got a kernel panic and had to reboot but then after I rebooted I realized I did not save my changes in the device template for comm method but it is now responding ok. I have not tried transmitting or learning yet.

 Dave

[hari]

do we still have that usb detection problem?

[tschak909]

It seems anything that sits on the end of a usb to serial chip isn't being detected properly.

-Thom

[posde]

And tschak said, he will fix it it might get fixed this week ...

[jimmejames]

Surely somebody else has to have done a fresh install using the 0810 scripts and come up against this?

As of tonight (May 3) I am running the latest alpha build and am getting a "failed to start" error after trying to manually add the MCV z-wave dongle (template 1754) to the core/hybrid- the device was not automatically detected.  (I'm using this controller:  http://shop.micasaverde.com/index.php?main_page=product_info&cPath=110&products_id=151) I hate to waste time on the IRC for what could be a simple issue- so if someone has something they would like me to try let me know.  I'm running 10x HA20 in-wall dimmers and a HA07 master controller FWIW.

Thanks

[totallymaxed]

Surely somebody else has to have done a fresh install using the 0810 scripts and come up against this?

As of tonight (May 3) I am running the latest alpha build and am getting a "failed to start" error after trying to manually add the MCV z-wave dongle (template 1754) to the core/hybrid- the device was not automatically detected.  (I'm using this controller:  http://shop.micasaverde.com/index.php?main_page=product_info&cPath=110&products_id=151) I hate to waste time on the IRC for what could be a simple issue- so if someone has something they would like me to try let me know.  I'm running 10x HA20 in-wall dimmers and a HA07 master controller FWIW.

Thanks

See Thom's post above.... "It seems anything that sits on the end of a usb to serial chip isn't being detected properly."

All these devices...MCV Stick, USB-UIRT, etc etc are buit around usb to serial components...

This issue is being worked on... be patient ;-)

Andrew

[posde]

totallymaxed,

it is not about detecting.

jimmejames has a problem with the stick, after he manually added it. First under the core, and after  that under the Core/Hybrid device.

[jimmejames]

I'm not pushing for a fix- just offering another test box.  I put the nas on a separate network so the GF has her music and my LMCE setup can be completely dedicated to testing.

[tschak909]

awesome, thanks. I'm trying to work towards a solution.

-Thom

[totallymaxed]

totallymaxed,

it is not about detecting.

jimmejames has a problem with the stick, after he manually added it. First under the core, and after  that under the Core/Hybrid device.

Hmmm...I did not mention auto-detection at all as far as i can see. This is an issue with usb connected serial devices... it has nothing to do with auto-detection per-se

Andrew

[tschak909]

The Problem is of course, related to HAL.

It seems that serial devices are reported differently under more recent versions of HAL. Our HAL DCE device has to be modified as a result. I'm trying to figure out WHAT exactly changed by cross referencing lshal outputs from 7.10 and 8.10.

-Thom