Okay, I'm going to try and explain this in order. But honestly, I have done so much searching and what seems like a zillion tests. I really, really want to get this working.

So, I have several BBS systems set up and they all terminate with TELNET at various ports. WildCat! supports TELNET natively, so I am all set there with up to 16 simultaneous connections. I also have Image BBS set up with a user port connection set to IP232 connection to TCPSER running as a windows service. Now, these two BBS servers run on emulated systems (Vice and VMWare Workstation) - but just remember: they are both accessible via TELNET and I can connect to them from my MacBook Pro with SyncTerm - no problem.

Here is the fun part: I have several vintage computers that I want to be able to connect to them as well... so, SEXPOTS! I have a Panasonic EZ-Phone system with 8 lines. Right now, my Amiga 1000 and Apple Iic are sharing the same line and I have one modem connected to the Windows 7 machine hosting the VMs (I wish I could provide a drawing - just have to create one first. I can get all this to work - but not consistently. Sometimes when I start SEXPOTS, the Modem Responses are the last set of characters in the INIT string and it seems to just fall through and connect to the TELNET endpoint without even waiting for a call. It also seems that when I get it to work for one scenario (say, the Amiga), the other computer dials in and it doesn't detect a pickup... it also seems to change what happens when I set the windows device baud rate up or down... trying to match the modems, etc. It also seems to affect success or failure trying different INIT strings. It just does not seem to be consistent in anything I do... sometimes, I think I nailed it. Then it has a problem re-initializing the modem after a successful connection.

So I know this is a lot and requires more precise detail to troubleshoot, but I was hoping to just shake the tree a bit and see if anyone else struggled with this. My Windows 7 machine has a USB Serial 4 port on it and connected to those four ports are 2 Hayes Smartmodem Optima 288s and two Hayes Smartmodem 1200s.

One important fact - when I pass a serial port to the VM running Wildcat! and set up Wildcat! with a modem as one of the nodes... everything works perfectly and consistently. Modem initializes, waits and I can connect just fine with My Amiga with the Modem 1200 RS and with the Apple Modem 1200. It seems like Wildcat! is doing something different right in handling the modems?

Thanks for reading and I will take any hints... any.

-Christopher

...Let me add that every AT Command that I have tried in the sexpots.ini has been verified first using HyperTerm on Windows 7 and returns an "OK".

So right now, I am just running it like this:

Windows 7 -> COM8 1200, N81 - HAYES Smartmodem 1200 <- SEXPOTS COM8 1200, N81 INIT:AT&F

LogLevel = INFO
Debug = FALSE
PauseOnExit = FALSE
Prompt =
PromptTimeout = 60

[COM]
Device = COM8
BaudRate = 1200
Hangup = TRUE
IgnoreDCD = FALSE
DCDTimeout = 10
DTRDelay = 100
NullModem = FALSE

[Modem]
Init = AT&F
AutoAnswer = ATS0=1
CleanUp = ATS0=0
EnableCallerID = AT+VCID=1
Timeout = 10
ReInit = 60
Answer = ATA
Ring = RING
ManualAnswer = FALSE

[TCP]
Host = 192.168.30.50
Port = 23
NoDelay = TRUE
Telnet = TRUE

[Telnet]
Enabled = TRUE
Debug = FALSE
AdvertiseLocation = FALSE
TermType = SEXPOTS
TermSpeed = 28800,28800

[Ident]
Enabled = FALSE
Port = 113
Interface = 0
Response = CALLERID:SEXPOTS

...and this is what happens:

c:\Program Files\Syncronet POTS>sexpots

Synchronet External POTS Support v1.32-Win32 Copyright 2020 Rob Swindell

6/7 16:36:06 Reading sexpots.ini
6/7 16:36:06 Synchronet Communications I/O Library for Win32 v1.13
6/7 16:36:06 Build Nov 11 2020 02:07:01 MSC 1927
6/7 16:36:06 WinSock 2.0 Running
6/7 16:36:06 TCP Host: 192.168.30.50
6/7 16:36:06 TCP Port: 23
6/7 16:36:06 Opening Communications Device (COM Port): COM8
6/7 16:36:06 COM Port device handle: 144
6/7 16:36:06 COM Port DTE rate: 1200 bps
6/7 16:36:06 Initializing modem:
6/7 16:36:06 Modem Command: AT&F
6/7 16:36:06 Modem Response: ERROR
6/7 16:36:06 Setting modem to auto-answer:
6/7 16:36:06 Modem Command: ATS0=1
6/7 16:36:07 Modem Response: OK
6/7 16:36:07 Enabling modem Caller-ID:
6/7 16:36:07 Modem Command: AT+VCID=1
6/7 16:36:07 Modem Response: ERROR
6/7 16:36:07 Waiting for incoming call (Carrier Detect) ...
6/7 16:36:08 Carrier detected
6/7 16:36:08 Connecting to 192.168.30.50 port 23
6/7 16:36:08 Connected from COM Port (handle 144) to 192.168.30.50 TCP port 23 using socket descriptor 156
6/7 16:36:12 Connection reset by peer on receive
6/7 16:36:12 Bytes sent-to, received-from COM Port: 1552, 548
6/7 16:36:12 Call completed (1 total)
6/7 16:36:12 Dropping DTR (attempt #1)

Re: SEXPOTS - Pulling my hair out... :)
By: cafarmer to Digital Man on Fri Jun 07 2024 05:55 am

Okay, I'm going to try and explain this in order. But honestly, I have done so much searching and what seems like a zillion tests. I really, really want to get this working.

So this is a local sub-board, not normally use for Synchronet (or SEXPOTS) tech support. https://wiki.synchro.net/howto:support

So, I have several BBS systems set up and they all terminate with TELNET at various ports. WildCat! supports TELNET natively, so I am all set there with up to 16 simultaneous connections. I also have Image BBS set up with a user port connection set to IP232 connection to TCPSER running as a windows service. Now, these two BBS servers run on emulated systems (Vice and VMWare Workstation) - but just remember: they are both accessible via TELNET and I can connect to them from my MacBook Pro with SyncTerm - no problem.

Here is the fun part: I have several vintage computers that I want to be able to connect to them as well... so, SEXPOTS! I have a Panasonic EZ-Phone system with 8 lines. Right now, my Amiga 1000 and Apple Iic are sharing the same line and I have one modem connected to the Windows 7 machine hosting the VMs (I wish I could provide a drawing - just have to create one first.
I can get all this to work - but not consistently. Sometimes when I start SEXPOTS, the Modem Responses are the last set of characters in the INIT string and it seems to just fall through and connect to the TELNET endpoint without even waiting for a call.

Which version of SEXPOTS? What if you use a shorter modem init string (e.g. just "ATZ")?

It also seems that when I get it to work
for one scenario (say, the Amiga), the other computer dials in and it doesn't detect a pickup... it also seems to change what happens when I set the windows device baud rate up or down... trying to match the modems, etc.

The device rate (DTE) rate is not supposed to match the connection (DCE) rate. It should be higher than your highest supported DCE rate (e.g. 38400 or 57600 is enough for all realistic connections).

It also seems to affect success or failure trying different INIT strings. It just does not seem to be consistent in anything I do... sometimes, I think I nailed it. Then it has a problem re-initializing the modem after a successful connection.

Is the modem configured to recognize DTR?

So I know this is a lot and requires more precise detail to troubleshoot, but I was hoping to just shake the tree a bit and see if anyone else struggled with this. My Windows 7 machine has a USB Serial 4 port on it and connected to those four ports are 2 Hayes Smartmodem Optima 288s and two Hayes Smartmodem 1200s.

I would imagine the 1200 modem needs a very different configuration (modem init strings, COM port settings) than the 288.

One important fact - when I pass a serial port to the VM running Wildcat! and set up Wildcat! with a modem as one of the nodes... everything works perfectly and consistently. Modem initializes, waits and I can connect just fine with My Amiga with the Modem 1200 RS and with the Apple Modem 1200. It seems like Wildcat! is doing something different right in handling the modems?

Thanks for reading and I will take any hints... any.

It's probably the serial port settings or the modem settings.
--
digital man (rob)

Steven Wright quote #34:
If at first you don't succeed, skydiving is not for you.
Norco, CA WX: 59.5°F, 89.0% humidity, 3 mph WNW wind, 0.00 inches rain/24hrs

Re: SEXPOTS - Pulling my hair out... :)
By: cafarmer to Digital Man on Fri Jun 07 2024 01:39 pm

6/7 16:36:07 Modem Command: AT+VCID=1
6/7 16:36:07 Modem Response: ERROR

It appears your modem doesn't support Caller-ID.
--
digital man (rob)

Steven Wright quote #8:
If you want the rainbow, you got to put up with the rain.
Norco, CA WX: 59.5°F, 89.0% humidity, 3 mph WNW wind, 0.00 inches rain/24hrs

My apologies on where I posted this. I click on the "go here" link and just started poking around not realizing you probably dropped me right where I needed to ask my question. We can move this if it makes more sense.

I will try to answer the responses in order asked:

1. As far as I can tell, this is the latest version of SEXPOTS taken from the latest install v1.32-Win32
2. The first two string I tried was the default one, AT&F and then ATZ. Neither would allow the modem to wait... it immediately detected carrier and tried to connect to the TCP host without an actual incoming call.
3. For the Hayes Smartmodem 1200, I cannot get it to communicate (DTE) to the modem with anything higher than 1200 baud via Hyperterminal on Windows 7. (for now, I am focusing this issue with the HSM 1200, I will take what I learn and try to apply it to the HSM Optima 288 later. It may be that the HSM 1200 didn't support a DTE speed higher than the analog side of the connection (I can't remember what to call modem-modem connectivity - DCE?)?
4. DTR? Not sure, I will have to look into that and how it might be affecting the connection.
5. I have tried so many HSM 1200 init strings proposed out there. None of them were a "silver bullet". (again, just focusing on the 1200 for now).
6. No, neither of these modems seem to support Caller ID, but I couldn't figure out a way to bypass the attempt to set it.

A lot of this stuff is not new to me - I used to configure modem banks for a financial institution back in the early 90's (91-93). But it was a long time ago and yes, sometime I struggled with some of the newer Microcom modems - but really it was just me trying to squeeze every last drop of speed vs. performance I could get for the originators out in the field.

Thank you very much for your responses as I work through this thing.

I see your Steven Wright and raise you a Jack Handy:

"If a kid asks where rain comes from, I think a cute thing to tell him is "God is crying." And if he asks why God is crying, another cute thing to tell him is "probably because of something you did."

I did notice that it has a hell of a time always trying to drop DTR - goes through all 10 attempts before bailing out to the command prompt. But since I can say for sure just now what all the parameters were on those specific attempts, take it with a grain of salt.

Re: SEXPOTS - Pulling my hair out... :)
By: cafarmer to Digital Man on Sun Jun 09 2024 08:06 am

