Hello,

I recently received my first two US Robotics modems for my Mystic BBS. Unfortunately, the first one was defective, but the seller refunded me.

The second modem is brand new, yet neither of them responds to AT commands. However, the new one does dial out and can synchronize with a BBS. The issue is that it doesn't respond to any AT commands sent to it. This is causing a significant problem with Windows because, without proper responses to AT commands like "OK" or "ERROR," Windows fails to recognize the modem. This also affects SEXYZ, as it expects the modem to acknowledge its commands.

I suspect there's something I'm missing or haven't done correctly. These are US Robotics 5686 modems, which are standard serial modems. I've tested them on several serial ports across multiple computers, including the built-in ports on the motherboard and special RS232 serial cards.

Does anyone know how to resolve this issue?

VA2RFC BBS Les Méchins, Québec Canada
SysOp: rmurray PhoneNet: 1000040 (Modem)
Telnet: va2rfcbbs.photorm.net:23 FsxNet: 21:1/235 FidoNet: 1:229/114

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: VA2RFC BBS (21:1/235)

Re: USR 5686 no reply at AT command
By: rmurray to All on Wed Aug 21 2024 11:02 pm

The issue is that it doesn't respond to any AT commands sent to it.

Try issuing the command:

AT&R1<ENTER>

Then try a plain AT<ENTER> and then ATI5<ENTER>.

I've tested
them on several serial ports across multiple computers, including the built-in ports on the motherboard and special RS232 serial cards.

By any chance are you using the same serial cable (and maybe adapters) when doing each of these tests? The AT&R1 command above will temporarily disable RTS handshaking on the modem side. If you get a response after issuing it, this will indicate the hardware handshaking isn't configured correctly.
--- SBBSecho 3.14-Win32
* Origin: The Fool's Quarter, fqbbs.synchro.net (21:1/149)

Re: USR 5686 no reply at AT command
By: rmurray to All on Wed Aug 21 2024 11:02 pm

I suspect there's something I'm missing or haven't done correctly. These are US Robotics 5686 modems, which are standard serial modems. I've tested them on several serial ports across multiple computers, including the built-in ports on the motherboard and special RS232 serial cards.

Does anyone know how to resolve this issue?

Check the DIP switches on the modem. I seem to recall one of them (or some combination) disables AT command support.

Or it could be your serial cable or serial port at fault.
--
digital man (rob)

This Is Spinal Tap quote #28:
We've got Armadillos in our trousers. It's really quite frightening.
Norco, CA WX: 77.0°F, 50.0% humidity, 4 mph NW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)

Hello rmurray!

On 21 Aug 2024, rmurray said the following...

The second modem is brand new, yet neither of them responds to AT commands. However, the new one does dial out and can synchronize with a

Check the DIP switches to see if they're in their default positions:

https://support.usr.com/support/5686g/5686g-ug/features.html

DIP switch #3 (Result Code Display) and #4 (Command Mode Local Echo Suppression) would probably be of particular interest. The default settings would be that the modem gives command results and that it also echoes back the characters (commands) you send to it, so that you can see what you're typing.

Fingers crossed! :)

Best regards
Zip

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

temporarily disable RTS handshaking on the modem side. If you get a response after issuing it, this will indicate the hardware handshaking isn't configured correctly. --- SBBSecho 3.14-Win32

Thank you, but no, it still doesn't give a response to my command.

What is the correct dip switch configuration? Could this be it?

VA2RFC BBS Les Méchins, Québec Canada
SysOp: rmurray PhoneNet: 1000040 (Modem)
Telnet: va2rfcbbs.photorm.net:23 FsxNet: 21:1/235 FidoNet: 1:229/114

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: VA2RFC BBS (21:1/235)

Check the DIP switches on the modem. I seem to recall one of them (or
some combination) disables AT command support.

My config is 3, 5 and 8 at on.

Or it could be your serial cable or serial port at fault.
digital man (rob)

And for my cable. I checked on many sites and I checked again. And the configuration that they tell me is this.

DB9 Color Signal Name DB25
1 White DCD (Data Carrier Detect) 8
2 Blue RXD (Receive Data) 3
3 Green TXD (Transmit Data) 2
4 Orange DTR (Data Terminal Ready) 20
5 Black GND (Signal Ground) 7
6 Brown DSR (Data Set Ready) 6
7 Yellow RTS (Request to Send) 4
8 Purple CTS (Clear to Send) 5
9 Red RI (Ring Indicator) 22

