Willkommen, Gast
Benutzername: Passwort: Angemeldet bleiben:
  • Seite:
  • 1
  • 2

THEMA:

JAVA/ANDROID receiver/sensor update program 24 Apr 2017 18:42 #7

  • Ludovico
  • Ludovicos Avatar Autor
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Beiträge: 5
  • Dank erhalten: 1
That truly would be the ultimate solution to this issue, but I'm afraid it should be almost impossible to enthuse the developers at JETI to put your idea into practice: On the one hand, it appears to be rather complicated/costly to implement a data link protocol and to keep the already existent high performance communication protocol for the exchange of control commands at the same time. On the other hand, the sheer existence of a wireless update routine would definitely be an incalculable security risk for many professional/commercial UAV applications.

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

Updates 25 Apr 2017 14:29 #8

  • Miko
  • Mikos Avatar
  • Offline
  • Gold Boarder
  • Gold Boarder
  • Beiträge: 183
  • Dank erhalten: 9
Updates Via RC droid box (bluetooth) will be fine for TX and RX/CBox/sensors already on board of our planes,Taking advantage of the Duplex features ?
M I K O

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

JAVA/ANDROID receiver/sensor update program 25 Feb 2018 09:31 #9

  • Ludovico
  • Ludovicos Avatar Autor
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Beiträge: 5
  • Dank erhalten: 1
Even though there doesn't seem to be much interest in this topic, I can nonetheless report that some progress has been made since the last answer to this thread. To avoid unnecessary tempering with my smartphone, I decided to write a short and simple routine for my raspberry pi (single-board computer) to manage receiver updates.

Equipped with a small battery, this credit card sized computer is quite handy: Simply plug in the USB-adapter, connect the cable to your receiver, wait for the status light to start flashing, unplug your receiver and that’s it - the raspberry pi automatically restarts the update program, hence this process can be repeated as often as you please.

However, since there still is only a Windows version available, things do not run 100% smooth using WINE and Arch Linux - according to the error log there (as usual) are some issues related to the emulated update program as well as the communication between the USB adapter and WINE. Of course, I could bother to implement this in a Windows virtual machine to get rid of the WINE errors but I am quite certain, that the adapter issues would prevail, which limits the range of applicability of this (maybe) unreliable update procedure to expendable foamies and very cheap fun models, and not the desired target group.

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

  • Seite:
  • 1
  • 2
Ladezeit der Seite: 0.211 Sekunden
Powered by Kunena Forum