Hi Tim and all other T2 (135) weather-APRSers, we run a station here in Germany with DR-135 / T2-135 / Peet 2100 combination.
http://aprs.fi/weather/DB0BIB?range=month As you can see, we also have peaks in our data (temperatures of 1000 degrees, peaks in pressure and precipation. If anybody finds out how to solve the problem, please give me a mail. We just went on air in the last weeks, as you can see. Still working on our rig. 73s de Mark, DL1GMC Am Samstag, den 10.04.2010, 07:33 -0500 schrieb Tim Cunningham: > > There seem to be a few issues with the T2-135. We have installed > several > Peet U2100 weather stations with he Alinco DR-135T and U2100 systems > in the > past month and I am running to a new installation this morning so I > have to > be quick. > > Make sure your cable to the weather station is good by verifying the > data is > coming out of the port. A poorly constructed cable or crimped > connector will > provide erroneous results in relation to the interval. We found this > by > simply wiggling the phone connecter on the side of the U2100 when data > was > intermittent and it started working. This is critical as a poor > connection > will yield erratic data interval output. We have one system that > simply > transmits bad data from the radio occasionally throughout the day. > One > reason is the code does not check to make sure the data is valid > before > transmission. We see non-printable characters in the output weather > packet > from time to time. This was more prevalent when the U2100 was in the > Data > Logging mode, but the Complete Record mode resolved many problems with > bad > data being transmitted. > > I wish the weather data could be programmed for interval separate from > the > position reports. Having a position report followed by a weather > packet > containing the same position report is redundant and adds extra > undesirable > loading to the network. > > Here are the settings from one site that doubles as a digi and it > works > quite well. WX data is transmitted on the INTERVAL setting > consistently. > > I am not intending to be critical by any means as the DR-135T and > T2-135 is > an awesome combination. There are just a few kinks. I modified the > code from > the WIKI link and verified a few conditions by reading a file > containing WX > data and observing the results and have become familiar with what > needs to > be changed. > > The most important settings are ABAUD/BBAUD and AMODE/BMODE for the > WX > settings. > > 1WIREWX OFF > ABAUD 2400 > ALIAS 1:WIDE 2:AL 3:TEMP 4:SAR > ALTITUDE OFF > AMODE AUTO > AUTOBAUD OFF > AUTOSAVE OFF > BBAUD 2400 > BMODE AUTO > CDINVERT OFF > CLIMB OFF > CNTRESET OFF > COMMENT /KN4CI > COMPRESS OFF > COUNTER OFF > CUSTSYM OFF > DAO OFF > DIGI ON > DIGIID 1:ON 2:ON 3:ON 4:ON 5:ON 6:ON 7:ON 8:ON > DUPETIME 30 > EXTSQL OFF > FAHRENHT OFF > GPSDATA OFF > HBAUD 1200 > HEADERLN OFF > HOPLIMIT 1:2 2:2 3:2 4:2 5:0 6:0 7:0 8:0 > INTERVAL 444 > LVINHIBIT 0 > MAXRANGE 0 > MONITOR OFF > MYCALL ESTLAW > NICE 0 > OUTPUT1 OFF > POSITION 3434.02N 08710.40W > POWER ON > PREEMPT 1:OFF 2:OFF 3:OFF 4:OFF 5:OFF 6:OFF 7:OFF 8:OFF > PTTINPUT OFF > PATH AL2-2 > QUIET 10 > REARM 250 > RETRIES 5 > RETRYTIME 7 > REQALL OFF > RING OFF > SHAREDPTT OFF > SLOT 16 > SMARTBCON OFF > SWDCD ON > STATUS 0 > SYMBOL /_ > TELEMETRY OFF > TEMP OFF > TEMPADJ 0 > TIMEHMS OFF > TIMESLOT ON > TIMESTAMP OFF > TXDELAY 30 > TXLEVEL 142 > TXNOFIX OFF > TXONCHG OFF > USEALIAS 1:ON 2:ON 3:ON 4:ON 5:OFF 6:OFF 7:OFF 8:OFF > VELOCITY OFF > VOLTAGE OFF > WAYPOINTS OFF > WPTLEN 9 > > Here are some tactical station calls you can check on FINDU that use > the > DR-135T / T2-135 / Peet U2100 combo: > > ESTLAW > MTHOPE > LAWEMA > HATSCH > HUBBRD > > Look for SPKSCH to come on line in a few hours. > > HUBBRD is the problem child with occasional bad data being > transmitted. We > need to investigate this problem a little closer to see what component > is > allowing it to happen. > > 73's, > > Tim - N8DEU > Decatur, Alabama, USA
