HP Forums

Full Version: HELP with programming the HP50G
You're currently viewing a stripped down version of our content. View the full version with proper formatting.

I am tinkering with RPL on the HP graphing calculators. Today I wrote a program on my HP50G to do multiple regression using vector/matrix commands. I was able to store, debug, and run the program just fine. HOWEVER, For some reason I was unable to store my test data in variables (I created a special directory for the program). When I enter the name of a variable (enclosed in single quotes) to store a vector or matrix, and click the STO button, the data disappears! I don't see new variables listed in either the current directory OR ANY OTHER directory. I ended up having to re-key in the data many times in several debugging sessions. Ugh!!!

What setting must I change for the HP50G to store data like it should?? I must be missing something or must have set something in the Mode->Flags menu that produces this bizarre behavior.



Edited: 28 July 2010, 6:34 p.m.

Hi, Namir;

the only explanation that comes (at this point, at least) to my mind is that you are storing data in local variables that have been created by instance(s) of the program still HALTed. Please, check if the HLT annunciator is shown in the upper right corner of the display and, if so, use KILL to stop/remove any pending session, hence killing any local variables still active.

I am not sure if there is something else, like storing/retrieving data in a directory chain, but once I had observed such particular memory handling structure while step-by-step executing HP48/49/50 programs, I think yours is the same case.

You see, if you are debugging a program and notice one problem, edit it, correct the problem, store the edited version and go ahead stepping through the halted version, you are actually stepping into the original, unmodified version. If you start a new one without KILLing any pending programs, you have something like a memory leak (described in previous threads... I liked the term!!!): the newly executed program, either in straight execution or in step-by-step mode, does not automatically kill the halted executions, and these program 'ghosts' use memory in a 'hidden' way. You can only go back to previously halted program(s) instances once you go ahead and finish the one(s) halted after those. KILL, however, wipes them all out.

Hope this helps a bit.

Luiz (Brazil)

Edited: 28 July 2010, 8:06 p.m.


You are a genius!!! Since I was debugging the program (several times) I had pressed the HTL menu and the HLT annunciator was on. I pressed KILL as you suggested and the proceeded to store data. It worked!

Thank you very much for your valuable help!


Edited: 28 July 2010, 8:44 p.m.

Hi, Namir;

good to know that the mystery is solved.

You are a genius!!!
I´m flattered, thanks! Anyway, the actual geniuses are the ones who created such gentle beasts... I just figured that out prior to read about it later, though.


Luiz (Brazil)

Edited: 28 July 2010, 10:27 p.m.