Arduino telemetry system project

Projects General Guidance
1

I want to make telemetry system with arduino. The project I have in mind will use this modules:

  • Accelerometer MPU6050 (as an input to the arduino)
  • GPS module GPS6MV2 (as an input to the arduino)
  • MicroSD card module (to storage data on a file.txt)
  • OLED display 128x32 (to display the current speed)

The basic idea is to display the current speed in the display with the information of the GPS. Also write on the microSD card the accelerations given by the accelerometer and the position, velocity and time given by the GPS, so I can export the file.txt with all the data to a excel file and process it.

My main question is: Can it be done?
And the follow up question is: What arduino should I use?
Because I was researching and I found that maybe the arduino UNO R3 have very little memory for the code, and I would have to use the MEGA.
I'm a complete beginner with arduino, but I know that if I use 4 modules, I will have to use 4 libraries at least, so I'm concerned with the arduino storage.

To resume: I want to display the current speed on a display and record all the data of the sensors on a microSD card

Thank you very much for your help

2

That is certainly doable, and the Arduino Uno is fine for what you have described so far. It would be more convenient to use an Arduino with the SD card slot on board.

Big project for a beginner, though. Get all the individual pieces working (and well understood) before tossing that salad.

Note: "telemetry" implies transmission of data somewhere else, usually by wireless means.

3

Thank you
I understand it's very difficult project for beginner, but as you said I will divide it in small parts. First of all get all the components to work individually. Then for example get the GPS and display working and in other project get the accelerometer to send data to the sd. And at the end mix all together.
The thing I'm most affraid is the final code, where I will combine all the modules projects, but is a long way to go and I'll go little y little.

4

Don’t do that, get one component working and then add in the second component and so on. This way you spot any integration issues when you know what it is, that is the last component you just added.

5

Yes yes, that's what I was trying to say. First get each component working with its own code, and after that merge all together.