Threaded Mode | Linear Mode

PeterP · 12-15-2023, 03:09 PM

Hi, just wanted to check if anyone has any news about the MAXX Module with regards to availability, functionality, etc.

Cheers

PeterP

Monte Dalrymple · 12-15-2023, 06:57 PM

(12-15-2023 03:09 PM)PeterP Wrote: Hi, just wanted to check if anyone has any news about the MAXX Module with regards to availability, functionality, etc.

Cheers

PeterP

I expect to start shipping before too long. Sylvain is nearly finished with his very thorough beta testing. I will be patching the included Time module code to fix the recently re-discovered bug in Time-1C. The manual is available here: https://www.systemyde.com/pdf/maxx-4d_manual.pdf

Monte

born2laser · 12-15-2023, 07:33 PM

(12-15-2023 06:57 PM)Monte Dalrymple Wrote: I expect to start shipping before too long. Sylvain is nearly finished with his very thorough beta testing. I will be patching the included Time module code to fix the recently re-discovered bug in Time-1C. The manual is available here: https://www.systemyde.com/pdf/maxx-4d_manual.pdf

Monte

That is great news Monte, you'll get my order as soon as you say the word.

PeterP · 12-16-2023, 12:01 PM

That is excellent news, as soon as you like it I’d love to place my order!

Monte Dalrymple · 01-02-2024, 08:36 PM

Sylvain finished his beta testing, but found a "feature" in some of the YREG functions that I lifted from Angel's work. Angel has supplied the fixes, but since there is no room in the MAXX ROM I need to replace some code by making changes to the hardware. This is easy to do with FPGA technology, but it means also redoing some of the testing. I have designed the hardware changes but haven't yet started incorporating Angel's software changes. Bottom line: A little longer...

Namir · 01-02-2024, 10:32 PM

Thanks Monte. I am sure it is worth the wait.

Namir

PeterP · 01-05-2024, 09:41 AM

Thanks for the update Monte!

floppy · 01-10-2024, 05:21 PM

It means, now (soon) we can buy a cheap second hand HP41C without any module instead an expensive HP41CX? (and just wait Monte parts to buy them).

Ángel Martin · (This post was last modified: 01-11-2024 11:59 AM by Ángel Martin.)

(01-10-2024 05:21 PM)floppy Wrote: It means, now (soon) we can buy a cheap second hand HP41C without any module instead an expensive HP41CX? (and just wait Monte parts to buy them).

it brings the 41C to a 41CV + TIME + X-Fns + 2x X-Mem... + 1024 regs of ExPanded memory.
That for me is better than a CX

'AM

Sylvain Cote · 01-11-2024, 02:22 PM

(01-11-2024 11:56 AM)Ángel Martin Wrote:
(01-10-2024 05:21 PM)floppy Wrote: It means, now (soon) we can buy a cheap second hand HP41C without any module instead an expensive HP41CX? (and just wait Monte parts to buy them).
it brings the 41C to a 41CV + TIME + X-Fns + 2x X-Mem... + 1024 regs of ExPanded memory.

+ 12x 4K 10-bit SRAM memory that can hold ROMs and/or be used as QROM.

PeterP · 01-11-2024, 03:07 PM

I cant wait.

floppy · 01-11-2024, 04:44 PM

Oh. Its means we have a new HP41 business cartell situation? :-)
- Diego is making battery systems
- Monte is making MAXX (which overtake the Nov64d content?)
..
Or lets be nicer in my question: how are Diego Nov64d/clonix interacting with the MAXX in the same machine?

born2laser · 01-11-2024, 06:36 PM

(01-11-2024 04:44 PM)floppy Wrote: Or lets be nicer in my question: how are Diego Nov64d/clonix interacting with the MAXX in the same machine?

As far as I understand they have some overlap on functionality, with the MAXX being a superset. It also represents a great alternative for those like myself that are late to the MLDL party.
I've been learning MCODE trying things out on V41, really antsy to try it out in the real thing!

Sylvain Cote · (This post was last modified: 01-14-2024 12:35 PM by Sylvain Cote.)

(01-11-2024 04:44 PM)floppy Wrote: Oh. Its means we have a new HP41 business cartell situation? :-)
- Diego is making battery systems
- Monte is making MAXX (which overtake the Nov64d content?)

Available hardware:

82120D LiPo Battery Pack [Diego Díaz]
Clonix-D Module [Diego Díaz]
- Flash: 48K 10-bit (12x 4K bank capable ROM pages)
  - can hold 12x 4K ROM images
  - can hold 6x 4K ROM images for odd ports and 6x 4K ROM images for even ports
NoV-64d Module [Diego Díaz]
- Flash: 48K 10-bit (12x 4K bank capable ROM pages)
  - can hold 12x 4K ROM images
  - can hold 6x 4K ROM images for odd ports and 6x 4K ROM images for even ports
- FRAM: 64K 10-bit
  - used as 4x 16K HEPAX RAM or QROM
  - used as 2x 32K HEPAX RAM or QROM
  - etc
