Programming issue HP41CX
|
02-13-2018, 07:59 AM
Post: #11
|
|||
|
|||
RE: Programming issue HP41CX
(02-13-2018 01:20 AM)jhaig99 Wrote: When empty it shows 319 registers. Fine. So the memory is empty. (02-13-2018 01:20 AM)jhaig99 Wrote: The program label is V13, but when I try to execute it, it cannot be found. Then something is going wrong. If you see a LBL V13 you can of course execute this program. Be sure to enter the "1" and "3" shifted, as you did when you entered the label: XEQ ALPHA V shift 1 shift 3 ALPHA. (02-13-2018 01:20 AM)jhaig99 Wrote: With all the program steps entered, when I then resize for 026 it packs and returns END REG 07 So there are only 7 registers left. And SIZE 007 is the limit. (02-13-2018 01:20 AM)jhaig99 Wrote: My catalog 4 (extended memory) on the CV has a lot of commands. i.e. *,/,+, -, ACOS, ADV, ASHF, ASN, etc. I did not put these there so not sure where they come from. CAT 4 and 5 are only available on the CX. They are equivalent to EMDIR and ALMCAT on a C or CX with extended memory. On any other device, like the CV, they do the same as CAT 3. Which is the catalog with the standard commands. You don't put anything there yourself, it's simply the built-in standard functions of any HP41. ;-) (02-13-2018 01:20 AM)jhaig99 Wrote: The CX where I entered the program, is showing Cat 4 "Dir Empty" Sure. Extended memory is not used here. (02-13-2018 01:20 AM)jhaig99 Wrote: I'm thinking the values in extended memory may be required for program execution. I think there is a general misunderstanding regarding CAT 4 and extended memory. ;-) (02-13-2018 01:20 AM)jhaig99 Wrote: When I run Cat 1 it list program labels, then END 2188. Since the total memory is 2233 bytes there are 45 bytes left. That's 6 registers and 4 bytes (so I wonder why you get 00 REG 07). (02-13-2018 01:20 AM)jhaig99 Wrote: I really think this V13 program is very sophisticated and have come to believe the data in the extended memory may be part of the program some how. I suspect there are some errors when you entered the program so that it consumes more memory than it should. At least we now can say for sure that SIZE 026 defniitely is not possible with the program the way you entered it. I wonder if it really requires SIZE 026, so I'd like to see the part of the documentation that say thiat this is required. Why don't you just set SIZE 007 and see if it runs? Dieter |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 2 Guest(s)