Silverware Wiki

User Tools

Site Tools

Trace:
silvervise

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
silvervise [2018/01/25 12:28]
silverag 		silvervise [2018/05/16 01:53] (current)
silverag
Line 9: Line 9:
  
   * Silvervise uses the Bluetooth-low energy BTLE communication standard   * Silvervise uses the Bluetooth-low energy BTLE communication standard
-  * App works on android 4.4 and higher+  * App works on android 4.4 and higher. For Android 5 and higher, for proper BLE working, you might need to turn on GPS and location permission (if needed)
   * Display of battery, pids, and other info on the phone   * Display of battery, pids, and other info on the phone
   * A specific "App" protocol needs to be set on the quad   * A specific "App" protocol needs to be set on the quad
Line 24: Line 24:
   * **For H8 green board: ** [[https://github.com/silver13/h8mini-dual|https://github.com/silver13/h8mini-dual]]   * **For H8 green board: ** [[https://github.com/silver13/h8mini-dual|https://github.com/silver13/h8mini-dual]]
   * **For H8 blue board:** [[https://github.com/silver13/H8mini_blue_board|https://github.com/silver13/H8mini_blue_board]]   * **For H8 blue board:** [[https://github.com/silver13/H8mini_blue_board|https://github.com/silver13/H8mini_blue_board]]
-  * **For BWHOOP B-03 boards**: [[https://github.com/silver13/BoldClash-BWHOOP-B-03|https://github.com/silver13/BoldClash-BWHOOP-B-03]] (official) and [[https://github.com/silverag123/BoldClash-BWHOOP-B-03|https://github.com/silverag123/BoldClash-BWHOOP-B-03]] (unofficial - supports dual telemetry - switching between SilverVISE and Devo telemetry using gestures and without need to re-flash and with PIDs on Devo screen)+  * **For BWHOOP B-03 boards**: [[https://github.com/silver13/BoldClash-BWHOOP-B-03|https://github.com/silver13/BoldClash-BWHOOP-B-03]] (official) and [[https://github.com/silverag123/BoldClash-BWHOOP-B-03|https://github.com/silverag123/BoldClash-BWHOOP-B-03]] (unofficial - supports dual PIDs, dual telemetry - switching between SilverVISE and Devo telemetry using gestures and without need to re-flash and with PIDs on Devo screen). NFE fork also supports SilverVISE: [[https://github.com/NotFastEnuf/E011-BWHOOP-H8-Silverware|https://github.com/NotFastEnuf/E011-BWHOOP-H8-Silverware]] 
 +  * **For E011 board:** [[https://github.com/silver13/Eachine-E011|https://github.com/silver13/Eachine-E011]] (in this version of firmware, SilverVISE presents E011 as H8 quad - so image and text will be changed in E011 in next SilverVISE release)
 Special thanks to all who tried and tested application, and very big thanks to users from RC GROUPS forum who helped to develop this (listed in random order): silverxxx, MegaloRex, bikemikem, Bonaventura, SirDomsen, sammy4703, samhain616, nigelsheffield, ltwvince, Nitro123, lostmyquad, Ian444, ArbitraryNotion, Markus Gritsch, 0a23cb7af4d242, eitama, Appelmoesman and others I forget to mention (sorry :( ). Special thanks to all who tried and tested application, and very big thanks to users from RC GROUPS forum who helped to develop this (listed in random order): silverxxx, MegaloRex, bikemikem, Bonaventura, SirDomsen, sammy4703, samhain616, nigelsheffield, ltwvince, Nitro123, lostmyquad, Ian444, ArbitraryNotion, Markus Gritsch, 0a23cb7af4d242, eitama, Appelmoesman and others I forget to mention (sorry :( ).
  
Line 104: Line 105:
  
 __Alarms:__ __Alarms:__
-  * "Telemetry off" alarm (TLM alarm) - triggers if app lost connection to quad (if quad goes out of bluetooth range or it is turned off) for longer that 2 to 3 seconds (how you will be alarmed depends on what you set in settings - check settings for details) with automatically reconnect and continuing of checking when back in range or turn off/on quad. If connection is lost for a shorter period than 2-3 seconds, you will get info in status bar but alarm will trigger only if connection is lost for longer than 2-3 sec - so occasional brief dropouts of signal won't cause unnecessary alarms. If you experience constant TLM alarms and lost connections, please read __"Possible problems you might get using app on your Android device and additional steps to check and solve"__. When TLM connections is back, you will be signaled by voice and/or vibration pattern (1 short vibration following 1 longer vibration), depending on TLM alarm style you set in settings+  * "Telemetry off" alarm (TLM alarm) - triggers if app lost connection to quad (if quad goes out of bluetooth range or it is turned off) for longer that 2 to 3 seconds (how you will be alarmed depends on what you set in settings - check settings for details) with automatically reconnect and continuing of checking when back in range or turn off/on quad. If connection is lost for a shorter period than 2-3 seconds, you will get info in status bar but alarm will trigger only if connection is lost for longer than 2-3 sec - so occasional brief dropouts of signal won't cause unnecessary alarms. If you experience constant TLM alarms and lost connections, please read __"Possible problems you might get using app on your Android device and additional steps to check and solve_ckgedit_QUOT___. When TLM connections is back, you will be signaled by voice and/or vibration pattern (1 short vibration following 1 longer vibration), depending on TLM alarm style you set in settings
   * "Telemetry off - duplicate name found" alarm - triggers if more than one quad with the same name is found transmitting in range of your Android device. App will stop telemetry and you need either to turn off other quad/quads or change name to more unique one and re-flash before use app with these quads.   * "Telemetry off - duplicate name found" alarm - triggers if more than one quad with the same name is found transmitting in range of your Android device. App will stop telemetry and you need either to turn off other quad/quads or change name to more unique one and re-flash before use app with these quads.
   * Remote controller signal (RC signal) low or lost alarm - beeping alarm to alert user when connection between RC and drone is lost (long beep) or drop below defined percentage (10% is initial value or user defined if set - and produce 4 short beeps that sounds like beeps from stock TX - these alarms are represented with beeps and not voice in case it overlaps with voice alarms so this way you can clearly differ warning sounds   * Remote controller signal (RC signal) low or lost alarm - beeping alarm to alert user when connection between RC and drone is lost (long beep) or drop below defined percentage (10% is initial value or user defined if set - and produce 4 short beeps that sounds like beeps from stock TX - these alarms are represented with beeps and not voice in case it overlaps with voice alarms so this way you can clearly differ warning sounds
Line 145: Line 146:
   * ''USE_ALL_BLE_CHANNELS'': TLM data will be transmitted on all 3 BLE channels (for better reception on some phones)   * ''USE_ALL_BLE_CHANNELS'': TLM data will be transmitted on all 3 BLE channels (for better reception on some phones)
  \\  \\  \\  \\
-Now, happy flying and TLM-ing (or whatewer that might be called {{https://static.rcgroups.net/forums/images/smilies/smile.gif?nolink&}}). \\+Now, happy flying and TLM-ing (or whatever that might be called {{https://static.rcgroups.net/forums/images/smilies/smile.gif?nolink&}}). \\
 I hope this is application is usefull at least to some extent… I hope this is application is usefull at least to some extent…
  
  
silvervise.1516879687.txt.gz · Last modified: 2018/01/25 12:28 by silverag

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki