CHATS: communications Messages: 8 Entries..

If for some unknown reason you want to see if the sodar 'ppp' link is up:

$ ifconfig

and look for something like this

ppp0      Link encap:Point-to-Point Protocol
          inet addr:192.168.13.1  P-t-P:192.168.20.20  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:11 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:815 (815.0 b)  TX bytes:133 (133.0 b)

at this time it'll be up roughly 20-min every odd hour, and is initiated
by the sodar side pc.

Also you can look in /var/log/messages to see if anything did go for
something like this:

May 18 13:04:48 aster mgetty[21177]: data dev=ttyS0, pid=21177, caller='none', conn='DIRECT', name='', cmd='/usr/sbin/pppd', u
ser='/AutoPPP/'
May 18 13:04:49 aster pppd[21177]: pppd 2.4.3 started by a_ppp, uid 0
May 18 13:04:49 aster pppd[21177]: Using interface ppp0
May 18 13:04:49 aster pppd[21177]: Connect: ppp0 <--> /dev/ttyS0
May 18 13:04:51 aster pppd[21177]: user isff_ppp logged in
May 18 13:04:51 aster pppd[21177]: PAP peer authentication succeeded for isff_ppp
May 18 13:04:51 aster pppd[21177]: local  IP address 192.168.13.1
May 18 13:04:51 aster pppd[21177]: remote IP address 192.168.20.20

Before I forget:

		Sodar		Repeater	Base
s/n		240-1951	240-1950	240-1946
mode		1=slave		4=reptr/slave	0=master
baud (ops)	115k (com1)	19.2k upper-ttyS20   115k (aster ttyS0)
baud (setup)

CallBook	0=1946		0=1946		0=1951
		1=1946via1950	1=1951		1=1951via1950
		2=1950				2=1950
	Use entry 1 for 'full-link' on either end.
	Use entry to 'repeater' to talk directly with it,
	and/or upper:/dev/ttyS20

Operational	Table=0, V1.62 (all are the same)

RadioCharacteristics (all are the same)
FreqKey		7
Maxpkt		8
Minpkt		9
xmit rate	1
data rate	3
power		9
etc.		0
etc		0
etc.		255
etc.		0

16:may07  10:50-13:30 and 15:15-16:15  Tower Climbed

Sodar Repeater put back up.
Discovered no power at top.
worked down to find no power at mid-level junction.
Taped connection had leaked and power pin was corroded away.
Installed new splice cable to ttyS20, upper, and confirmed
working at base.   Reclimbed later in day to rework the cables
and tape the new connections.   Left bad / gray cable on the
tower for now.   Put radio back at sodar, and both ends as far
as the freewaves are concerned are working.   Did not check
the sodar's pc.   When checking at the base later on, did not
see the ppp link running, nor anything in the system log,
but Gordon said to expect it'll only be up ~20min every 1-2 hours,
and it is initiated from the sodar side.

Scintillometer aligned.
I worked on it for awhile and then David took over (student in
charge of the instrument) and he, other student, Jan eventually
realigned it.   Uncertain but it may not have good signal because
the target is 'in the trees' despite being on their crankup tower.
Didn't ask them, just basing this on partially overheard conversation.
See their logs.

Sodar connection remains down as signal is insufficient. Additional tests will
be done during unsatisfactory winds during ops.

We lost communications to the 30m tower this afternoon.  After trying lots of
things (and it not being quite as high a priority as all the other stuff that
Keith just discussed), I just cycled power on the hub, which appears to have
gotten things working.  Unfortunately, we still have the 16% packet dropouts
which is causing Gordon to be unable to update the hotfilm acquisition code.
Thus, the triple-film probes probably still have the channel shift problem
but the singles on hfarray should now be running his new code.

Yesterday afternoon we started having network problems with hftower and it is
now mostly down.  I reseated many of the cables at about 1730 yesterday but
found no obvious problems.  Next steps would be swapping cables between 
hftower and upper and checking the cable itself going up the tower from
lower [with the hub] and hftower.  These will have to wait until tomorrow
when we can reenter the field.  Since hotfilms are all down, we aren't losing
data in the meantime.

What do you see for the value of the 802.11 signal strength at the
etherants?

When you point a browser at http://eantg  or http://eanta it will
display the signal strength.  There might be shortcuts to them at the
top of the firefox window.

BridgeA (horizontal array)
Signal = -46 dBm
SNR = 43 dB

BridgeG (tower)
Signal = -52 dBm
SNR = 22 dB

8mar07

Motosat working
	Established networking so Gordon can 'get in'

	Login to Motosat for adjustments:
	web browser to 192.168.1.1
	admin and pwd is .... (on aster pc there's a 'save' on it so
	you can get in, but otherwise we'll need to reset this)

	iss notes on this gizmo (some addressing is different)
	www.eol.ucar.edu/iss/SatelliteInternet

	Addresses:
	192.168.0.1	modem
	192.168.1.1	router lan
	192.168.0.2	router wan
	192.168.1.2	ASTER's eth2 interface that the motosat will
			fwd ssh's to.
			if you change this, use fedora-admin-network
			tool and restart the interface.

	
	
Initial 'wireless' working
	Still no power to array but a 'battery test' demo'd that the
	comms from base to array/tower is working a nominal.

	AP24 internal is on tripod next to base pointing under the
	trees to eant-A roughly 75' north of the array.  NOTE: this
	uses a 10m 'serial' cable extension (ie extra capacitance bad)
	to a ~40' cat5e cable.

	AP24 external antenna is on top of 5section pam mast roughly
	pointing to tall tower (180deg antenna)


Ping tests
	using
	ping -s 1048 -i .25 east
	ping -s 1048 -i .25 upper
	i saw over 15min. 0% loss with avg ~9mS per packet

	see: /etc/hosts on aster for ip addresses and for naming to
	ssh/ping such as:
	ping