Loosing time Marks

[lanzo]

I have a new problem I never had in the last year, i don’t remember if it began after upgrading firmware, I have v2.11.0.
In the last 6 surveys (700/1200 pictures) the number of the pictures is not the same as in the log, sometimes is ok, sometimes the log is missing, I see it creates more Rinex logs than number of flights/times I turn on the plane.
what should I check?
Thank you

Simple system report

app version: 2.11.0-r0
'wifi_status, interface: wlan0':
- Client state
- IP address: 192.168.1.108
  mac address: 90:b6:86:09:d5:cd
  ssid: RT
base mode:
  base coordinates:
    accumulation: '2'
    antenna offset:
      east: '0'
      north: '0'
      up: '0'
    coordinates:
    - '0'
    - '0'
    - '0'
    format: llh
    mode: single-and-hold
  output:
    enabled: false
    format: rtcm3
    path: tcpsvr://:9000#rtcm3
    type: tcpsvr
  rtcm3 messages:
    '1002':
      enabled: true
      frequency: '1'
    '1006':
      enabled: true
      frequency: '0.1'
    '1008':
      enabled: false
      frequency: '1'
    '1010':
      enabled: true
      frequency: '1'
    '1019':
      enabled: false
      frequency: '1'
    '1020':
      enabled: false
      frequency: '1'
    '1097':
      enabled: false
      frequency: '1'
    '1107':
      enabled: false
      frequency: '1'
    '1117':
      enabled: false
      frequency: '1'
    '1127':
      enabled: false
      frequency: '1'
bluetooth:
  discoverable: false
  enabled: false
  pin: '***'
camera:
  duty cycle: 20
  enable: false
  period: 2
  polarity: true
correction input:
  input2:
    enabled: false
    format: rtcm3
    path: ttyMFD2:38400:8:n:1:off
    send position to base: 'off'
    type: serial
  input3:
    enabled: false
    format: rtcm3
    path: :9028
    type: tcpsvr
logging:
  base:
    format: RINEX
    started: false
    version: '3.03'
  correction:
    format: RINEX
    started: false
    version: '3.03'
  interval: 86400
  overwrite: true
  raw:
    format: RINEX
    started: true
    version: '3.03'
  solution:
    format: ERB
    started: false
    version: null
position output:
  output1:
    enabled: false
    format: erb
    path: ttyMFD2:38400:8:n:1:off
    type: serial
  output2:
    enabled: false
    format: llh
    path: :2013
    type: tcpsvr
  output3:
    enabled: true
    format: llh
    path: :2014
    type: tcpsvr
  output4:
    enabled: true
    format: llh
    path: :2015
    type: tcpsvr
rtk settings:
  elevation mask angle: '15'
  glonass ar mode: 'on'
  gps ar mode: fix-and-hold
  max horizontal acceleration: '1'
  max vertical acceleration: '1'
  positioning mode: kinematic
  positioning systems:
    compass: false
    galileo: false
    glonass: false
    gps: true
    qzs: true
    qzss: false
    sbas: true
  snr mask: '35'
  update rate: '10'

[tatiana.andreeva]

Hi @lanzo,

Thanks for the report! We’ll look into the issue.

Could you please currently use logging of raw data in UBX format? There are no problems with time marks for UBX logs.

[lanzo]

Dear Tatiana, I have downloaded and converted the UBX log and I get the same number of pictures

[lanzo]

It seems that is missing the take off, I can only see the landing in this graphic
but even without strenght signal it must save timemarks as I test it inside the house and it works

first picture camera time / reach time: 11:06 / 14:07:35.285
latest picture camera time / reach time: 12:17 / 15:18:54.210

[lanzo]

Last picture seems ok

First picture seems not ok

I have checked the APM LOG and it shows the correct number of pictures ( I use 2 cables from the camera, one goes to pixhawk and other goes to Reach)

This is the flight log from MP, you can see it shows the takeoff while the reach not, (I have waited for the reach to blink green before takeoff )

[b_airben (ReStudio)]

Curious about this issue as well-

It was documented in 2017 that certain settings caused missing events (see here)

Has this been resolved with Reachview updates, or is that chart still the only reliable settings?

[lanzo]

I use GPS and SBAS @ 10hz, working well for a lot of time, but the problem here is the first part of the flight is missing, not just the time marks.
Today I have updated to 2.14.0-r0, build new adapter and double checked everything, tomorrow I will try again, I have a lot of succesful surveys with this plane, I think the only thing I have changed is the reach firmware.

[tatiana.andreeva]

Hi @lanzo,

Please try with standard configurations for time marks logging in our docs.

Let us know about the flight result.

[b_airben (ReStudio)]

Are there plans to provide more standard configurations in the future, or is this hardware limited?

[tatiana.andreeva]

Hi @b_airben,

These configurations were provided depending on the transmitted data size and the update frequency. If you specify Reach in another way, there is a big chance you’ll lose some time marks.

[b_airben (ReStudio)]

Thanks, I take that to read ‘hardware limited’.

In other words, at no time in the future will I be able to use GPS+GLONASS+GALILEO at 5 Hz (for example) with time marks, regardless of Reachview improvements?

[tatiana.andreeva]

In the meantime, it’s hardware limited.