Hi Actually the error message is a “feature” of SCPI. It’s one that I never remember when I’m using a terminal.
You need to send a command (or power cycle) to clear the error que. It’s like GPIB in that regard. The errors stack up as you send commands and you must toss out each one out. Once you have them all tossed, you get the “scpi>” prompt rather than an error message. Yes I’m sure there is slightly more to it than that, but this is the Cliff notes version. Bob > On Nov 8, 2014, at 11:03 AM, paul swed <[email protected]> wrote: > > I will check when I get things going but the error message you see may be a > parity error. I know some GPS things wanted even parity. > I'll take a run at it tonight I hope. > Regards > Paul > WB8TSL > > On Sat, Nov 8, 2014 at 10:56 AM, paul swed <[email protected]> wrote: > >> Even though Bob says it I also screwed up the 15 pin mini. >> To be very clear >> >> Viewed from the chassis front. >> Male plugs pin 1 left side >> Female plugs pin 1 right side >> >> But that said the systems running fine now by simply doing the pin 2 and 3 >> approach. >> Next things. Battery backup to the GPS unit then RS422 and communications. >> My unit took a solid 2.5 hours to lock etc. But I was not on the good >> antenna. Instead an inside unit on the bench. Far from optimum. I just did >> not want to screw with the antenna connector and the L + 220 ohm R to fake >> out the GPS unit. >> Thanks for the help every one. >> >> Regards >> Paul >> WB8TSL >> >> >> >> >> On Fri, Nov 7, 2014 at 9:14 PM, Bob Camp <[email protected]> wrote: >> >>> Hi >>> >>> The reason it was listed as #1 on the list is that I made the backwards >>> numbering mistake when I was trying to work out the resistances on the >>> interface connector. I’ve been doing this for > 40 years and I still mess >>> it up on a regular basis. We also seem to get it wrong from time to time >>> when we lay out connector connections on pc boards, but that’s another >>> story altogether ….. >>> >>> Bob >>> >>>> On Nov 7, 2014, at 9:09 PM, Alan Hochhalter <[email protected]> wrote: >>>> >>>> I got in a hurry and made mistake #1 listed by Bob a few replies back. >>> I >>>> hooked one up to the RS422/1PPI port transmit pins (same as on J8) and >>> was >>>> receiving data fine in the PC so I just hooked up the other pair of >>>> terminals to the receive pins for J8 and couldn't get any response to >>>> commands. >>>> >>>> I finally found that I had initially connected the Lucent box ouput >>> pins to >>>> the wrong terminals on the converter. The Time code data on J6 was >>> still >>>> getting into the PC even though it was connected wrong. So I just wired >>>> the Lucent box input pins to the other pins on the converter that are >>>> really inputs and couldn't get J8 sto work either. >>>> >>>> What I ended up with to make it work is: J8-9 to RX-, J8-5 to RX+, J8-8 >>> to >>>> TX- and T8-4 to TX+. >>>> >>>> Alan >>>> _______________________________________________ >>>> time-nuts mailing list -- [email protected] >>>> To unsubscribe, go to >>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >>>> and follow the instructions there. >>> >>> _______________________________________________ >>> time-nuts mailing list -- [email protected] >>> To unsubscribe, go to >>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >>> and follow the instructions there. >>> >> >> > _______________________________________________ > time-nuts mailing list -- [email protected] > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
