Complete
over 4 years ago

WERETECH-7776, JAZZ-2402, HESPER-2917, BERLIN-2552

Edge530 datafield ANT communication not work after the device restart

Hey!

I have a datafield which showing my external sensor`s data using ANT communication. It is flawlessly working on Edge 520/520plus since a year. 

If I set my datafield on Edge 530 and start it, it works perfectly. However if I restart the Edge and start the datafield it doesn`t communicate with my sensor, not showing any data. 

If I swap the datafield to another one, restart the device, swap back, and start it, it is working until I restart the device again.

I don`t know how to debug this problem. Is there anyone who met the same problem?  Is there a bug in my program or in Edge 530?

Thanks in advance! :)

DBezzeg
  • over 5 years ago in reply to PROFGRUEN

    IQ Ebike field does not work together with Garmin ebike sensor - which you have connected! See both datafields at the bottom!
    You must delete - or disable at least the Garmin ebike sensor!

  • over 5 years ago in reply to mcinner1

    Short question please - I uploaded the app on my mobile and connected to 1030 Plus - can insert connectiq- 0/10 datafield  - Ebike Field then but Edge 1030 Plus shows E-bike and no text (should be mode as text + battery level). Know I am the stupid guy in this Forum with my new 1030 Plus - sorry - but kindly ask for advice how device get data correctly from my Specialized  Kenevo (1. Gen)

    Thank you in advance

  • over 5 years ago

    I can report the same problem on Edge 1030 v.9.50. Sometime it loses the contact to the Levo and connects agagin after short time.

  • over 5 years ago in reply to Jan Čapek

    >>>How does the Ebike Field behave on your devices? Thanks!

    Behaves without problems on both my devices:
    Edge 1030 v9.50
    Edge 1030 PLUS v.2.30

    Sometimes - not very often - it loses contact to Levo, but connects self a minute (or so) after that.

  • over 5 years ago in reply to Jan Čapek

    Hey! My issue with normal ANT communication is solved with a firmware update. I can't say anything about the ANT+, but I guess it is also solved. :)