Page 1 of 2

web tag errors after a refresh

Posted: Fri 05 Jan 2024 6:12 am
by Stigian
Hi,

On a refresh via utils/bin/cumulusutils.exe SysInfo or with thrifty, errors are generated in the CMX log and they also show up on the website (System Info page). I am using Davis WLL.

Code: Select all

2024-01-05 06:49:30.082 Web tag error in file:
2024-01-05 06:49:30.083 token=<#DavisReceptionPercent tx=>
2024-01-05 06:49:30.083 Position in file (character)=187
2024-01-05 06:49:30.083 Exception: i=132 len=613
2024-01-05 06:49:30.083 inputText.Length=613
2024-01-05 06:49:30.083 System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
  at System.Collections.Generic.List`1[T].get_Item (System.Int32 index) [0x00009] in <d636f104d58046fd9b195699bcb1a744>:0
  at CumulusMX.Cumulus.TokenParserOnToken (System.String strToken, System.String& strReplacement) [0x00058] in <4841e3cfb2ea424dbd356dd14c3de7db>:0
  at CumulusMX.TokenParser.Parse3 () [0x00119] in <4841e3cfb2ea424dbd356dd14c3de7db>:0
2024-01-05 06:49:30.083 ** The output file will contain an error message starting "**Web tag error"
2024-01-05 06:49:30.083 Web tag error in file:
2024-01-05 06:49:30.083 token=<#DavisTxRssi  tx=>
2024-01-05 06:49:30.083 Position in file (character)=230
2024-01-05 06:49:30.083 Exception: i=215 len=613
2024-01-05 06:49:30.083 inputText.Length=613
2024-01-05 06:49:30.083 System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
  at System.Collections.Generic.List`1[T].get_Item (System.Int32 index) [0x00009] in <d636f104d58046fd9b195699bcb1a744>:0
  at CumulusMX.Cumulus.TokenParserOnToken (System.String strToken, System.String& strReplacement) [0x00058] in <4841e3cfb2ea424dbd356dd14c3de7db>:0
  at CumulusMX.TokenParser.Parse3 () [0x00119] in <4841e3cfb2ea424dbd356dd14c3de7db>:0
2024-01-05 06:49:30.083 ** The output file will contain an error message starting "**Web tag error"
2024-01-05 06:49:30.083 Web tag error in file:
2024-01-05 06:49:30.083 token=<#DavisTotalPacketsMissed tx=>
2024-01-05 06:49:30.083 Position in file (character)=283
2024-01-05 06:49:30.083 Exception: i=249 len=613
2024-01-05 06:49:30.083 inputText.Length=613
2024-01-05 06:49:30.083 System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
  at System.Collections.Generic.List`1[T].get_Item (System.Int32 index) [0x00009] in <d636f104d58046fd9b195699bcb1a744>:0
  at CumulusMX.Cumulus.TokenParserOnToken (System.String strToken, System.String& strReplacement) [0x00058] in <4841e3cfb2ea424dbd356dd14c3de7db>:0
  at CumulusMX.TokenParser.Parse3 () [0x00119] in <4841e3cfb2ea424dbd356dd14c3de7db>:0
2024-01-05 06:49:30.083 ** The output file will contain an error message starting "**Web tag error"
2024-01-05 06:49:30.083 Web tag error in file:
2024-01-05 06:49:30.083 token=<#DavisNumberOfResynchs tx=>
2024-01-05 06:49:30.083 Position in file (character)=381
2024-01-05 06:49:30.083 Exception: i=313 len=613
2024-01-05 06:49:30.083 inputText.Length=613
2024-01-05 06:49:30.083 System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
  at System.Collections.Generic.List`1[T].get_Item (System.Int32 index) [0x00009] in <d636f104d58046fd9b195699bcb1a744>:0
  at CumulusMX.Cumulus.TokenParserOnToken (System.String strToken, System.String& strReplacement) [0x00058] in <4841e3cfb2ea424dbd356dd14c3de7db>:0
  at CumulusMX.TokenParser.Parse3 () [0x00119] in <4841e3cfb2ea424dbd356dd14c3de7db>:0
