competentcompton wrote:
I have used this cable in the past to talk to the MSC on this very machine.
Of course that was quite a while ago. I do not have another machine to test it with.
I followed the documentation (I think) plug in the cable, connect then hit ctrl +t and enter and I should see
MSC>
right?
I just got done with some testing on a G-Brick that involved removing the L1 module and inserting an MSC (the L1 used in the G-Brick and the MSC used in the Onyx2 Graphics Module are mechanically interchangeable).
There are some obvious structural differences, but the integrated firmware (and underlying commands) by the MSC controllers used in the O2k/Onyx2 series and Origin 200 appear to be reasonably similar.
I noticed if I had the serial terminal running (and connected to the MSC diagnostics port) when I powered up the G-Brick, the MSC would automatically print version info to the terminal without the need for a control-t keypress:
Code:
MSC VER 3.1
If I then executed a control-t keypress I got the MSC> prompt you were expecting and could then query the MSC:
Code:
MSC> tmp
ok n
- perhaps a working O200 MSC will exhibit similar behavior if the serial terminal is running when your O200 is powered up.
For comparison, I'm using a standard DB9-to-DB9 null modem cable connected at 9600-8-N-1 with XON/XOFF flow control.
Attachment:
Putty.png [ 50.87 KiB | Viewed 306 times ]
competentcompton wrote:
I am leaning toward a PSU problem.
The previously linked thread, and especially SAQ's experience with a nearly identical problem, makes that sound like a reasonable suspicion.