JP1 Remotes

Greetings Everyone,
I used to own a ZaapTV 209 and it worked perfectly with my Slingbox solo, thanks to the slingbox remote codes I downloaded from this forum,

I upgraded to the latest model, 409N, and the remote codes do not work anymore, any idea how to get the remote codes for the new model (409N)?

Many thanks,

How about this: https://www.hifi-remote.com/forums/dload ... e_id=12048

So what happened ?

Guess we will never know

[quote="alanrichey"]How about this: https://www.hifi-remote.com/forums/dload ... e_id=12048[/quote]

the ZAAPtv is non responsive to the PL remote. it does however send firing commands to the ir wire connected thru the back of the solo. I verified firing commands thru a camera

any ideas

thanks

I assume you also tried the RV file ?

alanrichey wrote:I assume you also tried the RV file ?

yes. the RV file is not recognized by the solo as a valid file

If you are telling me that you are getting the message "Not a valid BIN file" then that is not the problem. What the message 'actually' means is that it cannot find the BIN file.

Where have you put the BIN file and what EXACTLY are you typing in as the location ?

[quote="alanrichey"]If you are telling me that you are getting the message "Not a valid BIN file" then that is not the problem. What the message 'actually' means is that it cannot find the BIN file.

Where have you put the BIN file and what EXACTLY are you typing in as the location ?[/quote]
the Pl and RV are both on the c drive root. I replace the PL with RV and it does not work

I repeat, what EXACTLY are you typing in as the location ?

[quote="alanrichey"]I repeat, what EXACTLY are you typing in as the location ?[/quote]

C:\c2010_PL.bin
C:\c2010_RV.bin

they are both in the same location on c root. the pl version will load up and show the remote. the RV version will not load and will say invalid custom bin file

thanks

Most odd. My first thought is that they should be case sensitive and you are using a lower case instead of upper case. But then the PL file should fail with the same message. I can see no logical reason why only the RV file generates that message.