Modular clock problems

More
7 months 2 weeks ago - 7 months 2 weeks ago #12372 by Ty_Eeberfest
Replied by Ty_Eeberfest on topic Modular clock problems

Ty_Eeberfest wrote: Once the bootloader has been burned onto the new chip you should be able to proceed as per normal, i.e stick the new chip into an UNO and flash with the clock firmware in the normal USB manner.


And... just to confirm, I just did the following using the "2 UNOs wired together scheme" from the picture in your earlier post:

- Put a brand new totally blank 328P in the Target UNO
- USB connected to the Programmer UNO
- Loaded "Atmega_Board_Programmer" in the Programmer UNO
- Blasted the new UNO with bootloader and fuse settings
- Loaded "Atmega_Board_Detector" in the Programmer UNO
- Verified that my new chip now had a bootloader and correct fuses
- Disconnected the jumpers, plugged USB imto Target UNO
- Flashed the Blink example sketch in the normal manner
- The LED is now blinking therefore it worked

So... your programming setup passes my tests ;)

Look into it later when the dust is clearing off the crater.
Last edit: 7 months 2 weeks ago by Ty_Eeberfest.

Please Log in or Create an account to join the conversation.

More
7 months 2 weeks ago #12375 by tgibbs99
Replied by tgibbs99 on topic Modular clock problems
Ty,

Thanks so much for your efforts.Very good to know you got the same results as me. I thought i got Preserve EEPROM through erase = NO on one of the factory chips, but i didn't have them labeled well enough.

At this point I need to make some short videos of the tube test and other behaviors of the setup.

Unfortunately, i will be pulled away for at least a week on another project.

If possible, I would like to order two factory chips, one set up for "REV3", and the other set up for FWV2. I will place the order tonight.

More troubleshooting to follow!

Tim

Please Log in or Create an account to join the conversation.

More
7 months 2 weeks ago #12376 by Ian
Replied by Ian on topic Modular clock problems
I received the order it will go out today!

Please Log in or Create an account to join the conversation.

More
7 months 2 weeks ago #12378 by Ty_Eeberfest
Replied by Ty_Eeberfest on topic Modular clock problems

tgibbs99 wrote: Ty,

Thanks so much for your efforts.Very good to know you got the same results as me. I thought i got Preserve EEPROM through erase = NO on one of the factory chips, but i didn't have them labeled well enough.
Tim


No problem. I'd never heard of the Nick Gammon utilities. Now I know they exist and work as advertised. Never hurts to have another too at ones disposal. I must say though that if you plan to do a lot of this sort of thing it might be worth buying a hardware ICSP at some point. I find my old AVRISP Mk.2 very useful.

If you have a moment before disappearing to your other project, let us know what boards you actually have: Rev. 3 or Rev. 3.01.


Look into it later when the dust is clearing off the crater.
Attachments:

Please Log in or Create an account to join the conversation.

More
7 months 2 weeks ago #12383 by tgibbs99
Replied by tgibbs99 on topic Modular clock problems
Ty,

I have 2- REV3 boards and 3-REV3.01.

Thanks.

Tim

Please Log in or Create an account to join the conversation.

More
6 months 3 weeks ago #12452 by tgibbs99
Replied by tgibbs99 on topic Modular clock problems
Ty,

Ok I'm back from other project. Good news today. After VERY carefully checking all contacts and connects, my clock #1 (REV3.01) has all leds working, and all Nixie digits working. However, it is showing the wrong time.

On the clock configuration page of the ESP8266 server I show the following:

Current Status
Name Value
WLAN IP 192.168.68.141
WLAN MAC 2C:3A:E8:4D:77:04
WLAN SSID GibbsCabin245
NTP Pool pool.ntp.org
TZ CST6CDT,M3.2.0,M11.1.0
Clock Name ESP-4D7704 ( esp-4d7704.local )
Last NTP time 2021:02:21 17:37:27
Last NTP update 12 m 46 s ago
Time before next NTP update 1 h 48 m 14 s
Display Time 2000:01:09 12:29:06
Uptime 24 m 17 s
Version vx58c
v2 Number 0x0x0x
Found I2C slave (DS3231 RTC) 104
Found I2C slave (Nixie clock) (default) 105
Status string WNSUAd
Total clock on time 20 m 0 s
Communicating with: Clock not found!

So it appears to have identified the DS3231 RTC and the Nixie clock
but then gives message clock not found. Attempt at updating NTP time was not helpful.
you can see display time and NTP time do not match.

Any suggestions?

Thanks.

Tim

Please Log in or Create an account to join the conversation.

Moderators: AccutronTy_EeberfestIan
Time to create page: 0.104 seconds
Go to top
JSN Boot template designed by JoomlaShine.com