Page 1 of 2

New version of JP1.2 serial driver - testing needed!

Posted: Sat Mar 21, 2009 10:57 am
by xnappo
Hello all,

The JP1.2/JP1.3 serial driver has, in the past, been modified to work with various tools and operating systems.

I have attempted to combine all of the modifications necessary to make the .dll/.so compatible with both IR and RM-IR and Windows/Linux.

I have tested as much as I can, but I only have one type of remote (Atlas OCAP 1056) and one interface (Tommy USB).

Please try the driver below with your setup, and let me know if it works for you, and what your configuration is:
http://www.hifi-remote.com/forums/dload ... le_id=6430

Thanks!
xnappo

Posted: Sun Mar 22, 2009 5:18 pm
by gfb107
xnappo, where's the updated Linux library? I expected it to be included in this zip file.

Posted: Sun Mar 22, 2009 6:09 pm
by johnsfine
Is there a 64bit linux .so version anywhere?

Or where is the source code?

Posted: Sun Mar 22, 2009 6:52 pm
by xnappo
gfb107 wrote:xnappo, where's the updated Linux library? I expected it to be included in this zip file.
Sigh. Sorry wrong file. Try now.

xnappo

Posted: Sun Mar 22, 2009 6:53 pm
by xnappo
johnsfine wrote:Is there a 64bit linux .so version anywhere?

Or where is the source code?
Hi John, see PM..

xnappo

Posted: Thu Mar 26, 2009 6:26 am
by gfb107
xnappo,

The new dll/.so seems to be missing the function Java_com_hifiremote_jp1_io_JP12Serial_getPortNames( JNIEnv *env, jobject jobj )

Posted: Thu Mar 26, 2009 6:55 am
by xnappo
gfb107 wrote:xnappo,

The new dll/.so seems to be missing the function Java_com_hifiremote_jp1_io_JP12Serial_getPortNames( JNIEnv *env, jobject jobj )
True - I left the port searching the way it was in 0.10. It seems to work for me like that. If you need that function for something in RM-IR I can try putting it back in the way you had it along with the isPortAvailable function.

[EDIT] I just tried, and I can get those functions back in - but where are they used?

xnappo

Posted: Thu Mar 26, 2009 7:22 am
by gfb107
Those functions are both used in RMIR when the user wants to specify the port the remote is connected to (Remote -> Interface -> (comm method)) instead of letting the comm library search.

A dialog pops up showing the list of available ports known to the comm library, allowing the user to choose one. The user can also choose Other and enter the desired port. This is particularly useful for JP1.X Serial on Linux cause different distributions have different names for the serial ports and especially for the USB serial ports.

It is also needed for the parellel port comm library if the user has added a parallel port card that uses a non-standard I/O port range.

Posted: Thu Mar 26, 2009 7:53 am
by xnappo
gfb107 wrote:Those functions are both used in RMIR when the user wants to specify the port the remote is connected to (Remote -> Interface -> (comm method)) instead of letting the comm library search.

A dialog pops up showing the list of available ports known to the comm library, allowing the user to choose one. The user can also choose Other and enter the desired port. This is particularly useful for JP1.X Serial on Linux cause different distributions have different names for the serial ports and especially for the USB serial ports.

It is also needed for the parellel port comm library if the user has added a parallel port card that uses a non-standard I/O port range.
Okay - I guess that when you select that and are using a version or the .dll/.so that doesn't have the function, RM-IR just ignores it - so I never saw that feature!

I will post a new version tonight assuming I see that dialog now with the functions in there.

xnappo

Posted: Thu Mar 26, 2009 8:28 am
by gfb107
It's not so much that RMIR ignores it, it's that I didn't allow for the functions not being implemented when I wrote that part of the code, so I don't catch and handle the exceptions that get thrown when I call them. All the code associated with the dialog is circumvented when that happens.

Posted: Thu Mar 26, 2009 9:34 am
by xnappo
gfb107 wrote:It's not so much that RMIR ignores it, it's that I didn't allow for the functions not being implemented when I wrote that part of the code, so I don't catch and handle the exceptions that get thrown when I call them. All the code associated with the dialog is circumvented when that happens.
It is just interesting that it still selects the serial driver anyway. Anyhow - of course this is a good and needed function. As mentioned in the Linux thread I put up some betas with the code today and will update all the packages tonight.

xnappo

Posted: Thu Mar 26, 2009 4:50 pm
by xnappo
xnappo wrote: As mentioned in the Linux thread I put up some betas with the code today and will update all the packages tonight.

xnappo
Both the binary and source packages have been updated to version 0.12 with support for the 'get ports' function.

Regards,
xnappo

Posted: Sun Mar 29, 2009 11:32 am
by xnappo
There was a bug with the RM-IR wrapper function for writing to the remote in version 0.12 of the driver and earlier. I have uploaded version 0.13 with this fixed.

xnappo

Posted: Sun Apr 05, 2009 8:37 am
by mathdon
Is version 0.13 stable enough to be included in the IR 8.00 distribution?
_________________

Graham

Posted: Mon May 18, 2009 9:46 pm
by TheShanMan
How possible is it for you to get it working in x64 windows (xp in my case)? I only run IR once every several years when I get a new remote (which I just did today), so I'm a perpetual noob and have to re-learn everything each time, but I'm fully willing to help with any testing you might need. In the meantime I guess I'll have to fire up a vmware image to use IR. :(