Re: SSC Failure - odd symptoms

[Zero dB <no@email.com>]

On Wed, 19 Aug 2009 19:49:10 -0700 (PDT), Polymorph
<polymorph69@hotmail.com> wrote:


>Sounds like a classic case of "if it ain't broke, don't fix it!".  ;-)
>
>Having said that, it is unusual for such a scenario to happen, so
>let's make sure it is a hardware problem first up, or if its just a
>configuration issue.
>
>Some things to check/try:
>* Are the commuincation parameters (baud rate, etc) set the same on
>both host & client?
>* Have you tried connecting to the Apple II via a terminal program? -
>i.e. typing IN#2 and then trying to connect via a terminal program on
>the host (e.g. HyperTerm in Windows) using the correct communication
>parameters as specified by the switches on the SSC. You should be able
>to type stuff on the host and see it appear on the Apple II if things
>are working.
>* Did you accidentally switch the jumper with the arrow on it the
>wrong way during cleaning?
>* Is the cable you're using a null modem cable or straight through?
>Double check the jumper with the arrow to ensure its sets correctly
>(check the docs if you need to).
>
>Let us know what you the results of the above checks show up.
>
>Cheers,
>Mike
>

Greetings Mike! Thanks for taking your time to reply. 

Seriously, how true is your first statement ? LOL. Quite, I'd say.
Argh. You know how it goes. Dust bunnies. Dirt. (AZ dirt to boot).
Shiny new air compressor. How was I to resist blowing out the dust ?
haha :) 

Yeah, I have gone through all of the criteria you speak of, and then
some. Repeatedly. In every possible configuration. I made sure to
eliminate the easy stuff before putting this one out on the group.....


*baud, parms etc; both 19.2, 8n1. 
 
*I did try the term feature with hyperterm, kermit and the SSC's 'T'
terminal mode.  no love there. Just a cursor. Hmm. Actually, I think i
tried turning on echo and typing from the apple, and i didn't even
seen a local echo. I'll have to revisit that. Anyhow, nothing seen
remotely regardless. 
(*) I am going to pull out the break out box next......

*my SSC came with a broken DTE/DCE jumper, so i have to set it with
wire jumpers. I can set it to 'modem' and 'term' no prob with a quick
change of jumper wires. I have doublechecked the pinout vs. schematic,
and check continuity each time across each jumper.  Again, this was a
working config as-is-was-is......

*i've used boxed null modem cables. handmade null modem cables (pinout
generic and the full pinout documented at rubywand's site). Basically
every iteration with and without handshaking, and with the proper mode
selected on the terminal jumper. 

Everything seems to be in order, I've spent a couple hours now
cumulative just making sure the basics are in order during testing. 

I'm wondering why local echo wasn't working on the SSC side. I believe
it's 'e' to toggle ? I 'll look that up, and try it with and without a
cable and full reset between each attempt. 

I spend a lot of time with dce/dte and blackbox stuff at work day in
and out so i'm pretty confident in all of the layer1-2 stuff..... i'm
stumped!

I will probably buy another SSC with intact jumper just to have (and
as a next step in T/S. 

Not sure if there is anything I can type for SSC diags......

i'm pretty dumb when it comes to layer 5-7

Thanks again for your time replying!   
Jayson

jayson DOT anderson removeme at gmail