I2C cable length, frequency, etc.

[André Kjellstrup]

What are the max length of I2C bus ? 
Is the frequency 100kHz , or higher ?
With the supplied cable type, how many pF/m are we at ?

I do not ask for absolute maximums, but I2C error free operation.

[Craig Elder]

http://www.nxp.com/documents/user_manual/UM10204.pdf

I

2C-bus specification and user manual

Rev. 6 — 4 April 2014 U

Page 60

7.5 Wiring pattern of the bus lines

In general, the wiring must be chosen so that crosstalk and interference to/from the bus 

lines is minimized. The bus lines are most susceptible to crosstalk and interference at the 

HIGH level because of the relatively high impedance of the pull-up devices.

If the length of the bus lines on a PCB or ribbon cable exceeds 10 cm and includes the 

VDD and VSS lines, the wiring pattern should be:

SDA _______________________

VDD ________________________

VSS ________________________

SCL _______________________

If only the VSS line is included, the wiring pattern should be:

SDA _______________________

VSS ________________________

SCL _______________________

These wiring patterns also result in identical capacitive loads for the SDA and SCL lines. 

If a PCB with a VSS and/or VDD layer is used, the VSS and VDD lines can be omitted.

If the bus lines are twisted-pairs, each bus line must be twisted with a VSS return. 

Alternatively, the SCL line can be twisted with a VSS return, and the SDA line twisted with 

a VDD return. In the latter case, capacitors must be used to decouple the VDD line to the 

VSS line at both ends of the twisted pairs.

If the bus lines are shielded (shield connected to VSS), interference is minimized. 

However, the shielded cable must have low capacitive coupling between the SDA and 

SCL lines to minimize crosstalk.

Pay attention to the 10cm bit.  We mostly get away with longer wires and can tolerate a few errors but don't take it for granted that it is not going to be problematic 

--
You received this message because you are subscribed to the Google Groups "drones-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Rick Std]

...arg... I'm all confuse again... I was planning on extending the I2C cables on my PixHawk in order to install the pito tube on the wing of my airplane.  But 10 cm is quite short wires compare to 30-40cm+ in order to fix on the wing.... should I rather place the pito on the side of the fuselage? if so. what would be acceptable spacing between the pito tube and the fuselage? (turbulance).  I can't install on the nose. I use a SkyEye from HK and the camera dome is there. For the record, I'm using 3DR digital airspeed sensor.  And of course my PixHawk is a 3DR genuine. :)  thanks in advance for the help.

-Eric 

[Craig Elder]

We typically run 30 - 45cm I2C wires without problems.  I just want to point out that people need to take the limitations of I2C into consideration rather than run 2m of it on a large plane.

[Rick Std]

Thank you Craig. Appreciate your response. So I will stick the Pito Tube on the wing.

[David Pawlak]

I guess certain sensors can get away with using I2C, accelerometers, maybe even magentometers. But peripherals like sonar, laser, airspeed, (static ports) ;) proximity, should really have a longer reaching interface.

I think we have adapted to the inherent chip interface in some cases because it's there, without really engineering a complete solution which depends on use and placement factors.

How much does a microcontroller cost these days, or the efforts to create a simple firmware translation?

Although PPM and SBUS are usually used for output ADC, the APM has PPM/SBUS input. (The future will likely bring those as output options). So perhaps, one could devise and input daisy chain scheme which inserts the device analog in a prposed channel slot.

[Kevin Hester]

> I think we have adapted to the inherent chip interface in some cases because it's there, without really engineering a complete solution which depends on use and placement factors.

> How much does a microcontroller cost these days, or the efforts to create a simple firmware translation?

I think there is some general consensus that CAN is the way to go here (good distance, great noise immunity, cheap cortex-m0 MCUs with built in transceivers/adcs/dacs).  I think mostly no one has gotten around to completing the various bits in pieces though I gather from reading posts progress is being made.

[john...@gmail.com]

No need to re-invert. The CAN bus is the standard for robust sensor interfacing in potentially noisy environment like the automotive industry etc. What is needed is a simple and cheap breakout board for adding CAN bus to existing sensors.

- JAB

[André Kjellstrup]

