XTR modem glitch

I recently connected an XTR-modem to my computer.
It is unclear why all the drivers detect non-existent short
tones and hang up. A long beep is ALWAYS (!) defined as a short one.
Connection with another modem is established, but only if it is possible to deceive the
driver (for example, pick up the handset on a neighboring telephone).
I checked the WAIT line (entered through the “I” element).
Who knows how to get rid of this?
I have not been able to start the BBS for the third week!

Regards, Sergey Karachentsev.

20 Nov 99 16:46, Sergey Karachentsev wrote to All:

SK> I recently connected an XTR-modem to my computer.
SK> It is unclear for what reasons all drivers detect non-existent
SK> short beeps and hang up. A long beep is ALWAYS (!) defined
SK> as a short beep. A connection with another modem is established, but only if
SK> manages to fool the driver (for example, pick up the handset on a neighboring
SK> telephone). I checked the WAIT line (entered through the
SK> “I” element). Who knows how to get rid of this? I haven’t been able to for the third week

WAIT probably has nothing to do with it. If bytes are transferred back and forth at all,
then most likely there is a glitch in the modem or PBX itself.

First, try plugging another XTR into your computer and see
what happens. If everything works - XTR to the landfill. If it’s the same, then
it’s most likely a PBX glitch.

BUT! If you are not transmitting or receiving anything at all,
then it is best to check whether all other ports of the computer are disabled
when accessing the XTR modem.

Lomov disseminated the XTR circuit to the people - now you can
find the glitch in the modem yourself.

But the computer is not with brake memory ?

Kirill Frolov. [ZX]

if it didn’t work, there would be no connection.

SK> Who knows how to get rid of this?

I ;)
at least you can try.

All the best.
Dmitry.

... LD..X-TRADE... [ZX]

KF> WAIT probably has nothing to do with it. If bytes are transferred back and forth at all,
KF> then most likely there is a glitch in the modem or PBX itself.
Or maybe the driver is to blame? How can a short beep spontaneously form in a faulty modem? I think that the whole reason is the
primitive algorithm for detecting short beeps in the modem driver. The author of this driver probably used a fairly high-quality telephone line when writing it, and therefore considered it unnecessary to create a more reliable algorithm for detecting short beeps. On our lines with extremely poor communication quality, this number will not work.

KF> First, try to plug another XTR into your computer and see
KF> what happens. If everything works - XTR to the landfill. If it’s the same, then
KF> it’s most likely an ATS glitch.
Where can I get it?

With respect, Sergey Karachentsev.

KF>> are transmitted, then most likely there is a glitch in the modem or PBX itself.
SK> Or maybe the driver is to blame? How can
SK> spontaneously generate a short beep in a faulty modem? I think that the whole
SK> reason is in the primitive algorithm for detecting short beeps in the
SK> modem driver. The author of this driver probably used a fairly high-quality telephone line when writing it
SK> and therefore considered it unnecessary
SK> to create a more reliable algorithm for detecting short beeps. On
SK> our own lines with extremely poor communication quality, this number will not
SK> work.

Well, I don’t know what kind of algorithm there is for detecting beeps.
There were problems with Vicomm, they were cured by rewriting such a program
for detecting short beeps. I had to compare the duration of the pause
with the duration of the beep.