JP1.2 cable does not work with JP1.3 remote

rodenti · Post by **rodenti** » Sun Sep 30, 2007 10:35 am

I have a JP1.2 cable that I purchased from diygadget earlier this year and it works great with all the JP1.2 remotes that I own but I tried it with a JP1.3 remote yesterday and IR doesn't detect it. (all remotes are Atlas 5 Day remotes)

Everything that I have read in the forums indicate that JP1.2 cables were alse compatible with JP1.3. Do I have a faulty JP1.3 remote, or is my cable specific to JP1.2 only?

Thanks.

binky123 · Post by **binky123** » Sun Sep 30, 2007 10:38 am

What version of IR7 do you have? I recall we had some timing issues with the jp12serial.dll on a JP1.3 remote. Try IR7.06.

rodenti · Post by **rodenti** » Sun Sep 30, 2007 7:32 pm

Does this mean that the cable should work with jp1.3 remotes?

I am already using IR7.06. Is there anything else that I can try?

Thanks.

binky123 · Post by **binky123** » Sun Sep 30, 2007 8:35 pm

Yes, a JP1.2 cable should work for a JP1.3 remote. Maybe you can try running the testing programs or perhaps you don't have a JP1.3 remote? Not sure what else to say.

rodenti · Post by **rodenti** » Sun Sep 30, 2007 10:20 pm

Step 1 of all troubleshooting tips should be to make sure you have fresh batteries in your remote.

RM now connects with my remote so my jp1.2 cable does indeed work with jp1.3 remotes.

Thanks for your help, I guess all I needed was verification that the cable should work with my remote for my brain to start working properly.

rodenti · Post by **rodenti** » Fri Oct 05, 2007 12:05 pm

Now that I have gotten my remote to work I am getting the following message when downloading from the remote with IR:
There is a conflict at fixed data Address $0200. Do you want to replace the existing data with the fixed data.

I have found other threads mentioning this message with the Atlas JP1.3 remote, but none at address $0200. What can I do to resolve this download message?

Thanks.

UPDATE: I downloaded the "RDF for 30003000 Atlas 5 PVR with Day button. JP1.3." from http://www.hifi-remote.com/forums/dload ... le_id=3953 and it no longer gives me the message.

Now it looks like I have two RDFs for this remote:
OLD one: 30003000 (Atlas 5-device PVR Day JP1.3).rdf
NEW one: 30003000_(Atlas_5-device_PVR_Day_3000_JP1.3).rdf

There are several differences between the two, most notably the processor (S3C80 and SCF80), the RAM address ($FF00 and $FE80), and the fixed data section ($0200, which is the address of my error above).

Should I keep both RDFs, or does the newer one supercede the previous one even though they have different names?

binky123 · Post by **binky123** » Fri Oct 05, 2007 12:33 pm

You should keep the new one and also remove the underscores from the filename. The underscores are added by IE7. The filename should be
30003000 (Atlas 5-device PVR Day 3000 JP1.3).rdf

greenough1 · Post by **greenough1** » Thu Oct 25, 2007 4:37 pm

I had this error. I downloaded the above file and made the edit to the filename as above.

When I download from the remote, I get 2 blicks and the IR file is blank (no devices or anything) and still has the default name for IR (REmote Control Programmer).

I'm running IR 7.06 and RDF's v 1.27 with the above linked file replacing the distributed rdf and renamed as above.

The interface works (thanks Tommy) and detects the correct sig for this jp1.3 remote, sig 30333033, memory address is $0600 and memory size is $140.

jeff

greenough1 · Post by **greenough1** » Thu Oct 25, 2007 6:47 pm

I tried again - unrolled the distributed rdf, downloaded the rdf, renamed it, and now it seems to work. Now on to setting it up.

jeff

Post by **The Robman** » Thu Oct 25, 2007 7:42 pm

This just in from Tommy Tyler...
http://www.hifi-remote.com/forums/viewtopic.php?t=9042

greenough1 · Post by **greenough1** » Thu Oct 25, 2007 8:35 pm

Hi Rob,
thanks for the pointer. My inability to get it to work was probably a minor mis-type of the rdf name. It seems to be working now.

thanks to Capn and binky for blazing the trail for me.

Best,
jeff