Serial logging stops at 2,059 Bytes

Development Boards Artemis
1

Hello,

I am using the Openlog Artemis (DEV-16832) to log serial data to a micro SD card with IMU logging disabled.

I am sending serial data at 115.2k, 8N1, to the RX pin on the board.

After opening the serialLog000xx file that is saved onto the micro SD on my computer, each serial log stops at the same position as the others and each serial log has a size of 2,059 Bytes.

Could this be due to the fact that the new line terminator is not configured properly on my Openlog Artemis and is causing the serial buffer to get full? If so, how would I go about configuring the new line terminator to the one that is used in my serial data?

I have copy-pasted the OLA_settings file on the SD card at the bottom of this post.

Please let me know if you have any other questions and thank you for your help.

OLA_settings:

sizeOfSettings=128
olaIdentifier=279
nextSerialLogNumber=5
nextDataLogNumber=4
usBetweenReadings=10000000
logMaxRate=0
enableRTC=1
enableIMU=0
enableSD=1
enableTerminalOutput=1
logDate=1
logTime=1
logData=1
logSerial=1
logIMUAccel=1
logIMUGyro=1
logIMUMag=1
logIMUTemp=1
logRTC=1
logHertz=0
getRTCfromGPS=0
correctForDST=0
americanDateStyle=1
hour24Style=1
serialTerminalBaudRate=115200
serialLogBaudRate=115200
showHelperText=1
logA11=0
logA12=0
logA13=0
logA32=0
logAnalogVoltages=1
localUTCOffset=0
printDebugMessages=0
powerDownQwiicBusBetweenReads=0
qwiicBusMaxSpeed=100000
qwiicBusPowerUpDelayMs=250
printMeasurementCount=0
enablePwrLedDuringSleep=1
logVIN=0
openNewLogFilesAfter=0
vinCorrectionFactor=1.47
useGPIO32ForStopLogging=0
qwiicBusPullUps=1
outputSerial=0
zmodemStartDelay=5
enableLowBatteryDetection=0
lowBatteryThreshold=3.40
frequentFileAccessTimestamps=0
useGPIO11ForTrigger=0
fallingEdgeTrigger=1
imuAccDLPF=0
imuGyroDLPF=0
imuAccFSS=0
imuAccDLPFBW=7
imuGyroFSS=0
imuGyroDLPFBW=7

2

How is the card formatted?

Have you tried using Option 10 in the configuration settings to have it create a new file after a certain period?
“Option 10 can be used to make the OLA open a new log file after the specified number of seconds. There is a small risk of data loss if the OLA’s power is removed while data is being written to the SD card. By telling the OLA to open a new log file say every hour (3600 seconds) then the most data you can lose is the past hour. (Connecting a stop logging button can prevent data loss too. See “Low Power Considerations” for further details.)”

1 Like
3

Hi Jorge (@jimboi9 ),

It looks like your OLA is running firmware version v1.7? That’s really old… We’ve made many improvements since then. Please try upgrading to v2.10 and repeat your test. Does the issue go away? You can always revert to v1.7 if you need to. I’d recommend making a copy of your OLA_settings.txt and OLA_deviceSettings.txt first, so you can restore those if needed. The upgrade will create newer versions of both files.

I hope this helps,
Paul

2 Likes
4

Thanks Russell and Paul,

I got it working now by adding the stop logging button and reducing the “usBetweenReadings” from 10 seconds to 1 second.

I also upgraded the firmware to v2.10.

I had a few questions regarding configuring the Artemis over USB-C serial. I am using Teraterm at 115.2k 8N1 and it appears that the changes I am making via the user menu are not reflecting on the OLA_settings.txt file that is written to the micro SD. After making the changes, I press ‘q’ to quit and turn off the Artemis, but it is not saving any of the changes I make to the SD card. Is there a different way to save the changes I make on Teraterm?

Thanks,
Jorge

5

Hi Jorge (@jimboi9 ),

Make sure you fully exit the menu after changing the settings. The changes are only saved as you exit the menu and the firmware returns to logging data. If you Quit without exiting, the changes aren’t saved - by design.

Best wishes,
Paul

1 Like
6

Thanks Paul,

For some reason, the RTC time I manually set is not saving, even after pressing ‘x’ to exit the menu. The timestamp on my serial log files show “01/01/2000,00:00:01.31“ as the first timestamp, and looking at the SD card files, it seems only OLA_deviceSettings.txt has its date modified tab set to the correct date (picture attached). If you have any tips on how to fix this I would greatly appreciate it. Thanks

image
image932×262 7.74 KB

7

Hi Jorge (@jimboi9 ),

Once the RTC is set, it should keep good time. But the RTC will reset if you disconnect the power without first putting the Apollo3 into deep sleep. There is some advice in the “Low Power Considerations” section of the Hookup Guide - link below.

After you’ve set the RTC, any subsequent serialLog timestamps should be correct…

I hope this helps,
Paul

1 Like