Activity

-17966.20 does seem a little bit cold for most offices.  Did you change your variable array so it has the ds18Temp named variable in it instead of the other new variable?  If not update step will update that other new variable and not the one that you’re calculating F from, though adding the “true” to the getValue should force it to update a…[Read more]

Now I got it to be 33.8 F by replacing
float TempF = TempCFromMaxiumDS18_Temp*1.8+32 with
float TempF = true*1.8+32

Awesome, thank you. That solved the error. I was wondering about my variable array because I saw the format of the variable array in the baro_rho_correction sketch and it was more bare bones.
Now I’m puzzling on the -17966.20 Degree F output I’m seeing in the serial monitor. I tried adding true to the ds18->getValue(true) but that didn’t work.

Thank you @mbarney!  That’s all correct!

And just FYI, prior to version ~5 of PlatformIO, libraries were only updated in the PlatformIO registry when the registry crawler got to it and noticed the change.  So sometimes it would be a day or two before you could see the updates using the pio lib update or similar commands.  With the current ve…[Read more]

Thanks @srgdamiano — and thanks so much for announcing the release here on the forum and sharing links to the release notes on GitHub!

Until somewhat recently, I didn’t fully grasp the connection between a ModularSensors GitHub release number and the version number in the PlatformIO library registry. To clarify for others who may be new to these…[Read more]

Does that make sense?

So, for example, in line 178 you created a variable for the DS18 (Variable *ds18Temp = new MaximDS18_Temp(&ds18, "12345678-abcd-1234-ef00-1234567890ab");) Since you’ve already done that, down in line 234 instead you can replace new MaximDS18_Temp(&ds18, "12345678-abcd-1234-ef00-1234567890ab"), with just ds18Temp,.  And you…[Read more]

In line 237 you don’t need the “new” or anything else with the calcTempF.

Replace new CalcTempF(&ds18, "12345689-abcd-1234-ef00-1234567890ab"), with just CalcTempF,

You’ve already created and named the variable, so you don’t need to re-create it, just reference it. Actually, since you’ve created all your variables with names, you should…[Read more]

Hi Sara,

Just wanted to say thank you for your help and kind support, now everything is working as expected and just need to calibrate the Y4000.

Attached is a screenshot about the final results, I needed to twerk the delay time a little bit and make sure grounding overall is respected, but other than that everything worked  fine.

Thanks again.

If it’s not going back to 2000, your battery is ok.

Is the board still running the “now” or “adjust” sketch?  If so, every time the board re-starts, it will reset to whatever time you told it in that program.

Yes, I do and it’s inserted print side up. I guess it’s possible the battery is dead, although it’s new.  I also just saw that the day, date and time are not changing. I last set it on Tuesday and left it plugged in and turned on and when I hit the Serial Monitor it’s still showing Tuesday 2/9/2021. Is that also a sign the battery is dead?

Do you have a coin battery in the slot?  Could that battery be dead?  If you don’t have a battery in the coin slot or if it’s dead, then the clock will reset to Jan 1, 2000 every time the board is unplugged from the computer or battery

Ah, perfect – thanks Sara!

The Arduino print function defaults to two decimal places for a float.  Normally, if you were using Serial.print(float) you could control the decimal places with Serial.print(float, decimalPlaces).  But because of the way the MS_DBG macro is written, that won’t work.  You’ll have to create a String from the number and then MS_DBG that:  MS_DBG(Stri…[Read more]