03-03-2023, 05:38 AM
Hola,
The commands being sent are pretty standard: ATZ|S0=0| for init (| = CR), with variations as I try different AT&Dx values. ATA for picking up, RING and CONNECT for the relevant events, and ~~~~+++~~~~ATH0| for hangup (which is only used if dropping DTR fails), and no busy string set (makes no sense here). I've locked the baud to 19200 for now (but it does work up to 115k).
The "nc" command - simply establishes a TCP socket - so RAW, not TELNET.
/Eirik
(02-27-2023, 11:17 AM)admin Wrote: Do you know what commands the BBS is sending to the modem and what it should be expecting? Typically, this type of problem is due to the BBS not receiving something that it expects to see. It could be that the BBS is sending some odd (unsupported) modem command and that is generating ERROR as a return. It could also be a stacked command (ie. ATZ0H0M0.. etc. where commands are all put together) that is not supported in the immediate mode. The only way to really diagnose these types of problems is by using a serial sniffer program or by connecting the serial port to another serial (via hardware) and watching the data.
The commands being sent are pretty standard: ATZ|S0=0| for init (| = CR), with variations as I try different AT&Dx values. ATA for picking up, RING and CONNECT for the relevant events, and ~~~~+++~~~~ATH0| for hangup (which is only used if dropping DTR fails), and no busy string set (makes no sense here). I've locked the baud to 19200 for now (but it does work up to 115k).
(02-27-2023, 11:17 AM)admin Wrote: I have no idea what "netcat" is. The WiModem232 supports RAW and TELNET modes.
The "nc" command - simply establishes a TCP socket - so RAW, not TELNET.
/Eirik