Serial and Other Diagnostics
Warren came up from South Dakota to help us get the serial ports working and do some more diagnostics.
Sunday night he made a cable to connect the serial card to the serial port on our computer tower. We are using Warrens modified copy of MTTTY (Multi Threaded TTY) as our TTY emulator. It is an old Windows program so we are running it in Wine and it has been working pretty well so far. After
On Monday...
We toggled in two simple programs. One was a send/receive program and the other was a send. The send would take the data input on the right switches and display the character or number associated with that number in MTTTY on the PC. The code for that is as follows:
The LAS instruction loads the AC with the switch register. TLS Sends the AC to the serial port. TSF will skip the next line if the flag is set. JMP will jump to 202 and then the next JMP will jump to 200. This program will continually display the character loaded in the switches in the terminal window.
We keyed in the RIM loader and then sent the BIN loader over the serial port.
We loaded the display test in (MAINDEC-12-D6BA-PB_VR12_Display_Test.bin). The display worked but the X and Y positions were off center. We adjusted these and it looked much better.
We then loaded in FOCAL (go big or go home, right?). FOCAL started up and displayed in MTTTY. We ran some initial tests with it. All seemed good except that when doing loops it seems to do 1 over the set number. For example, we set 100 as the loop count and it did 101. We set 1000 as the loop count and then it did 1001. More debugging on this to come.
We tested the tape drives to make sure the motors worked at all 3 torques. The top one works good. The bottom one doesn't fully work. When you are stopped and want to move to the left the torque doesn't change and the brake doesn't release. Warren says this a logic problem and not a motor problem.
Warren brought his Flip Chip tester. We tested the M222s and they all passed.
The M221s are not working, but this was because the test vectors aren't working properly.
Sunday night he made a cable to connect the serial card to the serial port on our computer tower. We are using Warrens modified copy of MTTTY (Multi Threaded TTY) as our TTY emulator. It is an old Windows program so we are running it in Wine and it has been working pretty well so far. After
On Monday...
We toggled in two simple programs. One was a send/receive program and the other was a send. The send would take the data input on the right switches and display the character or number associated with that number in MTTTY on the PC. The code for that is as follows:
0200 / 7604 LAS
0201 / 6046 TLS
0202 / 6041 TSF
0203 / 5202 JMP
0204 / 5200 JMP
The LAS instruction loads the AC with the switch register. TLS Sends the AC to the serial port. TSF will skip the next line if the flag is set. JMP will jump to 202 and then the next JMP will jump to 200. This program will continually display the character loaded in the switches in the terminal window.
We keyed in the RIM loader and then sent the BIN loader over the serial port.
We loaded the display test in (MAINDEC-12-D6BA-PB_VR12_Display_Test.bin). The display worked but the X and Y positions were off center. We adjusted these and it looked much better.
We then loaded in FOCAL (go big or go home, right?). FOCAL started up and displayed in MTTTY. We ran some initial tests with it. All seemed good except that when doing loops it seems to do 1 over the set number. For example, we set 100 as the loop count and it did 101. We set 1000 as the loop count and then it did 1001. More debugging on this to come.
We tested the tape drives to make sure the motors worked at all 3 torques. The top one works good. The bottom one doesn't fully work. When you are stopped and want to move to the left the torque doesn't change and the brake doesn't release. Warren says this a logic problem and not a motor problem.
Warren brought his Flip Chip tester. We tested the M222s and they all passed.
The M221s are not working, but this was because the test vectors aren't working properly.
Whats next: Firing up the working tape drive and loading a tape, running some more diagnostics, finishing up the serial cables, tracking down the failed logic with the FOCAL problem and the tape drive problem.
Is the loop count starting at 0, that is making it loop 101?
ReplyDeleteEssentially it was user error. If I recall, we needed a third line of code to tell it to stop after it finished 100. Otherwise it did 101.
Delete