My apologies on where I posted this. I click on the "go here" link and just started poking around not realizing you probably dropped me right where I needed to ask my question. We can move this if it makes more sense.

I will try to answer the responses in order asked:

1. As far as I can tell, this is the latest version of SEXPOTS taken from the latest install v1.32-Win32

The latest is v2.0

2. The first two string I tried was the default one, AT&F and then ATZ. Neither would allow the modem to wait... it immediately detected carrier and tried to connect to the TCP host without an actual incoming call.

ATZ loads whatever setting you have saved in the modem's NVRAM (stored with AT&W).

3. For the Hayes Smartmodem 1200, I cannot get it to communicate (DTE) to the modem with anything higher than 1200 baud via Hyperterminal on Windows

Yeah, that would be expected for older modems like that.

7. (for now, I am focusing this issue with the HSM 1200, I will take what I learn and try to apply it to the HSM Optima 288 later. It may be that the HSM 1200 didn't support a DTE speed higher than the analog side of the connection (I can't remember what to call modem-modem connectivity - DCE?)?

Yeah, those old (2400 and slower) modems without error correction usually expecte DTE rate the same as their highest connect (DCE) rate supported. But I would read the manual to know for usre.

4. DTR? Not sure, I will have to look into that and how it might be affecting the connection.

Data terminal ready.

