Callsign can not be updated

lu7did commented 1 year ago

@Charudatt

When the code from github is downloaded and executed once it initializes the EEPROM information with the default data on callsign, grid and other stuff.

If later this data is changed and the program recompiled the information isn't refreshed because a build version has not been detected.

@Workaround: Change the configuration data, increase by one the BUILD number, compile and flash. Then execute. After that return the BUILD number to the previous, compile and flash. The data should be correct now.

lu7did commented 1 year ago

Build #90 and up fixes this problem.

charudatt commented 1 year ago

Could you also fix the time set issue , setting decimal values in time. We are +5.30 and the system cannot take this value

regards

charudatt – VU2UPX

From: Dr. Pedro E. Colla (LU7DZ) @.> Sent: 24 July 2023 19:47 To: lu7did/RDX-rp2040 @.> Cc: charudatt @.>; Mention @.> Subject: Re: [lu7did/RDX-rp2040] Callsign can not be updated (Issue #8)

Closed #8 https://github.com/lu7did/RDX-rp2040/issues/8 as completed.

— Reply to this email directly, view it on GitHub https://github.com/lu7did/RDX-rp2040/issues/8#event-9900843536 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AA6TOF4BJHP3OT5U5FYQ62TXRZ7UBANCNFSM6AAAAAAXM3HXMA . You are receiving this because you were mentioned. https://github.com/notifications/beacon/AA6TOF6ZAHQ6ZJ73UNW5RV3XRZ7UBA5CNFSM6AAAAAAXM3HXMCWGG33NNVSW45C7OR4XAZNWJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XKUY3PNVWWK3TUL5UWJTYAAAAAETRC4IIA.gif Message ID: @. @.> >

lu7did commented 1 year ago

Yes, Charudatt, it is the issue #22 which is still open.

charudatt commented 1 year ago

some differences observed in v90 firmware with debug on-board

the Debug listing are not the same between the use of Si4732/CA2003
It does not show logging onto the WiFi and getting the time from NTP server as it used to show in the previous Listing
EEPROM does show the WiFi Credentials though
Setting the time zone to 0 does not show the UTC time on the display , as I feel it simply does not log onto the netwrok
Request - Please display the I2C status of the Si5351 also like shown for the Rx chip if used.

How do I change the default frequency from 70740 to 140740 ?

regards

charudatt

From: Dr. Pedro E. Colla (LU7DZ) @.> Sent: 24 July 2023 19:47 To: lu7did/RDX-rp2040 @.> Cc: charudatt @.>; Mention @.> Subject: Re: [lu7did/RDX-rp2040] Callsign can not be updated (Issue #8)

Build #90 and up fixes this problem.

— Reply to this email directly, view it on GitHub https://github.com/lu7did/RDX-rp2040/issues/8#issuecomment-1648005883 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AA6TOF3C2GN6KPCM5KNSXIDXRZ7T7ANCNFSM6AAAAAAXM3HXMA . You are receiving this because you were mentioned. https://github.com/notifications/beacon/AA6TOF6DQQBNUFIXDH4MXTDXRZ7T7A5CNFSM6AAAAAAXM3HXMCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTCHKJPW.gif Message ID: @. @.> >

lu7did commented 1 year ago

Hi Charudatt, it's the issue #22, still open.

El lun, 24 jul 2023 a la(s) 14:40, charudatt @.***) escribió:

Could you also fix the time set issue , setting decimal values in time. We are +5.30 and the system cannot take this value

regards

charudatt – VU2UPX

From: Dr. Pedro E. Colla (LU7DZ) @.> Sent: 24 July 2023 19:47 To: lu7did/RDX-rp2040 @.> Cc: charudatt @.>; Mention @.> Subject: Re: [lu7did/RDX-rp2040] Callsign can not be updated (Issue #8)

Closed #8 https://github.com/lu7did/RDX-rp2040/issues/8 as completed.

— Reply to this email directly, view it on GitHub < https://github.com/lu7did/RDX-rp2040/issues/8#event-9900843536> , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA6TOF4BJHP3OT5U5FYQ62TXRZ7UBANCNFSM6AAAAAAXM3HXMA> . You are receiving this because you were mentioned. < https://github.com/notifications/beacon/AA6TOF6ZAHQ6ZJ73UNW5RV3XRZ7UBA5CNFSM6AAAAAAXM3HXMCWGG33NNVSW45C7OR4XAZNWJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XKUY3PNVWWK3TUL5UWJTYAAAAAETRC4IIA.gif> Message ID: @. @.> >

— Reply to this email directly, view it on GitHub https://github.com/lu7did/RDX-rp2040/issues/8#issuecomment-1648334689, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHQ4QIOVUZWN2PLYUJWAYFTXR2XSHANCNFSM6AAAAAAXM3HXMA . You are receiving this because you modified the open/close state.Message ID: @.***>

lu7did commented 1 year ago

Hi Charudatt,

In your note in red.

73 de Pedro, LU7DZ

El mar, 25 jul 2023 a la(s) 01:09, charudatt @.***) escribió:

some differences observed in v90 firmware with debug on-board

the Debug listing are not the same between the use of Si4732/CA2003

The code is different, therefore the traces might differ. Remember the DEBUG clause must be activated for the trace to occur, it's de-activated in the repository code.

It does not show logging onto the WiFi and getting the time from NTP server as it used to show in the previous Listing

The standard source code at the repository is for the Raspberry Pico and not the Raspberry Pico W, therefore all WiFi related functions are disabled by default, you might activate the support for the Raspberry Pico W uncommenting the sentence

//#define RP2040_W 1 //Comment if running on a standard Raspberry Pico (non Wireless)

EEPROM does show the WiFi Credentials though

Yes, because of the above, they are stored but not used.

Setting the time zone to 0 does not show the UTC time on the display , as I feel it simply does not log onto the netwrok

Nope, because of the above NTP doesn't connect to the network, with the Raspberry Pico standard the only time available is the manual synchronization.

Request - Please display the I2C status of the Si5351 also like shown for the Rx chip if used.

Please log in as an enhancement for future implementation.

How do I change the default frequency from 70740 to 140740 ?

You should change it while the firmware is running and it will be stored in the EEPROM for the next power up, it will be reversed when you flash code again though. For a permanent change you should change the definition to the frequency of your wish.

unsigned long freq = 7074000UL;

I'll post this note as a question in GitHub in case any other had a similar problem.

regards

charudatt

From: Dr. Pedro E. Colla (LU7DZ) @.> Sent: 24 July 2023 19:47 To: lu7did/RDX-rp2040 @.> Cc: charudatt @.>; Mention @.> Subject: Re: [lu7did/RDX-rp2040] Callsign can not be updated (Issue #8)

Build #90 and up fixes this problem.

— Reply to this email directly, view it on GitHub < https://github.com/lu7did/RDX-rp2040/issues/8#issuecomment-1648005883> , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA6TOF3C2GN6KPCM5KNSXIDXRZ7T7ANCNFSM6AAAAAAXM3HXMA> . You are receiving this because you were mentioned. < https://github.com/notifications/beacon/AA6TOF6DQQBNUFIXDH4MXTDXRZ7T7A5CNFSM6AAAAAAXM3HXMCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTCHKJPW.gif> Message ID: @. @.> >

— Reply to this email directly, view it on GitHub https://github.com/lu7did/RDX-rp2040/issues/8#issuecomment-1649075338, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHQ4QIP4GFTHAPGM63J35Y3XR5BHBANCNFSM6AAAAAAXM3HXMA . You are receiving this because you modified the open/close state.Message ID: @.***>

charudatt commented 1 year ago

Thank you for the reply

regards

charudatt – VU2UPX

From: Dr. Pedro E. Colla (LU7DZ) @.> Sent: 25 July 2023 19:46 To: lu7did/RDX-rp2040 @.> Cc: charudatt @.>; Mention @.> Subject: Re: [lu7did/RDX-rp2040] Callsign can not be updated (Issue #8)

Hi Charudatt,

In your note in red.

73 de Pedro, LU7DZ

El mar, 25 jul 2023 a la(s) 01:09, charudatt @. <mailto:@.> ) escribió:

some differences observed in v90 firmware with debug on-board

the Debug listing are not the same between the use of Si4732/CA2003

The code is different, therefore the traces might differ. Remember the DEBUG clause must be activated for the trace to occur, it's de-activated in the repository code.

It does not show logging onto the WiFi and getting the time from NTP server as it used to show in the previous Listing

The standard source code at the repository is for the Raspberry Pico and not the Raspberry Pico W, therefore all WiFi related functions are disabled by default, you might activate the support for the Raspberry Pico W uncommenting the sentence

//#define RP2040_W 1 //Comment if running on a standard Raspberry Pico (non Wireless)

EEPROM does show the WiFi Credentials though

Yes, because of the above, they are stored but not used.

Setting the time zone to 0 does not show the UTC time on the display , as I feel it simply does not log onto the netwrok

Nope, because of the above NTP doesn't connect to the network, with the Raspberry Pico standard the only time available is the manual synchronization.

Request - Please display the I2C status of the Si5351 also like shown for the Rx chip if used.

Please log in as an enhancement for future implementation.

How do I change the default frequency from 70740 to 140740 ?

You should change it while the firmware is running and it will be stored in the EEPROM for the next power up, it will be reversed when you flash code again though. For a permanent change you should change the definition to the frequency of your wish.

unsigned long freq = 7074000UL;

I'll post this note as a question in GitHub in case any other had a similar problem.

regards

charudatt

From: Dr. Pedro E. Colla (LU7DZ) @. <mailto:@.> > Sent: 24 July 2023 19:47 To: lu7did/RDX-rp2040 @. <mailto:@.> > Cc: charudatt @. <mailto:@.> >; Mention @. <mailto:@.> > Subject: Re: [lu7did/RDX-rp2040] Callsign can not be updated (Issue #8)

Build #90 and up fixes this problem.

— Reply to this email directly, view it on GitHub < https://github.com/lu7did/RDX-rp2040/issues/8#issuecomment-1648005883> , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA6TOF3C2GN6KPCM5KNSXIDXRZ7T7ANCNFSM6AAAAAAXM3HXMA> . You are receiving this because you were mentioned. < https://github.com/notifications/beacon/AA6TOF6DQQBNUFIXDH4MXTDXRZ7T7A5CNFSM6AAAAAAXM3HXMCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTCHKJPW.gif> Message ID: @. <mailto:@.> @. <mailto:@.> > >

— Reply to this email directly, view it on GitHub https://github.com/lu7did/RDX-rp2040/issues/8#issuecomment-1649075338, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHQ4QIP4GFTHAPGM63J35Y3XR5BHBANCNFSM6AAAAAAXM3HXMA . You are receiving this because you modified the open/close state.Message ID: @. <mailto:@.> >

— Reply to this email directly, view it on GitHub https://github.com/lu7did/RDX-rp2040/issues/8#issuecomment-1649930680 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AA6TOFY4KKHKWCGX6XQ5NH3XR7IK3ANCNFSM6AAAAAAXM3HXMA . You are receiving this because you were mentioned. https://github.com/notifications/beacon/AA6TOFYGPOYIZZ65LUZWN4TXR7IK3A5CNFSM6AAAAAAXM3HXMCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTCK7Y3Q.gif Message ID: @. @.> >

lu7did / RDX-rp2040

Callsign can not be updated #8