It's that???

VA2RFC BBS Les Méchins, Québec Canada
SysOp: rmurray PhoneNet: 1000040 (Modem)
Telnet: va2rfcbbs.photorm.net:23 FsxNet: 21:1/235 FidoNet: 1:229/114

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: VA2RFC BBS (21:1/235)

https://support.usr.com/support/5686g/5686g-ug/features.html
Fingers crossed! :)

Best regards

From what I saw on the page i'm doing everything ok...

VA2RFC BBS Les Méchins, Québec Canada
SysOp: rmurray PhoneNet: 1000040 (Modem)
Telnet: va2rfcbbs.photorm.net:23 FsxNet: 21:1/235 FidoNet: 1:229/114

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: VA2RFC BBS (21:1/235)

Hello rmurray!

On 22 Aug 2024, rmurray said the following...

From what I saw on the page i'm doing everything ok...

Hmm, bummer...

AT&F&W doesn't heal anything? (I'm thinking if NVRAM settings have become corrupt in some way.)

Best regards
Zip

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

AT&F&W doesn't heal anything? (I'm thinking if NVRAM settings have become corrupt in some way.)
Zip

No, this command does not display anything on the screen either. :(

I have 4 used modems of the same brand and model that are arriving in about a week. I will be able to see if they also do the same thing. That will tell me that it is not the NVRam or something else like that that is the problem. I also just ordered a USB to DB9 cable with LEDs on it on Amazon.ca to diagnose the problem. I also have a DB9 to DB25 converter that I ordered. With that I will be able to replace the serial port on my machine and test if it would not be the serial port configuration on Windows 10 Pro x64 that is causing the problem. And I will be able to make sure that my cables that I also made are good. Although I know that the Pinout is ok because I tested twice rather than once with my multimeter.

I am not giving up, I want to find out. Especially since I will be able to compare with several modems too.

What frustrates me the most is that I am rusty. It's been so many years since I worked with modems that I think that in the past we would have found the problem easily. But now we have lost knowledge and also our network of contacts to compare our research. In the past when everyone had modems we would not have had so much difficulty finding I think.

VA2RFC BBS Les Méchins, Québec Canada
SysOp: rmurray PhoneNet: 1000040 (Modem)
Telnet: va2rfcbbs.photorm.net:23 FsxNet: 21:1/235 FidoNet: 1:229/114

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: VA2RFC BBS (21:1/235)

Hello rmurray!

On 22 Aug 2024, rmurray said the following...

I have 4 used modems of the same brand and model that are arriving in about a week. I will be able to see if they also do the same thing. That

Sounds good! It will be interesting to hear if any of the port replacements will make any difference as well!

What frustrates me the most is that I am rusty. It's been so many years since I worked with modems that I think that in the past we would have found the problem easily. But now we have lost knowledge and also our

We all are by now. :-D

But, hopefully, trying different things one at a time will reveal the solution in due time...

Fingers crossed!

Best regards
Zip

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

But, hopefully, trying different things one at a time will reveal the solution in due time...

Fingers crossed!

Best regards
Zip

Yes, I'm not giving up. I'm really going to do everything I can to find it. And if I succeed, as I hope, I'Il let you know how I did it.

VA2RFC BBS Les Méchins, Québec Canada
SysOp: rmurray PhoneNet: 1000040 (Modem)
Telnet: va2rfcbbs.photorm.net:23 FsxNet: 21:1/235 FidoNet: 1:229/114

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: VA2RFC BBS (21:1/235)

On 22 Aug 2024, rmurray said the following...

I am not giving up, I want to find out. Especially since I will be able
to compare with several modems too.

Is it possible its an echo issue?

|23|04Dr|16|12Claw
|16|14Sysop |12Noverdu |14BBS |20|15Radio|10@|14HTTP://Noverdu.com:88
|16|10 Standard ports for SSH/Telnet |04 WEB|14@|12HTTP://noverdu.com:808 |20|15Global Chat, Global Messaging and Games! |16|10Ditch the Unsocial Media

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Noverdu BBS (21:1/210)

Hello rmurray,

Answering a msg of <22 Aug 24>, from you to Zip:

tell us about PhoneNet :)

