[rmpfyf]

That should be correct, however I’m one of those people that insists you need to use a real null
Modem cable - all lines correctly hooked up, not just three wires.  I’ve had perfect success over the years on SGI terminal connections with two things in mind.

1. Fully pinned out Null modem cable, configured for hardware flow control on the PC terminal.
2. Use a laptop with a Real serial port, unless you know you’re using a FTDI/prolific USB-to-rs323 chipset that definitely uses hardware signaling and doesn’t fake it.

Most USB to serial adapters are pinned out to use hardware flow control incorrectly.  I make sure when I find an adapter at a used PC store or something that it check the online GPS community for complaints against the adapter.  External GPS receivers are still one of the few devices that often require hardware flow control pins and adapters that cannot do that won’t work. 


Otherwise your settings should work: https://wiki.preterhuman.net/Headless

What I have (just probed with a multimeter) is this - is this correct? (https://en.wikipedia.org/wiki/Null_modem...Wiring.png)
Should be using hardware flow control, not software?

[weblacky]

Sorry, Image posting didn't work. So I can't see anything at this time.

But yes, I always try hardware flow control first, but again make sure if you're using a USB adapter it even WORKS with hardware flow control. Many people who have come on the forum looking to get serial working and conveniently forget to mention they aren't using a native serial port (using a USB adapter) find it helps simplify things when they use a native serial port. So unless you're sure about the USB adapter, if you're having issues, I'd use a real Serial port on an old laptop or something until you're sure, then you can swap back to a USB adapter and if it works, then you know.

[rmpfyf]

Sorry, Image posting didn't work.  So I can't see anything at this time.

But yes, I always try hardware flow control first, but again make sure if you're using a USB adapter it even WORKS with hardware flow control.  Many people who have come on the forum looking to get serial working and conveniently forget to mention they aren't using a native serial port (using a USB adapter) find it helps simplify things when they use a native serial port.  So unless you're sure about the USB adapter, if you're having issues, I'd use a real Serial port on an old laptop or something until you're sure, then you can swap back to a USB adapter and if it works, then you know.

Updated with a link to a wikipedia reference reflectng what I tagged out. In short pins 1 and 6 shorted on each end, 2 & 3, 4 & 6, 7 & 8 swapped end to end, 5 straight through and 9 not connected. 

Using a real serial port on a server board.

[Raion]

The image has to be under a certain size. It's a disk space constraint issue.

[rmpfyf]

The image has to be under a certain size. It's a disk space constraint issue.

Clicking the link doesn't work?

[Raion]

Oh, I didn't see. I was not expecting that. I thought you tried to attach an image.

[weblacky]

Raion - How about a top hardware sticky thread on terminal cable pinouts...I feel like this topic is brought up often enough that we should just have a post-it with the known cabling.  Someone can verify what I'm saying, then let's stick it up...

OK...you forced me to do this...I actually found my old 90's 9v cable pinout tester for PCs and tested the one Null-modem cable I use for EVERYTHING...that always works for DB9.  The last thing I used this on was my Tezro Console port.  I don't own another DB9 Null-Modem cable, this is the one. So this should work.

So this agrees with the most advanced-wiring Null-Modem article I could fine online (https://www.aggsoft.com/rs232-pinout-cab...to-db9.htm).  Here it is:
_____________________

Octane, O2, Tezro, and Fuel definitely have IBM PC pinout style-ports (manuals confirms this).

Both cable ends are DB 9 - FEMALE
Shields are connected together. Shield is NOT connected to ANY other pin, even ground, only shield to shield.

Code:

Signal - Pin           -> Pin - Signal
DCD - 1 & DSR - 6      -> 4 - DTR
RD  -  2               -> 3 - TD
TD  -  3               -> 2 - RD
DTR - 4                -> 1 - DCD & 6 - DSR
SG  - 5                -> 5 - SG
DSR - 6                -> 4 - DTR
RTS - 7                -> 8 - CTS
CTS - 8                -> 7 - RTS
RI  - 9                -> #UNCONNECTED#

So, there you go.  Also if you try to use the 3-wire, it claims you have to use like cu on tty?  I assume because of the software signaling.  I use teraterm for Windows 10 and have used HyperTerminal in XP in the very past. I've used Putty with another DIY MiniDin 8 cable on an Indigo2 Last year.  So I know those applications work.

[Raion]

Everything SGI that has an RS-232, 9-pin serial uses an industry standard serial port in my experience. This includes the Onyx2, Origin 3x0, Origin 200, etc.

The ones with 9-pin Mac-style serial cables are identical to Mac ones.

[weblacky]

If I was in error, I apologize. I was indicating what SGI models, that I know, use RS-323 through a DB9 connector instead of the Mini Din 8 connector. I was grammatically affirming both the Pinout and Connector type in that statement. I didn't mean to imply there are DB9 serial connectors in SGIs that are wired differently.

[rmpfyf]

Raion - How about a top hardware sticky thread on terminal cable pinouts...I feel like this topic is brought up often enough that we should just have a post-it with the known cabling.  Someone can verify what I'm saying, then let's stick it up...

OK...you forced me to do this...I actually found my old 90's 9v cable pinout tester for PCs and tested the one Null-modem cable I use for EVERYTHING...that always works for DB9.  The last thing I used this on was my Tezro Console port.  I don't own another DB9 Null-Modem cable, this is the one. So this should work.

So this agrees with the most advanced-wiring Null-Modem article I could fine online (https://www.aggsoft.com/rs232-pinout-cab...to-db9.htm).  Here it is:
_____________________

Octane, O2, Tezro, and Fuel definitely have IBM PC pinout style-ports (manuals confirms this).

Both cable ends are DB 9 - FEMALE
Shields are connected together. Shield is NOT connected to ANY other pin, even ground, only shield to shield.

Code:

Signal - Pin           -> Pin - Signal
DCD - 1 & DSR - 6      -> 4 - DTR
RD  -  2               -> 3 - TD
TD  -  3               -> 2 - RD
DTR - 4                -> 1 - DCD & 6 - DSR
SG  - 5                -> 5 - SG
DSR - 6                -> 4 - DTR
RTS - 7                -> 8 - CTS
CTS - 8                -> 7 - RTS
RI  - 9                -> #UNCONNECTED#

So, there you go.  Also if you try to use the 3-wire, it claims you have to use like cu on tty?  I assume because of the software signaling.  I use teraterm for Windows 10 and have used HyperTerminal in XP in the very past. I've used Putty with another DIY MiniDin 8 cable on an Indigo2 Last year.  So I know those applications work.

Alright. That's a standard null cable supporting full handshaking, which is what I have. Either there is a problem with the Octane (unlikely) or a problem with the operator (more likely). 

I will now nick off into a corner and try to Do This Properly. I've got permission/lock issues with minicom (Ubuntu user here) and so will try chip away at that.