One of my first tasks here at Wyolum was updating the old ClockTHREE Jr. software for Arduino 1.6.9, the newest version. I focused specifically on updating the file specified in the original tutorial for reprogramming the ClockTHREE Jr., ClockTHREE_04.ino. At first, when I tried compiling the sketch, the number of error messages that popped up frightened me. It was just a sea of blaring orange text, informing me on the multitude of errors spanning a variety of different documents. The task seemed to be very daunting, and I did not know if I would be able to complete this task. However, after I had gotten over my initial shock, i decided to be brave and actually read the error messages, rather than judge the difficulty of the task by their quantity. This act turned out to be immensely helpful, as after my analysis, I discovered that there were only 6 documents that needed to be changed, as opposed to my crazy original assumption of 20 or 25. Furthermore, there seemed to be one term that resonated throughout the error messages: “const.” With these 2 helpful facts in mind, I got to work. Below is a detailed analysis of what I did to the 6 documents:<\/p>\n

\n
1. In the original file itself, ClockTHREE_04.ino, I included the english_v3.h file, uncommented the line that let the ClockTHREE Jr. account for Daylights Savings Time, and most importantly, changed \u201cprog\u201d in the line \u201cPROGREM prog_uint32_t DST[] = {\u201c to a \u201cconst.\u201d<\/li>\n
2. In the next document I changed, english_v3.h, I simply added a const after the “uint8\/32_t” in the lines with WORDS[] PROGMEM, DISPLAYS[] PROGMEM, MINUTE_LEDS[] PROGMEM, and MINUTES_HACKS[] PROGMEM.<\/li>\n
3. The next file I had to change took me away from the ClockTHREE Jr. file and into the CHRONOGRAM2 file, where I had to update the english2_v1.h file. In this file, I changed “prog_char” to “const_char” in the lines with HOUR_WORDS[], HOUR_SEQ[], MINUTE_WORDS[], and MINUTE_SEQ[].<\/li>\n
4. In the files font.cpp and mem_font.cpp, I respectively changed “PROGMEM static char prog_char font8x8[] = {” to\u00a0\u201cPROGREM static const char font8x8[] = {\u201c\u00a0<\/b>and\u00a0\u201cstatic prog_char font8x7[] PROGMEM = {\u201c to \u201cstatic const char font8x7[] PROGMEM = {.\u201c<\/li>\n
5. In the final document I changed, DateStrings.cpp, I added a “const” to:<\/li>\n<\/ol>\n
   \n
   \n
   \n
   1. char monthShortNames_P[] PROGMEM = “ErrJanFebMarAprMayJunJulAugSepOctNovDec”;<\/li>\n
   2. char dayStr0[] PROGMEM = “Err”;<\/li>\n
   3. char dayStr1[] PROGMEM = “Sunday”;<\/li>\n
   4. char dayStr2[] PROGMEM = “Monday”;<\/li>\n
   5. char dayStr3[] PROGMEM = “Tuesday”;<\/li>\n
   6. char dayStr4[] PROGMEM = “Wednesday”;<\/li>\n
   7. char dayStr5[] PROGMEM = “Thursday”;<\/li>\n
   8. char dayStr6[] PROGMEM = “Friday”;<\/li>\n
   9. char dayStr7[] PROGMEM = “Saturday”;<\/li>\n
   10. PGM_P dayNames_P[] PROGMEM = { dayStr0,dayStr1,dayStr2,dayStr3,dayStr4,dayStr5,dayStr6,dayStr7};<\/li>\n
   11. char dayShortNames_P[] PROGMEM = “ErrSunMonTueWedThrFriSat”;<\/li>\n
   12. char monthStr1[] PROGMEM = “January”;<\/li>\n
   13. char monthStr2[] PROGMEM = “February”;<\/li>\n
   14. char monthStr3[] PROGMEM = “March”;<\/li>\n
   15. char monthStr4[] PROGMEM = “April”;<\/li>\n
   16. char monthStr5[] PROGMEM = “May”;<\/li>\n
   17. char monthStr6[] PROGMEM = “June”;<\/li>\n
   18. char monthStr7[] PROGMEM = “July”;<\/li>\n
   19. char monthStr8[] PROGMEM = “August”;<\/li>\n
   20. char monthStr9[] PROGMEM = “September”;<\/li>\n
   21. char monthStr10[] PROGMEM = “October”;<\/li>\n
   22. char monthStr11[] PROGMEM = “November”;<\/li>\n
   23. char monthStr12[] PROGMEM = “December”;<\/li>\n
   24. PGM_P monthNames_P[] PROGMEM =<\/li>\n<\/ol>\n<\/ol>\n<\/ol>\n

       After saving all of my changes, I compiled the code in Arduino 1.6.9, and to my utter delight, it worked!<\/p>\n","protected":false},"excerpt":{"rendered":"

       One of my first tasks here at Wyolum was updating the old ClockTHREE Jr. software for Arduino 1.6.9, the newest version. I focused specifically on updating the file specified in the original tutorial for reprogramming the ClockTHREE Jr., ClockTHREE_04.ino. At … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":14,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1995","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/wyolum.com\/wp-json\/wp\/v2\/posts\/1995","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wyolum.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wyolum.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wyolum.com\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/wyolum.com\/wp-json\/wp\/v2\/comments?post=1995"}],"version-history":[{"count":1,"href":"https:\/\/wyolum.com\/wp-json\/wp\/v2\/posts\/1995\/revisions"}],"predecessor-version":[{"id":1996,"href":"https:\/\/wyolum.com\/wp-json\/wp\/v2\/posts\/1995\/revisions\/1996"}],"wp:attachment":[{"href":"https:\/\/wyolum.com\/wp-json\/wp\/v2\/media?parent=1995"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wyolum.com\/wp-json\/wp\/v2\/categories?post=1995"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wyolum.com\/wp-json\/wp\/v2\/tags?post=1995"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}