open https://gitlab.synchro.net/main/sbbs/-/issues/970

I'm having some problems with connections getting drops under some odd circumstances, for example, when pressing # to connect to the viewdata service using BeebEm with a real modem attached to a windows machine. Connecting to the terminal works fine.

Being able to see characters received/sent on the serial line may be able to give me a clue as to what is being sent that I might not be picking up. It may also help in other situations.
--- SBBSecho 3.29-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/970#note_7574

Setting `Debug=true` in the `[com]` section of your sexpots.ini file should already enable debub-level log output of every character received from on the serial line, e.g.
`Received char from COM port (COM1): ^C (3)`

Is that working?
--- SBBSecho 3.29-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/970#note_7575

Ah so it does. It wasn't immediately obvious from the wiki that I could do that. I guess I should have tried it.

Sep 5 01:49:30 wibble sexpots-line1: Writing char to COM port (/dev/ttyACM0): 'a' (97)
Sep 5 01:49:30 wibble sexpots-line1: Writing char to COM port (/dev/ttyACM0): 'm' (109)
Sep 5 01:49:30 wibble sexpots-line1: Writing char to COM port (/dev/ttyACM0): 'e' (101)
Sep 5 01:49:30 wibble sexpots-line1: Writing char to COM port (/dev/ttyACM0): '.' (46)
Sep 5 01:49:30 wibble sexpots-line1: message repeated 2 times: [ Writing char to COM port (/dev/ttyACM0): '.' (46)]
Sep 5 01:49:30 wibble sexpots-line1: Writing char to COM port (/dev/ttyACM0): ^M (13)
Sep 5 01:49:30 wibble sexpots-line1: Writing char to COM port (/dev/ttyACM0): ^J (10)
Sep 5 01:49:30 wibble sexpots-line1: Loss of Carrier Detect (DCD) detected


I'm trying to determine why the modem is disconnecting.

```
Prompt=^MENTER for Terminal or _ for Viewdata
PromptTimeout = 0
```

I display the prompt with no timeout and when I dial in then it displays ok.

Pressing _ (Which is # in viewdata mode) starts the videotexserver.js and it tries to send data mean while on the dialing side I get "NO CARRIER" I can't imagine the modem itself would initiate the dropped call so I'm at a bit of a loss as to what is going on and where to debug it.

It all works fine when doing a direct tcp/ip connection and not going through the modem. Most odd.
--- SBBSecho 3.29-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/970#note_7576

Did you still want more debug information from sexpots?
--- SBBSecho 3.29-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/970#note_7577

I'm not sure. I might open a separate issue to try and debug the dropped carrier issue. Just doing a few more tests.
--- SBBSecho 3.29-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

close https://gitlab.synchro.net/main/sbbs/-/issues/970
--- SBBSecho 3.29-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)