MAXX Module [Monte Dalrymple]
- 1x 4K 10-bit MAXX ROM.
- 4x 82106A memory modules, if missing.
- 1x 82180A X-Functions/Memory module, if missing.
- 2x 82181A X-Memory modules, if missing.
- 1x 82182A Time module, if missing.
- 3x 1024 56-bit SRAM Y-Memory registers.
- 12x 4K 10-bit SRAM bank capable QROM pages.
  - can hold HEPAX ROM images and HEPAX RAM pages
  - can hold RAMBOX ROM image and QROM pages
  - etc

(01-11-2024 04:44 PM)floppy Wrote: Or lets be nicer in my question: how are Diego Nov64d/clonix interacting with the MAXX in the same machine?

Perfectly, use BOTH ! (Clonix-D + MAXX) or (NoV-64d + MAXX)

Diego modules are fantastic for holding ROM modules and the NoV-64d has the best HEPAX emulation.
While Monte MAXX module is first and foremost a system module that

bring an HP-41 registers based RAM to it's fullest capacity
add Extended Functions, Extended Memory & Time modules
bring 41CL Expanded Memory feature to all HP-41 machines
add bank capable QROM pages that is unique and a must for modern machine code development

Just to be clear, it is nice to have both modules but it is not mandatory, you can run RAMBOX/HEPAX virtual modules with the MAXX module only. The configuration part is different between the Clonix/NoV and the MAXX modules, but in the end, both can handle RAMBOX or HEPAX functionality.

edit 1: small correction on Diego module spec.
edit 2: last paragraph

Sylvain Cote · (This post was last modified: 01-17-2024 04:42 PM by Sylvain Cote.)

Example showing how to load and use the RAMBox32 ROM image with the MAXX module.

Hardware/Software needed:

HP-41C, HP-41CV or HP-41CX
MAXX module (the following example assume that the module is inserted into port #1 and initialized)
HP-IL module (82160A)
PIL-Box
HP-IL peripherals emulator (Virtual HP-IL, pyILPER, etc)
HP-41 ROM files (see: 41CL ROM files Archive)
LIF Utilities

Steps on a computer:

Create virtual tape file:

Code:

lifinit -z -m cass rambox.dat 32
Label virtual tape file: (optional)

Code:

liflabel rambox.dat RAMBOX
Add RAMBox32 ROM image to virtual tape file: (Unix/macOS/Linux)

Code:

cat RAMBOX32.ROM | rom41er RB32 | lifput rambox.dat
Add RAMBox32 ROM image to virtual tape file: (Windows)

Code:

type RAMBOX32.ROM | rom41er RB32 | lifput rambox.dat
Show virtual tape file content:

Code:

lifdir rambox.dat

Code:

Volume : RAMBOX , formatted : 14/01/24 12:00:00 Tracks: 2 Surfaces: 1 Blocks/Track: 256 Total size: 512 Blocks, 131072 Bytes RB32 X-M41 5121/5120 1 files (32 max), last block used: 25 of 512
Connect the PILBox to the computer
Start the HP-IL peripheral emulator with a virtual mass storage active and loaded with the virtual tape file (rambox.dat)

Steps on a HP-41:

Connect the HP-IL cables to the PILBox
Configure MAXX Q-ROM block 1 for RAMBox32 ROM image

Code:

10 // HP-41 ROM page where we will load the RAMBox ROM 1 // MAXX Q-ROM block number that will hold the RAMBox ROM QRRWD // MAXX fnc: Disable MAXX Q-ROM block 1 read & write access QRCLR // MAXX fnc: Clear MAXX Q-ROM block 1 QRABY // MAXX fnc: Map MAXX Q-ROM block 1 to HP-41 page 10, bank switching disabled QRWO // MAXX fnc: Enable MAXX Q-ROM block 1 write only access
Configure MAXX Q-ROM block 2 for a custom FOCAL ROM

Code:

11 // HP-41 ROM page that we will use to create my custom FOCAL ROM 2 // MAXX Q-ROM block number used for my custom FOCAL ROM QRRWD // MAXX fnc: Disable MAXX Q-ROM block 2 read & write access QRCLR // MAXX fnc: Clear MAXX Q-ROM block 2 QRABY // MAXX fnc: Map MAXX Q-ROM block 2 to HP-41 page 11, bank switching disabled QRRWE // MAXX fnc: Enable MAXX Q-ROM block 2 write & read access
Load RAMBox32 ROM image into HP-41 page 10 mapped to MAXX Q-ROM block 1

Code:

10 // HP-41 ROM page where we will load the RAMBox ROM "RB32" // RAMBox32 ROM image filename in virtual tape RDEIL // MAXX fnc: Read RAMBox32 ROM image encoded in ERAMCO ROM format from HP-IL mass storage to HP-41 ROM page 10
Update MAXX Q-ROM block 1 access to read only

Code:

1 // MAXX Q-ROM block number where RAMBox ROM is located QRRO // MAXX fnc: Enable MAXX Q-ROM block 1 read only access
Initialize custom FOCAL ROM image in HP-41 ROM page 11 mapped to MAXX Q-ROM block 2 (see HP-41 Module Database for XROM ID usage)

Code:

3 // Custom FOCAL ROM XROM number 11 // Custom FOCAL ROM page "-MYROM 1A" // Custom FOCAL ROM header (aka "MR1A") INITPG // RB32 fnc: Initialize Q-ROM Page
Add programs to the custom FOCAL ROM in page 11 mapped to MAXX Q-ROM block 2
- Create your focal program
  
  Code:
  
  LBL "BEEPX" ABS INT LBL 00 BEEP DSE X GTO 00 END
- Run your focal program from main memory to validate it
  
  Code:
  
  3 // number of time the BEEP will sound XEQ "BEEPX" // execute BEEPX program
- Copy your focal program from main memory to Q-ROM
  
  Code:
  
  11 // Custom FOCAL ROM page "BEEPX" // Program name to copy from main RAM to Q-ROM space LDPGM // RB32 fnc: Load main Program into Q-ROM
- Delete your focal program from main memory
  
  Code:
  
  CLP "BEEPX"
- Run your focal program from Q-ROM
  
  Code:
  
  3 // number of time the BEEP will sound XEQ "BEEPX" // MR1A program: execute BEEPX
Close custom FOCAL ROM in page 11 mapped to MAXX Q-ROM block 2

Code:

11 // Custom FOCAL ROM page "MR1A" // Custom ROM ID [MR] and version [1A] ENDPG // RB32 fnc: End Page
Update custom FOCAL ROM checksum in page 11 mapped to MAXX Q-ROM block 2

Code:

11 // Custom FOCAL ROM page PGSUM // RB32 fnc: update page checksum
Write custom FOCAL ROM to tape in ERAMCO format

Code:

11 // Custom FOCAL ROM page "MR1A" // Custom ROM image filename WRTPG // RB32 fnc: save custom ROM to tape in ERAMCO format

edit: reformating

gdgeist · 01-19-2024, 12:35 PM

Would love to pre-order; pre-fund this effort. Half nut CX that I rescued from the trash needs to be rewarded for surviving battery corrosion and neglect. The CL is appealing but still on the hunt for a donor that’s a good candidate.

dmh · 04-01-2024, 07:19 AM

Hi Monte, have you worked out pricing yet?

I'm in Australia so international shipping estimate would be good to know too.

Thanks

(01-02-2024 08:36 PM)Monte Dalrymple Wrote: Sylvain finished his beta testing, but found a "feature" in some of the YREG functions that I lifted from Angel's work. Angel has supplied the fixes, but since there is no room in the MAXX ROM I need to replace some code by making changes to the hardware. This is easy to do with FPGA technology, but it means also redoing some of the testing. I have designed the hardware changes but haven't yet started incorporating Angel's software changes. Bottom line: A little longer...

Monte Dalrymple · 04-01-2024, 05:00 PM

(04-01-2024 07:19 AM)dmh Wrote: Hi Monte, have you worked out pricing yet?

I'm in Australia so international shipping estimate would be good to know too.

Thanks

(01-02-2024 08:36 PM)Monte Dalrymple Wrote: Sylvain finished his beta testing, but found a "feature" in some of the YREG functions that I lifted from Angel's work. Angel has supplied the fixes, but since there is no room in the MAXX ROM I need to replace some code by making changes to the hardware. This is easy to do with FPGA technology, but it means also redoing some of the testing. I have designed the hardware changes but haven't yet started incorporating Angel's software changes. Bottom line: A little longer...

MAXX is $135 if you supply a module housing, $155 if not. With international shipping what it is, it doesn't make sense for international customers to try to supply the module housing. Shipping to Australia is $23 for First Class and $48 for Priority Mail. UPS and FEDEX are slightly more expensive than Priority Mail.

I am waiting the final go-ahead from Sylvain's testing.

Monte

Sylvain Cote · (This post was last modified: 04-01-2024 06:38 PM by Sylvain Cote.)

(04-01-2024 05:00 PM)Monte Dalrymple Wrote: I am waiting the final go-ahead from Sylvain's testing.

Arrggg .... available free time and priorities.
Diego testing is done for now, still need to report the result to him though.
Meindert project is on hold, so building a breadboard test setup for his upcoming module can wait a bit.
Mike is waiting for his NoV module, so his configuration can also wait.
Putting you back on top.
HEPAX works, edge cases still need to be tested, we are almost there.
Monte, have you fix the issue I have found several weeks ago ?

Monte Dalrymple · (This post was last modified: 04-01-2024 07:38 PM by Monte Dalrymple.)

(04-01-2024 05:24 PM)Sylvain Cote Wrote:
(04-01-2024 05:00 PM)Monte Dalrymple Wrote: I am waiting the final go-ahead from Sylvain's testing.
Arrggg .... available free time and priorities.
Diego testing is done for now, still need to report the result to him though.
Meindert project is on hold, so building a breadboard test setup for his upcoming module can wait a bit.
Mike is waiting for his NoV module, so his configuration can also wait.
Putting you back on top.
HEPAX works, edge cases still need to be tested, we are almost there.
Monte, have you fix the issue I have found several weeks ago ?

Sylvain, no need to do that. I am trying to get the batch of 41CL boards ready right now anyway. I think I have fixed everything. Which issue are you referring to?