How can I log /display I2C errors ?
- I built it with minimal lengths, as usual - but the I2C airspeed, and use of the I2C "splitter" (the PCB that came with pixhawk) makes me wish to verify everything is ok.

[Kevin Hester]

Hi Andre,

That's actually one of the weaknesses of i2c for this application: The hw interface is assumed to be error free by design/verification.  Some drivers have ad hocish retry algorithms but there is no standard crc and most i2c devices don't provide such a thing.   For some types of devices it would be possible to do some retries, error counts.

The only way I'm aware of to be sure is to look at SCL/SCA with a scope.

On Sat, May 24, 2014 at 10:35 AM, André Kjellstrup <andre.kj...@gmail.com> wrote:

How can I log /display I2C errors ?
- I built it with minimal lengths, as usual - but the I2C airspeed, and use of the I2C "splitter" (the PCB that came with pixhawk) makes me wish to verify everything is ok.

--

[Randy Mackay]

     In ArduCopter (and probably arduplane) the PM (performance monitor) dataflash message has a column that shows the number of I2C errors.  I assume it works although I don't remember ever seening it be non-zero... but then I've never looked at a log where we thought there might be I2C errors.

-Randy

[Jaime Machuca]

Anyone know where I can download an older version of mission planner? the latest is broken for image geotagging with the time offset and I need to urgently tag some images?

Jaime Machuca 

[Michael Oborne]

Jamie, can you tell me where its failing?

 

Michael

--

[Aytek Canak]

http://firmware.diydrones.com/Tools/MissionPlanner/

On Sun, May 25, 2014 at 9:03 PM, Jaime Machuca <ja...@droidika.com> wrote:

Anyone know where I can download an older version of mission planner? the latest is broken for image geotagging with the time offset and I need to urgently tag some images?

Jaime Machuca 

[Jaime Machuca]

Hi Michael, 

Its failing when it tries to parse the log file for the locations, it goes to line 885 in georefimage.cs.

 if (shotLocation == null)
                {
                    TXT_outputlog.AppendText("File time not found in Log.  Aborting..... \n");
                    return null; 
                }

From the comments on the code, I assume its looking for CAM Messages on the log, but since I am not using them thats why it fails. 

I don’t have much time this week as I am giving a training on how to do a mapping mission, and with this not working its a bummer for me. I am preping the course now so I don’t have much time to look into the code this week otherwise I would.

Jaime Machuca Mercado

[Josh Welsh]

Jaime,

 

I’m sure Mike will be able to help with your problem, but, previous versions of MP can be found here:

 

http://firmware.diydrones.com/MissionPlanner/

 

 

[Jaime Machuca]

Thanks everyone, the I used the previous version with out problems so I got the images geotagged. I’ll try to see if I can find out whats going on.

Jaime Machuca Mercado

[MikeRover]

I've had reasonable success with Cat 5 (or maybe 6) network cable.  Each of the solid coloured wires from a pair is a signal (VDD, SCL, SDA) and all the white striped ones are joined to ground (VSS), as per:

 

"If the bus lines are twisted-pairs, each bus line must be twisted with a VSS return. "

[Jaime Machuca]

Hi Michael, 

I took a closer look at the code, it seems that the function that is failing is:

private VehicleLocation LookForLocation(DateTime t, Dictionary<long, VehicleLocation> listLocations)

It wants to have the time on the picture exactly match the GPS logged message time. This does not work for the case when the picture time does not exactly match one of the GPS log messages, I am not sure how this was done before. Or maybe there is a problem with the time conversion for the picture time. I’ll keep looking.

Jaime Machuca Mercado

On May 25, 2014, at 6:05 PM, Michael Oborne <mic...@oborne.me> wrote:

[Jesus Alvarez]

Hola Jaime.

