Recent content by antiquekid3

I did not immediately see it, so apologies if they're somewhere obvious, but where is the DECUS C documentation located? The local museum I work with has three binders labeled DECUS 1 through 3, which seem to contain a number of crummy scans of DECUS C and related documentation. I can likely...

Oops... I was conflating two boards. My M8655 is set to 9600. I repaired an M8650 which I've set to 38.4k.

We briefly looked at the DW8E this morning. Here's what we're seeing: Yellow: IOP2 Light blue: AC CLEAR Purple: REG BUS 11 Dark blue: AC LOAD As I suspected, AC CLEAR seems to be happening too late, or AC LOAD too early, as the AC data is not disappearing from the register bus in time for...

And, a video of the Straight-8 power up:

A few DW8E debugging photos from the evening... The M8655 installed in the box: The M8655 transmit test successfully working: Examining AC CLEAR and related signals on the backplane: The Arduino plugged into the backplane has since been removed and replaced with a modern baud rate...

Today was a busy day. Vince, Doug, and Malcolm helped me connect my DW8E to the PDP-8/I. We started with an M8655 in the backplane, which we configured for address 40/41 at 38.4k baud. A transmit test loop worked perfectly! Unfortunately, an echo test showed that, while the first character was...

You'll likely want to use the scope loop and single step to see which part is failing. Regardless, looking at the interrupt signal and working backwards is probably going to point you to the hardware issue.

Are you looking at the source code for the test? Find the address that's halting (PC: 2157) and read the surrounding test code to understand what it's testing and how it's determining a failure.

Thanks, Tom. Attached is the diagnostic we're running, which was extracted from diag-games-kermit.rk05. Documentation (also within the .zip) appears to match from what I've seen. Currently, DHRKBG is running with my best board set and my emulator on my 8/E without issue. And, Malcolm's board...

I'll check the listing I'm using to confirm it matches the executable we're running. Problem is, the errors are not consistent. Sometimes it fails at 1507 and sometimes it fails at 1172. Disk address is random. Sometimes it reads back zeros, sometimes it reads back 2525 instead of 5252. Are...

To further eliminate possibilities, we've cabled up in the following way: PDP-8/M with RK8E (with M7106 that was previous failing DHRKB with the emulator) RK8E to RK05 emulator with an original ~12 ft cable (RK05 emulator is address 0) RK05 emulator terminated with an original DEC terminator...

We've hooked up the system in the following way: PDP-8/M with RK8E (with M7106 that was previous failing DHRKB with the emulator) RK8E to RK05J with an original ~12 ft cable (RK05J is address 0) RK05J to RK05 emulator with a 1m cable from George (RK05 emulator is address 1) RK05 emulator...

That didn't stop our mutual friend from Melbourne from joining us! :)

I haven't attempted any update. I bought my kit on 30 April. I assumed it was running the latest firmware. Doug and I both read your whole thread hoping to find some common errors between what you saw and what we're seeing. Unfortunately, we're not getting a status error, but rather, a data...

Very intriguingly, the M7106 that was failing DHRKB with the RK05 emulator passed with the real RK05J. I will re-run this test tomorrow with the emulator and confirm it fails again.