JP1 Remotes

The latest version of the protocol-builder spreadsheet (PB v4.00) is available.

PB supports all known JP1-compatible remote processors, though support for the P8/740 and M6805-C9 is not as complete as that for the HCS08, SST, S3C80, M6805-RC16/18 based remotes.

This is new version release that adds support for the HCS08 and SST remote processors, as well as fixing some bugs. Changes include:

• Add support for HCS08 and SST remotes.
• Added assembler & disassembler for HCS08 and SST protocols.
• Added auto-translate between 6805-RC16/18 & SST protocols.
• Added Export ASM button on Assembler sheet to allow saving a .asm file.
• Changed S3C8 generator to use same logic as 6805-RC16/18 & HCS08 for mid-frame bursts (call to $0161).
• Added hex number format option to disassembler.
• Added registry save/recall of disassembler WReg & hex number format options.
• Corrected integer rounding problem in assembler expression evaluations.
• Corrected incorrect S3C8 assembly of LD W0,@W3.
• Corrected incorrect P8 assembly of STA xx,Y.

Note to PB users: While PB has an integrated assembler, its use is strictly optional. You may choose to ignore the assembler and use PB to generate protocol executors by entering parameters alone. The assembler is provided mainly to allow advanced users and experts to create and/or modify complex protocol executors. For those interested in using the assembler, a separate readme file explains its use, and an example PB file is provided.

Note to users of prior v4.00 beta versions:
Due to an error in the saved file format, the assembled pcode may become associated with the incorrect processor. Before using assembled pcode output on the Setup sheet, be sure to re-assemble after loading any file saved with an earlier beta version of PB.

Mike,

I just noticed that the Protocol-Builder.doc Word help document is no longer in the zip file for PB. I found this to be the best and easiest-to-use of the various docs available with PB to understand the whole identification of lead-in, zeroes, ones, lead-out, and repeat stuff.

I recommend restoring it to the PB zip file.

Hey Mike,
I wonder if it would be possible to add support for the mid-stream burst pairs where the pair uses the '1' ON time and the leadin OFF time (the Proton protocol is an example of this sort of protocol).

I have created an example PB file here...
https://www.hifi-remote.com/forums/dload ... le_id=3896

I notice that the way PB currently does it generates the same signals, but if I try to decode a UEI protocol like the 005C protocol, it doesn't decode as using a mid-steam burst.

I just checked PB 3.12 to see how it handled mid-stream bursts and those signals ended up using the leadin pair as the mid-stream burst.

It would be useful if PB offered a choice of which format to use for the mid-streams.

pb 4.0
Based on context, I'm suspicious of disassembly of F5 04 03. It says LD DCBUF,@DCBUF+1. Assembly side looks ok to me - when you assemble ld @dcbuf,dcbuf+1 it returns F5 04 03.

Hello,

When I try to save a protocol file on a newly populated PB 4.0, I see an error;

File saved failed.
The file may be open or in use by anoother program.

What would you recommend to try?

Yesok

yesok wrote:File saved failed.
The file may be open or in use by anoother program.

That error would indicate that you either have a file with the same name open in another app that has it locked, or you're specifying an invalid filename.

If you open an exisitng PB file and try to resave it, do you get the same error?

That error would indicate that you either have a file with the same name open in another app that has it locked, or you're specifying an invalid filename.

If you open an exisitng PB file and try to resave it, do you get the same error?

Yes, the same thing happened when I load a PB file for Apple iPod, and try to save it.

I am grateful for your quick response.

Thanks in advance.

Yesok