开云体育

Gentlemen, Your understanding of these issues is an order of magnitude beyond my own, but being ignorant of something never caused me to stop chiming it! I just wanted to point out a few things: The

Although the TELVOLTTWK has a resolution of 0.27v / bit, so you should be able to do the math and get it close in 1 shot (1.5 / 0.27 or 4 - 5 bits.? Since you said "almost", I set TELVOLTTWK 124 and

Thank you Robert! I am just using the ^V method, however I will turn on the telemetry option as well since it will likely produce a sexy graph in APRS.fi that is something I can check from anywhere

Thank you Rob. There seems to be issues with TT4 and PEET Brothers telemetry. I do have the weather packets going out now without the position. The system seems to ok with the format once time and

Sent from e-mail but did not seem to post. Yes, the MTT4BT voltage monitor is a simple voltage divider of 10k / 2.2k. So Vread = Vin * 2.2/12.2 or 0.180 Vin.? So reverse conversion would be Vread /

I don't know much about sending weather information using the Byonics products, so can't help there. BUT ...Looking through the configuration file? you attached to the original message for anything

Yes, the MTT4BT voltage monitor is a simple voltage divider of 10k / 2.2k.? So Vread = Vin * 2.2/12.2 or 0.180 Vin.? So reverse conversion would be Vread / 0.18.If the power source is limited in

sent over email, but did not seem to post. I don't know much about sending weather information using the Byonics products, so can't help there. BUT ... Looking through the configuration file? you

Good day, I've got two MTT4BT's deployed in Central BC as digi's. We're finding that the voltage they're reporting is off by more than a volt each. One, "TWOSIS" is low by about 1.5V most of the time,

I have made some progress... Path1 cannot be empty (null). Just putting anything in there caused expected behavior to happen in Proportional Pathing. Beacon Text: Beacon a message, bulletin or

Hey Bob, It is the middle of August. Any updates???? ///Paul

OMG, LOL, is that like HAM^2 ????? /// Paul

Hello. The Lakes Region Repeater Assoc. in NH has an MTT4 that I am trying to get to do all the above. Attached are the current settings. The goal is / was to use proportional pathing (PPATHING is

On serial DB-9 connectors, pins 7 & 8 are RTS and CTS, two flow control handshaking lines. Some serial cables short these together to bypass hardware handshaking. The TT4 uses pins 7 & 8 as the

I understand what the "intention" was of the default to Status Report, but software cannot read intent, just content.? So anything that doesn't fit something else is, by definition, a Status

The TT4 can be set to 5V TTL interface with jumpers.? If you didn't change the jumpers, then the TT4 is using RS232 level logic and will cause serious problems with the Pi. Some people have used a

Yes, anything manually typed into a TNC for transmission should at least be transmitted and we called that a default status packet. But this situation is different. It is not someone generating

Well, we call them "bad" or "bogus" packets, but the aprs101.pdf spec actually would classify them as "APRS Status Reports" and as such, IGate software is completely spec-compliant to be passing them

Hi John: I can't answer your question on TT4 integration as I have not tried that, but I have also dabbled with a home-brew wx station, and fought my share of integration battles. Regarding your

Insure that you do not have spaces in the hard coded latitude value. This will enable position ambiguity per the APRS spec. APRS.fi also supports optional position ambiguity.