I find myself confused by the terminology used to describe the various clock hardware revisions and code versions.
It seems like things are now broadly divided into "v1" and "v2" hardware. The v1 seems to use RGB LEDs, where the v2 boards use Neopixels addressable LEDs. There may be other differences.
Then within "v1" hardware I see references to Classic Rev4, Classic Rev5, All In One IN-14 and Arduino All In On Shield. Are all of these variations of "v1" hardware? Does that mean there is a "v1, Rev. 5" board?
Within the "v1" boards, there are software revisions (54, 55, 56, etc) that seem to be identified as such only in the code itself, but not in the repositories. Also, there seems to be no way to retrieve and older v1 software revision from the new or old repositories.
Are these correct assumptions. Just trying to figure out the correct terminology here.
but fundamentally you are right in your assumption that the basic root difference is the RGBs. Using NeoPixels freed up two GPIOs which were used for a PIR input and a driver for the decimal points.
ALL OF THE software versions between V1 and V2 work on all boards of that version. There are no special cases. That's the good news. If you have a Classic Rev4, Classic Rev5 or All In One, they all run exactly the same code.
For the tags, if you go into the "commits" view, you can find the tags:
If you see a tag like "v56" that is for the 6 digit code. If you see "v456" that means it is for the 4 digit code.
Got it! That helps a lot. I use Github and am a bit unfamiliar with Bitbucket.
Of course, I'm running my own homebrew 6-tube v1 version, constructed from the open source schematics and using an external WIFI ESP8266 development board module, but I could see that the code for all of the v1 6-tube boards was the same, or appeared to be.
Thanks for taking the time to clarify this. I had missed the Commit tags.
I should mention that the latest v1 version 56 codes runs perfectly well on my homebrew hardware with the RTC module. I compile in the Arduino IDE for an Atmega328p, extract the non-bootloader hex code, and burn it directly to a bare Atmega328p chip with manually set fuses for reasonable brownout values and external 16MHz crystal operation.
That part works perfectly.
Just trying to figure out my ESP-12E errors for the Wifi module code. I use the board with the latest libraries for other projects with no issues.
I just bought a classic 6 digit PCB + programmed micro controller. The PCB is classiv Rev 4c and runs software V56.... The construction manual for classic rev 4c PCB has some mistakes, meaning that at some stages you refer to the new PCB but there are indications with old picture from the PCB rev 4 and in the user manual for V56 there are some mistakes regarding the number of pages of the clock menu, from 00:00:09 jumps to page 00:00:15... not a big problem for me, bt may be for others.
Anway, i mounted the rev 4c PCB and i have a problem with the RGB s, the Red, Green and Blue stays lit in the same time despite i set from the menu just the Red color to be lit and neither the cycle, fixed, dimmed cycle function does not work and i cannot figure out the problem. Otherwise, the clock runs normally.
I am not sure if you have a Classic Re4 or Classic Rev6: The important thing is that the LED back lights on the Rev6 are completely different to the Rev4 or Rev5. On the Rev6 they use NeoPixels on the Rev4 and Rev5 just PWM using standard RGB common anode LEDs.