HP35s Program Logger (sort of)

[Chuck]

Well, this is not quite the program logger I wanted to write, but my programming days are long past. Instead, I created an Excel spreadsheet that automatically creates line numbering. Changing a LBL variable will change the line accordingly. You can also leave a space between programs for easier reading. The spreadsheet allows for 100 lines of program (I can make it longer if needed, or just use a new page for larger programs.) Enter program commands in the "Command" column beginning with the LBL command.

Not sure if anyone will find it useful, but it was a good self-test on creating Excel functions to do this.

If the formatting of the line number isn't the same as in the graphic, let me know, and I'll fix it (or tell you how). Here's what it will look like.

HP35s Logger Spreadsheet

CHUCK

[Don Shepherd]

Hey Chuck, that's pretty clever! Good job.

[Jeff O.]

Chuck, thanks for your effort, I found it useful. Not being able to leave well enough alone, I considered what improvements might be desirable. In addition to auto-numbering, it would be nice to find a way to keep track of the jump start points and the targets. A column for comments would also be handy. With these concepts in mind, I took the liberty of modifying your workbook. Here is a screenshot of what I came up with:

The workbook looks for and sequentially numbers the GTO and XEQ commands, placing a sequence number in the “Start” column. It also changes the font color to green. You have to manually enter the sequence numbers in the “Target” column at the target line, and then the font color is changed to red. To insert a program step or steps, I have not found a better way than to copy everything in columns D, E, F, and G below the line where you want to insert down one or more lines. Then type the new instruction(s) in the newly created line(s). The jump starts and targets have to be manually reviewed and edited as required. Extra care must be taken if a new jump start is inserted between two existing ones as that will change the sequence numbers of all jump starts after the new jump instruction, so the sequence numbers of their targets will no longer match. (Automating the insertion and jump tracking and editing process would be very helpful, of course, but so far I haven’t tried to tackle that.)

Here is the workbook if you are interested....