Skip to main content ↑ ↓
Topic: WinLIRC 0.8.6b Configuration (Read 5422 times) previous topic - next topic

WinLIRC 0.8.6b Configuration







Re: WinLIRC 0.8.6b Configuration

Reply #1 –
Thanks, I'll include this in the post about the new WinLIRC driver.
Got a question? Please ask in the forum for the fastest answers.

Re: WinLIRC 0.8.6b Configuration

Reply #2 –
First screenshot was from version 0.6.5, I replaced it with version 0.8.6b. Same window, but different version numbers.

Re: WinLIRC 0.8.6b Configuration

Reply #3 –
Is this a means to test that your (hex) codes are sent ? I tried this with Hercules, but ping-ing gives an error... (wrong port?)

btw: this gave me some problems ?! as it did not work, I changed to the Serial TAB, and tried to open the COM3 port (in my case). that gave an error (conflicting with WinLIRC I assume). I quit WinLIRC, but still no go. Ended up rebooting my PC, and tried only Hercules on COM3, but I get no response (with T command) at all now.
So: I decided to bridge my UIT so that it would appear in my HID overview, and thought I would find the TCPIP port there. Unfortunately, I got a driver error now (similar to the one I got when using the terminal with $). Luckily, it did not lock up my UIT. Tested it afterwards, and still working (i can still program my rc).

bottomline: something went wrong when conflicting between WinLirc and Hercules. I'm pretty confident that if I update the firmware again under XP that it will work (but i'm not bothered for the time being)...
(note: when it did work and I sent a T command, I only get a FA02 message whether pointing to a white sheet or not). When I first connected the UIT - with its original firmware - it immediately returned V102 (or v101, can't remember exactly))

Re: WinLIRC 0.8.6b Configuration

Reply #4 –
For looking at hex codes use the "Serial" tab, the "TCP Client" tab allows you to see the messages it sends to whatever other application might be listening to these messages, like PC control software, script, etc.

1) Make sure WinLIRC is running.
2) Make sure to enter address 127.0.0.1, port 8765 in Hercules.
3) Make sure your firewall is allowing the connection, disable it if in doubt (or "allow all"). Firewalls sometimes fail to ask if you want to allow a connection.

Re: WinLIRC 0.8.6b Configuration

Reply #5 –
Thanks for the report about the self-test. I've been messing with it in the last few releases.

Usually only one program can open a serial port at a time, for example I don;t think it's normally possible to open WinLIRC and Hercules at the same time. If you wanted to spy on the traffic between the IR Toy and WinLIRC you could use something like portmon.
Got a question? Please ask in the forum for the fastest answers.

Re: WinLIRC 0.8.6b Configuration

Reply #6 –
you can; just do not connect Hercules to your Com port while WinLirc is running (and connected to that very same port).

in the meantime, I've simply restored my recent ghost copy of windows 7 (as I first wanted to see if it was a hw problem, rather then a sw one); and everything is fine again. This means that the aforementioned situation causes some sort of driver conflict (under win 7?).
I'm pretty sure this can be resolved without such a drastic restore, but i'm not planning in reproducing this on purpose :)

as for liyin:
do i understand that the winlirc server is listening on port 8765. I did precisely what is shown in your printscr (and explanation), but no response if i just send some codes via winlirc... is it obligatory to have a receiving programming running ?
in this last case, i read then: winlirc receives incoming ir codes (from a remote control), then sends it to an application over port 8765 ?! Bs player can work with winlirc; at least i saw an option reference there. so i could try that...

Re: WinLIRC 0.8.6b Configuration

Reply #7 –
Always make sure is not the firewall (or any security program), just verifying before posting I tried getting TCP data on Hercules and got the same error (no pinging, no data) and no notification from the firewall. I tried again some minutes later and the firewall alerted me of the connection, which I allowed and everything worked fine.

Quote
do i understand that the winlirc server is listening on port 8765.

WinLIRC sends messages on port 8765 and your application (BS Player) should listen to this port (localhost address).

Quote
is it obligatory to have a receiving programming running ?

No, WinLIRC doesn't check if anyone is listening (normal behavior).

WinLIRC has been around for a long time now, so is not hard to find programs or plugins that work with WinLIRC.