A1200 RPI and TCPser problem

[McMiga]

Hi

Trying to configure my Raspberry Pi2 as an emulated Hayes modem with tcpser, so I can browse telnet BBS's on my A1200 using JR-Comm.

I can successfully connect to BBS's from my A1200 when using tcpser or internet modem in windows, but I can't when using tcpser in Raspian Jessie on the RPi2.

I'm using a generic PL2303 USB to serial cable which works fine in Windows and is recognised as ttyUSB0 in Raspian using the pre-installed drivers.  When hooked up to the RPi, JR-Comm detects the carrier signal from the tcpser modem but when I try and connect to a BBS JR-Comm just returns random, gobbldegook characters and doesn't connect.

In Raspian i'm running tcpser using the following command: sudo tcpser -s 9600 -I -l 4 -d /dev/ttyUSB0 -tsS and I get a info messages confirming server socket bound to port, server socket listening for connections, opened serial device /dev/ttyUSB0 at speed 9600 as fd 8, serial device configured, control lines DSR:1 DCD:1 CTS:1

If I run tcpser without -I I get DCD:0 as I should, but the results are the same.

Tried a powered hub - no difference

Also added in "&k0" to stop flow control but again, no difference.

Any ideas? Basically, everything works perfectly in Windows but not at all in Raspian.

[Pat the Cat]

If I may ask a silly question - which bit is actually connected to the local telephone exchange? I would guess it's an ADSL router.

The reason I ask is, some part of the hardware has to be licensed for connection by voice. On a PC, they typically have a built in modem heavily backed up by licensed drivers.

On a PI, you don't have that. The system wasn't designed for connection to the public telephone network, and ADSL routers aren't licensed for carrying analog voice data over phone lines (you need a telephone plugged in to do that). Modems give analog output and read analog input.

Anyway you could plug a landline phone in alongside and just listen for differences in the exchange? That might highlight the problem, and is a very useful way of monitoring differences between "real" modem connections.

It's a lot easier when dealing with mobile phone systems, because they are completely digital. Not that I do that sort of thing. Although I have seen other people doing similar things.

Couple links that might help you - first is issue description, second is a "hand on" tutorial.

http://www.tldp.org/HOWTO/Modem-HOWTO-2.html

http://extradio.sourceforge.net/extmodem.html

[kolla]

@McMiga

Have you tried using for example minicom directly on /dev/ttyUSB0 on the pi?

[Pat the Cat]

Oh right... by "modem emulation" you mean something else.

Found this thread, appears to do same thing (use an Amiga for surfing without having it's own TCPIP stack)...

http://amiga.org/forums/showthread.php?t=67191

However, that approach meant using a "real" RS232 port on the PC side, not USB. Could be where the problem lies.