Compatibility between RM and KM issue

[Eiffel]

As I'm about to embark on the extender journey, I downloaded the latest version of every application/spreadsheet and kicked tires...

What surprised me is that RM could read my old KM device configurations (RDF) correctly (all the buttons and remapping are there)... but it couldn't read the files I just edited with the latest version of KM (all the EFC/OBC are zeroed)

I'm wondering if this is a known issue, and if there is a workaround? I did try a search and looked at the recent positings here but didn't find anything conclusive...

Am I doing anything wrong? (For now, I'm going to use the latest version of KM and go with it, as I'm more familiar with this tool)

Thanks

Eiffel

[Mark Pierson]

What surprised me is that RM could read my old KM device configurations (RDF) correctly (all the buttons and remapping are there)...

RDF's have nothing to do with KM. Are you talking about regular KM upgrade files created using the SAVE button on the Setup sheet?

but it couldn't read the files I just edited with the latest version of KM (all the EFC/OBC are zeroed)

Is this a new device upgrade, or an older one that you edited?

I'm wondering if this is a known issue, and if there is a workaround?

I can't answer that since I'm not exactly sure what you're talking about.

[johnsfine]

From that vague discription with wrong terminology, I don't expect anyone else will recognise any "known issue". I certainly don't.

RM reads most KM .txt files. If you have one it doesn't read and want it diagnosed, at least give basic information (protocol name, etc.) or preferably post the txt file from KM to the diagnosis folder.

An RDF file is a description of a model of UEI remote, not a description of a device upgrade. KM doesn't use nor edit RDF files in any way. RM and IR use RDF files (neither of them edit RDF files).

[Eiffel]

Sorry for not being 100% correct in my report and thanks for the feedback!

My issue was with opening KeyMapMaster (.txt) files (typically device upgrades, or new devices I created) with RemoteMaster v 0.96a

I can load any of my old KMM files in RM, as long as they use one of the protocols known to RM (which excludes some of my device upgrades such as the one for my Airboard keyboard).

If I open the same KMM files (from about a year ago) in Keymap-master-v8.19 and save them, they no longer have any function defined (no EFC/OBC... in the corresponding tab) when loaded in RM

Upon looking at the KMM files, I discovered that this is an Excel/Java/Windows location issue (In Europe, where I recently moved, the list separator is the semi colon -commas indicate decimals-, whereas in the US it is the comma), and I presume that RM only works with a comma.

I'm glad I found what happened... The workaround is to change the decimal and list separator in Windows Settings before importing the files in RM, or to change all the separators in a text editor.

[johnsfine]

Upon looking at the KMM files, I discovered that this is an Excel/Java/Windows location issue (In Europe, where I recently moved, the list separator is the semi colon -commas indicate decimals-, whereas in the US it is the comma), and I presume that RM only works with a comma.

That's one that deserves a little attention.

We made the (slightly questionable) decision long ago to use the local seperator in KM txt files. That's easier (I think) for KM's load and save code to deal with than the alternate decision (which I would have preferred) to use comma regardless of the local setting. There have been various complications from that decision (most of which I've either forgotten or never understood).

But apparently we aren't handling that in RM import of KM files.

[gfb107]

I tried to make RM's importing of KM files determine the delimeter from the KM file itself. I've found a spot where I goofed, though.

It's where RM goes searching for the function definitions. This is the line that looks like:

Code: Select all

Functions,OBC,byte2,Buttons,Functions,Notes,Device Combiner (max 16):,

or

Code: Select all

Functions,EFC,byte2,Buttons,Functions,Notes,Device Combiner (max 16):,

or

Code: Select all

fFunctions,fEFC,fByte2,bButtons,bFunctions,fNotes,Device Combiner,,kmFunctions,kBoundDev,kBoundKey,kShift,b$-Functions

or

Code: Select all

fFunctions,fOBC,fByte2,bButtons,bFunctions,fNotes,Device Combiner,,kmFunctions,kBoundDev,kBoundKey,kShift,b$-Functions

depending on the version of KM used and wheter the upgrades used OBCs or EFCs.

I suspect that if just that line is changed to have commas, the importing will work. If that is the case, I already know what to change to fix this is RM.

[gfb107]

Please try this with version v0.98. It should be fixed.

[Eiffel]

Thanks for the quick fix... I confirm than I am now able to read my KM files in RM without having to first do a search and replace.

Much appreciated!

Eiffel