Subj : sexpots: Add extra debugging for displaying send/received characters o
To   : GitLab note in main/sbbs
From : Nigel Reed
Date : Fri Sep 05 2025 00:04:19

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)

.