5. I have tried so many HSM 1200 init strings proposed out there. None of them were a "silver bullet". (again, just focusing on the 1200 for now).

I would start with the newer modem, myself.

6. No, neither of these modems seem to support Caller ID, but I couldn't figure out a way to bypass the attempt to set it.

Set the Caller-ID string to blank.

A lot of this stuff is not new to me - I used to configure modem banks for a financial institution back in the early 90's (91-93). But it was a long time ago and yes, sometime I struggled with some of the newer Microcom modems - but really it was just me trying to squeeze every last drop of speed vs. performance I could get for the originators out in the field.

Thank you very much for your responses as I work through this thing.

I see your Steven Wright and raise you a Jack Handy:

"If a kid asks where rain comes from, I think a cute thing to tell him is "God is crying." And if he asks why God is crying, another cute thing to tell him is "probably because of something you did."

:-)
--
digital man (rob)

Rush quote #86:
Follow men's eyes as they look to the skies .. Jacob's Ladder
Norco, CA WX: 74.0°F, 62.0% humidity, 3 mph WSW wind, 0.00 inches rain/24hrs

Re: SEXPOTS - Pulling my hair out... :)
By: cafarmer to Digital Man on Sun Jun 09 2024 08:10 am

I did notice that it has a hell of a time always trying to drop DTR - goes through all 10 attempts before bailing out to the command prompt. But since I can say for sure just now what all the parameters were on those specific attempts, take it with a grain of salt.