2024-01-05 06:49:30.083 ** The output file will contain an error message starting "**Web tag error"
2024-01-05 06:49:30.083 Web tag error in file:
2024-01-05 06:49:30.083 token=<#DavisMaxInARow tx=>
2024-01-05 06:49:30.083 Position in file (character)=460
2024-01-05 06:49:30.083 Exception: i=409 len=613
2024-01-05 06:49:30.083 inputText.Length=613
2024-01-05 06:49:30.084 System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
  at System.Collections.Generic.List`1[T].get_Item (System.Int32 index) [0x00009] in <d636f104d58046fd9b195699bcb1a744>:0
  at CumulusMX.Cumulus.TokenParserOnToken (System.String strToken, System.String& strReplacement) [0x00058] in <4841e3cfb2ea424dbd356dd14c3de7db>:0
  at CumulusMX.TokenParser.Parse3 () [0x00119] in <4841e3cfb2ea424dbd356dd14c3de7db>:0
2024-01-05 06:49:30.084 ** The output file will contain an error message starting "**Web tag error"
2024-01-05 06:49:30.084 Web tag error in file:
2024-01-05 06:49:30.084 token=<#DavisNumCRCerrors tx=>
2024-01-05 06:49:30.084 Position in file (character)=528
2024-01-05 06:49:30.084 Exception: i=481 len=613
2024-01-05 06:49:30.084 inputText.Length=613
2024-01-05 06:49:30.084 System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
  at System.Collections.Generic.List`1[T].get_Item (System.Int32 index) [0x00009] in <d636f104d58046fd9b195699bcb1a744>:0
  at CumulusMX.Cumulus.TokenParserOnToken (System.String strToken, System.String& strReplacement) [0x00058] in <4841e3cfb2ea424dbd356dd14c3de7db>:0
  at CumulusMX.TokenParser.Parse3 () [0x00119] in <4841e3cfb2ea424dbd356dd14c3de7db>:0