Regards,
--
dp

telnet://bbs.roonsbbs.hu:1212 <<=-

... Uptime: 94d 7h 11m 22s (?! or 44d 13h 56m 26s)
--- GoldED/2 1.1.4.7+EMX
* Origin: Roon's BBS - Budapest, HUNGARY (21:4/148)

Hello rmurray,

Answering a msg of <22 Aug 24>, from you to Zip:

tell us about PhoneNet :)

Regards,
--
dp

This is a project I had, but it seems that FidoNet hasn't given me any feedback or comments about it. So, it seems like people aren't interested and don't want it. I didn't mention it on FsxNet because FidoNet kind of discouraged me from wanting to move things forward.

VA2RFC BBS Les Méchins, Québec Canada
SysOp: rmurray PhoneNet: 1000040 (Modem)
Telnet: va2rfcbbs.photorm.net:23 FsxNet: 21:1/235 FidoNet: 1:229/114

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: VA2RFC BBS (21:1/235)

Hello rmurray,

23 Aug 24 12:22, you wrote to me:

Hello rmurray,

Answering a msg of <22 Aug 24>, from you to Zip:

tell us about PhoneNet :)

Regards,
--
dp

This is a project I had, but it seems that FidoNet hasn't given me any feedback or comments about it. So, it seems like people aren't
interested and don't want it. I didn't mention it on FsxNet because FidoNet kind of discouraged me from wanting to move things forward.

thanks, now i can see :)

do you know http://2600.network ?

also i am using an asterisk pbx for my phone lines, we can link together if you'd like. i think who is interested in using real modems have a pbx installed.

Regards,
--
dp

telnet://bbs.roonsbbs.hu:1212 <<=-

... Uptime: 94d 10h 50m 48s (?! or 44d 17h 35m 51s)
--- GoldED/2 1.1.4.7+EMX
* Origin: Roon's BBS - Budapest, HUNGARY (21:4/148)

do you know http://2600.network ?

also i am using an asterisk pbx for my phone lines, we can link together if you'd like. i think who is interested in using real modems have a pbx installed.

Thank you for the information, no I didn't know that.

VA2RFC BBS Les Méchins, Québec Canada
SysOp: rmurray PhoneNet: 1000040 (Modem)
Telnet: va2rfcbbs.photorm.net:23 FsxNet: 21:1/235 FidoNet: 1:229/114

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: VA2RFC BBS (21:1/235)

On 23 Aug 24 12:22:40, Rmurray said the following to Roon:

This is a project I had, but it seems that FidoNet hasn't given me any feedback or comments about it. So, it seems like people aren't interested a don't want it. I didn't mention it on FsxNet because FidoNet kind of discouraged me from wanting to move things forward.

To be fair, its not a Fidonet problem. All Nets these days have the same exact people and same lack of traffic. Its just how it is.

You asked me to start two FR echoes which was done with no complaint as the idea had some merit. But it is up to you to promote them... you cannot just post a few messages in your own echoes and claim there is no interest.

Atreyu

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (21:1/176)

do you know http://2600.network ?

I use this service to allow modem users to dial into 2oFB. 2600.network sets my bbS up with a login code "20forbeers" - users dial into any of 2600.network's POTS numbers;

564-244-2600
760-330-2600
929-470-2600
743-500-2600
956-300-2600
515-400-2600
833-PLZ-DIAL

... the user enters the login code and viola - gets a TELNET to 2oFB. (Or any other BBS w/ a login code.) 2600.network also offers private numbers that connect directly to the BBS its associated with.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Re: Re: USR 5686 no reply at AT command
By: rmurray to Digital Man on Thu Aug 22 2024 12:46 pm

And for my cable. I checked on many sites and I checked again. And the configuration that they tell me is this.

What you posted is correct. However, double and triple check the pin numbers. Is the pin you are calling pin 1 the same as what the rest of the world considers pin 1? It's an easy mistake to make.

Two other questions. Is the TR light on as you are attempting to communicate with the modem? And second, what type of cable did you use? Specifically, is this twisted pair of any type?
--- SBBSecho 3.14-Win32
* Origin: The Fool's Quarter, fqbbs.synchro.net (21:1/149)