Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.sys.sinclair > #4886

Re: RS232 - built-in versus Interface 1

From Russell Marks <zgedneil@spam^H^H^H^Hgmail.com>
Newsgroups comp.sys.sinclair
Subject Re: RS232 - built-in versus Interface 1
References <3af4e4ae-3587-400c-8358-e1e38a83bcae@googlegroups.com>
Organization this space intentionally left blank
Message-ID <E_htH.49936$zz79.40162@usenetxs.com> (permalink)
Date 2020-11-18 23:20 +0000

Show all headers | View raw


Lee Osborne <losborne74@gmail.com> wrote:

> Hello all. After some advice, and I figured someone here would
> probably be able to help.

This is hilariously late and probably pointless by now, but since I'm
already here why not. :-)

> I'm the owner of a (grey case) Spectrum +2, and I'm keen to try
> communication with other devices via RS232. Obviously, the +2 has a
> built-in RS232 port, but as far as I can tell, it's not much good for
> two-way comms with other machines, and is of course hampered by the
> completely non-standard plug. I've used the port for printing via a QL
> serial-to-parallel cable, and it works fine for that, but I'm guessing
> it isn't great for anything else.

It can be vaguely tolerable if you make sure you use RTS/CTS
handshaking, and your serial lead is properly wired. It's still pretty
bad though. I think I got my best results at 2400 baud.

> If I want to play with sending data to and from a PC, and also other
> old crap I have lying around like my Amstrad NC100, is it best to use
> the built-in port or the IF1? Also, is the IF1 RS232 port useable in

I seem to remember the IF1 port was very slow, but I could be wrong on
that. My hunch would be to go with the builtin one anyway.

> 128K mode? I've not been able to answer this, and it doesn't seem
> well-documented. Obviously the P channel is attached to stream 3, and
> in 48K mode drives the ZX printer, and in 128K mode goes to the RS232,
> so does that mean the T and B channels will correctly use the IF1
> RS232 in 128K mode? I hope it does - or will I have to stick to 48K
> mode if I want to use the IF1 RS232?

Given how it works my hunch would be 48k-only, but I'm not sure.

> Also, as I have the IF1 printer cable, which ends in a 25-pin male
> plug, is it possible to just get hold of one other cable that will let
> me connect direct to a PC?

I imagine this might be possible, but I doubt it's the best option.

> Any other hints and tips for connection to other machines? Like
> software for the Speccy? Am I insane for wondering if it's possible to
> convert text from the PC to Tasword files???

I think Tasword Two files (at least) were pretty much just a straight
dump of the 64-column ASCII text with no line breaks. So 64 chars for
one line, 64 for the next, and so on. I still have a few old Tasword
files from the 80s (originally from microdrive) and they all seem to
be like that.

-Rus.

Back to comp.sys.sinclair | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

RS232 - built-in versus Interface 1 Lee Osborne <losborne74@gmail.com> - 2020-05-28 13:07 -0700
  Re: RS232 - built-in versus Interface 1 Russell Marks <zgedneil@spam^H^H^H^Hgmail.com> - 2020-11-18 23:20 +0000
    Re: RS232 - built-in versus Interface 1 Volker Bartheld <news2020@bartheld.net> - 2020-11-19 14:26 +0100
      Re: RS232 - built-in versus Interface 1 Russell Marks <zgedneil@spam^H^H^H^Hgmail.com> - 2020-11-19 15:38 +0000
        Re: RS232 - built-in versus Interface 1 Volker Bartheld <news2020@bartheld.net> - 2020-11-19 16:47 +0100
          Re: RS232 - built-in versus Interface 1 Russell Marks <zgedneil@spam^H^H^H^Hgmail.com> - 2020-11-19 16:27 +0000

csiph-web