Comments: OpenLog Artemis Hookup Guide
Looking for answers to technical questions?
We welcome your comments and suggestions below. However, if you are looking for solutions to technical questions please see our Technical Assistance page.
If you've found an issue with this tutorial content, please send us your feedback!
I'm using Thing Speak. In your interface, what option fields are setup in the Thing Speak menu option values (API Key, etc)??
Hi,
I don't believe there is a feature with the OpenLog Artemis to use with ThingSpeak. Try looking at the SparkFun DataLogger IoT. That board has the ability to connect to ThingSpeak.
How can we add a Pulse Oximeter and buttons to get data labeled?
Please, submit a feature request in the issues tab of the GitHub repo.
Artemis let us log inertial measurements, and no need to write a single line for logging other measurements from any of the listed sensors -- because Artemis automatically detects and log the data from an attached sensor/breakout. This sounds (almost) all good. But to be called an Open, this ambitious product should've had and/or missed a couple of important facts/features (or maybe lack of documentation if the followings are already covered at somewhere)
What are those values (e.g., inertial measurements)? Are they filtered or raw? Remembering that at somewhere in the hookup guide, GNSS measurements could be used for post-processing, there is a high chance that they are all raw values. Except those measurements refined by a post-processing, what good are these raw values for? I mean, why do we even bother to log these noisy values for what?
What if we want to upload a code to Artemis? How could one do this? I want to upload a filter code that essentially fuses inertial measurements with GNSS measurements, (e.g., values from NEO-M9N) for odometry. So far, I had no luck in finding any documentations about this -- uploading any codes to Artemis. Is it possible to do so? If yes, where can I find any documentation about this?
If you don't have any practical answers to the above questions, this product won't fly as you would have expected or wished (and Bang goes my $114.9+ = $49.95 + $64.95 + tax!). It'd be better if you could mention such limitations of this product up front.
There is one firmware package for GNSS logging to a ubx file (useful for rover/base PPK), and a separate firmware for logging other data (ie, IMU). How do you do these simultaneously so you get one ubx file and one csv for each recording? Would love more thorough instructions on how to do that in the hookup guide.
Can we configure OLA so that it logs timestamps with more than 2 digits after the decimal point to the csv file?
Please, submit a feature request in the issues tab of the GitHub repo.
Does the CCSV file overwrite itself until stopped? Looking to use this as a Monitor that I can pull data only when there is an issue seen.
Would it be possible get the data from the artemis logger somehow electronically? For example into an adafruit feather ... so the data can be uploaded to a server using GPRS? Or put it another way, .. what would be the best way to get the data from the logger into a server app without having to manually get the SD card.
We just released v1.6 of the firmware that supports data output over serial1. This means you could solder any external device to the TX pin on OLA and then pipe the data where ever you need (feather, cellular, what have you).
Yes, v1.6 goes a long way in the right direction. The zModem function is nice but only available through USB. The serial log does not really help for this case. If you need a robust solution that ensures you're getting all data into that server, it would mean you'd have to build a robust listener on the serial port, write each incoming data-record to a SD Card and on some interval send data from the SD Card to the server. But this is hard to get right, and it is 80% the same thing the OLA already solves. This is highly reduntant. If we use a feather which could request data from the OLA and send it over WIFI to the server ... then the solution would be much more compact. If only OLA would provide a mechanism for the other MCU to fetch the data.....
We just released version 2.0.0 of the Apollo3 Arduino core, which now, includes support for the ArduinoBLE library.
I think someone might have mentioned being able to retrieve data with a Raspberry Pi from a different (non-OLA) Artemis board, using Bluetooth. However, I am not sure it they were developing in the Arduino IDE or with Mbed OS.
That could be an interesting option, thanks for sharing this idea! Would be great if this will be supported in a future version of the Artemis OpenLog V10 binaries ...
I would like to second the serial out (member 1274742's ) request. I have an application that uses a radio link and being able to stream the csv data over a serial link would be awesome.
This has been added to v1.6 of the firmware. Please have a look and let us know what you think!
Can one stream the SD CSV file dataLog00000.TXT to a serial output port?
All the same data is steamed out the USB connection. We had not thought to stream it out the serial pins but it's easy enough to do and a fine feature idea. Do you mind filing a feature request on the OLA repo?
Request is here. We'll try to get it into the next release candidate.