If the modem isn't responding to dropped DTR (normally, that behavior is enabled with AT&D2, but it's possible some really old modems may not support it - I would check):
&D2 Hang up on DTR-drop and go to command mode

If the modem doesn't support DTR, then you would have to configure SEXPOTS appropriately, but use of DTR is definitely preferred.
--
digital man (rob)

This Is Spinal Tap quote #33:
Nigel Tufnel: Well, so what? What's wrong with bein' sexy?
Norco, CA WX: 74.1°F, 62.0% humidity, 11 mph W wind, 0.00 inches rain/24hrs

I am going to look into the DTR settings just to make sure. If I recall Dn (0-3) are the settings that are supported.

Also, I downloaded a serial port monitor and reconfigured the modem with Wildcat! to see what it was sending to the modem and this is what I recorded:

ATZOKATATOKATE0V1ATE0V1OKATX4OKATS0=0OKRINGATACONNECT 1200..

This was initialization, waiting for call and picking up the call. It all worked just fine with the HSM 1200. I am going to split this string on the OK responses.

ATZ
OK
ATAT
OK
ATE0V1ATE0V1
OK
ATX4
OK
ATS0=0
OK
RING
ATA
CONNECT 1200..

I tried to concatenate those separate commands into one init string and it didn't like it... just FYI if you know how to do it... I will research what I am doing wrong. I thought it was only one AT and all the other commands added individually using & signs... but I am clearly missing something.

Thanks Bob!

Sorry, Rob.

Re: SEXPOTS - Pulling my hair out... :)
By: cafarmer to Digital Man on Sun Jun 09 2024 05:21 pm

I tried to concatenate those separate commands into one init string and it didn't like it... just FYI if you know how to do it... I will research what I am doing wrong. I thought it was only one AT and all the other commands added individually using & signs... but I am clearly missing something.

No, that's not how AT commands work.
--
digital man (rob)

Sling Blade quote #15:
Doyle Hargraves: What'cha doin' with that lawn mower blade Karl?
Norco, CA WX: 74.4°F, 60.0% humidity, 6 mph WSW wind, 0.00 inches rain/24hrs

Yeah, that's why I need to research it. It's been a while since I have had to troubleshoot an issue like this. But hopefully, the commands Wildcat! is using may shed some light on why SEXPOTS just drops down to immediately answering a call that didn't really happen.

Thanks again, Rob. If you think of something I should try, I would greatly appreciate it. Meanwhile, I'm off to research.

Re: SEXPOTS - Pulling my hair out... :)
By: cafarmer to Digital Man on Sun Jun 09 2024 06:35 pm

Yeah, that's why I need to research it. It's been a while since I have had to troubleshoot an issue like this. But hopefully, the commands Wildcat! is using may shed some light on why SEXPOTS just drops down to immediately answering a call that didn't really happen.

No, I don't think there's anything special in those AT commands.

