| |
ZL3AI > APRDIG 08.06.03 11:09l 272 Lines 10784 Bytes #999 (0) @ WW
BID : 1447-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jun 03, 4/5
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<SP7MGD<VK7AX<VK3AC<ZL2BAU<ZL3VML
Sent: 030607/1336Z @:ZL3VML.#80.NZL.OC #:1870 [Chch-NZ] FBB7.00i $:1447-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Questions to the group
From: "Daron J. Wilson" <daron@wilson.org>
Date: Tue, 3 Jun 2003 13:35:21 -0700
X-Message-Number: 29
>My laptop is a Dell Inspiron 2500. 900mhz running Win ME (yeah I know some
>say its' unstable...but it came with the LT) I know my KPC3 and PK12 both
>work.
>I know the serial cable is good.
Well since a 9 pin serial connection may require anywhere from 3 to all
9 pins (depending on hardware implementation of the port and chosen
software) how do you know your serial cable is good? Just because it
talks to some device does not actually mean it will talk to all devices
(could be no hardware flow control on the first test, the second device
could be looking for hardware flow control). I would make sure the
cable checks out pin for pin according to the TNC's requirements, and
then probably turn all hardware flow control off anyway to see if it
works.
>Not even trying to use APRS yet, just to narrow the problem of he TNC not
>talking to
>Com1. I know that Com1 works because I have hooked my Garmin 12 to it and
>it works
>fine.
Based on that, you have ground and the receive pin, so that portion is
working.
>But for some reason the TNC's will not communicate. Thought perhaps
>maybe the
>fact that PacTerm is a DOS program it was not making the backard
>compatible
>trip and
>keeping contact with Com1. So I downloaded a demo version of PacTerm 1.71
>for Win
>and it was not able to find the TNC either. I hook the same cable/tnc to
>my
>old Dell P133
>laptop and it takes right off. I could use that for APRS but it is slow
>and
>does not have a
>built in CD drive.
Use the most simple basic comm program you can to start, probably
hyperterminal in your case. Make sure it is set to the proper baud,
parity, stopbits, bit length. Disable all the hardware and software
flow control in hyperterminal and start there. If it still doesn't
work, I'd try enabling hardware flow control since the TNC may be
looking for a particular pin to be held at one state before it will
transmit to the computer.
>So, first Question, Does anyone else own a Dell Inspiron or similar that
>has had the same
>problem and if you fixed it how? I call DELL and get connected to someone
>in a desert
>somewhere whom I can barely understand the broken English much less try
>and
>explain
>what a TNC is/does.
I don't think bothering dell will get you anywhere, sounds to me like it
is a configuration issue. Double check all settings, make the minimum
cable connections (ground, tx, rx) and see if works.
RS-232 - the worst implemented "standard" I know of, it can use anywhere
from 3 to 20 pins depending on how the engineer felt about implementation.
Good luck!
P.S. I have a Dell insprion 4000, use the serial port all the time for
programming equipment, I also carry and RS-232 breakout box that allows
me to fool either side into thinking they have control as well as
allowing me to force the state of any pin. It's a lifesaver.
73's N7HQR
----------------------------------------------------------------------
Subject: and in summary
From: "Daron J. Wilson" <daron@wilson.org>
Date: Tue, 3 Jun 2003 14:55:44 -0700
X-Message-Number: 30
The point to all of this is pretty simple.
1. Make sure everyone knows what it means to the network when you
transmit an emergency signal, it means there is immediate danger to
life/property and the nearest authorities WILL be notified and you WILL
be responsible for your transmission.
2. Do not program it in to some place that is easily activated by
mistake. Use some common sense, be very aware of what it takes to
activate it, and take appropriate precautions. I should be the same as
the voice equivalent MAYDAY, or activating an ELT/EPIRB and it should be
treated with that reverence. You are the control operator right?
I too have done SAR work for years, many of them as a professional, many
as a volunteer. If your plan is really to have responders on their own
with APRS for their only reliable means of identification and
communications....you need a better plan.
73's N7HQR
----------------------------------------------------------------------
Subject: Re: Questions to the group
From: "Dave Thege" <dthege@ncfcomm.com>
Date: Tue, 3 Jun 2003 17:12:30 -0500
X-Message-Number: 31
Did you ck the baud rate? That will cause a tnc to not talk to your
computer.
Dave N0XBN
----------------------------------------------------------------------
Subject: PCsat<=>PCSAT2 joint sat test success.
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 3 Jun 2003 18:46:51 -0400 (EDT)
X-Message-Number: 32
PCsat <=> PCSAT2 constellation test sucess.
Today we rolled the PCSAT2 (fully coinfigured flight prototype) out onto
the Plaza for the 1210z pass of PCsat for a dual-satellite constellation
test. Since PCSAT2 was in its normal flight configuration (but sitting on
the ground), this would demonstrate the range over which the two
spacecraft could communicate on orbit between their whip antennas. The
results were excellent!
PCSAT2 was set to transmit a packet via PCsat once every 20 seconds.
Both birds on 145.825 MHz. These packets normally compete with other user
packets (The channel is contention based so 100% is never expeceted).
But a success means that the two spacecraft can comunicate over that
range. There were 7 other spacecraft users at the time.
TIME AZ EL RANGE Comments
-------- --- -- ------- ------------------------------------
08:10:18 Finished commanding PCsat into proper mode for test
08:10:29 107 49 1024 km Success
08:10:49 095 48 1040 km not heard
08:11:05 087 46 1066 km Success
08:11:25 078 43 1112 km not heard
08:11:45 070 39 1173 km Success
08:12:05 064 36 1246 km not heard
08:12:25 059 32 1329 km Success
08:12:45 055 29 1420 km Success
08:13:05 051 26 1510 km not heard
08:13:24 049 23 1616 km not heard. Blocked by RIckover Bldg
THen it rained again. We have been waiting to do this test for almost 2
weeks. So we don't know if the ultimate range was about 1500 km or
whether we could have heard more if the building had not intervened. There
was no success before the time shown, as that time was spent commanding
PCsat to the proper mode... We wont get to test again for at least 2
weeks.
We hope others that are building small AX.25 packet satellites will
consider including a TNC digipeater on 145.825 to add to this Amateur
Satellite constellation.
PCSAT2's July launch has been delayed by the Shuttle problem to
January.
Bob
http://www.ew.usna.edu/~bruninga/pcsat2.html
----------------------------------------------------------------------
Subject: RE: PCsat<=>PCSAT2 joint sat test success.
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Tue, 3 Jun 2003 23:07:12 -0000
X-Message-Number: 33
Bob, what does this get us? Is it just to extend the effective footprint?
Do you have any analysis of how often the birds will be able to hear each
other? I just did a quick check and it looks like ISS's footprint is about
1,000 miles less than PCSAT, but it's still about 2,700 miles. ISS has an
orbital inclination of about 51 degrees - will PCSAT ever see it from the
poles?
Maybe I'll run a quick scenario in STK to show access opportunities. I'd
make a nice animation, but I think my license for the visualization module
has expired.
Scott
N1VG
----------------------------------------------------------------------
Subject: Re: Questions to the group
From: "Mark Fellhauer" <sparkfel@qwest.net>
Date: Tue, 03 Jun 2003 19:18:51 -0500
X-Message-Number: 34
Depending on your hardware, DOS programs will not be able to access a com
port under Windows unless you add a statement into an autoexec.bat file
like:
mode com1: 19200,n,8,1
You will probably need to modify the baud rate - in this case 19200, to
whatever baud rate your TNC is set to. This must also match your DOS
program. I won't go into advanced stuff like dosstart.bat, because it's
obvious you're having more basic problems...
Obviously, Microsoft tried to pull Real-Mode DOS support starting with ME,
so I'm not sure if the IO.SYS even processes autoexec.bat or config.sys
files, but it should read environment variables. I don't have a machine
win ME around here so I can't test it myself. There are a number of hacks
to reinstate Real DOS Mode to ME if it doesn't work.
>So I downloaded a demo version of PacTerm 1.71 for Win
>and it was not able to find the TNC either. I hook the same cable/tnc to
>my old Dell P133
>laptop and it takes right off. I could use that for APRS but it is slow
>and does not have a
>built in CD drive.
If the GPS works in Windows ME on the serial port, how are you determining
that? What program are you using? If it's a terminal program that shows
raw NMEA data, you should also be able to see something coming from the TNC
with the same program...
I would go into Hyperterminal - set in for 4800 8,N,1 on whatever com port
is active, do a hard reset on the TNC, and press "*" to get it set to the
right baud.
>So, first Question, Does anyone else own a Dell Inspiron or similar that
>has had the same
>problem and if you fixed it how? I call DELL and get connected to someone
>in a desert
>somewhere whom I can barely understand the broken English much less try
>and explain
>what a TNC is/does.
Dell outsourced it's Toll-Free Technical Telephone Support to India (to a
company called Client Outsource that was started by two former Dell
employees). I suggest everyone who owns a Dell write a letter (not email)
with an ATTN: to Michael Dell, Kevin B. Rollins, or the Dell Board of
Directors. Let them know in a concise professional manner that you are not
happy with their decision to OUTSOURCE technical support to people who are
not fluent in English. Let them know the decision is unacceptable and
that it will negatively influence any decision you have to purchase a Dell
Computer in the future.
The last two times I called Dell on warrantee support, I was connected to
people who could speak English about as well as I speak Hindi, and both
times they used this to try and deny replacing defective parts under the
terms of Dell's warrantee...
BTW, technical support provided by Computer OEM's only relates to issues of
hardware or software addressed under the terms of the warrantee and to
products provided or sold by that company. If you call Dell with a problem
related to a 3rd party product, they will refer you to the maker of that
product. In some cases they can help you with aftermarket hardware or
software on a PAY-FOR basis, but I doubt they would touch a TNC.
Regards,
Mark
KC7BXS
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
