Skip to main content ↑ ↓
Topic: post update: will no longer receive and port not freed (Read 2792 times) previous topic - next topic

post update: will no longer receive and port not freed

Hi,
Received new Toy today.
All was working fine until i moved all to another PC.
Then it stopped working and the LED stayed lit.
So I (blindly) did as was suggested when this happens and updated to firmware v22.
The update seemed to work fine (it said "completed").
But now the unit will not receive at all.

If I try to record ("Create Config" in WINLIRC), it just says "something went wrong" - then the window eventually closes.

And it seems that something is preventing the virtual port from being freed w WINLIRC:
WINLIRC starts up ok (but will not receive).
And if i re-configure, it times out and goes RED (in the system tray).
Then no software will work until i disconnect/re-connect (to free the port).

Self test *does* work.

I've updated the firmware some 20 times now, and am out of ideas (and patience).
WHAT AM I DOING WRONG ???

Thanks,
Mark

Re: post update: will no longer receive and port not freed

Reply #1 –
You sure you have selected the correct com port ? And you tried IRGraph in winlirc, if you close winlirc and open it, you should be able to see raw signals from the device. If that works, recording should too.

Re: post update: will no longer receive and port not freed

Reply #2 –
Problem "SOLVED" (at least to a satisfactory degree):
I left the unit (plugged in to the PC that it originally worked on) for a few days (with no software running).
Then when i tried it again, it WORKED (have no idea why, as i changed nothing).
Then i re-connected it to the PC/USB-hub upon which it failed - did not work.
At this point, i suspected an issue w the USB hub (which is a quality hub, btw).
So i connected it to "native" USB port on that PC - and it WORKED.

CONCLUSION:
There is something about my hub (or hubs in general?) that causes the Toy to fail.

The remaining mystery is why would the Toy start working again after a few days of inactivity.

Re: post update: will no longer receive and port not freed

Reply #3 –
UPDATE:
Though I was able to get it to work for a while (on a native USB port), WINLIRC eventually stopped receiving.
Could only restore operation via a reboot.
Gave up - INTO TO THE DRAWER IT GOES :-(.

FYI:
I purchased the StreamZap remote (in hopes it would work).
Works fine w the StreamZap software.
But receives fail with WINLIRC (on 2 diff PCs - Win32 and WIN64).
The only thing I have found that works with WINLIRC is the Packard Bell Fast Media.
But it requires a physical serial port.

Re: post update: will no longer receive and port not freed

Reply #4 –
For streamzap with winlirc, you must close their software otherwise it can't work. Only one handle to a device is allowed.

Re: post update: will no longer receive and port not freed

Reply #5 –
i did so.
never could get it to receive any signals under any circumstances (or any PC).