Thanks again, Rob. If you think of something I should try, I would greatly appreciate it. Meanwhile, I'm off to research.

First, run the latest version of SexPOTS (v2.0).
--
digital man (rob)

Synchronet "Real Fact" #91:
Captured chat with Wayne Bell: http://wiki.synchro.net/history:waynebell_chat Norco, CA WX: 74.4°F, 60.0% humidity, 6 mph WSW wind, 0.00 inches rain/24hrs

Re: SEXPOTS - Pulling my hair out... :)
By: Digital Man to cafarmer on Sun Jun 09 2024 06:53 pm

Thanks again, Rob. If you think of something I should try, I would greatly appreciate it. Meanwhile, I'm off to research.

First, run the latest version of SexPOTS (v2.0).

I updated the files in the sexpots.zip hosted here on Vertrauen to make it easier for you to find.
--
digital man (rob)

Sling Blade quote #4:
Doyle: wimpy-ass kids or mental retards.. she got one of each livin' with her. Norco, CA WX: 71.1°F, 67.0% humidity, 13 mph NW wind, 0.00 inches rain/24hrs

Where exactly did you upload that file to? Thanks!

-Chris

Re: SEXPOTS - Pulling my hair out... :)
By: cafarmer to Digital Man on Sun Jun 09 2024 08:06 pm

Where exactly did you upload that file to? Thanks!

https://synchro.net/Synchronet/sexpots.zip
--
digital man (rob)

Rush quote #52:
His world is under observation, we monitor his station .. Digital Man
Norco, CA WX: 65.7°F, 76.0% humidity, 7 mph WNW wind, 0.00 inches rain/24hrs

Found it - Thanks! I was reading the description on the file - then it dawned on me.

Re: SEXPOTS - Pulling my hair out... :)
By: cafarmer to Digital Man on Sun Jun 09 2024 08:17 pm

Found it - Thanks! I was reading the description on the file - then it dawned on me.

Okay, description updated now. Thanks,
--
digital man (rob)

Breaking Bad quote #10:
Get a big old raging hard-on at the idea of catching this piece of shit! - Hank Norco, CA WX: 64.9°F, 77.0% humidity, 4 mph NNW wind, 0.00 inches rain/24hrs

Settings and Result from v2.0

LogLevel = INFO
Debug = FALSE
PauseOnExit = FALSE
Prompt =
PromptTimeout = 60

[COM]
Device = COM8
BaudRate = 1200
Hangup = TRUE
IgnoreDCD = FALSE
DCDTimeout = 10
DTRDelay = 100
NullModem = FALSE

[Modem]
Init = ATZ
AutoAnswer = ATS0=1
CleanUp = ATS0=0
EnableCallerID = AT+VCID=1
Timeout = 10
ReInit = 60
Answer = ATA
Ring = RING
ManualAnswer = FALSE

[TCP]
Host = 192.168.30.50
Port = 23
NoDelay = TRUE
Telnet = TRUE

[Telnet]
Enabled = TRUE
Debug = FALSE
AdvertiseLocation = FALSE
TermType = SEXPOTS
TermSpeed = 28800,28800

[Ident]
Enabled = FALSE
Port = 113
Interface = 0
Response = CALLERID:SEXPOTS


Synchronet External POTS Support/Win32 v2.0 Copyright 2024 Rob Swindell https://gitlab.synchro.net - master/3a029fa8f Jun 09 2024 18:42

