Sara Damiano

I’m sorry, could you paste your whole code and a more detailed error message.

I’m so sorry about the bad version number!  I’ll put out a new release to fix it!

@aufdenkape – The only reason was that I was thinking about the way Windows sorts files alphabetically where having the leading zero helps.  That’s pretty meaningless for this, so it needs to be fixed.

I’ve been using primarily VSCode for a while because it loads faster on my computer, but I believe I set Atom up to force ino’s as cpp’s:  https://docs.platformio.org/en/latest/integration/ide/atom.html#force-arduino-file-as-c

If you’re still using the Arduino IDE, you might consider switching to VSCode (or Atom) with PlatformIO.  I know VSCode seems very scary to start with, but if you’re writing new code or even just copy-pasting chunks the linting tools it provides are invaluable.  When I created a project for your code in VSCode, it immediately highlighted the e…[Read more]

I think you just missed commenting out one more reference to the EEPROM in line 144: EEPROM_read(KVALUEADDR, Kvalue); //1.0 means no change to raw readings. Just commenting or deleting that line should fix the compiler error.

If you wanted to, you could use the “extVoltage” sensor in ModularSensors with >1 reading do simplify all your code for…[Read more]

The bottom cut-off (below which the logger will only sleep) exists so that when a near-dead or completely dead solar-powered logger suddenly sees sunshine it gives the battery some time to charge before putting any load on it.  Otherwise the logger can get in a loop of repeatedly resetting when the just-barely-charged battery browns out with any…[Read more]

I’m confused by your tests and your results.  The purpose of having the voltage threshold for data upload is to conserve power for the sensors so that data will still be *collected* as long as possible, even if that data isn’t reported online.  Of course, decreasing the minimum threshold for powering the modem will increase the amount of time t…[Read more]

I’m sorry I’m late to this.  But @mbarney the problem with turning off power to I2C devices isn’t universal.  It depends on how your external I2C device is wired.  If the SCL and SDA of your external device are directly pulled up to the incoming Vcc, then when you turn off the switched power, suddenly the system SCL and SDA will be pulled *<…[Read more]

Fixed!  Thank you!

I *think* when Platformio pulls it, they pull from a compressed version on their own registry.

The print-outs are always going to be updated about a minute behind because the board will go to sleep at the end of the logdata() function and won’t do the printing until the next time it wakes up (which will be the next minute).

Sorry, the formatter and I were having an argument. I think it’s right now.

Here’s the version without the extra un-needed BME code.  I left in all the code for the display.

/*****************************************************************************
Based on logging_to MMW.ino
Adapted by Anthony and Brian
from source by:  Sara Damiano (sdamiano@stroudcenter.org)
Development Environment: PlatformIO
Hardware…

[Read more]

The C-to-F is working for me with this calculation function:

float calculateTempF(void)
{
  float TempCFromMaximDS18_Temp = ds18Temp->getValue();
  float TempF = (TempCFromMaximDS18_Temp)*1.8 + 32;
  if (TempCFromMaximDS18_Temp == -9999)
  {
    TempF = -9999;
  }
  // Serial.print("DS18 Temperature in Celsius:");
  //…

[Read more]

Hm.  Can you post your current code? I’ll try running it.  I have a DS18 here so hopefully once I attach things and start trying to run them whatever issue I’m missing will jump out at me.

You can throw a Serial.println(TempCFromMaxiumDS18_Temp); into the middle of your calculation equation just for testing.  I can try testing your code myself later this afternoon.

-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]

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]

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]