Yes I did that.gfb107 wrote: In the menu bar, Remote -> Interface -> JP1.X Serial
That tells rmir to use serial rather than parallel.
What tells it which serial port to use? I have only one, but I'm not sure even Mepis knows that, much less rmir.
Moderator: Moderators
Sorry for the oversight. I have uploaded a minimally tested 32-bit Linux binary version here:gfb107 wrote:See the discussion starting at http://www.hifi-remote.com/forums/viewt ... 4998#74998
When you click Remote -> Interface -> JP1.X Serial you should see a dialog giving you the choice toTurns out that doesn't work with the latest driver, because 2 functions RMIR uses for that were left out of the .so file.
- Auto-detect
- Choose from the known, available Serial ports
- Enter the name of an Other port
First several times it had all sorts of problems: access violation dialogs were popping up, lots of error messages in the shell window I started it from about unimplemented ntoskrnl functions, IR.exe kept forgetting the rdf directory I gave it. Every download from the remote double blinked both the remote and the indicator in bottom left of IR and when sometimes it reported the correct signature in an rdf not found error message. But regardless of whether it reported rdf not found or not, it never had any data, no raw data, no indication that it knew the remote type, nothing. Also no behaviors other than having no data and double blinking was reproducible. Different errors every time I tried the same thing.xnappo wrote: Also - have you tried running IR with WINE? Does that work?
I already edited Makefile_Linux enough that I can do that. But it certainly didn't start out able to do that. Then I needed to mess with LD_LIBRARY_PATH to get it to find libjp12serial.so, then I added lots of printfs to get a clue what it is doing. I didn't really get any clue.xnappo wrote: The test programs are with the source, just run 'make -f Makefile_Linux jp12test.exe'
johnsfine wrote:I doubt it is the baud rate, but there are a TON of other serial port settings that could cause a failure. When I first started messing with this, the only way anything would work was if I turned off my computer, turned it on, ran IR using WINE and THEN ran RM-IR. I figured out that the problem was that the serial driver wasn't specifying all of the serial parameters. To debug, I used the command 'stty -a -F <port>' to report how the port was set after running IR and then added those settings to the serial driver.xnappo wrote:
The jp12test and rmir still fail totally. Wild guess is they never set the right baud rate on the serial port. Any way to test that?
Not sure if that will help or not...
xnappo
John, any chance that this will lead to you providing DecodeIR shared libraries as part of the 'normal' DecodeIR distribution? Support for decoding learned IR signals is almost as important as being able to upload to/download from remotes.johnsfine wrote:I'm trying to use rmir in 64 bit Mepis Linux.