I wrote the georef new code and Michael merged it in.
So if anything is failing it is likely my fault :(

Did you selected in the radio buttons the Time offset mode?

I tested it and it worked for me.

What fw version generated the log? Is it a dataflash log or a tlog?
If you can attach it I can look at the problem this afternoon.

The function you refer goes searching for GPS time messages into the log for a given time. If it does not find it, it returns null and gives the message you are seeing.

I guess you may be using old version logs or less GPS message refresh times.

However it has to work at least as the last version so please attach that log and either michael or me will see what happens.

Sorry for the inconvenience!

[Jesus Alvarez]

Jaime.

I think I know what is failing and the way to fix it.

If you send me the log to test it, I'll have the fix ready today.

Jesus

[Jaime Machuca]

Hi Jesus, I'm on the field all day today I will not be able to send the log until late today. I did check the radio button, and the offset is calculated correctly.
One thing to note is that the offset In this particular data set is very large because the camera was new and the date was set wrong to jan 1, 2013.
The old mission planner worked, but the new one breaks at the function I meantime because the flattened time variable does not match any of the GPS locations exactly. I will upload the data set to a Dropbox later today.
And don't worry about, as long as we can fix it it's not a problem. Thanks.



Jaime Machuca

Sent from my iPhone

[Jesus Alvarez]

Jaime

I have extracted the GeoTag Part for you to test it. See if it works now so I can create a pull request to Michael

These small extract GeoTagAPM only works with dataflash logs.

https://drive.google.com/file/d/0BzRzbaLTcOpbWXN2aHZIdkxoR3M/edit?usp=sharing

good night

[Jaime Machuca]

Thanks Jesus, I’ll try it out. I am using the Dataflash logs, What was the change?

Jaime Machuca Mercado

CTO | Droidika | www.Droidika.com

Mail. Ja...@Droidika.com

Tel. +52 (33) 3777 5327

Cel. +52 1 (33) 3945 3350

Este correo electrónico y cualquier archivo transmitido en él, son confidenciales y para uso exclusivo de los individuos y entidades a quienes está dirigido. Si usted no es el destinatario previsto o la persona encargada de recibirlo, y tiene por error este mensaje, queda prohibido y sin validez el uso, difusión, re-envío, reimpresión o copia. Toda oferta y/o aceptación de propuestas comerciales, celebración de contratos u otros actos tendientes a la adquisición de bienes o servicios, así como el establecimiento de cualquier clase de obligación legal para Droidika S.A. de C.V., deberá confirmarse por escrito firmado autógrafamente por funcionario competente, excepto que se cuente con un contrato vigente que autorice el uso de este medio para tales fines. Si usted recibió este correo por equivocación, favor de notificar inmediatamente por este medio a su remitente, y después borrarlo de su correo

[Jaime Machuca]

Hi Jesus, I just tried it, I get the same error. This time with a dataset with much closer offset. 

Jaime Machuca Mercado

CTO | Droidika | www.Droidika.com

Mail. Ja...@Droidika.com

Tel. +52 (33) 3777 5327

Cel. +52 1 (33) 3945 3350

Este correo electrónico y cualquier archivo transmitido en él, son confidenciales y para uso exclusivo de los individuos y entidades a quienes está dirigido. Si usted no es el destinatario previsto o la persona encargada de recibirlo, y tiene por error este mensaje, queda prohibido y sin validez el uso, difusión, re-envío, reimpresión o copia. Toda oferta y/o aceptación de propuestas comerciales, celebración de contratos u otros actos tendientes a la adquisición de bienes o servicios, así como el establecimiento de cualquier clase de obligación legal para Droidika S.A. de C.V., deberá confirmarse por escrito firmado autógrafamente por funcionario competente, excepto que se cuente con un contrato vigente que autorice el uso de este medio para tales fines. Si usted recibió este correo por equivocación, favor de notificar inmediatamente por este medio a su remitente, y después borrarlo de su correo

On May 27, 2014, at 5:20 PM, Jesus Alvarez <wja...@gmail.com> wrote:

[Jesus Alvarez]

It's extrange.

I'll take a look at the log as soon as I get home.
I have done 1ms granularity so I guess the next thing to look is a UTC / Local time problem.

[Jesus Alvarez]

Jaime

I have just checked the logs and files you provided.

There is a huge gap in the log file. That is the reason why it is failing.

I think the previous way of geotagging was more permissive and it just passed.... However it would have passed with a super-huge error from the gap onwards.

The tool is working as far as I can say. But for gaps bigger than 20 seconds it fails (which I think is normal so you are advised that there is a problem)

See here

GPS MSG - UTCMillis = 1401038147800  GPS Week =  1794  TimeMS =  62147800

GPS MSG - UTCMillis = 1401038148000  GPS Week =  1794  TimeMS =  62148000

GPS MSG - UTCMillis = 1401038148200  GPS Week =  1794  TimeMS =  62148200

GPS MSG - UTCMillis = 1401038148400  GPS Week =  1794  TimeMS =  62148400

GPS MSG - UTCMillis = 1401038148600  GPS Week =  1794  TimeMS =  62148600

GPS MSG - UTCMillis = 1401038148800  GPS Week =  1794  TimeMS =  62148800

GPS MSG - UTCMillis = 1401038172600  GPS Week =  1794  TimeMS =  62172600

GPS MSG - UTCMillis = 1401038172800  GPS Week =  1794  TimeMS =  62172800

GPS MSG - UTCMillis = 1401038173000  GPS Week =  1794  TimeMS =  62173000

GPS MSG - UTCMillis = 1401038173200  GPS Week =  1794  TimeMS =  62173200

GPS MSG - UTCMillis = 1401038173400  GPS Week =  1794  TimeMS =  62173400

GPS MSG - UTCMillis = 1401038173600  GPS Week =  1794  TimeMS =  62173600

GPS MSG - UTCMillis = 1401038173800  GPS Week =  1794  TimeMS =  62173800

[Jaime Machuca]

This does not make sense. For one thing it's not just failing with that data set, it's failing with all data sets I have that work with the previous version. And also, why would there be a 20sec gap? I never most GPS signal at any point during the flight. Would you like to do a hangout to check the other data sets, and discuss this, at the least it should work as it did before if not better. To me this is a step backward.

Jaime Machuca 

Sent from my iPhone

[Jesus Alvarez]

Jaime

Please, could check your log?

This is an extract from it

It goes from 62148800 ms to 62172600 ms. This is a gap of 23.8 seconds. 

If it was working before, I really do not know how! And if it really was, your photos were not getting accurate positions (at least from that gap on)! They were 20 seconds into the future at least. 

Did you check with the old version the photo locations on google earth with the .kml? Was it correct?

I really see no error in the GeoTag Tool. However I have a pull to michael to prevent indexes out of range in the position offsets that could occur if user enters bad offsets. But that's another story.

GPS, 3, 62148800, 1794, 11, 1.65, 20.7241818, -103.6307508, 0.52, 1446.02, 0.04, 319.95, 0.04, 445230

ATT, 445241, 0.00, 4.49, 0.00, 4.66, 81.87, 81.87

IMU, 445241, -0.01001418, -0.004734617, -0.003263175, 0.7599961, -0.7940483, -9.82591

IMU2, 445241, -0.007786042, -0.004117243, 0.003705116, 0.6945162, -0.6889598, -9.866691

ATT, 445261, 0.00, 4.49, 0.00, 4.67, 81.85, 81.85

IMU, 445261, -0.00905093, -0.002608657, -0.001257333, 0.7483183, -0.7471708, -9.818783

IMU2, 445261, 0.006655274, 0.004870858, 0.008279265, 0.7787337, -0.6393341, -9.849605

ATT, 445281, 0.00, 4.49, 0.00, 4.67, 81.84, 81.84

IMU, 445281, -0.009240795, -0.004527945, 0.003228092, 0.7796818, -0.7643572, -9.848997

IMU2, 445281, 0.001868421, -0.004122702, 0.002057766, 0.7580693, -0.6475583, -9.734026

MAG, 445290, 70, -228, 304, -161, 22, 59, -2, 0, 0

MAG2, 445290, 23, -379, 626, 0, 0, 0, 0, 0, 0

CTUN, 445301, 0, 0, 0, 0, 0.52, 0.84, 0.00, 0.00, 0, -12

ATT, 445302, 0.00, 4.49, 0.00, 4.67, 81.84, 81.84

RCIN, 445302, 1514, 1514, 1095, 1092, 1233, 1514, 1685, 1528

RCOU, 445302, 1165, 1165, 1165, 1165, 1165, 1165, 0, 0

ATT, 445302, 0.00, 4.49, 0.00, 4.67, 81.84, 81.84

IMU, 445302, -0.008922946, -0.005220063, 0.004071635, 0.7832175, -0.8088629, -9.814036

IMU2, 445302, 0.001122913, -0.008787472, 0.01316254, 0.7780238, -0.6993307, -9.793553

ATT, 445321, 0.00, 4.49, 0.00, 4.67, 81.83, 81.83

IMU, 445321, -0.008134967, -0.003633115, 0.001733934, 0.8034207, -0.8317709, -9.778274

IMU2, 445321, 0.004353009, -0.003576964, 0.003093665, 0.7113184, -0.7019423, -9.809234

ATT, 445340, 0.00, 4.49, 0.00, 4.67, 81.82, 81.82

IMU, 445340, -0.01020194, -0.004486002, -0.0009244457, 0.7522605, -0.7388979, -9.807453

IMU2, 445340, 0.005672947, -0.003082974, 0.005341287, 0.8085349, -0.6325233, -9.765627

ATT, 445360, 0.00, 4.49, 0.00, 4.67, 81.81, 81.81

IMU, 445360, -0.01023212, -0.002962284, -0.001139558, 0.7673458, -0.7882153, -9.797329

IMU2, 445360, 0.0005416367, 0.002058443, 0.006500769, 0.7297944, -0.6859856, -9.737373

ATT, 445381, 0.00, 4.49, 0.00, 4.67, 81.80, 81.80

IMU, 445381, -0.01082667, -0.001781754, 0.00110154, 0.7972059, -0.789917, -9.799644

IMU2, 445381, 0.003691431, -0.005165651, 0.006827269, 0.707634, -0.7469073, -9.782754

MAG, 445390, 71, -227, 305, -161, 22, 59, -2, 0, 0

MAG2, 445390, 24, -380, 627, 0, 0, 0, 0, 0, 0

EV, 11

D32, 9, 7560

CMD, 9, 0, 16, 0, 0, 0.00, 20.7241745, -103.6307444

EV, 10

CTUN, 468900, 0, 0, 0, 0, 0.88, -0.07, 0.00, 0.00, 0, 0

ATT, 468901, 0.00, 4.58, 0.00, 4.30, 75.60, 75.60

RCIN, 468901, 1514, 1514, 1095, 1931, 1233, 1514, 1518, 1528

RCOU, 468901, 1165, 1165, 1165, 1165, 1165, 1165, 0, 0

ATT, 468901, 0.00, 4.58, 0.00, 4.30, 75.60, 75.60

IMU, 468901, -0.008115757, -0.00244531, 0.0004554689, 0.7700554, -0.8180211, -9.798737

IMU2, 468901, 0.003771398, -0.0001931861, 0.00761604, 0.8008318, -0.7090201, -9.803809

ATT, 468921, 0.00, 4.58, 0.00, 4.30, 75.60, 75.60

IMU, 468921, -0.009079746, -0.00254456, 0.0006879121, 0.7939475, -0.8112305, -9.82114

IMU2, 468921, 0.004538018, 0.002478842, 0.008476734, 0.6838053, -0.7104659, -9.800569

ATT, 468941, 0.00, 4.58, 0.00, 4.30, 75.60, 75.60

IMU, 468941, -0.009776918, -0.003014278, 1.055934E-05, 0.7842826, -0.805331, -9.826738

IMU2, 468941, 0.003443377, 0.003390864, 0.005154572, 0.7665074, -0.7033993, -9.85812

ATT, 468961, 0.00, 4.58, 0.00, 4.30, 75.60, 75.60

IMU, 468961, -0.009499857, -0.002401602, 0.0004108706, 0.7890722, -0.7990544, -9.815866

IMU2, 468961, 0.0004450064, 0.002097912, 0.008355724, 0.7923467, -0.637825, -9.868955

ATT, 468981, 0.00, 4.58, 0.00, 4.30, 75.60, 75.60

IMU, 468981, -0.009544331, -0.002984196, -6.51218E-05, 0.7965363, -0.8044269, -9.822542

IMU2, 468981, 0.001091151, -0.001603954, 0.007472544, 0.737875, -0.7284266, -9.833819

GPS, 3, 62172600, 1794, 11, 1.65, 20.7241748, -103.6307439, 0.83, 1445.91, 0.18, 319.95, -0.08, 468990

MAG, 468990, 71, -223, 304, -161, 22, 59, -2, 0, 1

MAG2, 468990, 26, -379, 623, 0, 0, 0, 0, 0, 0

CTUN, 469000, 0, 0, 0, 0, 0.83, 0.01, 0.00, 0.00, 0, 0

ATT, 469001, 0.00, 4.58, 0.00, 4.30, 75.60, 75.60

RCIN, 469001, 1514, 1514, 1095, 1931, 1233, 1514, 1518, 1528

RCOU, 469001, 1165, 1165, 1165, 1165, 1165, 1165, 0, 0

ATT, 469001, 0.00, 4.58, 0.00, 4.30, 75.60, 75.60

IMU, 469001, -0.009127714, -0.00424007, 0.0003961921, 0.7733239, -0.8070641, -9.801329

IMU2, 469001, 0.003493296, -0.0008953866, 0.006257311, 0.8034247, -0.684604, -9.779648

ATT, 469020, 0.00, 4.58, 0.00, 4.30, 75.60, 75.60

IMU, 469020, -0.009337462, -0.003740072, 0.0002894299, 0.7725662, -0.7931337, -9.815335

IMU2, 469020, -0.001607405, 0.0003361851, 0.004100896, 0.7512671, -0.6901245, -9.766108

ATT, 469040, 0.00, 4.59, 0.00, 4.30, 75.59, 75.59

IMU, 469040, -0.009063104, -0.004192725, 0.000274431, 0.8001118, -0.8042656, -9.809197

IMU2, 469040, 0.001911459, -0.005378235, 0.006864864, 0.8143563, -0.7067743, -9.884753

ATT, 469060, 0.00, 4.59, 0.00, 4.30, 75.59, 75.59

IMU, 469060, -0.009280208, -0.004249778, 0.001095327, 0.7869523, -0.8121997, -9.791698

IMU2, 469060, 0.005373243, -0.00215218, 0.007621663, 0.7927004, -0.6626105, -9.725616

ATT, 469081, 0.00, 4.59, 0.00, 4.30, 75.59, 75.59

IMU, 469081, -0.009058377, -0.00449598, 0.001238782, 0.7787896, -0.8068191, -9.795875

IMU2, 469081, 0.007753529, 0.001010705, 0.007529852, 0.7812296, -0.6921726, -9.887113

MAG, 469090, 71, -226, 303, -161, 22, 59, -2, 0, 0

MAG2, 469090, 25, -379, 625, 0, 0, 0, 0, 0, 0

CTUN, 469100, 0, 0, 0, 0, 0.78, 0.03, 0.00, 0.00, 0, -1

ATT, 469100, 0.00, 4.59, 0.00, 4.29, 75.59, 75.59

RCIN, 469100, 1514, 1514, 1095, 1931, 1233, 1514, 1518, 1528

RCOU, 469101, 1165, 1165, 1165, 1165, 1165, 1165, 0, 0

ATT, 469101, 0.00, 4.59, 0.00, 4.29, 75.59, 75.59

IMU, 469101, -0.009900507, -0.004136108, 0.000701163, 0.799562, -0.837777, -9.786465

IMU2, 469101, 0.00289581, -0.004522555, 0.003664535, 0.7404348, -0.7141953, -9.859962

ATT, 469120, 0.00, 4.59, 0.00, 4.29, 75.59, 75.59

IMU, 469120, -0.009039532, -0.002750624, 0.0005620606, 0.8018644, -0.8035694, -9.843288

IMU2, 469120, 0.004564736, -0.00108527, 0.0003029099, 0.7630092, -0.7322123, -9.803256

ATT, 469141, 0.00, 4.59, 0.00, 4.29, 75.59, 75.59

IMU, 469141, -0.007995535, -0.00371173, 6.456859E-06, 0.7802728, -0.7784967, -9.799286

IMU2, 469141, 0.003657347, -0.004294004, 0.009277081, 0.7608323, -0.7327408, -9.779025

ATT, 469161, 0.00, 4.59, 0.00, 4.29, 75.59, 75.59

IMU, 469161, -0.009478418, -0.003819883, 0.0005520033, 0.7771921, -0.8105543, -9.809543

IMU2, 469161, 0.002032236, -0.004999716, 0.00544005, 0.7293742, -0.7025542, -9.799137

ATT, 469181, 0.00, 4.59, 0.00, 4.29, 75.59, 75.59

IMU, 469181, -0.01040425, -0.002503194, 0.0008824477, 0.7662454, -0.8228087, -9.791972

IMU2, 469181, 0.00528864, -0.003454588, 0.001619745, 0.7419192, -0.713057, -9.968134

GPS, 3, 62172800, 1794, 11, 1.65, 20.7241748, -103.6307436, 0.73, 1445.94, 0.12, 319.95, -0.07, 469191

[Jesus Alvarez]

By the way.

Are you using pixhawk? If so, there is a known bug in log download that create repeated entries and gaps... I always extract the SD from pixhawk to read logs...

[Jesus Alvarez]

I think I know what happens

You made in that exact point in the log a DISARM (event 11) and ARM (event 10).

There it is the gap.

I guess you are not using TRIGG DISTANCE but some intervalometer?

The thing is that there are photos taken in the middle of that gap that do not have a gps position to lock to, because there was no logging at that time (it was disarmed).

So what the tool can do to fix your problems is to ignore those photos that do not have a GPS match position in the log. That ... I can do. 

AG, 445390, 71, -227, 305, -161, 22, 59, -2, 0, 0

MAG2, 445390, 24, -380, 627, 0, 0, 0, 0, 0, 0

EV, 11

D32, 9, 7560

CMD, 9, 0, 16, 0, 0, 0.00, 20.7241745, -103.6307444

EV, 10

CTUN, 468900, 0, 0, 0, 0, 0.88, -0.07, 0.00, 0.00, 0, 0

ATT, 468901, 0.00, 4.58, 0.00, 4.30, 75.60, 75.60

[Jesus Alvarez]

Jaime

There it is for you to test 

https://drive.google.com/file/d/0BzRzbaLTcOpbdGYwT21zd2cxeTQ/edit?usp=sharing

But just a comment. The problem you are seeing is just telling you that some photos are not well aligned against the time of the log.

I have taken a look at the log and it seems that the real flight starts after those events of disarming and arming. So what I mean is that I think the offset you are setting is not the correct one. If the first part of the log has no photos, the estimated time that the Geotag tool gives you is far from the real one.

[Jaime Machuca]

Thanks Jesus, I’ll give it a try. I am using a Pixhawk, I copy the .bin files from the SD card and then convert them to .log. In the past that is I think what the tool did, ignore the pictures that did not match, in the case of the current one once it can’t find one it breaks. When I tag the photos, I get the estimated offset, then generate the locations KML and I check if the locations are correct, if they are not I can usually figure out the error in the offset from looking at the pictures and the time stamps. Then I change the estimated offset by the amount I calculated, and that usually gets me the correct geotagging. I’ll try your tool in a while and let you know. Thanks.

Jaime Machuca

[Jaime Machuca]

Hi Jesus, 

I tested it, it works great now. Thanks for the change, I think I already saw the pull request for mission planner. thanks!

Jaime Machuca Mercado

CTO | Droidika | www.Droidika.com

Mail. Ja...@Droidika.com

Tel. +52 (33) 3777 5327

Cel. +52 1 (33) 3945 3350

Este correo electrónico y cualquier archivo transmitido en él, son confidenciales y para uso exclusivo de los individuos y entidades a quienes está dirigido. Si usted no es el destinatario previsto o la persona encargada de recibirlo, y tiene por error este mensaje, queda prohibido y sin validez el uso, difusión, re-envío, reimpresión o copia. Toda oferta y/o aceptación de propuestas comerciales, celebración de contratos u otros actos tendientes a la adquisición de bienes o servicios, así como el establecimiento de cualquier clase de obligación legal para Droidika S.A. de C.V., deberá confirmarse por escrito firmado autógrafamente por funcionario competente, excepto que se cuente con un contrato vigente que autorice el uso de este medio para tales fines. Si usted recibió este correo por equivocación, favor de notificar inmediatamente por este medio a su remitente, y después borrarlo de su correo

[Jesus Alvarez]

Glad it works Jaime

Now it's on Michael's roof!