JP1 Remotes

mathdon · Posted: Tue Apr 07, 2015 5:29 am Post subject:

OK, I am right out of ideas. To go further needs a Mac expert. I will PM one and ask him to look at this thread.
_________________
Graham

laudou · Joined: 15 Dec 2013 Posts: 20 Location: Canada

Hi Graham

I'm sorry I gave you all those headaches. Meanwhile, I am still unable to load an upgrade to that Atlas remote even when using Windows 8.1 where RM keeps giving me a "No remotes found" message.

Have a nice day

Laudou

mathdon · Posted: Tue Apr 07, 2015 10:56 am Post subject:

We're not giving up. Unclemiltie, an experienced Mac user, is going to look at this thread and give you the benefit of his experience with RMIR on a Mac.

As for "No remotes found" with the Atlas 1056B01 under Windows, that is a separate puzzle. I've looked again at your earlier messages and you say the other remote you have successfully downloaded on Windows is a URC-8990. I can't find such a remote among the ones we support. Is there is a misprint in the number? If not, and you can download it, please look at the Raw Data tab and tell me what that lists (on the right-hand panel) as Interface. Is it by any chance JP1.2? The Atlas is JP1.3. If they are both JP1.3 then it suggests to me that there is something wrong in the hardware of the Atlas, as even if there is some reason why RMIR cannot download from the Atlas, it should at least recognise its presence. However, we have recently come across a Chinese-made interface lead being advertised as supporting JP1.3 when it in fact only supported JP1.1 and JP1.2.

Edit: A weird thought! I've just looked at my Atlas 1056 B03, whose external appearance is the same as the B01. I see that the 6-pin connector is the other way round from my other remotes. Looking into the battery compartment, pin 1 is top right. Have you by any chance got your lead the wrong way round when using the Atlas?
_________________
Graham

unclemiltie · Posted: Tue Apr 07, 2015 11:03 am Post subject:

Graham asked me to respond since he knows that I use a Mac for "most" of my JP1 work (extender development has to be done on PC since the S3F8 assembler still only runs on Windows, but I do it on a Parallels virtual machine)

I am currently running RemoteMaster 2.03 build 14 on my Yosemite Mac (10.10.2) with no issues.

There are a couple of things that you need to get right to get the thing to work properly:

1: download and install the FTDI drivers for Mac, the version that I am using is

FTDIUSBSerialDriver_v2_2_16

and is available on the FTDI site

2: you need to make sure that you have the JP1 serial libraries in the right spot within the folder that holds the RemoteMaster.jar file. this is

/Mac OS X-x86-64

There are three files in there that come with the distribution:

libDecodeIR.jnilib
libhidapi.jnilib
libjp12serial.jnilib

Note: Graham, I remember when I upgraded to Yosemite that I had to rename some of those files since the newest JVM on Mac applied some different file extensions and things weren't working, but I think you were going to force the issue in a newer release of the code. Could that be the issue?

3: I did not need to run any of the scripts for Linux to make it work. I don't know if maybe the Linux script screwed up some of the mac stuff? I'd suggest re-downloading and re-installing into a different folder so that you get the "clean" permissions, etc.

if you need me to look up some permissions or other things let me know. I've been running JP1 tools on Mac for a couple of years now and it all seems to work pretty well. There are the occasional issue like when the JVM decided to look for new default file extensions, but in general things are good.

FYI - Graham, there are still numerous warnings in the master.err file on my mac, mostly about protocol versions and names. I assume you know about this but if you would like me to send it to you let me know.
_________________
this JP1 stuff is a sickness!

mathdon · Posted: Tue Apr 07, 2015 11:20 am Post subject:

Further to unclemiltie's reply:

a) the serial libraries should automatically be in the right place when you unzip the RMIR distribution, and the issue with extensions in the latest JVM is resolved in all builds of Alpha 28.

b) Don't worry if you don't see libhidapi.jnilib in the library folder immediately after unzipping the RMIR distribution. It is created by RMIR when you first run it, and only in the library folder your setup actually uses (i.e. 32-bit or 64-bit).

Do note my edit to my previous post. I have this nasty suspicion that you are connecting the interface cable the wrong way round.
_________________
Graham

laudou · Joined: 15 Dec 2013 Posts: 20 Location: Canada

Hi
You are right, I mistyped the URC #. Actually, it is a 8910. I just repeated the experience with my URC-8910 downloading from remote using RM 28 v19 on my mac using Yosemite 10.10.2. I then tried downloading from the Atlas remote and I got the same RM message saying that the download error that it might be due to a bug in RM and suggesting to make a raw download and send it to your diagnosis area, which I just did.

My Atlas remote is China made. It bears the Time Warner Cable sign on its front face. As you are saying, pin number one is located in the top right corner and I did try placing the JPI connector int the two possible positions: they both return error message described above.

Thanks again

laudou · Joined: 15 Dec 2013 Posts: 20 Location: Canada

Hi
Thanks for helping me.

To begin with, let me tell you that I tried to load an upgrade to my Atlas1056B01 remote via VMWare Fusion running Windows 7. The result was a bit different from what I got with my Mac and from my PC. In fact, when I clicked on "upload to remote" the normal uploading activity symbol at the bottom of the RM window started up and continued after the infamous "no remotes found" window appeared. I had to cancel the upload that was obviously not working in spite of the "right" appearance. I should mention that all my attempts were made using RM 2.0.3 Alpha28 Build 19.

FTDIUSBSerialDriver_v2_2_16 does not seem to be available for download from FTDI site that is why I downloaded v.2.2.18. I checked the /Mac OS X-x86-64 folder and the necessary files are there.

I am afraid I made you guys spend a lot of time on what might be a hardware problem with the Atlas remote I just bought.

If that is the case, will you forgive me?

Thanks again
Laudou

mathdon · Posted: Tue Apr 07, 2015 1:13 pm Post subject:

Hi, Laudou
As far as I can see, you haven't said whether your attempt to download your URC-8910 on the Mac was successful. Do please let us know. If you can use the Mac to download from the URC-8910 but not the Atlas, as they are both JP1.3 remotes I think we have to conclude that there is a fault in the Atlas. If you can download from the URC-8910 in Windows but not the Mac then there is still something that we need to investigate.
_________________
Graham

mdavej · Expert Joined: 08 Oct 2003 Posts: 4501

The 8910 is JP1 EEPROM, not JP1.3.

ElizabethD · Advanced Member Joined: 09 Feb 2004 Posts: 2348

laudou · Joined: 15 Dec 2013 Posts: 20 Location: Canada

Yes, I was able to download from my URC-8910 on my Mac after installing the FTDI software but not the Atlas. As for Windows I will have to do the tests over again to make sure I give you the right answer. I'll report as soon as I am done.

mdavej · Expert Joined: 08 Oct 2003 Posts: 4501

mathdon · Posted: Tue Apr 07, 2015 5:38 pm Post subject:

laudou · Joined: 15 Dec 2013 Posts: 20 Location: Canada

mathdon · Posted: Wed Apr 08, 2015 3:26 am Post subject:

Wow, success at last Very Happy

. Could you finally confirm that you are using build 19 on the Mac to do your upload? It would be nice to have confirmation that build 19 really does work with the Mac. And are you starting it by simply double-clicking the .jar file?
_________________
Graham