I would like to purchase a KX134 accelerometer and a data logger, but it looks like there’s not a pre-coded data logger that supports that sensor you sell?
Hi Jacob (@jcorbin ),
OpenLog Artemis supports the KX134 accelerometer - with firmware >= 2.8. 2.9 is the latest.
But I can see that that the product page is out of date. I’ll ask for that to be updated.
I hope this helps,
Paul
Hi Jacob -
We’ll also get this device added to the DataLogger IoT firmware for a release in March - if you want a solution that is network connected …
-Kirk
1 Like
Thanks for your help. I ordered the parts!
Ok, I’ve got the parts in hand. When selecting the Main Menu option 6) “Detect / Configure Attached Devices”, it says “No devices detected on Qwiic bus”. I have the KX134 sensor and a cable both from your store. There does not seem to be a way in TerraTerm to determine which firmware version you are using, but I figured I should upload v10, and this would correct the problem. There were lots of versions and I just chose one at random: OpenLog_Artemis-V10-v20.bin. However, after doing this, it still did not detect the sensor. Am I missing something? Thanks!
Hi Jacob (@jcorbin ),
Apologies for the lots of versions! The OLA firmware has been updated a lot over the years… Please see the upgrade instructions in the link below. If you load v2.10, all should be well.
I hope this helps,
Paul
Thanks, I think it works!
I would note that there seems to be a small counting error with the Hz output, as it seems to average the number of samples divided by time. At 10 Hz, the series goes: 0, 20, 15, 13.333, 12.5, 12.0, and asymptotes to 10. Adding one to the sample count in that calculation would help it at least not be a bit confusing!
Hi again,
I have to say that I’m a little bit disappointed in this product considering the amount of time it appears to has been put into it.
First off, I find it annoying that it expects a user input within 15 seconds or it “goes up a level” in the user interface “tree”. When you are setting things up, it’s strange that the attitude would be “I’d like to get back to recording data instead of making sure the data I’m recording is actually wanted”.
But far more critically, although I can configure the external sensor, and expect it to record when I restart, any other settings don’t seem to save between when the battery is removed, which I assumed was the case. Since it just starts recording, I unplugged the battery, because otherwise I would be overwhelmed with data.
So I set things up, unplugged the battery, cleared the SD card, got my experiment ready, and then plugged in the battery to start recording. The time reset to January 1 2000, the sampling rate returned to 10 Hz (after I set it to the maximum rate I seemed to be able to get of 88 Hz). I also didn’t know it would stop recording for a few seconds every minute or two as it switched to writing a new log file.
The data that I was recording was destructive to the part under test, so the lower sampling rate and the gaps in the data turned what I was hoping to be a “decent snapshot” of what was happening into guesswork.
I’m trying to salvage what I thought was going to be an “out of the box” type solution, but I have to figure out how to make this work given these wrong assumptions. I have one more chance to record the data, but maybe if you have any advice that’d be great.
I’m guessing that I have to cut the “MEAS” jumper, change the settings via serial with a battery plugged in to preserve the settings, set up a recording trigger, and then trigger recordings for each measurement? So solder a momentary switch between pin 11 and ground? Or a toggle switch?
perhaps I’m doing things very wrong?
Thanks for your help.
Test the logger without performing the destructive portion; ie just try getting the logger to work in a way that you can predict and then try the actual test
Are you using x or b to save/exit?
Your final plan seems workable, though you shouldn’t need the MEAS jumper at all and with saved settings you should be able to just use the reset button
Hi Jacob (@jcorbin ),
Thanks for the feedback.
Having the menus auto-close was a conscious decision. It allows the firmware to resume logging if a stray serial character causes the menu to open (and logging to be paused).
Please make sure you are exiting the menus fully each time you make changes. The changes are only saved when you fully exit the menus and the firmware resumes logging.
Please be careful when removing the power. The small rechargeable battery can only deliver enough current to sustain the RTC, and only when the Artemis is in deep sleep. For best results, connect a “Stop Logging” button as per the HookUp Guide.
You shouldn’t need to open the MEAS jumper. That’s there in case you want to MEASure the OLA’s current draw, or connect a true power-disconnect switch.
I hope this helps,
Paul