The Sinclair QL Forum

Sparrowhawk wrote: ↑Sun Apr 14, 2024 5:01 pm

t0nyt wrote: ↑Sun Apr 14, 2024 2:06 pm
It locks up for me at the question. Probably me as I've not tried to connect to a BBS in 40 years

Yep me too. Works ok using telnet from my Linux laptop. I’ve sent a query to the admin on Mastodon. Will let you know what he says.

Thanks. It works for me in Win11 Telnet

Just in case anyone else has this device:
The double char issue is an issue with the firmware of the adapter/modem. A bunch of people om the discord support server have the same issue.
I'll try to grab latest and reflash over the weekend and report back.

https://github.com/TheOldNet/theoldnet- ... e-binaries

the issue where you changed to 9600, then saved it, it seems to me , you did not then change the baud of the terminal too. this is why you then saw the output from the modem after hard resetting it, as I believe the modem will then default to 1200 Baud and the ONLY way you'd see the display on the screen is if the baud rate of the terminal was matching, otherwise it would display garbage. if the modem is set to 9600, thus the terminal should be too, but BEWARE as a stock QL may change to a faster speed but a stock QL may not be able to work that fast and display garbage.
p.s to turn off the 'double lettering' you would need to disable the echoing on the modem as well as the terminal if I remember rightly.

No, I did set the terminal to 9600: I managed to get to the BBS once. It was only after I hard-set the baud to 9600 using the configurator program that everything ground to a complete halt.

Anyway, I'll double check this weekend and let you know.

The default speed for that particular modem is 300 baud. Which is s.l.o.o.o.o.o.o.o.w

Hi,

I think you're all getting the Serial port Baud rate confused with the Modem connect speed

The serial port on the QL, usually SER2, should have it's Baud rate set to the highest reliable speed. Which could be 9600 Baud, using the BAUD command:

BAUD 2,9600

This sets the data speed from computer to modem on the connecting cable.

The BBS called up will have a range of connect speeds, the required Connect speed is set by the ATB command, either in the dialing connect string of the terminal preferences.

The terminal preferences may set both data rates, and they can be different.

Ah, you are right Derek. My apologies.

Although... would I be wrong to think that QL Terminal will set the QL rate too? Because when I connected to the BBS at 9600, it flew (well it flew in comparison to when I did it at 300). And I did not explcitely set the QL ser2 baud rate from SuperBASIC at that stage.

Hi,

It seems the QLTERM does not work in way I suggested, it sets the QL serial port speed to the same speed as the modem connect speed.

The QLTerm manual says that the QL Baud Rate can be set in the terminal preferences, by pressing I

So set the QL Baud Rate to 9600, Modem type buffered, serial port SER2I

The oldnet wifi modem manual says the connect speed of the modem is set to 300 Baud.

But can be changed by using: AT$SB command, so to set to 9600 Baud:

AT$SB=9600

You can save the commands entered in the modem with ATW

Type

AT? for a list of commands
AT&V for speed dial list.


I get my Simulant WIFI modem setup and try out the various commands.

It might be an idea to setup a BBS.

QLTerm does not know anything about Hayes commands and responses. It just forwards them to the display and from the keyboard.
So if you set the baud rate in QLTerm to 9600, it will stay at 9600 regardless of what the modem reports.
Of course, your modem should not change the baud rate once connected (I doubt if a wifi modem would switch to 300 bps).
One way to avoid QLTerm setting the baud rate is to open a channel from BASIC and then start QLTerm using EW QLTerm,#channel.