Home Page Forums MAME MAME Labtam 3000

Gentlemen, maybe in the new year who wants to continue working on LABTAM emulation?
If there is interest in this, then I can try to draw a circuit on PCB.

Are you able to catalogue them ie which operating systems and versions?, languages?, diagnostics? etc have the potential to be preserved?

Xolod, we now have a slightly more functional Multibus emulation in MAME, which should give a good base to get this system working. Can you please share some information about the system configuration with the 3232 card installed? Does the 3232 board fit in the same card cage that was used for the Z80 and 8086 boards? Does it work standalone, or does it require the Z80 and/or 8086 cards installed to make a working system? The datasheet indicated it has a SCSI device, but I don't see one on the board picture - does your system have anything connected to those ribbon cable connectors on the top edge of the 3232 board and/or can you verify if either or both of them are SCSI?

Is your unit the "desk top unit" mentioned in the manual, or some other configuration? Which slot is the 3232 board installed in?

Do you have any NS32000 software for the 3232 board aside from the firmware?

Also the photograph of the board you provided isn't ideal - there are a number of devices where it's very difficult to read the part number. Can you possibly provide additional images with better quality?

By the way, Patrick, if you want to take on the base system itself, you're more than welcome. I just don't have the bandwidth or inclination to debug it at this point.

Now there is Concurrent DOS v4.1. Other software needs to be dump from a large number of 8 inch floppy disks.

Yes, same boards. And in V32 machine with four 8086 board for work 16 terminals.


Z80 and 8086 required for V32. (terminals, video, keyboard, FDD)


Yes, the SCSI controller was an option, and it does not soldered into my 3232 board. The photo of the board shows unsoldered microcircuits and a SCSI connector. I assume that it was an NCR 5380.
Two connectors on the top of the board connect RAM expansion boards.

Unfortunately, I don't have any software for 3232. But maybe these guys have something.
https://arvutimuuseum.ut.ee/index.php?m=eksponaadid&id=223

I will take good photos of the boards in the near future.
To run this machine, you need to start with the implementation of the Z80 board, then the 8086 board, and then the 3232 board.
It shouldn't be very difficult as there is a System Manual with a description of the system architecture. It is also possible to debug the Z80 board using the In Circuit Emulation device. And if necessary, restore part of the circuit on the PCB.
I will be glad if you @pmackinlay try it.

Here is what we managed to collect from the models:
3000 1983
???

3003 1983
Desktop
Board:
one - Z80 SBC
one - 8086 VDU/COMM
one - WD1002-HDO (Like Kaypro-10) https://retrocmp.de/kaypro/kay-p2_hrdw.htm#hdc
one - FDD 5'25 - Connect to WD1002 board
one - MFM HDD 5'25 NEC D5124 10MB - Connect to WD1002 board

3006 1983
Monoblock
Board:
one - Z80 SBC
one - 8086 VDU/COMM
two - FDD 8" - Connect to Z80 SBC board (to WD2793A on board)
one - FDD 5"25 - Connect to Z80 SBC board (to WD2793A on board)

3015-V32 1985
Tower
Board:
one - Z80 SBC
four - 8086 VDU/COMM (one board with main ROM and others slave ROM)
one - V32 (main processor board on CPU - NS32032, MMU - NS32082, FPU - NS32081, 2 Megabyte RAM), Optional SCSI contoler on board.
one or two - Additional one or two RAM board with 6 Megabyte.
one - INTERPHASE SMD 2190 (Controller SMD HDD)
one - Xylogics 472 (Controller 1/2 inch TAPE with PERTEC interface)

Thanks so much for all that extra detail. Just to clarify are you saying that you have one of each of these Labtam models?

3000, 3003, 3006 and 3015-V32

I've done some work on the Z80 SBC and believe I've found a plausible explanation for the 0x1800 firmware offset. According to the manual, all Z80 memory accesses pass through the address mapping logic, which maps logical to virtual addresses with a 2K page size granularity. The mapping logic supports 8 maps of 32 pages, and generates address bits 19..11 as well as RESB (resident bus vs Multibus access), MEM/IO and WP (write protect) signals. My theory is that during reset (and probably during interrupts) the mapping hardware is disabled, and its outputs are forced or float high. This has the effect that Z80 memory accesses during these cycles have address bits 15..11 driven high, and the other signals indicate resident bus, memory, read-only accesses (i.e. on-board EPROM). When combined with the initial mapping established by the firmware indicating EPROM #0 is decoded at 0xe000 on the resident bus, the result is the Z80 fetching logical address 0 from physical 0xf800, which is offset 0x1800 in the firmware.

Based on an initial implementation, it's now trying to access the floppy disk drive, so that's promising.

With lots of help from Xolod, I have the Z80 and 8086 boards up and starting to talk to each other.



This is the current result of starting up with the CP/M-86 floppy in the drive, but the system doesn't do anything else after this - maybe it's waiting for a keyboard.

We made a remake of the Labtam Z80 SBC board and completely restored the circuits of this board.