2024-01-05 06:49:30.084 ** The output file will contain an error message starting "**Web tag error"
2024-01-05 06:49:30.084 Web tag error in file:
2024-01-05 06:49:30.084 token=<#txbattery channel=>
2024-01-05 06:49:30.084 Position in file (character)=590
2024-01-05 06:49:30.084 Exception: i=552 len=613
2024-01-05 06:49:30.084 inputText.Length=613
2024-01-05 06:49:30.084 System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
  at System.Collections.Generic.List`1[T].get_Item (System.Int32 index) [0x00009] in <d636f104d58046fd9b195699bcb1a744>:0
  at CumulusMX.Cumulus.TokenParserOnToken (System.String strToken, System.String& strReplacement) [0x00058] in <4841e3cfb2ea424dbd356dd14c3de7db>:0
  at CumulusMX.TokenParser.Parse3 () [0x00119] in <4841e3cfb2ea424dbd356dd14c3de7db>:0
2024-01-05 06:49:30.084 ** The output file will contain an error message starting "**Web tag error"

Re: web tag errors after a refresh

Posted: Fri 05 Jan 2024 9:16 am
by AndyKF650
Just a thought but shouldn't the webtag "token=<#DavisReceptionPercent tx=>" contain an extra identifier ie "tx=1"

Re: web tag errors after a refresh

Posted: Fri 05 Jan 2024 10:40 am
by HansR
Stigian wrote: Fri 05 Jan 2024 6:12 am On a refresh via utils/bin/cumulusutils.exe SysInfo or with thrifty, errors are generated in the CMX log and they also show up on the website (System Info page). I am using Davis WLL.
Two remarks at this point:
  1. Could you post the whole logfile as the device you have is the WLL cloud, if I remember well, and you are the first to use that afaik so there may be an error there.
  2. @Andy may have a point there: the parameter Tx in section SysInfo must contain a comma separated list of the transmitters used. I am no WLL expert (I have no Davis at all) but I think you can choose transmitter 1 to 8 for different devices and it does not have to start with 1 so, 4,5 is perfectly legal as long as your WLL setup is valid.
And the error you show is the CMX MXdiags error, in 1 I am asking for the CUtils logfile ;)

Re: web tag errors after a refresh

Posted: Fri 05 Jan 2024 10:52 am
by HansR
And btw... I am preparing a maintenance release for 6.23.1, I'll await the fix for this one.

Re: web tag errors after a refresh

Posted: Fri 05 Jan 2024 10:57 am
by Stigian
Hi Hans,
[*]Could you post the whole logfile as the device you have is the WLL cloud, if I remember well, and you are the first to use that afaik so there may be an error there.
Here you go;
2401050649cumulusutils.log

Re: web tag errors after a refresh

Posted: Fri 05 Jan 2024 11:10 am
by HansR
OK, Thanks. You are using just WLL, don't know where I got that WLL Cloud thing... aha, did not read this thread to completion or accurately...

So I suggest you try to fill in the Tx parameter according to your configuration and run again. Let me know the result.
I will add a test for the validity of Tx (must have a value) but I cannot check in any way whether the value(s) you put in there is/are correct.

Re: web tag errors after a refresh

Posted: Fri 05 Jan 2024 11:14 am
by HansR
And btw: I saw that you had issues with the pressure. If those issues have set your all time pressure record the scale of the pressure in the charts may not function correctly and you may have to reset those records (the min/max value for the pressure scale are taken from the the All Time records).

So checking that may be useful.

Re: web tag errors after a refresh

Posted: Fri 05 Jan 2024 11:25 am
by HansR
Some other remarks on the new stup:
  1. You will need to either set the evapotranspiration values somewhere or calculate those through CMX (advised, personally I think the Davis values are far too high)
  2. You may want to inverse your windrose to get the high winds on the outer part of the segments (it is a taste thing)
  3. You may want to fill in the normal values for rain and temperature to get your reference values right in the climate charts
  4. You may want to switch off the solar graphs as you don't have the solar sensor

Re: web tag errors after a refresh

Posted: Fri 05 Jan 2024 11:34 am
by Stigian
Just a thought but shouldn't the webtag "token=<#DavisReceptionPercent tx=>" contain an extra identifier ie "tx=1"
I wonder where to add this webtag? It's no a part of the station settings...

Re: web tag errors after a refresh

Posted: Fri 05 Jan 2024 11:36 am
by Stigian
HansR wrote: Fri 05 Jan 2024 11:25 am Some other remarks on the new stup:
  1. You will need to either set the evapotranspiration values somewhere or calculate those through CMX (advised, personally I think the Davis values are far too high)
  2. You may want to inverse your windrose to get the high winds on the outer part of the segments (it is a taste thing)
  3. You may want to fill in the normal values for rain and temperature to get your reference values right in the climate charts
  4. You may want to switch off the solar graphs as you don't have the solar sensor
Thanks Hans.. still something to do :)

Re: web tag errors after a refresh

Posted: Fri 05 Jan 2024 11:56 am
by HansR
Stigian wrote: Fri 05 Jan 2024 11:34 am
Just a thought but shouldn't the webtag "token=<#DavisReceptionPercent tx=>" contain an extra identifier ie "tx=1"
I wonder where to add this webtag? It's no a part of the station settings...
That is automatic because of the device. It is not for you, just fill in the Tx because you have a WLL

[EDIT:]see the Wiki

Re: web tag errors after a refresh

Posted: Fri 05 Jan 2024 12:02 pm
by Stigian
That is automatic because of the device. It is not for you, just fill in the Tx because you have a WLL
Can you tell me where I can enter that? Or is it something you need to modify and you need a value from me? From what I can see it should be a "1". Because that is my device ID.

Re: web tag errors after a refresh

Posted: Fri 05 Jan 2024 12:05 pm
by Stigian
Hi Hans,

We crossed paths ;) I adjusted it and it works now.

[EDIT] Processor Temperature: -999.0 °C :lol:

Re: web tag errors after a refresh

Posted: Fri 05 Jan 2024 12:06 pm
by HansR
Stigian wrote: Fri 05 Jan 2024 12:02 pm Can you tell me where I can enter that? Or is it something you need to modify and you need a value from me? From what I can see it should be a "1". Because that is my device ID.
The transmitter value(s) must in the configuration of the WLL. As I don't have one, I can't help you here, can't guide you through it.
Maybe @Mark, @Mapantz or @PaulMy or any other with a WLL device will jump in to help you with the transmitter value(s)

Re: web tag errors after a refresh

Posted: Fri 05 Jan 2024 12:56 pm
by HansR
Stigian wrote: Fri 05 Jan 2024 12:05 pm We crossed paths ;) I adjusted it and it works now.

[EDIT] Processor Temperature: -999.0 °C :lol:
OK. Solved then.

Wrt the CPU temperature, we'll look at that later. It is caused because you run on a PC and not an RPi. This means that the Debian apparently is a slightly different dialect on a PC and requires a different method to access the CPU temperature. I am currently busy doing a lot of other things wrt CMX and personal so this will be much later. Sorry for that.