likwid_courage
New member
I'm having an issue with saving data to a uSD on a Teensy 3.6, and more correctly reading back the data.
My main problem is looking back at the text file data, instead of seeing a collimated list, I see a huge string of what appears to be special and Chinese/Japanese/Korean characters.
I have the Teensy payload reading and recording a plethora of sensors (PM, pressure, temperature, etc.), as well as sending a signal to a transistor that will in turn open a separately powered solenoid to allow for the collection of an air sample. While I could read and trigger the opening of a solenoid valve with a second Teensy 3.2 in real time (communication via XBee radio), all of the data was being stored on a uSD card on the 3.6. No filenames or other files seem to be effected, so I don't think it's a corrupted SD card. All of the data/variables were stored as strings, which is what I'm leaning towards the issue being. Overall, the Teensy payload ran for about 10 hours straight off of a 9-volt battery (changing the battery once, but which I think was a crash, not the 9-volt dying).
So my big question is:
1. Is there any way to recover and/or make sense of the data that was being saved to the text file?
and
2. What might cause this to happen?
I'm attaching the sketch that was being used for reference, and will be around to answer questions as I'm sure I left out a lot as I'm a little frantic in trying to fix the issue (hopefully possible).
The only things I can think it might be due to are a crash of the Teensy, relying on the string variable, or possibly the large uSD card at 32gb. Any help or insight is greatly appreciated!
My main problem is looking back at the text file data, instead of seeing a collimated list, I see a huge string of what appears to be special and Chinese/Japanese/Korean characters.
I have the Teensy payload reading and recording a plethora of sensors (PM, pressure, temperature, etc.), as well as sending a signal to a transistor that will in turn open a separately powered solenoid to allow for the collection of an air sample. While I could read and trigger the opening of a solenoid valve with a second Teensy 3.2 in real time (communication via XBee radio), all of the data was being stored on a uSD card on the 3.6. No filenames or other files seem to be effected, so I don't think it's a corrupted SD card. All of the data/variables were stored as strings, which is what I'm leaning towards the issue being. Overall, the Teensy payload ran for about 10 hours straight off of a 9-volt battery (changing the battery once, but which I think was a crash, not the 9-volt dying).
So my big question is:
1. Is there any way to recover and/or make sense of the data that was being saved to the text file?
and
2. What might cause this to happen?
I'm attaching the sketch that was being used for reference, and will be around to answer questions as I'm sure I left out a lot as I'm a little frantic in trying to fix the issue (hopefully possible).
The only things I can think it might be due to are a crash of the Teensy, relying on the string variable, or possibly the large uSD card at 32gb. Any help or insight is greatly appreciated!