Notifications
Clear all
2023-01-13 3:36 pm
@witchdoc59 I realized you did sort of publish your sketch and the link to Bill's so here is the first cut at the merged sketch. NOTE: I used the sample sketch, Bill's version is the same just a little neater.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
2023-01-15 5:51 am
@zander Hi there; I managed to get it all working. At line 108 there is a delay(). It seemed to be that area where the sketch was failing. So I commented out the delay and recompiled. I was pleasantly surprised to see it all start working. Now to figure out why the altitude is so erratic. And figure out how to manipulate the time for my time zone.
2023-01-15 6:08 am
@witchdoc59 Good to hear. Yes, delay() is a problem with certain functions as it blocks everything. If you want/need to only sample every x secs or mins then use a standard millis() based delay.
As far as time zone look at any of the parsing samples, there are I think 3? I2C, HardwareSerial, SoftwareSerial. Good luck.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
Page 6 / 6
Prev