Configured as a digipeater.
I've enabled telemetry, but all it reports is 32 °F 100% 0.0 mbar repeating. So no live data.
I've doublechecked the pinout and the connections are very short.
I've verified I have 3v3 power.
I've soldered my sensor to the J6 header of the Wisblock, but I confirmed that there is only 1 i2c bus on this module shared with the I/O slots.
Configured as a digipeater.
I've enabled telemetry, but all it reports is 32 °F 100% 0.0 mbar repeating. So no live data.
I've doublechecked the pinout and the connections are very short.
I've verified I have 3v3 power.
I've soldered my sensor to the J6 header of the Wisblock, but I confirmed that there is only 1 i2c bus on this module shared with the I/O slots.
<!-- github-sync-id:4923953833 -->
I answered your other issue, should we talk in detail the use case? sensors used and all of it to make it work soon?
Hi Jullian,
I answered your other issue, should we talk in detail the use case? sensors used and all of it to make it work soon?
<!-- github-comment-id:5026669631 -->
Re: this wx issue I'm starting to suspect I have a bad sensor, so I'll get a replacement to try.
I did run into another WX/telemetry issue so I'll include it here rather than make a new post.
Telemetry stops decoding at aprs.fi when WX is enabled.
I've included some examples of the WX, message, and telemetry payloads.
Using a RAK4631 configured as digipeater.
WX, msg, telemetry NOT decoding-!G.../...g...t032h00b00000LoRa APRS 433.775|#x%R|
WX, telemetry NOT decoding - !G.../...g...t032h00b00000|)&%R|
WX, telemetry NOT decoding - !G.../...g...t032h00b00000|)'%S|
WX - !G.../...g...t032h00b00000
Telemetry DECODES! - !G|$P%T|
Re: this wx issue I'm starting to suspect I have a bad sensor, so I'll get a replacement to try.
I did run into another WX/telemetry issue so I'll include it here rather than make a new post.
**Telemetry stops decoding at aprs.fi when WX is enabled.**
I've included some examples of the WX, message, and telemetry payloads.
Using a RAK4631 configured as digipeater.
WX, msg, telemetry NOT decoding-!G.../...g...t032h00b00000LoRa APRS 433.775|#x%R|
WX, telemetry NOT decoding - !G.../...g...t032h00b00000|)&%R|
WX, telemetry NOT decoding - !G.../...g...t032h00b00000|)'%S|
WX - !G.../...g...t032h00b00000
Telemetry DECODES! - !G|$P%T|
<!-- github-comment-id:5026842137 -->
Base 91 Telemetry can only appear in a comment.
A Weather Report has no provision for a comment field.
73,
John WB2OSZ
Base 91 Telemetry can only appear in a comment.
A Weather Report has no provision for a comment field.
73,
John WB2OSZ
<!-- github-comment-id:5026997591 -->
APRS.fi decodes encoded telemetry only when packets is not a WX packet. So is one or the other (not both)
we should use pure "old not encoded" telemetry as a second packet to also have Wx packet available , or just avoid encoded telemetry when Wx packet is sent
APRS.fi decodes encoded telemetry only when packets is not a WX packet. So is one or the other (not both)
1) we should use pure "old not encoded" telemetry as a second packet to also have Wx packet available , or just avoid encoded telemetry when Wx packet is sent
<!-- github-comment-id:5027005331 -->
Sounds like setting of WX and Telemetry in the configurator should be mutually exclusive. Or at least give warning.
It would be neat to either add unencoded telemetry or alternate between WX/telem. at each transmission.
After reading some more I feel like the best solution is to sequence through all enabled modes/packet structures when multiple are selected.
position
WX
Telem.
repeat
Sounds like setting of WX and Telemetry in the configurator should be mutually exclusive. Or at least give warning.
It would be neat to either add unencoded telemetry or alternate between WX/telem. at each transmission.
After reading some more I feel like the best solution is to sequence through all enabled modes/packet structures when multiple are selected.
position
WX
Telem.
repeat
<!-- github-comment-id:5027717300 -->
Sounds like setting of WX and Telemetry in the configurator should be mutually exclusive. Or at least give warning. It would be neat to either add unencoded telemetry or alternate between WX/telem. at each transmission.
After reading some more I feel like the best solution is to sequence through all enabled modes/packet structures when multiple are selected. position WX Telem. repeat
sure, this week I release an update, but for next comes the full telemetry implementation
> Sounds like setting of WX and Telemetry in the configurator should be mutually exclusive. Or at least give warning. It would be neat to either add unencoded telemetry or alternate between WX/telem. at each transmission.
>
> After reading some more I feel like the best solution is to sequence through all enabled modes/packet structures when multiple are selected. position WX Telem. repeat
sure, this week I release an update, but for next comes the full telemetry implementation
<!-- github-comment-id:5028169554 -->
Re: this wx issue I'm starting to suspect I have a bad sensor, so I'll get a replacement to try. I did run into another WX/telemetry issue so I'll include it here rather than make a new post.
I got a new batch of BMP280's, but I still get the same result.
...t032h00b00000
> Re: this wx issue I'm starting to suspect I have a bad sensor, so I'll get a replacement to try. I did run into another WX/telemetry issue so I'll include it here rather than make a new post.
>
I got a new batch of BMP280's, but I still get the same result.
...t032h00b00000
<!-- github-comment-id:5112390280 -->
it seems tue sensor is showing temperature but no pressure and no humidity. What sensor is it?
if it was a BME it should show them all
it seems tue sensor is showing temperature but no pressure and no humidity. What sensor is it?
if it was a BME it should show them all
<!-- github-comment-id:5120891155 -->
The 32 deg. temp. isn't accurate and it never changes. This the just the same values that the last sensor kept repeating by default it seems.
I tried shorting the SCL and SDA pins together to force a I2C failure just to see the behavior, but that just seems to keep the board from booting.
They're listed as BMP280's:
https://www.aliexpress.us/item/3256809748948289.html
The 32 deg. temp. isn't accurate and it never changes. This the just the same values that the last sensor kept repeating by default it seems.
I tried shorting the SCL and SDA pins together to force a I2C failure just to see the behavior, but that just seems to keep the board from booting.
<!-- github-comment-id:5133773490 -->
found the issue and it is a little childish error on my side:
RAK modules have BME680 and I've never added any other BME/BMP module to be added like a regular external module. I can add the required code for this very soon.
found the issue and it is a little childish error on my side:
RAK modules have BME680 and I've never added any other BME/BMP module to be added like a regular external module. I can add the required code for this very soon.
<!-- github-comment-id:5133930760 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Configured as a digipeater.
I've enabled telemetry, but all it reports is 32 °F 100% 0.0 mbar repeating. So no live data.
I've doublechecked the pinout and the connections are very short.
I've verified I have 3v3 power.
I've soldered my sensor to the J6 header of the Wisblock, but I confirmed that there is only 1 i2c bus on this module shared with the I/O slots.
Hi Jullian,
I answered your other issue, should we talk in detail the use case? sensors used and all of it to make it work soon?
Re: this wx issue I'm starting to suspect I have a bad sensor, so I'll get a replacement to try.
I did run into another WX/telemetry issue so I'll include it here rather than make a new post.
Telemetry stops decoding at aprs.fi when WX is enabled.
I've included some examples of the WX, message, and telemetry payloads.
Using a RAK4631 configured as digipeater.
WX, msg, telemetry NOT decoding-!G.../...g...t032h00b00000LoRa APRS 433.775|#x%R|
WX, telemetry NOT decoding - !G.../...g...t032h00b00000|)&%R|
WX, telemetry NOT decoding - !G.../...g...t032h00b00000|)'%S|
WX - !G.../...g...t032h00b00000
Telemetry DECODES! - !G|$P%T|
Base 91 Telemetry can only appear in a comment.
A Weather Report has no provision for a comment field.
73,
John WB2OSZ
APRS.fi decodes encoded telemetry only when packets is not a WX packet. So is one or the other (not both)
Sounds like setting of WX and Telemetry in the configurator should be mutually exclusive. Or at least give warning.
It would be neat to either add unencoded telemetry or alternate between WX/telem. at each transmission.
After reading some more I feel like the best solution is to sequence through all enabled modes/packet structures when multiple are selected.
position
WX
Telem.
repeat
sure, this week I release an update, but for next comes the full telemetry implementation
I got a new batch of BMP280's, but I still get the same result.
...t032h00b00000
it seems tue sensor is showing temperature but no pressure and no humidity. What sensor is it?
if it was a BME it should show them all
They're listed as BMP280's:
https://www.aliexpress.us/item/3256809748948289.html
The 32 deg. temp. isn't accurate and it never changes. This the just the same values that the last sensor kept repeating by default it seems.
I tried shorting the SCL and SDA pins together to force a I2C failure just to see the behavior, but that just seems to keep the board from booting.
found the issue and it is a little childish error on my side:
RAK modules have BME680 and I've never added any other BME/BMP module to be added like a regular external module. I can add the required code for this very soon.