6/9 23:26:44 Reading sexpots.ini
6/9 23:26:44 Synchronet Communications I/O Library for Win32 v1.13
6/9 23:26:44 Build Jun 9 2024 19:21:30 MSC 1916
6/9 23:26:44 WinSock 2.0 Running
6/9 23:26:44 TCP Host: 192.168.30.50
6/9 23:26:44 TCP Port: 23
6/9 23:26:44 Opening Communications Device (COM Port): COM8
6/9 23:26:44 COM Port device handle: 144
6/9 23:26:44 COM Port DTE rate: 1200 bps
6/9 23:26:44 Initializing modem:
6/9 23:26:44 Modem Command: ATZ
6/9 23:26:44 Modem Response: OK
6/9 23:26:44 Setting modem to auto-answer:
6/9 23:26:44 Modem Command: ATS0=1
6/9 23:26:45 Modem Response: OK
6/9 23:26:45 Enabling modem Caller-ID:
6/9 23:26:45 Modem Command: AT+VCID=1
6/9 23:26:45 Modem Response: ERROR
6/9 23:26:45 Waiting for incoming call (Carrier Detect) ...
6/9 23:26:46 Carrier detected
6/9 23:26:46 Connecting to 192.168.30.50 port 23
6/9 23:27:07 SOCKET ERROR 60 connecting to 192.168.30.50 port 23
6/9 23:27:11 Dropping DTR (attempt #1)

The TCP host socket error is most likely because I do not have the BBS running right now. But it shouldn't have gone that far because there was no RING (I didn't call it).

Re: SEXPOTS - Pulling my hair out... :)
By: cafarmer to Digital Man on Sun Jun 09 2024 08:29 pm

Settings and Result from v2.0

LogLevel = INFO

It's often helpful to set the LogLeve to "Debug" when debugging issues.

EnableCallerID = AT+VCID=1

Set this to blank if your modem doesn't support it.

Synchronet External POTS Support/Win32 v2.0 Copyright 2024 Rob Swindell https://gitlab.synchro.net - master/3a029fa8f Jun 09 2024 18:42

6/9 23:26:44 Reading sexpots.ini
6/9 23:26:44 Synchronet Communications I/O Library for Win32 v1.13
6/9 23:26:44 Build Jun 9 2024 19:21:30 MSC 1916
6/9 23:26:44 WinSock 2.0 Running
6/9 23:26:44 TCP Host: 192.168.30.50
6/9 23:26:44 TCP Port: 23
6/9 23:26:44 Opening Communications Device (COM Port): COM8
6/9 23:26:44 COM Port device handle: 144
6/9 23:26:44 COM Port DTE rate: 1200 bps
6/9 23:26:44 Initializing modem:
6/9 23:26:44 Modem Command: ATZ
6/9 23:26:44 Modem Response: OK
6/9 23:26:44 Setting modem to auto-answer:
6/9 23:26:44 Modem Command: ATS0=1
6/9 23:26:45 Modem Response: OK
6/9 23:26:45 Enabling modem Caller-ID:
6/9 23:26:45 Modem Command: AT+VCID=1
6/9 23:26:45 Modem Response: ERROR
6/9 23:26:45 Waiting for incoming call (Carrier Detect) ...
6/9 23:26:46 Carrier detected
6/9 23:26:46 Connecting to 192.168.30.50 port 23
6/9 23:27:07 SOCKET ERROR 60 connecting to 192.168.30.50 port 23
6/9 23:27:11 Dropping DTR (attempt #1)

Socket error 60:

WSAETIMEDOUT
10060
Connection timed out.
A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.

So... my guess, there was no TCP server listening on that IP address and port at that time.
--
digital man (rob)

Sling Blade quote #2:
Karl (re: killing Doyle): I hit him two good whacks in the head with it.
Norco, CA WX: 63.9°F, 79.0% humidity, 8 mph NW wind, 0.00 inches rain/24hrs

Yeah, I didn't have the BBS up and running... but why didn't it wait for a call? I never called the modem. It just drops through. Note the time stamp... no waiting. Just says "carrier detected" and tries to connect to the TCP port.

Re: SEXPOTS - Pulling my hair out... :)
By: cafarmer to Digital Man on Sun Jun 09 2024 08:32 pm

The TCP host socket error is most likely because I do not have the BBS running right now. But it shouldn't have gone that far because there was no RING (I didn't call it).

Right, but your modem is raising/asserting the DCD (data carrier detect) signal.

For modems that support DCD correctly, the command to enable it is AT&C1:

AT&C1
DCD follows carrier state (default).

It sounds like your modem is set for AT&C0:

AT&C0
Always keep DCD on.
--
digital man (rob)

Rush quote #46:
One day I feel I'm on top of the world, and the next it's falling in on me Norco, CA WX: 63.2°F, 81.0% humidity, 7 mph WNW wind, 0.00 inches rain/24hrs

