JP1 codes from raw data?

[gfb107]

A lot depends on the "RMFunctions" export format, which I haven't seen, so maybe I'm wrong here.

It might be slightly easier to just reorder the columns (by dragging the column headers) on the functions tab in RM to match the exported data and then just paste without modifying the exported data.

Maybe an additional step could be saved if IrScrutinizer could export directly to the system clipboard rather than having to go through a file.

Also I would point out that "to delete the cruft already there" just click the "Clean up" button, either before or after the paste.

We should now import this file into RemoteMaster. There are some steps for this:

6. Open the export file with a program of your choice. Just selecting Actions->Open last export file in IrScrutinizer may suffice.

7. Open Remotemaster. Since we are making a NEC1 based update, select Protocol NEC1. Select the "Functions" pane and (optionally) delete the cruft already there.

8. We see that the RemoteMaster table needs OBC (=F in IrScrutinizer) as column #4. Therefore, in the spreadsheet, introduce a new, empty, column after the names column. Mark and copy the interesting area from first name (LEFT) to last F/OBC.

9. Mark the name column in the first line of the Functions table in RemoteMaster. Press Paste in the right-mouse-button popup menu.


I hope to be able to extend Remotemaster to import from IrScrutinizer directly later this year, thus eliminating step 6-9.

[Barf]

A lot depends on the "RMFunctions" export format, which I haven't seen, so maybe I'm wrong here.

The RMFunctions format is really nothing advanced. It came out of
a discussion with Vicky , more as an example on how simple it is to define new export formats than an atttempt to create something useful. It is definined in file exportformats.xml, close to the end:

Code: Select all

<exportformat name="RMFunctions" extension="tsv" multiSignal="true" simpleSequence="false">
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
        <xsl:output method="text" />

        <xsl:template match="/">
            <xsl:apply-templates select="remotes/remote/commandSet/command"/>
        </xsl:template>

        <xsl:template match="command">
            <xsl:value-of select="@name"/>
            <xsl:text>	</xsl:text> <!-- EFC -->
            <xsl:text>	</xsl:text>
            <xsl:value-of select="parameters/parameter[@name='F']/@value"/>
            <xsl:text>	</xsl:text> <!-- Hex -->
            <xsl:text>	</xsl:text>
            <xsl:value-of select="@comment"/>
            <xsl:text>
</xsl:text>
        </xsl:template>

    </xsl:stylesheet>
</exportformat>

This is an XSLT-script for generating the export of an in-memory XML-DOM. To get F/OBC in column #4 instead of column #3, just add a TAB to a suitable <xsl:text> content. Or define a new export format of your liking.

It might be slightly easier to just reorder the columns (by dragging the column headers) on the functions tab in RM to match the exported data and then just paste without modifying the exported data.

Yes. Thanx.

Maybe an additional step could be saved if IrScrutinizer could export directly to the system clipboard rather than having to go through a file.

Good idea. It should probably not be called "export" but "copy to clipbard" from the tables. Let's see....

Also I would point out that "to delete the cruft already there" just click the "Clean up" button, either before or after the paste.

I was looking for something like that, but did not find it. sorry.

Thanx a bunch for your comments.

@mdavej: Thanx for those kind words!

I plan to try to teach RM to import the Girr-export of IrScrutinizer for creating a device update, if possible. But that is at least two months in the future.