This repo documents the NODE Systems DATAPAC, RAMPAC, and a new clone, the MiniNDP.
The NODE Systems DATAPAC was a popular ram disk peripheral for TRS-80 / TANDY Models 100, 102, & 200 computers.
Later versions of the same device were called RAMPAC. They functioned the same as DATAPAC and used the same software, just in a much smaller form factor.
The schematic and PCB below documents the DATAPAC from examining 2 units. If I ever aquire a RAMPAC, I'll add that.
Here is some disorganized INFO mostly gathered from the M100SIG archive and club100.
TLDR: To use the hardware, install RAMDSK, and what you get is a ram disk of 128k to 512k depending on model and installed ram.
The printing on the DATAPAC enclosure says 256k, and the circuitry and parts are all there to support 256k, but my two units only had 128k installed.
The PCB has footprints for four 32k sram chips (62256 equivalent), for a total of 128k.
To get 256k, a second set of chips are soldered piggyback on top of the first four, each with pin 20 bent out and connected to the pcb separately, and all other pins connected to the chip below.
No other parts or changes are needed to upgrade an existing 128k unit to 256k.
The original manual does not seem to be scanned or archived anywhere.
All we have today is a few bits of info from discussions in the M100SIG archive and Paul Globmans software on club100.
Some of these are collected in docs.
See also the docs for the various bits of software.
A few of those documents say that the device originally shipped with the user manual pre-loaded onto the DATAPAC as a 12k text file, along with at least one BASIC program.
If/when the battery died in the device and all data was lost, the Format operation in the option rom would also re-create the text file.
Neither the option rom nor the text file are archived anywhere that I have been able to find yet.
If anyone has a RAMPAC, they probably also have the option rom, and the original manual could be recovered from that. Maybe one will turn up some day.
The magazine article by Paul Globman below says that the rom was called RAM+, and there IS an archived option rom image available called RAM+, but it is for an entirely different type of device, the PCSG / Cryptronics RAM Expansion which provides RAM, like the PG Designs or QUAD, not a RAM DISK. These devices all replace the internal 32k where the ram files live and where programs run etc. The DATAPAC/RAMPAC does something entirely different, see Theory of Operation. It is possible the NODE rom was also called RAM+, but PCSG RAM+ definitely does not drive the DATAPAC or RAMPAC.
Other References
- "Database management with both the Node RAMPAC & DATAPAC."
Alspaugh, Ron - Portable 100, Nov 90:8-11 - "Node utility mini-extravaganza! Here are two special programs for Node Datapac/RAMPAC users."
Globman, Paul - Portable 100, Dec 90:19-20
This is a new drawing but aims to reflect the original actual device as exactly as possible.
It's meant to be a form of documentation or reference describing the original hardware as it was.
For instance, the inconsistent thickness of power traces, and the 5V power trace that almost touches one of the mounting screw heads, are both exactly as in the original.
(I added a fiber washer to that screw in my units after noticing that. The case is isolated, not connected to ground, but still...)
PCB TOP
PCB BOTTOM
The original PCB has no silkscreen. This image has silkscreen added to show where the components from the schematic go.
The three HC161 chips form a 0-1023 counter, setting local sram address bits A0-A9. We'll call this the byte or byte-position counter.
The HC374 sets local sram address bits A10-A17 from the bus AD0-AD7, and latches and holds that address on its outputs until triggered to update to a new address.
Four lines from the system bus: A8, A9, /Y0, and (A), combine to produce two signals which I am calling /BLOCK and /BYTE.
Each time /BLOCK goes low it sets SRAM A0-A9 to 0 and copies BUS AD0-AD7 to SRAM A10-A17,
then holds A10-A17 latched while /BLOCK is high.
Call this a BLOCK op.
Each time /BYTE goes low it enables SRAM for read or write while low, then when /BYTE goes high it disables SRAM and increments A0-A9 by 1. Call this a BYTE op.
So the device provides up to 256 blocks of 1k bytes each. The host computer does a BLOCK op to select a block number from 0-255, then does a BYTE op to read or write a byte of data at byte #0 in the block, then repeats the BYTE op 1023 more times to read or write all 1024 bytes in the block.
The device actually does operate like a disk even though it has no brains or firmware.
Later versions of RAMPAC were offered with 384k or 512k by adding a second bank of 128k or 256k, and later versions of RAMDSK.CO know how to access it.
The extra 256K is accessed by the state of BUS address line A10 during a BLOCK op.
BLOCK with BUS_A10 low accesses bank0, BLOCK with BUS_A10 high accesses bank1.
The state of BUS_A10 is essentially copied to the SRAM A18 address line and latched during BLOCK ops along with A10-A17, like adding a 9th bit to the HC374.
The 512k 2-bank operation is just deduced from watching what RAMDSK does on the system bus when you press the Bank button, then the theory tested with a breadboard circuit, and finally with MiniNDP below.
MiniNDP actually works with RAMDSK, but probably does not implement the circuit the same way that the RAMPAC did.
What this all means from the host computer software side of things
The original battery is no longer made, and the modern cross-reference is almost 2mm taller and does not fit inside the enclosure.
NODE Systems themselves used to perform an update to older units to replace the original rechargeable NiCD cell with a non-rechargeable lithium cell which was supposed to last about 5 years.
The change is simple and easy, and the parts are common. You just remove the old battery and the 200 ohm resistor, and replace them with a CR2032 holder and a diode. That's it. Both parts fit and solder right in the same locations where the old parts came out. Point the diode stripe away from the battery, just like the other diode that is right there next to it. Any standard diode will do. Schottky is not recommended because the reverse leakage is not good for a lithium cell. Another 1N4148 like the one that's already there is perfect.
This should give at least 4 years of memory.
(The original NiCD battery may have only lasted as little as a few months per charge according to a review in the archives. So the coin cell mod is not merely more conveniently available with current parts, it's an improvement.)
BEFORE
AFTER
STEPS
If you wish to keep using a rechargeable battery, then a suitable option is FL3/V80H. That is 3 16x5.8mm NiMH button cells in a flat in-line pack with wire leads. It fits perfectly in the space next to the ribbon cable. It needs to be secured with hot glue or foam mounting tape, and connected with wires run to the original battery location.
The charging circuit is utterly basic, so do not connect any other type of battery except NiCD or NiMH.
You can use any cell form factor and any larger or smaller mAh capacity, but must be 3.6v and only NiCD or NiMH chemistry.
Only Models 100, 102, & 200 were ever supported.
The device is probably hardware compatible with the Olivetti M-10 and Kyotronic KC-85, though RAMDSK was never ported to them.
The device is not compatible with the NEC PC-8201/PC-8300 at all.
The connector on the DATAPAC does not actually fit in a Model 200 without cutting the opening wider around the bus connector on the 200.
The only connector that fits in a 200 without hacking on the 200s case is a solder-type 2x20 male box header, which could be soldered back to back with the female version, to make an adapter to allow connecting to a 200 without having to damage the 200's case.
The case says "102/200", but it actually works on Model 100 also. It needs an adapter cable, but the cable is simple. It's just a "wire-to-board" IDC-DIP-40 crimp-on DIP connector and a standard 2x20 female IDC connector, both crimped on to a 40-pin ribbon cable about 8 inches long.
The Model 100 part of this 3-part cable for the Disk/Video Interface is exactly the same thing.
About all we can say currently is that we know it was sold in 128k, 256k, 384k, and 512k capacities, and was "about 2 inches square".
We can say how it's banks worked, because we can look at RAMDSK and see what it wants, which is how banks were added to MiniNDP.
Originally these shipped with an option rom from NODE (written by Travelling Software), which does not seem to be archived anywhere.
Later, each unit was also shipped with a copy of RAMDSK licensed from Paul Globman.
Today all we have is RAMDSK, but it claims to do everything that the option rom did. Although it does not reproduce the pre-loaded manual and utility files which the option rom did.
Some software culled from the M100SIG archive and Club100 are collected here in the software directory.
Much of that software actually requires the original option rom, which is not available. Some of that could possibly be converted to work with RAMDSK instead of the rom by translating the call addresses per the RAMDSK.TIP file.
How to access the hardware from BASIC.
See RAMDSK.TIP
There are two low level operations that you use to access the device,
BLOCK and BYTE, and each of those has two variations, for four total ops.
Select a BLOCK from BANK 0
OUT 129,n
Selects block# n (0-255) in bank 0, and resets the byte position to 0.
Select a BLOCK from BANK 1
OUT 133,n
Selects block# n (0-255) in bank 1, and resets the byte position to 0.
Read a BYTE
INP(131)
Reads the byte at the current byte position, and advances the byte position by one.
Write a BYTE
OUT 131,n
Writes the value n (0-255) to the current byte position, and advances the byte position by one.
The first read or write after selecting a block# applies to byte #0 of that block.
The byte position advances by one after each read or write, so the next read or write will be byte #1, then byte #2, etc up to 1024.
And actually, it's not "up to 1024", it wraps around to 0 of the same block again if you keep reading or writing more than 1024 times without selecting some other block.
Since the device can only read or write a single byte at a time, it's most efficient to use integer variables with the % suffix, ie, use B%=INP(131) instead of B=INP(131) etc where possible.
The general sequence is always:
1 - select a bank+block
2 - read/write byte 0-1024 times
If you need to read or write some arbitrary set of bytes from the middle of a block, you must still read (or write) all the bytes from 0 up to the desired offset.
For instance, in RBOOT.DO, to skip over the first 16 bytes of the block it does FORA=0TO15:N=INP(131):NEXT
N is not actually used, it's just reading 16 times and ignoring the data. This just advances the byte position counter to get from byte #0 up to the start of the bytes that it actually wants.
Examples
Select bank 0 block 0
OUT129,0
read a byte, which will be byte #0 of this block
INP(131)
Read and print the ascii of all the bytes in bank 0 block 2.
(this will mess up the display from control bytes if there is a binary .CO file in this block)
10 OUT 129,2
20 FOR I=0 TO 1023
30 PRINT CHR$(INP(131));
40 NEXT
Do the same but in bank 1
change line 10 to:
10 OUT 133,2
Manually repair the first two bytes of block 0 to mark the bank as being formatted without touching any of the data.
This means:
- Select bank0 block0
- write one byte, value 64
- write one byte, value 4
OUT129,0:OUT131,64:OUT131,4
(BTW you usually don't need to do that manually because RAMDSK.CO will do it for you if you just answer "Y" at the "Fix?" prompt.)
The "driver" software for the device is RAMDSK
RAMDSK claims to provide the same functionality as NODEs option rom, and even NODE themselves later licensed RAMDSK and included a copy with each unit.
Even the rom calls from the option rom have equivalents in RAMDSK, though at different addresses. (see RAMDSK.TIP)
One thing RAMDSK does not do which the original option rom did, is re-create the user manual text file as part of the Format operation.
Archived docs mention an 8 line BASIC program called BOOT that could be manually typed in to BASIC to bootstrap a copy of RAMDSK from a RAMPAC after a cold start.
That program does not seem to be archived anywhere, so in it's place there is RBOOT and NBOOT below which are new.
This only works after a copy of RAMDSK has been copied to the RAMPAC.
To get RAMDSK installed the first time, copy RAM100.CO or RAM200.CO to the 100 or 200.
The most convenient way is to use a TPDD client & server to copy the file, then adjust HIMEM to run it.
But if you don't already have something like a REX# with a TS-DOS option rom image, a more self-contained option is a BASIC loader:
software/RAMDSK/RAM100/RAM100.DO for Model 100/102
software/RAMDSK/RAM200/RAM200.DO for Model 200
To bootstrap the BASIC loader from a PC running Windows:
Install tsend
Then: C:> tsend.ps1 -file RAM100.DO
To bootstrap the BASIC loader from a PC running Linux, MACOS, FreeBSD, any unix, Cygwin/MSYS2:
Install dl2
Then: $ dl -v -b RAM100.DO
Another option for mac/linux, pdd.sh also has a bootstrap function and does not require you to compile anything.
Once you have RAMDSK installed, if you save a copy to the RAMPAC as the very first file after a fresh format, then in the future you can re-install RAMDSK from the RAMPAC itself after a cold reset without needing another computer or TPDD drive by manually typing in a short BASIC program.
These are optimized to tetris-pack into the fewest possible 40-column lines, not to be the most efficient code possible, please excuse the inexcusable IF and math inside the byte read loop. :)
RBOOT for Model 100
software/RAMDSK/RAM100/RBOOT.100
for software/RAMDSK/RAM100/RAM100.CO
1 CLEAR0,61558:T=61558:E=62957:OUT129,2
2 FORA=0TO15:N=INP(131):NEXT:FORA=TTOE
3 POKEA,INP(131):IFA=T+1007THENOUT129,1
4 ?".";:NEXT:SAVEM"RAM100",T,E,T
RBOOT for Model 200
software/RAMDSK/RAM200/RBOOT.200
for software/RAMDSK/RAM200/RAM200.CO
1 CLEAR0,59715:T=59715:E=61101:OUT129,2
2 FORA=0TO15:N=INP(131):NEXT:FORA=TTOE
3 POKEA,INP(131):IFA=T+1007THENOUT129,1
4 ?".";:NEXT:SAVEM"RAM200",T,E,T
RBOOT for Model 200, booting from Bank1
If you want to get fancy, you could support both model 100 and model 200 at the same time on the same RAMPAC by putting a copy of RAM100.CO in Bank0 and a copy of RAM200.CO in Bank1, and modify RBOOT.200 to read from bank1 instead of bank0 by just changing OUT129 to OUT133.
1 CLEAR0,59715:T=59715:E=61101:OUT133,2
2 FORA=0TO15:N=INP(131):NEXT:FORA=TTOE
3 POKEA,INP(131):IFA=T+1007THENOUT133,1
4 ?".";:NEXT:SAVEM"RAM200",T,E,T
Usage is mostly pretty self-explanatory.
The F1-Bank button switches between 2 banks of 256k, and is only functional on a RAMPAC that has more than 256k.
It is fairly common for the first byte to get corrupted ...Don't Panic(tm)
You could do the manual BASIC one-liner OUT129,0:OUT131,64:OUT131,4, but RAMDSK also has a first-byte-fixer built-in.
If you get the "Format RAM-Disk?" prompt on power-on, just answer "N".
Then it will ask "Fix?", answer "Y".
Just for reference, to boot some other CO instead of RAMDSK,
here is a more flexible and generic bootstrapper for any .CO file up to 2038 bytes.
- Reads the filename and start/length/exec values from the file itself
- Works on any .CO file that fits in 2 blocks
- Works on both Model 100 and 200
1 CLEAR32,59000:CLS:P=131:OUT129,2
2 FORA=0TO9:F$=F$+CHR$(INP(P)):NEXT
3 GOSUB8:T=N:GOSUB8:E=T+N-1:GOSUB8:X=N
4 F$=LEFT$(F$,6):N=T+1007:FORA=TTOE
5 ?@0,A:POKEA,INP(P):IFA=NTHENOUT129,1
6 NEXT:?@0,"Installed "F$:?"Type:"
7 ?"CLEAR 0,"T":NEW":SAVEMF$,T,E,X:END
8 N=INP(P)+INP(P)*256:RETURN
XOS-C is sort of an OS for the Model 200.
XOS-C does not require a RAMPAC, but leverages one if available.
Several of the NODE utils from the M100SIG require XOS-C.
Smaller than RD or N-DKTR, no machine code or calls, doesn't require the NODE ROM or RAMDSK, supports banks / all 512k.
Just displays the data, no parsing or interpretation of directory/file structures etc.
Functions the same as DATAPAC / RAMPAC. Essentially the same circuit, just with a single 512k ram chip instead of 8 32k chips, surface mount parts instead of through hole, and directly attached instead of connected by a cable.
Has 512k in 2 banks of 256k like the final versions of RAMPAC.
The connector fits in a Model 200 without having to modify the 200.
The diode on RAMRST is copied from a user mod found on a DATAPAC. It appears to be intended to prevent a battery drain on the host computer while the DATAPAC is left connected to the host while the host is turned off.
Installed on a TANDY 102
Installed on a TANDY 200
The 512k board also still supports 256k and 128k. There is no real reason to do this now but if you wanted to install a 256k (AS6C2008A) or 128k (AS6C1008, IS62C1024, etc) SRAM, omit the U8 part (the 1G79), and solder-blob U8 pads 4 & 5 together. Those two pads are modified to also be a solder-jumper for this purpose.
BOM DigiKey
PCB PCBWAY, or there is a gerber zip in releases
For the PCB, you want ENIG copper finish so that the battery contact is gold. PCBWAY and JLCPCB are a bit expensive for ENIG. Elecrow is cheaper, and OSHPark is always ENIG.
You can optionally make a thinner card by replacing BT1 and C1 with lower profile alternatives.
| BATTERY | estimated life | holders that fit the footprint | height | C1 Capacitor |
|---|---|---|---|---|
| CR2032 | 7.5 years | Keystone 3034 TE/Linx BAT-HLD-001-SMT Adam Tech BH-67 MPD BK-912 |
4.1mm | TAJC227K010RNJ - 6032-28 220u 10v |
| CR2016 | 3 years | Keystone 3028 | 1.7mm | TLJW157M010R0200 - 6032-15 150u 10v |
CR2032 height
CR2016 height (nominally a CR2012 holder, but can take a CR2016)
There are a few versions of printable cover in the enclosure directory.
There is OpenSCAD source and exported STL for a snap-on cover, with both a thick version for a card with CR2032 holder, and a thin version for a card with a CR2016 holder.
There is also an STL for a slip cover by F. D. Singleton.
The printable STLs are in releases.
You can get both the PCB and enclosure at the same time from Elecrow by submitting the gerber zip and the enclosure stl, and it arrives in under 2 weeks even with the cheapest economy shipping option.