PDA

View Full Version : PIR-1, Windows 10 startup issue



fredrikno
February 22nd, 2016, 04:53 PM
Under Windows 10, the PIR-1 doesn't receive IR events unless I unplug the USB cable and plug it in again. After this, the PIR runs perfectly.
This is 100% reproducible and happens every time I reboot the PC.

I'm running the latest Girder 6.0.16.3. The PC is running Windows 10 on an ASUS Z170I motherboard.


Are there any log files I can check for what can cause this issue? The PIR-1 shows up in Device Manager as a HID Keyboard Device directly after reboot so it seems recognized by Windows properly.


Regards
Fredrik

Ron
February 22nd, 2016, 04:57 PM
Is it able to send IR signals before you do the unplug and replug? Is it 32 or 64 bit windows? Does restarting Girder make any difference?

fredrikno
February 22nd, 2016, 05:19 PM
Is it able to send IR signals before you do the unplug and replug? Is it 32 or 64 bit windows? Does restarting Girder make any difference?

I'm only using it as a receiver, never tried to transmit

It's 64 bit windows

Restarting makes no difference. I'm running in Local mode.

Ron
February 22nd, 2016, 06:04 PM
OK. Thanks, let's work on this tomorrow. I'll probably have a new firmware for your PIR-1. I assume it's a new PIR-1?

fredrikno
February 23rd, 2016, 10:33 AM
OK. Thanks, let's work on this tomorrow. I'll probably have a new firmware for your PIR-1. I assume it's a new PIR-1?

Not exactly. I bought it Nov 29th, 2012. Maybe you fixed it in firmware already?

It had issues under Win7/8 as well, but there I could solve it by rebooting another time (which always worked) and wasn't needed that often since it's my HTPC which runs basically 24/7. With the new motherboard and Win10, I actually have to crawl under the table and replug cables... muuuch more annoying.

/Fredrik

Ron
February 23rd, 2016, 10:43 AM
Hmm, that's a PRE mk2 PIR-1. Maybe we can exchange your PIR-1 for a newer unit. Are you in the US?

fredrikno
February 23rd, 2016, 01:15 PM
Hmm, that's a PRE mk2 PIR-1. Maybe we can exchange your PIR-1 for a newer unit. Are you in the US?

That may be the easiest instead of spending time on old hardware.

I'm located in Sweden. My address details can be found in the original order #493

Ron
February 23rd, 2016, 02:04 PM
Hey we've shipped you a replacement PIR-1. Please hold on to the old one for a bit till we are sure the new one does the trick. I'll send you the tracking number in an email.

Bought in 2012, no fuss free replacement in 2016, that's not bad customer service I hope!

fredrikno
February 23rd, 2016, 04:17 PM
Hey we've shipped you a replacement PIR-1. Please hold on to the old one for a bit till we are sure the new one does the trick. I'll send you the tracking number in an email.

Bought in 2012, no fuss free replacement in 2016, that's not bad customer service I hope!

Ron, you have always provided great support, but I had NOT expected this. THIS is what great service looks like!

fredrikno
February 29th, 2016, 01:09 PM
Ron, you have always provided great support, but I had NOT expected this. THIS is what great service looks like!

Hi Ron,

I got the replacement unit today. That was quick!

Unfortunately it did not solve the issue. I swapped it, rebooted and still needed to replug the USB cable to get it working.

Is there anything else I can try?

fredrikno
February 29th, 2016, 01:50 PM
I did some testing... removing OTHER USB devices and rebooting about 30 times.

If I remove my keyboard (Logitech TK820 with integrated trackpad) and reboot - the PIR works! Replug keyboard, reboot - PIR fails. The keyboard uses Logitechs unifying receiver and has both the keyboard and a separate mouse connected to it if that makes any difference.

Another interesting fact, might be critical in debugging is that when I enter the faulty state - with everything plugged in and PIR not working, the first event I get from Girder is the "PIR-1 Removed" event when I pull the cable. So the PIR seems to be detected at boot, it just doesn't receive the IR events!

Ron
February 29th, 2016, 02:57 PM
I'm going to prepare a firmware that does not expose the keyboard endpoint. Maybe that is confusing your computer.

Ron
February 29th, 2016, 03:28 PM
I hadn't seen your update, that is _very_ interesting.

Let me think about that for a bit. Maybe a driver update will be enough... Does the remove message have the PIR-1's serial number in PLD1?

Ron
February 29th, 2016, 03:54 PM
Can you replace pirlib.dll with the attached version. Then run debugview (https://technet.microsoft.com/en-us/sysinternals/debugview.aspx)after startup and use a remote to send a few IR codes to Girder. Copy and paste the output here.

fredrikno
March 1st, 2016, 12:04 PM
Can you replace pirlib.dll with the attached version. Then run debugview (https://technet.microsoft.com/en-us/sysinternals/debugview.aspx)after startup and use a remote to send a few IR codes to Girder. Copy and paste the output here.

This will hopefully give you an idea:

[5492] WARNING: QApplication was not created in the main() thread.
[5492] SetProcessDpiAwareness failed: "COM error 0xffffffff80070005 (Unknown error 0x0ffffffff80070005)"
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[5492] qrc:///Qml/Common/CNText.qml:5:30: Unable to assign [undefined] to double
[3624] shell\lib\bindctx.cpp(1144)\explorerframe.dll!0000 7FFAD7EA186D: (caller: 00007FFAD7EBDE22) ReturnHr[PreRelease](8) tid(1d00) 80070057 The parameter is incorrect.

Ron
March 1st, 2016, 12:07 PM
That's not at all what I expect to see. Would you have time to do an remote desktop session in a bit?

fredrikno
March 1st, 2016, 12:08 PM
For reference, here's what I get during replugging the PIR and sending commands

fredrikno
March 1st, 2016, 12:11 PM
That's not at all what I expect to see. Would you have time to do an remote desktop session in a bit?

Sure, just let me know what to do. Should I reboot first?

Ron
March 1st, 2016, 12:23 PM
Give me about 15 minutes, I will contact you via email.

Ron
March 1st, 2016, 12:47 PM
Are you around? I've sent the invitation for the remote desktop session.

Ron
March 1st, 2016, 02:25 PM
For those of you following this. We've found the issue and have it fixed. If your PIR-1 is exhibiting the behavior in this thread, drop me an email (support@promixis.com) and I'll set you up with the modified firmware. PIR-1 shipping starting today will have the updated firmware.