#Fast PPI14400FXSA
45 messages in this thread
I was wondering if anyone else is experiencing the problem that I
am, and if so, is there a fix for it.
I am running an Amiga 2000, 3MB RAM, WB 1.3 with a stock 7.12MHz
68000.
I recently acquired a PPI 14440FXSA modem and I seem to be having
trouble downloading files at high speed (19200, 14400, 9600).
I have tried NComm 2.0 (with the XPR-based transfer protocols) and
connected to a local BBS at Carrier 14400 and 9600, with term to modem
speed set at 19200. A ZModem download with V42bis, compression on, would
go fine for the first 28-32K, then start reporting errors like BAD DATA
BLOCK and checksum type errors. I would generally have to abort the
download.
I also tried the same conditions, but using Baud Bandit (V1.51, I
believe), and would generate an unhealthy number of errors during the
download. But at least that test file (about 50K) did get through in one
try.
This is all while the modem is reporting QUALITY HIGH for the
V.32bis signal quality indicator.
Any ideas?
Thanks.
Joe Buckley
Are you sure that you are uasing a seven wire serial cable? Do you have
CTS/RTS ON?
Here are the modem settings I use, that have worked for me:
ACTIVE PROFILE: DTE:38400 DCE:9600 PARITY:NONE
B16 B1 E1 L2 M0 N1 T Q0 V1 W2 X4 Y0 &A0 &C1 &D2 &G0 &J0 &K3 &L0 &Q5 &R0
&S0 &T4 &U0 &X0 &Y0
S00:000 S01:000 S02:043 S03:013 S04:010 S05:008 S06:002 S07:050 S08:002
S09:006 S10:014 S11:095 S12:050 S18:000 S25:005 S26:001 S30:000 S36:007
S37:000 S38:020 S43:009 S46:002 S48:007 S63:000 S82:128 S86:000 S95:000
S97:030 S108:1 S109:062 S110:2 S118:001 S119:1
Michael
…..on AutoPilot
Michael,
Thanks for the dump of your settings.
I currently have the software set for xON/xOFF. I'll try it out
CTS/RTS and get back here.
Thanks.
Joe,
I also have a PPI 14.4 and I know you must use a modem cable capable of
RTS-CTS as well as set your terminal's serial parameters to use RTS-CTS. In
the modem's default mode, RTS-RTS is on, not XON-XOFF, and I really doubt
that XON-XOFF could prevent flow-control-related errors from occuring –
especially at high-speed on a stock machine.
As a general rule, use only RTS-CTS. The basic init-string that works best
for me is: AT&F1
Joe,
A couple of things come to mind. First of all, make SURE that you have
your serial preferences set to use "Hardware Handshaking" (also known as
CTS/RTS handshaking). If your term programs have configuration options
for this (some do, others default to what Preferences is set to), make
sure that CTS/RTS is enabled there too. You will also need to be using a
7-wire (or more) serial cable from your amiga to your modem.
A second thing to watch out for is interference from _some_ hard disk
controller boards. You can try to download files to RAM: instead. Also,
downloading direct to floppy disk can cause real problems for high-speed
transfers, as it takes a long time to write the buffer to disk.
Remember that the stock 68000 is (in relative terms) fairly slow, and
that you really are pushing things to try to keep up with high-speed
transfers. There's little margin of error, so "little" things can cause
glitches. I would try to keep "background" programs to a minimum when
attempting to do a high-speed download.
Of course, an accellerator will also help, but I suspect that you don't
particularly want to hear that one. <grin>
Hope this helps…
– BobR
Bob,
Thanks.
I am currently running without an HD and I always download to RAM
anyway.
The CPU side of things is set at 19200, since I have heard (and
exper experienced) the 19200 limit.
To make life MORE interesting, I just got my 2.04 ROM installed
yesterday!
Joe
Joe,
I don't know what is causing your problem. I received my new PPI
14400FSXA modem last week. I unhooked my old modem, plugged the new one
in without making any changes at all in its defaults, and it is working
fine with CompuServe and with all three of the local boards I call. One
of these boards uses an old HST Dual Standard, and it gave me lots of
trouble when I first got my PPI 9600SA, but not a whimper with the new
FXSA.
If you are having problems with the modem, however, I suggest that you GO
PPIFORUM and ask for help there. PPI supports their products right here
on CIS, and they are VERY knowledgeable and helpful.
Betty,
Thanks. I know about the PPIFORUM already.
As for the trouble, I am having it on my local BBSes. One uses USR
Dual Standards, the other I don't know about.
Joe
Betty,
I just ordered my PPI 144000FXSA modem and should be receiving it shortly.
I couldn' use WHAP with my current AE internal modem, but will use it as
soon as the PPI modem arrives.
I'm also long overdue in upgrading my term program. I want to upgrade from
Access. I've basically heard about all the current PD/Shareware and
commercial term programs. To give me a headstart before I make my decision
are there any term programs that you could recommend to me, and any that I
should stay away from?
I'm looking for a top-of-the-line program with auto-log-on options,
without having to use Arexx. I know a few PD programs that don't allow
auto-log-on, or only allow it through Arexx.
Any suggestions?
Thanks.
Dom Fontana
P.S. I'd be interested in any one else's suggestions, too.
Wayne:
I use PicSaver… it will capture a screen, a window, or a user defined
area via a hot key… saves files out as .IFF's. I downloaded it from
AmigaUser, I think. Also, check out Khalid's SWITCHER (SWITCH.LZH) in lib
15 of AmigaUser.
Michael
…..on AutoPilot
DOM,
I use Whap! with Backtalk. Whap! can sign you on in interactive mode and
turn things over to BackTalk as soon as the signon is complete. BackTalk
also can make use of all the XPR protocols, so it can serve as a general
terminal for anywhere you might want to call.
I also use ATALKIII, which has a learn mode for learning logon scripts as
you call manually, but I've not used it that way.
Betty,
Thanks. I forgot, is Backtalk a commercial product? If so, who's the
manufacturer? Also, who makes ATALKIII?
Thanks.
Dom Fontana
Dom:
BackTalk was written by Don Curtis and Steve Ahlstrom. You'll find it in
Lib: 5… it is freely redistributable…. and a _great_, trouble free
program. Perfect for the interactve mode of Whap! (surprise <g>)
Michael
…..on AutoPilot
Thanks for the BackTalk info, Michael.
Dom Fontana
Dom –
> I'd be interested in any one else's suggestions, too.
One vote for JR-Comm 1.02a (Next version already in beta testing….)
. . . . . JimDoc
Jim,
Thanks for the suggestion. I had an earlier version of JR-Comm, but didn't
like it. They must have improved it.
Dom Fontana
Well, VLT, in it's latest revision will do that…. v5.517 is the latest —
I think…
Brian
– via Whap!
Brian,
I think your VLT message was meant for someone else, but I got it instead.
Dom Fontana
Oops…. I hope the guy looking for a comm program that does scripting w/o
ARexx saw it….
Brian
– via Whap!
Brian,
I'm the guy looking for a comm program that does scripting w/o ARexx. What
is it that you hope I saw?
Dom Fontana
Dominick, don't know if this was the question or not, but Online! has a
script language that is not ARexx dependent. The version I have was
practically written before ARexx was around, but still does the job for me.
Let me know if you have any q's about it.
–jp–seattle–
John,
Don't they have an Online! Platinum edition now?
Dom Fontana
That the latest version of VLT (5.517) does some scripting without ARexx.
Maybe enough for you to use. And what the heck, you already paid for it
-with your taxes!
Brian
– via Whap!
Joe,
Try the other suggestions mentioned in this thread (RTS/CTS set from
perferences, at least 19.k baud set from preferences, do no multitasking
while downloading, etc.). The problem is that the 68000 just doesn't have
the horsepower to keep up at 9600 much less 14.4k baud. The problem isn't
with your modem but with your computer's ability to take the data from
your serial buffer before it overflows (and you lose characters). If you
have a non-error correcting protocol you can use (ie, ymodem-g) try that
if the other modem is also a v.42 modem. You'll eliminate a layer of
(software) error checking with the protocol and let the modems handle the
error checking and retries as they were designed to. This just may give
you the extra "oomph" you need. As, with whatever term program you're
using, if they have an option of running in multiple colors, chose the
least amount (1 bitplane would be the best) — keep the system overhead
down as much as possible.
-sja
Steve,
Thanks for the reply.
I have been having this trouble when attempting ZModem xfers with
V32bis/V.42bis active.
Disabling all error correction and going only 9600 seems to work
fine, but at the reduced throughput.
Joe
Joe;
Your handshaking between the modem and the computer is probably not
working. Another thing can affect the performance and that is buffer
size. ZModem has "preferences" settings (different programs implement
this differently so you'll have to check the telcom program itself but you
can also create a set up file for ZModem "XPRZModem" in envarc: with a
line something like this:
TC,ON,B10,F0,E10,AY,DN,KY,SN,RN,PCDC:DOWN
Besure to change the default download path to the correct place (RAM
rather than DOWN?). The important term is the third one (B10). This sets
the buffer size. If you set this too big then AmigaDOS will ignore the
modem for too long a period of time when it tries to write out the buffer
and this can cause data loss (if handshaking is not working).
I am not convinced that C= has the serial.device working correctly yet.
-bill
Bill,
I've not had any problems with CBM's serial.device, but I'm not too sure
they've gotten the A2232 serial.device working correctly yet.
On a related subject, Supra still hasn't gotten their modem0.device
cleaned up yet either. For instance, with BackTalk's XPR implemenatation,
QB protocol works fine with the 1.6 version, does not work at all with
their 2.2 version.
-sja
Steve;
I have never owned anything by Supra and from the horror stories that my
dealer relays to me, I won't likely either.
-bill
Bill,
I have 2 (non-error correcting) Supra 2400s and 1 Supra ZI. The externals
work great. The internal works well also except for the not fully
functional modem0.device.
-sja
Steve,
It hasn't arrived yet, but is there a special cable I need for the PPI
14400FXSA modem? I'd like to buy the cable before the modem arrives.
Thanks.
Dom Fontana
Get a straight 25 pin cable.
Steve,
Wow, that was a fast response!
Thanks.
Dom Fontana
Dom:
CTS/RTS handshaking requires a full serial connection… when you get your
cable, be sure that it's not a cheap 3 wire serial cable. It must be a 7
wire cable (I believe that the other pins are just grounds).
Michael
…..on AutoPilot
Bill,
Thanks for the info.
I have tried both software (xON/xOFF) and hardware (CTS/RTS) handshaking
with no noticable difference.
I am using NComm 2.00 and it allows resizing the ZModem receive buffer
and I have it currently set to about 64K.
The default system serial buffer is temporarily set to 64K (via the
Serial preference program).
I might try playing with the ENVARC: XPR ZModem preference, but since I
just got the 2.0 ROM installed this week, I am only beginning to get used
to the differences with it.
I assume the BXX term means buffer size in K?
And that the last entry is for the default transfer path?
Thanks.
Joe Buckley
Joe;
Your assumptions are correct. I would suggest that 64 k is too large. I
did not explicitly try 64 k but 100 k was too large for me, ie: I
received occassional errors.
-bill
Bill (an everyone else who helped),
I have now arrived at a software set up that seems to work fine. I have
been able to download 300K files at 14.4Kbps carrier modulation with a
CPU-modem connection of 38.4Kbps (obviously with V.42bis compression
active) without problems.
I am using NComm and I have ZModem ACK active and a ZModem I/O buffer of
4KB. The default system serial buffer size has been changed to 4Kb as
well.
My guess is that the data isn't being flushed from the recieve buffer
until it is fairly full, and at only 7.12MHz, the 68000 can't move it all
before it drops things. A guess only!
Still, it now works, so I can't complain.
Thank you all for you suggestions.
Joe Buckley
Joe,
Your problem is either not setting your serial port for hardware
handshake (CTS/RTS) or having it set…and not having the proper serial
cable…one that carries the CTS/RTS lines thru.
I'm using a PM14400FXSA on my 2500 with NO problems whatsoever.
Don
Don (and the others!),
I have tried the software (NComm 2.00) with the handshaking set to
CTS/RTS to no changes.
I checked my cables and switch box. The cables carry pins 1-8, 11, and
20. The switchbox carries all 25 lines through.
If I disable error correction and log in at only 9600, there is no
trouble.
I have set the buffers to maximum, so it doesn't appear to be an
overflow problem.
For what appears to be a relatively common occurance, I'm surprised that
there is so little concurrence on the solution.
Joe Buckley
Joe,
Then I'd suggest the problem is with NComm. And since I don't use
it, I can't verify that. I do have a PM14400FXSA and I use it with
BackTalk (naturally) and it works just fine here on CIS.
Don
Don,
How amny CIS nodes run at a carrier of 14.4Kbps with V.42bis active?
I have no trouble on CIS, it is the high-speed connections I have
trouble with.
Joe Buckley
Joe,
None of the CIS nodes run at 14,400. They're "locked" at 9600bps.
Call PPI's BBS…that's what I did to test the 14,400 connection.
They're at 805.496.4445 (that's different than what's in the 14.4
manual since they moved after the manual was printed).
Don
Don,
I was originally worried that my problem was the modem, but I am now
leaning toward its being the software.
Seems like buffers being overflowed, but no one seems to know.
Joe Buckley
Joe,
Yes…I'd lean that way too. I notice that others are also
complaining of NComm's problems.
Don
Joe –
Under 1.3, 19200 may be too fast; the incoming data from the modem-to-modem
link may be over-running the Amiga's buffers. Try 9600.
Under 2.04, 19200 works. Like me, you need an accelerator to do everything
you want to….
. . . . . JimDoc
Jim,
I've heard that under 1.3, 19200 works fine, with minimum overhead in
the system. I now have 2.0 ROMs installed and 38400 now works fine.
The caveat being that I haven't tried too much actual 38400 data
transfer.
File transfers have generally been at carrier 14.4K and of compressed
files, so V.42bis has minimal, if any, effect.
I should try getting a friend with a similar modem to dump a huge text
file directly to me. Without the types of minor waits a BBS has between
messages in a continuous message dump.
Joe Buckley