Re: SEXPOTS - Pulling my hair out... :)
By: cafarmer to Digital Man on Sun Jun 09 2024 08:50 pm

Yeah, I didn't have the BBS up and running... but why didn't it wait for a call? I never called the modem. It just drops through. Note the time stamp... no waiting. Just says "carrier detected" and tries to connect to the TCP port.

Because your modem is raising the "carrier detect" signal, as I already explained.
--
digital man (rob)

Synchronet/BBS Terminology Definition #16:
CR = Carriage Return (ASCII 13, Ctrl-M)
Norco, CA WX: 63.2°F, 81.0% humidity, 7 mph WNW wind, 0.00 inches rain/24hrs

Thank you for all of your help Rob, this seems like a bust with these modems (I did try a Microcom Deskporte FAST as well - no love). I think you built something great and it was exactly what I was looking for when Al (bucko) mentioned it to me. I agree that Wildcat! isn't sending anything of enlightnement to the modem that I can't with SEXPOTS... (I tried your suggestion sending C1 to the modem - no change)... just can't pinpoint what is going on. Maybe I will get a second wind and pick this up later.

Thanks again for all your help and suggestions.

-Chris

Re: SEXPOTS - Pulling my hair out... :)
By: cafarmer to Digital Man on Mon Jun 10 2024 07:02 am

Thank you for all of your help Rob, this seems like a bust with these modems (I did try a Microcom Deskporte FAST as well - no love). I think you built something great and it was exactly what I was looking for when Al (bucko) mentioned it to me. I agree that Wildcat! isn't sending anything of enlightnement to the modem that I can't with SEXPOTS... (I tried your suggestion sending C1 to the modem - no change)...

I suggested AT&C1, not ATC1 (those are different things). https://wiki.synchro.net/util:sexpots#modem_settings

just can't pinpoint what is going on.

Did you read the modem's manual?

Thanks again for all your help and suggestions.

No problem.
--
digital man (rob)

Synchronet/BBS Terminology Definition #24:
DOVE = Domain/Vertrauen
Norco, CA WX: 69.2°F, 71.0% humidity, 4 mph WNW wind, 0.00 inches rain/24hrs

I tried both AT&C1 (it was a suggested init string for the optima AT&C1&D2) and ATC1. The modem didn't like AT&C1 - Error.

I cannot find the manual for the HSM 1200. But I did find the manual for the HSM 300 and a General Smartmodem Guide.

D.5.1 Using the CD line
If you are confident of the communications environment and cabling requirements, and have access to the RS-232 signal status, then monitoring the CD line is the easiest carrier loss detection method to implement. This requires &C1 to be programmed at setup time, or be stored in the modem as the value recalled on reset or powerup.
However, this is the most restrictive and risky choice. It requires a properly wired cable and support of &C1 by the modem's command set or proper DIP- switch settings.

Since there may be some confusion on my part between ATC1 and AT&C1, I'm not exactly sure if this text applies now:

Cn - Controls 
Smartmodem’s
 transmitter carrier; i.e.,
signal sent when
 calling, answering or 
connected to a distant modem.
Default C=1
n = 0 Transmitter Off
n = 1 Transmitter On

So this was for the HSM 300 that came before the HSM 1200... I would be surprised if most of the commands were not supported in the HSM 1200.

ATC1 = OK (not sure what this does. ATC? returns 000)
AT&C1 - ERROR

Re: SEXPOTS - Pulling my hair out... :)
By: cafarmer to Digital Man on Mon Jun 10 2024 12:26 pm

I tried both AT&C1 (it was a suggested init string for the optima AT&C1&D2) and ATC1. The modem didn't like AT&C1 - Error.

Both modems didn't that AT&C1 or just the 1200? If the modem doesn't accept AT&C1, then you'll need to set IgnoreDCD = TRUE in the sexpots.ini file used for that modem.

I cannot find the manual for the HSM 1200. But I did find the manual for the HSM 300 and a General Smartmodem Guide.

D.5.1 Using the CD line
If you are confident of the communications environment and cabling requirements, and have access to the RS-232 signal status, then monitoring the CD line is the easiest carrier loss detection method to implement. This requires &C1 to be programmed at setup time, or be stored in the modem as the value recalled on reset or powerup.
However, this is the most restrictive and risky choice. It requires a properly wired cable and support of &C1 by the modem's command set or proper DIP- switch settings.

