[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
//c adventures...
Well, I just successfully connected my Psion 3a and my //c and got them
talking to each other at 19,200 baud. A couple of things I encountered--
1) For the pinouts, I consulted Nathan's FAQ. I should note that based
on the DIN-5 connector I have, he has the pin numbers misidentified. But
he does have the correct signal associated with the correct position on
the connector, so ignore any numbers that happen to appear on the
connector frame.
2) My //c has been upgraded to a ROM-$00 from a ROM-$FF (I think that's
right) but it has the suspect serial clock. One I got the cable built, I
set the Psion at 300 baud and connected to the modem port. I did the
IN#2/PR#2 trick from BASIC. When I typed on the Psion, I got clean text
on the //c. But when I typed on the //c, I got garbage on the Psion. 8-(
I then tried using Kermit-65, but when I configured it, it crashed. On a
whim, I moved the serial cable to the printer port, reconfigured
Kermit-65, and behold, it worked beautifully.
I am aware that some //c's have trouble communicating at certain speeds
through the modem port. But knowing that the ImageWriter and Scribe are
supposed to talk to the //c at either 9600 baud or 19,200 baud (I forget
which), and I am unaware of any problems with using those printers on the
//c, I wonder if the printer port is less likely to have problems than the
modem port. That, or the problem only shows up at certain speeds...or I
simply got lucky.
Just thougt I would pass on those comments...any comments welcome... 8-)
--Dave Althoff, ][.
--
/-\ _ _ *** Thanks for a great season!!! ***
/XXX\ /X\ /X\_ _ /X/|_ _ _ _____
/XXXXX\ /XXX\ _/XXXX\_ /X\ <#&/XXX\ /X\ /X\ /XXXXX
_/XXXXXXX\__/XXXXX\/XXXXXXXX\_/XXX\_o==oXXXX\__/XXX\_/XXX\_/\_/XXXXXX