Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- TinyTrak
- Messages
Search
|
Re: TT4TrackerConfig software.?
Thanks.? I was wondering, as I am resurrecting an old TT4 (2012-ish?) and TinyTrak4 Alpha Config v0.68 is what I used at the time.?
Are there any issues using it with the v0.72 firmware? (I flashed the TT4 a few days ago and am trying it with YAAC).? Also, where on the Byonics site are they hiding the config software - I found the TT3 config software, but can't locate a current copy for the TT4, glad I hung onto the earlier copy (storage is cheap).? Plan B would be one command at a time using TeraTerm or Putty.?? 73 Steve KS1G |
|
Re: MTT4BT Digipeater, weather station, Beacon, and Message issues....
There is provision for a local time stamp tht indicates it is not real-time
toggle quoted message
Show quoted text
but CPU clock time. I instead of ending with DDHHMMz it ends (I think) with HHMMSSh from the last time the CPU was started. THe "h" indicates it is CPU time. (Alll this from memory since I dont have the energy to look it up). In any case the original post was correct in that time stamps should usually be ignored in systematic use and the TIME OF RECEPIT should be used for accuracy. Bob, WB4APR (forgetting a lot these days)... On Wed, Aug 25, 2021 at 11:46 AM AC1DW <KC1HEP@...> wrote:
|
|
Re: MT4BB Voltage Accuracy
If the TVOLTTWK adjusts the reading by 27mV, it implies an offset (not a gain change). That was why I asked the question. Next point: As I read the TT4 firmware manual, the telemetry output is either 255 (8-bit) or rescaled (in firmware) to 999 bits FS, not true 10-bits because the protocol only allows 3 digits in the message.? So on TELHIRES TRUE, the reported value at 5V would be 999, not 1023 (or 1024). Enables sending of high resolution telemetry data. If false, telemetry reports range fromAlthough between 999 and 1023 would probably be very high battery voltages: ??? 999 / 1023 * 5 / 0.18 = 27.13 to 27.78 Volts, so I guess it could be truncated. Robert Giuliano
On Wednesday, August 25, 2021, 08:40:06 AM EDT, AC1DW <kc1hep@...> wrote:
Rob, you really get me going with your posts. Thank you. What we know: Vin is voltage divided: 2.2/12.2 = 0.180 Vin has diode protection dropping it ~0.2 V Vadc = 0.180*(Vin-0.2) = Vin*0.180 - 0.036 The Atmega ADCs are 10 bit with programmable gains of x1, x10, x200 bits = 1024/5*Vadc (0.00488 Volt/bit) [999*0.00488=4.878 or a -2.5% FS error) ?????? divide by 4 (255 bits or 0.0195 Volt/bit) is simply dropping the last two bits. (bit shift) Combining the above I get: bits*5/(0.18*1024)+0.2 = Vin or bits*0.0271+0.2 = Vin I think "the TELVOLTTWK has a resolution of 0.27v / bit," is a typo. I am guessing it is 27mV/bit. Your "bits + (128 - TVOLTTWK)" is probably the correct answer. I don't have a TT4 here to test this out. Thoughts? btu, AC1DW PS> So I went to the TT4 firmware manual to see where the 0.27V/bit came from. ???????? Yup; typo. From the manual "Default is 128 and each adjustment unit up or down will tweak the reading by 27mV" ???????? But I had fun reverse engineering it just the same. |
|
Re: MTT4BT Digipeater, weather station, Beacon, and Message issues....
Any system that does not have an active GPS should not use an APRS
toggle quoted message
Show quoted text
protocol that includes a time stamp. There should be a non-time-stamp version of every packet type. (I hope) Bob, WB4APR On Wed, Aug 25, 2021 at 2:21 AM Gil Smith <tinytrak@...> wrote:
|
|
Re: MT4BB Voltage Accuracy
Rob, you really get me going with your posts. Thank you.
What we know: Vin is voltage divided: 2.2/12.2 = 0.180 Vin has diode protection dropping it ~0.2 V Vadc = 0.180*(Vin-0.2) = Vin*0.180 - 0.036 The Atmega ADCs are 10 bit with programmable gains of x1, x10, x200 bits = 1024/5*Vadc (0.00488 Volt/bit) [999*0.00488=4.878 or a -2.5% FS error) ?????? divide by 4 (255 bits or 0.0195 Volt/bit) is simply dropping the last two bits. (bit shift) Combining the above I get: bits*5/(0.18*1024)+0.2 = Vin or bits*0.0271+0.2 = Vin I think "the TELVOLTTWK has a resolution of 0.27v / bit," is a typo. I am guessing it is 27mV/bit. Your "bits + (128 - TVOLTTWK)" is probably the correct answer. I don't have a TT4 here to test this out. Thoughts? btu, AC1DW PS> So I went to the TT4 firmware manual to see where the 0.27V/bit came from. ???????? Yup; typo. From the manual "Default is 128 and each adjustment unit up or down will tweak the reading by 27mV" ???????? But I had fun reverse engineering it just the same. |
|
Re: MTT4BT Digipeater, weather station, Beacon, and Message issues....
Gil, that is what I read too.?
Rob, the PEET data has a date (MM/dd) and time (hh:mm) in the packet it sends (data or packet modes). The TT4 is decoding like this is a leap year. It is a day behind now. Don't know what January would look like though.?? I'm going to do a reset to factory defaults and start from there. I haven't been able to recreate some of the anomalies I've observed. One being; when both ports were in TEXT mode, the decoded received packets were being transmitted as "UI" input.? 2021-08-22 13:34:02 >APTT4,WIDE2-1,NH4-4,qAR,:W1IMD>APN391:!4350.15NS07049.05W#PHG3464 |
|
Re: MTT4BT Digipeater, weather station, Beacon, and Message issues....
Some time back I corresponded with a fellow in the aprs-is (group/provider...?) system when I was formatting wx packets to be posted via the net.? I recall something about the aprs-is system ignoring times in packets and adding a real timestamp when packets arrived -- something about them not trusting any other times given to them, since they would often be bogus (or just off, as in the case of a battery-backed rtc or such).? Makes sense to me.? I was sending incorrect times in packets when I was first playing around, those incorrect timestamps were ignored by the system.? I would guess that the radio side of aprs would do the same thing as those packets get added to the system. ----- Original message ----- From: "Rob Giuliano via groups.io" <kb8rco=[email protected]> Subject: Re: [TinyTrak] MTT4BT Digipeater, weather station, Beacon, and Message issues.... Date: Tuesday, August 24, 2021 4:27 PM You have a TEXT port and a PEET port, so no GPS port. I am curious how the MTT4BT gets a time and date with no GPS attached? As far as I can tell, there is no RTC and no means of setting the time. The timing appears to be either from delta time between TX, or time from the GPS. I cannot say I've ever investigated this, but I see 3 scenarios: 1. No GPS.? Assume poackets sent without timestamp 2. With GPS -> GPS provide time 3. Start with GPS attached, then remove GP.? ??? Does the MTT4BT keep time from last acquired information - that would likely get out of date fairly quickly. Robert Giuliano KB8RCO |
|
Re: MT4BB Voltage Accuracy
Although I understand these are just "indicators", I would have guessed the resistors would be 5% or 1% (typically not a big cost hit). I always wondered how the TVOLTTWK value worked.? Is it an offset or a gain? ???? Gain:??? bits / (TVOLTTWK * 2) *5 /0.18 ?? Offset:??? bits + (128 - TVOLTTWK) /255 *5 /0.18?????????????????????????? (I used 255 since max ADC value is 255 at 5V) The gain would be more of a compensation of resistor tolerances. The offset would be 0.11 V per bit. Neither formula gives a 0.27V per bit delta. ??? Voltage with TELREAD TRUE???? 0,0.100,0????????(0x^2 + 0.100x + 0)?? so if x=131 => 0 + 13.10 + 0 = 13.10 Volts ??? Voltage with TELHIRES FALSE?? 0,0.109,0 ?????? (0x^2 + 0.109x + 0) ?? so x = 120 => 0 + 13.08 + 0 = 13.08 Volts ??? ??? Voltage with TELHIRES TRUE??? 0,0.005,0 ??????? (0x^2 + 0.005x + 0) ?? so x = 471 => 0 + 13.08 + 0 = 13.96 Volts ?? Where 'x' is the value reported in the telemetry packet.? NOTE: with TELREAD TRUE, this is not the ADC value. ? Otherwise, it depends on the TELHIRES setting.? Robert Giuliano
On Tuesday, August 24, 2021, 12:01:40 PM EDT, vhsproducts via groups.io <vhsproducts@...> wrote:
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 Voltage Sampling on the MTT4BT is as Robert pointed out, derived from the 10K and 2.2K Voltage divider. Note please that these are 10% value resistors, and you might do well to keep that in mind when estimating derived values. ( I am not sure what the tolerance of the resistors used in the standard TT4) Also, keep in mind that the Voltage sample is taken AFTER the polarity protection series input diode. In every version of the MTT4BT, this is a Schottky Diode, and you will see nominally .20 Volts of drop on the sampling part of the circuit. Although this may not be idea for Voltage Telemetry, is does keep the TT4 chip from being blown to smithereens by transient reverse polarity power supplies or plain old accidents. As Bob supposes, I discussed the issue of when sampling occurs with Byon some years ago, and I believe that the Voltage and Temperature values are both read immediately before a scheduled transmission. Both values are essentially derived from an analog Voltage of 0-5 Volts from Voltage dividers. In the case of the temperature sensor, that's an LM335Z biased with a 2.2K resistor.?
Somewhere in my notes is a explanation of how to modify the EQNS values to trim up these values, but if you figure it out, you would do us all a great service in posting it!?
73,
Allen AF6OF
( The Micro-Trak hardware guy)? -----Original Message-----
From: Rob Giuliano via groups.io <kb8rco@...> To: [email protected] <[email protected]> Sent: Tue, Aug 24, 2021 5:17 am Subject: Re: [TinyTrak] MT4BB Voltage Accuracy 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 see what happens.
As for sending the voltage in Telemetry packets, you may have to change the coefficients, depending on your settings of TELREAD and/or TELHIRES.
Post questions, and we can help sort that out if needed.? First step is to get the voltage read properly.
Good luck!
Robert Giuliano
KB8RCO
On Tuesday, August 24, 2021, 12:42:48 AM EDT, Bob Holowenko <holowenko@...> wrote:
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 instead of the private Cacti instance ingesting APRS-IS packets and slicing them in perl....It's not pretty.
The current source is roughly 2000Ah of batteries?and is not significantly restricted. We only see a drop of a few 10ths of a V under transmit. When we measured the voltage we checked it at the source (actually a fused bus bar) with the unit powered up, and again at the DIN connector with the unit not powered. Neither showed any voltage differential.?
My assumption is that the AtoD reads the result of the divider, does the math mentioned above, and turns that into a V string, stuffs that into the packet, THEN transmits that packet it crafted in memory. I would only expect the V to drop at the DIN connector under TX load and cause low voltage as that's the least surface area contact in the power rail, HOWEVER, it should not matter as I suspect the sampling happens pre-PTT activity.
I will certainly play with the "TVOLTTWK" command and see if I can tighten it up again. I am perfectly fine with the lower-res power readings, as I really only care to the tenth of a volt anyway.?
Cheers,
Bob Holowenko B.Tech & ASC (Computer Forensics), Dipl Technical Studies, CCNA CCNP ASC? Quesnel Search and Rescue Society, Director? On Mon, Aug 23, 2021 at 1:38 PM Rob Giuliano via <kb8rco=[email protected]> wrote:
|
|
Re: MTT4BT Digipeater, weather station, Beacon, and Message issues....
You have a TEXT port and a PEET port, so no GPS port. I am curious how the MTT4BT gets a time and date with no GPS attached? As far as I can tell, there is no RTC and no means of setting the time. The timing appears to be either from delta time between TX, or time from the GPS. I cannot say I've ever investigated this, but I see 3 scenarios: 1. No GPS.? Assume poackets sent without timestamp 2. With GPS -> GPS provide time 3. Start with GPS attached, then remove GP.? ??? Does the MTT4BT keep time from last acquired information - that would likely get out of date fairly quickly. KB8RCO |
|
Re: MT4BB Voltage Accuracy
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 Voltage Sampling on the MTT4BT is as Robert pointed out, derived from the 10K and 2.2K Voltage divider. Note please that these are 10% value resistors, and you might do well to keep that in mind when estimating derived values. ( I am not sure what the tolerance of the resistors used in the standard TT4) Also, keep in mind that the Voltage sample is taken AFTER the polarity protection series input diode. In every version of the MTT4BT, this is a Schottky Diode, and you will see nominally .20 Volts of drop on the sampling part of the circuit. Although this may not be idea for Voltage Telemetry, is does keep the TT4 chip from being blown to smithereens by transient reverse polarity power supplies or plain old accidents. As Bob supposes, I discussed the issue of when sampling occurs with Byon some years ago, and I believe that the Voltage and Temperature values are both read immediately before a scheduled transmission. Both values are essentially derived from an analog Voltage of 0-5 Volts from Voltage dividers. In the case of the temperature sensor, that's an LM335Z biased with a 2.2K resistor.?
Somewhere in my notes is a explanation of how to modify the EQNS values to trim up these values, but if you figure it out, you would do us all a great service in posting it!?
73,
Allen AF6OF
( The Micro-Trak hardware guy)? -----Original Message-----
From: Rob Giuliano via groups.io <kb8rco@...> To: [email protected] <[email protected]> Sent: Tue, Aug 24, 2021 5:17 am Subject: Re: [TinyTrak] MT4BB Voltage Accuracy 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 see what happens.
As for sending the voltage in Telemetry packets, you may have to change the coefficients, depending on your settings of TELREAD and/or TELHIRES.
Post questions, and we can help sort that out if needed.? First step is to get the voltage read properly.
Good luck!
Robert Giuliano
KB8RCO
On Tuesday, August 24, 2021, 12:42:48 AM EDT, Bob Holowenko <holowenko@...> wrote:
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 instead of the private Cacti instance ingesting APRS-IS packets and slicing them in perl....It's not pretty.
The current source is roughly 2000Ah of batteries?and is not significantly restricted. We only see a drop of a few 10ths of a V under transmit. When we measured the voltage we checked it at the source (actually a fused bus bar) with the unit powered up, and again at the DIN connector with the unit not powered. Neither showed any voltage differential.?
My assumption is that the AtoD reads the result of the divider, does the math mentioned above, and turns that into a V string, stuffs that into the packet, THEN transmits that packet it crafted in memory. I would only expect the V to drop at the DIN connector under TX load and cause low voltage as that's the least surface area contact in the power rail, HOWEVER, it should not matter as I suspect the sampling happens pre-PTT activity.
I will certainly play with the "TVOLTTWK" command and see if I can tighten it up again. I am perfectly fine with the lower-res power readings, as I really only care to the tenth of a volt anyway.?
Cheers,
Bob Holowenko B.Tech & ASC (Computer Forensics), Dipl Technical Studies, CCNA CCNP ASC? Quesnel Search and Rescue Society, Director? On Mon, Aug 23, 2021 at 1:38 PM Rob Giuliano via <kb8rco=[email protected]> wrote:
|
|
Re: MT4BB Voltage Accuracy
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 see what happens. As for sending the voltage in Telemetry packets, you may have to change the coefficients, depending on your settings of TELREAD and/or TELHIRES. Post questions, and we can help sort that out if needed.? First step is to get the voltage read properly. Good luck! Robert Giuliano
On Tuesday, August 24, 2021, 12:42:48 AM EDT, Bob Holowenko <holowenko@...> wrote:
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 instead of the private Cacti instance ingesting APRS-IS packets and slicing them in perl....It's not pretty. The current source is roughly 2000Ah of batteries?and is not significantly restricted. We only see a drop of a few 10ths of a V under transmit. When we measured the voltage we checked it at the source (actually a fused bus bar) with the unit powered up, and again at the DIN connector with the unit not powered. Neither showed any voltage differential.? My assumption is that the AtoD reads the result of the divider, does the math mentioned above, and turns that into a V string, stuffs that into the packet, THEN transmits that packet it crafted in memory. I would only expect the V to drop at the DIN connector under TX load and cause low voltage as that's the least surface area contact in the power rail, HOWEVER, it should not matter as I suspect the sampling happens pre-PTT activity. I will certainly play with the "TVOLTTWK" command and see if I can tighten it up again. I am perfectly fine with the lower-res power readings, as I really only care to the tenth of a volt anyway.? Cheers, Bob Holowenko B.Tech & ASC (Computer Forensics), Dipl Technical Studies, CCNA CCNP ASC? Quesnel Search and Rescue Society, Director? On Mon, Aug 23, 2021 at 1:38 PM Rob Giuliano via <kb8rco=[email protected]> wrote:
|
|
Re: MT4BB Voltage Accuracy
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 instead of the private Cacti instance ingesting APRS-IS packets and slicing them in perl....It's not pretty. The current source is roughly 2000Ah of batteries?and is not significantly restricted. We only see a drop of a few 10ths of a V under transmit. When we measured the voltage we checked it at the source (actually a fused bus bar) with the unit powered up, and again at the DIN connector with the unit not powered. Neither showed any voltage differential.? My assumption is that the AtoD reads the result of the divider, does the math mentioned above, and turns that into a V string, stuffs that into the packet, THEN transmits that packet it crafted in memory. I would only expect the V to drop at the DIN connector under TX load and cause low voltage as that's the least surface area contact in the power rail, HOWEVER, it should not matter as I suspect the sampling happens pre-PTT activity. I will certainly play with the "TVOLTTWK" command and see if I can tighten it up again. I am perfectly fine with the lower-res power readings, as I really only care to the tenth of a volt anyway.? Cheers, Bob Holowenko B.Tech & ASC (Computer Forensics), Dipl Technical Studies, CCNA CCNP ASC? Quesnel Search and Rescue Society, Director? On Mon, Aug 23, 2021 at 1:38 PM Rob Giuliano via <kb8rco=[email protected]> wrote:
|
|
Re: MTT4BT Digipeater, weather station, Beacon, and Message issues....
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 date is inserted. The TT4 doesn't decode the day correctly though. They are showing a day behind. (8/22 instead of 8/23). Guess not a big deal since time is dropped in those packets at the iGate. Funny though, is that my time in the packet is more correct than what ever system is putting the time stamp on the data. Thank you for the PREEMPT explaination. The online information and manual wasn't clear enough for me to try it. I will be using. Yes, I did finally see/realize the SS should be NH. If I use PREEMPT and an alias1 of NH, would I digipeat any NHn-N and decrement correctly? Would a NHn* NOT be digipeated? I have changed my alias-list to: alias1 is NH (We want to be sure NH message get around the mountains.) alias2 is WIDE2 and set PREEMPT is TRUE. Thank you for chiming in. AC1DW |
|
Re: MT4BB Voltage Accuracy
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 / 0.18.
If the power source is limited in current, the voltage will drop on TX.?
? You should check (compare) the volyage readings when the MTT4BT transmits.
?
Check TVOLTTWK for adjusting.
???? Allows the supply voltage sensor reading to be adjusted. Default is 128 and each
???? adjustment unit up or down will tweak the reading by 27mV ?
You don't say how you are reviewing the voltage:
?
?? 1. Direct reading value in beacon using ^V????????? This allows direct reading of the voltage in volts (with decimal)
?
?? 2. Telemetry Data (format is important)??????????????? This depends on other settings to convert.
?????? TELHIRES {true or false}? ????????????????????????????? TRUE means 0 - 999 rather than 0 - 255
?????? TELEVOLT {true or false}? ????????????????????????????? TRUE means this data is included in a telemetry packet in either 'Volts' or 'bits'
?????? TELREAD {true or false}? ?????????????????????????????? TRUE 131 is 13.1 Volts in the telemetry packet (TELEHIRES doesn't matter)?
?
EXAMPLE:
?? TELEVOLT TRUE??????? Data shows 131 so Vin is read as 13.1V? use TVOLTTWK to adjust to match reality
?? TELHIREAS FALSE ??? Data shows 120 so Vin = 120/255 * 5 / 0.18 = 13.072 Volts |
|
Re: MTT4BT Digipeater, weather station, Beacon, and Message issues....
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 obvious that I could spot, there are a lot of other settings that should be investigated: The ALIAS setting are used for what the TT4 will DIGI ????ALIAS1 TEMP ????ALIAS2 WIDE ????ALIAS3 SS2 These appear to be some kind of default, especially SS2? ??? SS is typically an abbreviation for your 2 character state code and the 2 would limit the TT4 ???????? to DIGI only paths with first element of 2 (SS2-2 and SS2-1). ???????? In your case, it appears it would be NH2 (not SS2) ??? I am not a fan of TEMP, but it may be in use in your area. ??? I prefer to limit my ALIASes (as you have done on the SS) by giving them a number. ??????? The down side to this is that it requires more ALIASes to cover a setting. ??????? PREEMPT TRUE can help with that. You should check with any local APRS groups on what is used in your area. My recommendation would be: ????ALIAS1 TEMP2 ????ALIAS2 WIDE2 ????ALIAS3 NH2 ??? PREEMPT TRUE That is if you want to DIGI TEMP paths.? This limits them to 2 settings, but PREEMPT means it will DIGI the packet if TEMP2, WIDE2, or NH2 are anywhere in the path. As you stated, PATH elements need to be used in order.? If you only use one path element, it needs to be in PATH1. Robert Giuliano
On Monday, August 23, 2021, 11:00:29 AM EDT, AC1DW <kc1hep@...> wrote:
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 announcement; I had to add the ":BLNx???? :" address block. Not many characters after that are left. Weather is still an issue. The MTT4 does not like to stay in contact with the PEET Brothers output. Even with power cycling the weather w/ position packet doesn't like to stay connected. 2021-08-23 10:40:49 EDT: >APTT4,qAR,:!4341.89N/07109.20W_.../...g003t...r...p...P000h..b.....TU2k If I try to send a weather w/o position, APRS.fi complains that it doesn't support the weather format. 2021-08-22 14:11:23 EDT: >APTT4,qAR,:_........c...s...g...t...r...p...P...h..b.....TU2k [Unsupported weather format] Neither of the above have data, but only the one is 'accepted'. The Ultimeter 100 in data logger mode feds this into the MTT4: !!0059000702A0060B----------------00E9032F00010027 But at about 2 per second. I don't want to take down the local network. :o? But it is an acceptable packet. Didn't have time to really test it yesterday to see if the weather was being decoded by APRS.fi or local radios. In Packet Mode the follow is outputted every five minutes: $ULTW00B2000402A2060C----000086A00001----00E9034300020032 APRS.fi accepts this fine too. In both cases, I put port B to TEXT mode. But it appeared that received packets were being sent to the Ultimeter and the ultimeter was in full duplex. Ergo, all received packets were being sent again as UI packets. OOPS. I see DeafText now and think that might be better for port B. Two questions still remain; why doesn't Weather without position work and why does the TT4 not stay in communication with the PEET Data Logger Mode? //AC1DW |
|
Re: MT4BB Voltage Accuracy
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 current, the voltage will drop on TX.? ? You should check (compare) the volyage readings when the MTT4BT transmits. Check TVOLTTWK for adjusting. ???? Allows the supply voltage sensor reading to be adjusted. Default is 128 and each ???? adjustment unit up or down will tweak the reading by 27mV You don't say how you are reviewing the voltage: ?? 1. Direct reading value in beacon using ^V????????? This allows direct reading of the voltage in volts (with decimal) ?? 2. Telemetry Data (format is important)??????????????? This depends on other settings to convert. ?????? TELHIRES {true or false}? ????????????????????????????? TRUE means 0 - 999 rather than 0 - 255 ?????? TELEVOLT {true or false}? ????????????????????????????? TRUE means this data is included in a telemetry packet in either 'Volts' or 'bits' ?????? TELREAD {true or false}? ?????????????????????????????? TRUE 131 is 13.1 Volts in the telemetry packet (TELEHIRES doesn't matter)EXAMPLE: ?? TELEVOLT TRUE??????? Data shows 131 so Vin is read as 13.1V? use TVOLTTWK to adjust to match reality ?? TELHIREAS FALSE ??? Data shows 120 so Vin = 120/255 * 5 / 0.18 = 13.072 Volts?? TELHIREAS TRUE????? Data shows 471 so Vin = 471/999 * 5 / 0.18 = 13.096 Volts Yes, the Robert Giuliano
On Monday, August 23, 2021, 12:05:04 PM EDT, Bob Holowenko <holowenko@...> wrote:
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, and "FISHPT" is about 1.1V low. The issue is that this number is not linear. It seems that when compared to a trusted Fluke meter at the source (power distribution bus bars) it's showing low, and we have even tested to see if the short lead is causing a voltage drop, but without the load of the MTT4BT it's the same as at the power distribution. The schematic in the document is incredibly grainy, but I presume it's just an AtoD input on a voltage divider, being fed into a simple equation to figure out the volt equivalent. Any suggestions on how we can improve accuracy? |
|
Re: MTT4BT Digipeater, weather station, Beacon, and Message issues....
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 attached to the original message for anything obvious that I could spot, there are a lot of other settings that should be investigated:
The ALIAS setting are used for what the TT4 will DIGI
????ALIAS1 TEMP
????ALIAS2 WIDE
????ALIAS3 SS2
These appear to be some kind of default, especially SS2?
??? SS is typically an abbreviation for your 2 character state code and the 2 would limit the TT4
???????? to DIGI only paths with first element of 2 (SS2-2 and SS2-1).
???????? In your case, it appears it would be NH2 (not SS2)
??? I am not a fan of TEMP, but it may be in use in your area.
??? I prefer to limit my ALIASes (as you have done on the SS) by giving them a number.
??????? The down side to this is that it requires more ALIASes to cover a setting.
??????? PREEMPT TRUE can help with that.
You should check with any local APRS groups on what is used in your area.
My recommendation would be:
????ALIAS1 TEMP2
????ALIAS2 WIDE2
????ALIAS3 NH2
??? PREEMPT TRUE
That is if you want to DIGI TEMP paths.? This limits them to 2 settings, but PREEMPT means it will DIGI the packet if TEMP2, WIDE2, or NH2 are anywhere in the path.
?
As you stated, PATH elements need to be used in order.? If you only use one path element, it needs to be in PATH1. |
|
MT4BB Voltage Accuracy
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, and "FISHPT" is about 1.1V low. The issue is that this number is not linear. It seems that when compared to a trusted Fluke meter at the source (power distribution bus bars) it's showing low, and we have even tested to see if the short lead is causing a voltage drop, but without the load of the MTT4BT it's the same as at the power distribution. The schematic in the document is incredibly grainy, but I presume it's just an AtoD input on a voltage divider, being fed into a simple equation to figure out the volt equivalent. Any suggestions on how we can improve accuracy? |
AC1DW
to navigate to use esc to dismiss