Wouldn't the HSM 300 be older than the 1200? I'd be very suprirsed if an older (300bps?) modem supported AT&C1 while the newer modem (1200bps?) did not.

Since there may be some confusion on my part between ATC1 and AT&C1, I'm not exactly sure if this text applies now:

Cn - Controls ¿Smartmodem's¿ transmitter carrier; i.e.,¿signal sent
when¿ calling, answering or ¿connected to a distant modem.
Default C=1
n = 0 Transmitter Off
n = 1 Transmitter On

So this was for the HSM 300 that came before the HSM 1200... I would be surprised if most of the commands were not supported in the HSM 1200.

ATC1 = OK (not sure what this does. ATC? returns 000)
AT&C1 - ERROR

Weird. Anyway, telling SexPOTS to ignore DCD should work around *that* modem issue.
--
digital man (rob)

Sling Blade quote #4:
Doyle: wimpy-ass kids or mental retards.. she got one of each livin' with her. Norco, CA WX: 78.5°F, 55.0% humidity, 12 mph W wind, 0.00 inches rain/24hrs

I am only working with the 1200 right now to avoid confusion. The hope was that if I figured out the 1200, the Optima 28.8 would be easier as it is newer.

The only manual I have right now is the HSM 300. I was assuming if it was in that manual, the 1200 would support it as well. So, in the HSM 300 manual, there is some info on the Carrier Signal, Cn. But they don't ever show an example of how it it used. So when I tried ATC1, the HSM 1200 responded with "OK". But then I tried to read that back by typing ATC?, it responded "000". So I wasn't sure what was going on there. Then you stressed ATCn and AT&Cn were different. So, I tried AT&C1 and it responded "ERROR".

I tried setting IgnoreDCD = FALSE a while ago thinking it might affect the behavior, but it didn't. If I recall, it still picked up a "Carrier Detected" and made the connection to the TCP endpoint without ever receiving an actual call. It's not really fair to you to present recollection vs. a controlled test with output, so maybe later today, I will set the IgnoreDCD and provide the .ini settings along with the output. BTW, Debug didn't reveal anything I could use to figure it out either.

As always, thank you very much for your help.

-Chris

EDIT: I tried setting IgnoreDCD = TRUE, not FALSE. (glad I re-read that). Again, IgnoreDCD = TRUE did not affect the behavior. But, in the name of science, I should back that up with an new test to verify and share.

Re: SEXPOTS - Pulling my hair out... :)
By: cafarmer to Digital Man on Tue Jun 11 2024 05:46 am

I tried setting IgnoreDCD = FALSE a while ago thinking it might affect the behavior, but it didn't. If I recall, it still picked up a "Carrier Detected" and made the connection to the TCP endpoint without ever receiving an actual call.

"IgnoreDCD = FALSE" is the default behavior - which means SEXPOTS watches the DCD signal on the serial line to detect carrier. Since that doesn't work with your modem, you'll need to set "IgnoreDCD = TRUE", but only for that old modem that doesn't support AT&C1.

I'd recommend working with the *newer* modem first, since it's more likely to "just work" with the default behavior of SEXPOTS.
--
digital man (rob)

Synchronet/BBS Terminology Definition #35:
FTN = FidoNet Technology Network
Norco, CA WX: 75.9°F, 62.0% humidity, 5 mph SW wind, 0.00 inches rain/24hrs

Re: SEXPOTS - Pulling my hair out... :)
By: cafarmer to Digital Man on Tue Jun 11 2024 06:14 am

EDIT: I tried setting IgnoreDCD = TRUE, not FALSE. (glad I re-read that). Again, IgnoreDCD = TRUE did not affect the behavior. But, in the name of science, I should back that up with an new test to verify and share.

Please do.
--
digital man (rob)

This Is Spinal Tap quote #33:
Nigel Tufnel: Well, so what? What's wrong with bein' sexy?
Norco, CA WX: 75.9°F, 62.0% humidity, 5 mph SW wind, 0.00 inches rain/24hrs

Hi,
Thank you for sharing this information.