JP1 Remotes

[mathdon]

I have replaced v2.15.0 with v2.15.1 in the RMIR Development folder. I believe it fixes both bugs. Please test.

[davecs]

[davecs]

BINGO!

RMIR: Opened setup from 2.14.18 correctly, re-saved it and the Multi=true and Multi=false entries had been added.

RMDU opens correctly and seems to work correctly both as standalone or when called from RMIR.

Upload to remote works fine, macros on Activity Buttons work as expected.

It feels ready to me!
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[HamburgerHelper1]

Multi Macros are working for me too
I like how it pink highlighted for a conflict I purposely made

[davecs]

The only change now that I'd like to see, is the DSM Type moved next to the DSM column on the Special Functions page.

But, to quote the late, great, Robin Williams.... SHOWTIME!!
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[davecs]

Maybe I was too hasty. A few more tests on the 6440/OARUSB04G, but currently charging their batteries back to 100%. Should be ready before I go to bed, so will report this evening.
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[davecs]

Problems with the 6440. I was too obsessed with the 3661 to really push the 6440 and test it fully. I loaded my current settings rmir file (produced on an earlier version, not sure which) into RMIR2.15.1, and uploaded it to the 6440, the remote didn't appear dead, but it didn't work properly. I was worried if it was a flat battery, so I recharged the battery and tried again, but exactly the same problem. So I loaded the settings rmir file into RMIR2.14.18 and uploaded it to the 6440, and now it works properly again.

When it was not working properly, pressing some buttons did nothing, others produced what I can only describe as a weird combination of lights.

-----------------

Another unfortunate thing: I can't test on the 7980 because it has vanished into thin air, and I can't test on the 7562 or 8910 because the little dongle that I used to put between the FTDI cable and the remote has also vanished, though more likely into a vacuum cleaner, some time ago. Still hoping that both will turn up one day.
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[davecs]

Even stranger: I opened the rmir file for the 6440 in two separate RMIR windows, one 2.15.1 and one 2.14.18 — I should say with Extender 1.04

I looked at each tab, and could see no difference until I got to the Segments and Raw Data. Even then, I wonder whether some of the segments have been put in a different order. Both lots of data end at 1E6BD, before the succession of blank space (FF) bytes.

In 2.15.1, when I checked "Preserve Original Data", the contents of the Raw Data page changed to the same as the page on 2.14.18, and when I uploaded to the remote, it worked just fine.

One difference, though, without POD, was the first two bytes of the Raw Data at 1D800. With version 2.15.1 it's 1A E5. With version 2.14.18 it's 05 FA. After that, they are the same until 1E0BB.

On both versions, I started a "New" 6440 with Extender 1.04, and got different results in the raw data. Is there a reason that should be the case? I checked the RDF files using Kompare and they are identical.
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[davecs]

@mathdon

Graham, do you want me to post my 6440 rmir to diagnostics?

It seems that the only people testing and posting here are 366/80/1 owners, it's important to get others involved or else we end up with the new version becoming official but breaking for many users.
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[mathdon]

[HamburgerHelper1]

Oh trust me i will be testing other remotes as well.
Just have not gotten to it yet
I do have the OARUSB04G along with the inteset int 422 versions 1, 2, and 3 .
along with many others such as the Insignia NS-RMT415 and others

[davecs]

OK. I've had to go out. Will be back later this afternoon. Will post it then.
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[davecs]

[davecs]

I've found something!

I used 2.14.18 to make a fresh upload to the 6440. I downloaded it directly into 2.15.1. Two lines in the Special Functions tab came out in different places, so I edited them in 2.14.18 to match the same order as what had been downloaded into 2.15.1, and used SaveAs to make a new rmir file that I then loaded up into 2.15.1, and all the lines were in the same order and it enabled me to find what might be the error.

In the segments from 1E19E ending 1E205, the first byte in the Data column has been changed to 0F. They should be 10. Apart from these entries, and the first two bytes, the Raw Data was now identical.

Assuming the first two bytes at 1D800 are some kind of checksum, it's these 7 segments that are causing the error. Well the only type of thing I have exactly 7 of in the Special Functions, are Global DKPs.

Now where my knowledge ends, is how to fix it. But am I right?

EDIT: Just realised also: When I downloaded from the working remote into 2.15.1, the Device Button column in Special Functions, for these 7 functions, was blank, but when I loaded up the file made by 2.14.18 into 2.15.1, it said <none>. More convinced that I'm right!
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[HamburgerHelper1]

RMIR 2151 Ran into problem with the Insignia 67100 according to rmaster.err
Caused by: java.lang.NullPointerException
Full rmaster.err file here

http://www.hifi-remote.com/forums/dload.php?action=file&file_id=26710