Hi forum members.
I have a couple of niggly items I have been unable to solve so thus the call for help.
1. All the CSV files on my SD card appear to have the correct data etc but the files are all with the same date. January 1st 2000. Am I missing something to get the dates corrected.
The online csv converter works up until I load the file then it says wait. And wait, and wait, and wait. I get a little greyed out stop sign over the pointer on my mouse so I figure its not working. Does anyone use another csv - kml converter. If so what or where and any settings I need to change to get this to work.
My gps is working perfectly, Im not sure about the accelerometers yet as I have been unable to view a kml file generated with my data.
All help greatly appreciated people.
Cheers.
Kiwi53.
CSV to KML conversion
Re: CSV to KML conversion
Ok, 
Im getting a little bit brassed off with the silence on this problem. Im finding a lot of issues and I'm not sure they are of my doing.
First and foremost the CSV files being generated have no header column. I have copied another CSV from a system we use daily and the difference is chalk and cheese.
YYYY-MM-DD hh:mm:ss.s Variable Event Value
10/3/14 42:53.4 logging stopped
YYYY-MM-DD hh:mm:ss.s Variable Event Value
10/3/14 42:53.5 CLI_Zone LOG_TIMER1_EXPIRED_EVENT -1
10/3/14 42:53.5 r_WaterPattern LOG_TIMER1_EXPIRED_EVENT -1
10/3/14 42:53.5 r_SpeedIndication LOG_TIMER1_EXPIRED_EVENT -1
10/3/14 42:53.5 FlowRate LOG_TIMER1_EXPIRED_EVENT -1
10/3/14 42:53.5 DailyFlowTotal LOG_TIMER1_EXPIRED_EVENT 72335
10/3/14 42:53.5 LatitudeLog LOG_TIMER1_EXPIRED_EVENT -22.851415
10/3/14 42:53.5 LongitudeLog LOG_TIMER1_EXPIRED_EVENT -69.347423
10/3/14 42:53.5 WaterDensity LOG_TIMER1_EXPIRED_EVENT 2
10/3/14 42:53.5 Paused LOG_TIMER2_EXPIRED_EVENT 1
10/3/14 42:53.5 r_HydraulicPressure LOG_TIMER2_EXPIRED_EVENT -1
10/3/14 42:53.5 HydraulicFluidTemperature LOG_TIMER2_EXPIRED_EVENT 117
10/3/14 42:53.5 r_DCM4_TShoot_PulsesPerRev LOG_TIMER2_EXPIRED_EVENT -1
10/3/14 42:53.5 r_DCM4_TShoot_SupplyVolts LOG_TIMER2_EXPIRED_EVENT -1
10/3/14 42:53.5 r_DCM4_TShoot_GearRatio LOG_TIMER2_EXPIRED_EVENT -1
10/3/14 42:53.6 r_DCM4_TShoot_RPM LOG_TIMER2_EXPIRED_EVENT -1
As you can see there are five columns with the date and time. being the first two. Without these any CSV file is useless.
Now lets look at a freematics CSV file.
55700119 10 12122040
0 D 0
0 A -2365924
0 B -7040242
0 C 24
52 111 20
62 10C 1465
59 10D 0
14 10 12122060
0 D 0
0 A -2365924
0 B -7040242
0 C 24
39 104 66
Pretty obvious there is something wrong. No date, no time and the data headers are gobbledegook. What is A, B, C, 10D 111, etc etc. No CSV converter can make anything out of that.
Stanley your system has huge potential especially in fleet vehicle blackbox data recording but as it stands out of the box its not living up to expectations. Can you give me a heads up on why the data I have is not usable and what I can do about it. I want this system to work because I see potential with it. It just needs some tweaking to make it user friendly.
The test vehicle is a Ford F150 Platinum 2014 model. On boot up I get all green arrows on the data fields to be recorded etc on the screen.
Can you help please mate.....
Im getting a little bit brassed off with the silence on this problem. Im finding a lot of issues and I'm not sure they are of my doing.
First and foremost the CSV files being generated have no header column. I have copied another CSV from a system we use daily and the difference is chalk and cheese.
YYYY-MM-DD hh:mm:ss.s Variable Event Value
10/3/14 42:53.4 logging stopped
YYYY-MM-DD hh:mm:ss.s Variable Event Value
10/3/14 42:53.5 CLI_Zone LOG_TIMER1_EXPIRED_EVENT -1
10/3/14 42:53.5 r_WaterPattern LOG_TIMER1_EXPIRED_EVENT -1
10/3/14 42:53.5 r_SpeedIndication LOG_TIMER1_EXPIRED_EVENT -1
10/3/14 42:53.5 FlowRate LOG_TIMER1_EXPIRED_EVENT -1
10/3/14 42:53.5 DailyFlowTotal LOG_TIMER1_EXPIRED_EVENT 72335
10/3/14 42:53.5 LatitudeLog LOG_TIMER1_EXPIRED_EVENT -22.851415
10/3/14 42:53.5 LongitudeLog LOG_TIMER1_EXPIRED_EVENT -69.347423
10/3/14 42:53.5 WaterDensity LOG_TIMER1_EXPIRED_EVENT 2
10/3/14 42:53.5 Paused LOG_TIMER2_EXPIRED_EVENT 1
10/3/14 42:53.5 r_HydraulicPressure LOG_TIMER2_EXPIRED_EVENT -1
10/3/14 42:53.5 HydraulicFluidTemperature LOG_TIMER2_EXPIRED_EVENT 117
10/3/14 42:53.5 r_DCM4_TShoot_PulsesPerRev LOG_TIMER2_EXPIRED_EVENT -1
10/3/14 42:53.5 r_DCM4_TShoot_SupplyVolts LOG_TIMER2_EXPIRED_EVENT -1
10/3/14 42:53.5 r_DCM4_TShoot_GearRatio LOG_TIMER2_EXPIRED_EVENT -1
10/3/14 42:53.6 r_DCM4_TShoot_RPM LOG_TIMER2_EXPIRED_EVENT -1
As you can see there are five columns with the date and time. being the first two. Without these any CSV file is useless.
Now lets look at a freematics CSV file.
55700119 10 12122040
0 D 0
0 A -2365924
0 B -7040242
0 C 24
52 111 20
62 10C 1465
59 10D 0
14 10 12122060
0 D 0
0 A -2365924
0 B -7040242
0 C 24
39 104 66
Pretty obvious there is something wrong. No date, no time and the data headers are gobbledegook. What is A, B, C, 10D 111, etc etc. No CSV converter can make anything out of that.
Stanley your system has huge potential especially in fleet vehicle blackbox data recording but as it stands out of the box its not living up to expectations. Can you give me a heads up on why the data I have is not usable and what I can do about it. I want this system to work because I see potential with it. It just needs some tweaking to make it user friendly.
The test vehicle is a Ford F150 Platinum 2014 model. On boot up I get all green arrows on the data fields to be recorded etc on the screen.
Can you help please mate.....
Re: CSV to KML conversion
The date of the created file is not modified as I didn't find a way to do so with Arduino SD library. I hope I was wrong.
Re: CSV to KML conversion
Stanley,
Many thanks for taking a look. My first problem is all the CSV files are being recorded on the SD card with the same date of Jan 1st 2000. I would have expected the file date to be logged by the gps.
DD-MM-YY-HH-MM-SS
How can we sort that one out first mate?
Regards
Kiwi53
Many thanks for taking a look. My first problem is all the CSV files are being recorded on the SD card with the same date of Jan 1st 2000. I would have expected the file date to be logged by the gps.
DD-MM-YY-HH-MM-SS
How can we sort that one out first mate?
Regards
Kiwi53
Re: CSV to KML conversion
I appear to be having the same or at least a similar problem.
The .CSV files that my megalogger is creating do not have values for A, B, C... as defined in the datalogger.h therefore when converting them the KML has no GPS data just a bunch of info from the OBDII PID's which by itself is useless.
I also found that the file I'm converting has to be in the same location as the data2kml.exe otherwise google earth will get an error.
Hope you can help.
PS: All other functions of the megalogger appear to be working other than Batt Voltage always being 41.0V
The .CSV files that my megalogger is creating do not have values for A, B, C... as defined in the datalogger.h therefore when converting them the KML has no GPS data just a bunch of info from the OBDII PID's which by itself is useless.
I also found that the file I'm converting has to be in the same location as the data2kml.exe otherwise google earth will get an error.
Hope you can help.
PS: All other functions of the megalogger appear to be working other than Batt Voltage always being 41.0V
Re: CSV to KML conversion
Files are not dated as there is no API for doing this in Arduino's SD library.
Re: CSV to KML conversion
If you GPS data in KML, check if there is GPS data in CSV. If not, GPS might not be detected or GPS data logging is disabled.