chip@tct.uucp (Chip Salzenberg) (09/21/90)
Here at TCT we have two T2500s. We love them. PEP mode is just what the doctor ordered for remote demos on our development machine. However, there is trouble in paradise... I've been trying to make our T2500 answer with V.32 tones so we can dial in with UDS and Hayes V.32 modems. So far I have been unsuccessful. Nothing I try -- not even "AT~F3" -- makes the T2500 generate V.32 answer tones. As an experiment, I tried to make it answer with V.32 only, using "AT S50=6 S94=0". When I called it, it went off hook and then back on hook, without uttering a peep! What is wrong? What have I missed? Is my ROM version obsolete? Why is the sky blue? Please answer any three of these questions. :-) To assist diagnosis, here is a complete register dump. Note that this T2500 is used for both dial-in and dial-out. E0 F1 M1 Q8 P V1 W0 X3 Y0 &P0 &T4 Version GA2.00 S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=040 S08=002 S09=006 S10=007 S11=070 S12=050 S18=000 S25=005 S26=000 S38=000 S41=000 S45=000 S47=004 S48=000 S49=000 S50=000 S51:252 S52:004 S54:003 S55:003 S56=017 S57=019 S58:002 S59=000 S60=000 S61=150 S62=003 S63=001 S64:001 S65=000 S66=000 S67:001 S68=255 S69=000 S90=000 S91=000 S92:001 S93=008 S94=001 S95:002 S96=001 S100=000 S101=000 S102=000 S104=000 S105=001 S110=255 S111=255 S112=001 S121=000 S130=002 S131:001 S150=000 S151=004 S152=001 S153=001 S154=000 S155=000 S160=010 S161=020 S162=002 S163=003 S164=007 S255=000 adTHANKSvance -- Chip Salzenberg at Teltronics/TCT <chip@tct.uucp>, <uunet!pdn!tct!chip>
gemini@geminix.in-berlin.de (Uwe Doering) (09/23/90)
chip@tct.uucp (Chip Salzenberg) writes: >Here at TCT we have two T2500s. We love them. PEP mode is just what >the doctor ordered for remote demos on our development machine. > >However, there is trouble in paradise... > >I've been trying to make our T2500 answer with V.32 tones so we can >dial in with UDS and Hayes V.32 modems. So far I have been >unsuccessful. Nothing I try -- not even "AT~F3" -- makes the T2500 >generate V.32 answer tones. As an experiment, I tried to make it >answer with V.32 only, using "AT S50=6 S94=0". When I called it, it >went off hook and then back on hook, without uttering a peep! Two friends of me had the same problem (at different times). There is a piggy-back board on the modem main board that is responsible for V.32 and V22(bis). Obviously, this piggy-back board likes to jump off its connector pins if the vibrations during shipment are strong enough. You can check this with your modem by simply shaking it. If there is a rattle inside, you've found the problem. :-) Simply put the board back on its two connector rows. Now it should work. The interesting thing is that the modem works perfectly without the V.32 board as long as you stick with PEP mode. Telebit, do you read this? It would be a good idea to fasten this piggy-back board somehow. Uwe -- Uwe Doering | Domain : gemini@geminix.in-berlin.de Berlin |---------------------------------------------------------------- Germany | Bangpath : ...!unido!fub!tmpmbx!geminix!gemini
melanie@pnet51.orb.mn.org (Melanie Bennin) (09/23/90)
My guess is that you have a daughterboard in your modem, and that it shook
loose during shipment. I had the same problem. Telebit recommended that I
unscrew the 4 screws on the bottom, remove the cover, and gently press down
on the daughterboard. Apparently they are now using some glue to make sure
this doesn't happen with new T2500's, but some got out. When I opened my
T2500's up, the daughterboard was just barely attached. Pressing it down did
the trick.
UUCP: {amdahl!bungia, crash}!orbit!pnet51!melanie
ARPA: crash!orbit!pnet51!melanie@nosc.mil
INET: melanie@pnet51.orb.mn.orgsean@utoday.UUCP (Sean Fulton) (09/24/90)
In article <26F8FEE1.5D3C@tct.uucp> chip@tct.uucp (Chip Salzenberg) writes: > >I've been trying to make our T2500 answer with V.32 tones so we can >dial in with UDS and Hayes V.32 modems. So far I have been >unsuccessful. Nothing I try -- not even "AT~F3" -- makes the T2500 >generate V.32 answer tones. I have the same problem here and it is *immensly* annoying! Help. -- Sean Fulton sean@utoday.com UNIX Today! (516) 562-5430 /* The opinions expressed above are not those of my employer */