YaV1, tutorial, design, functionality suggestion

Discussion in 'Official YaV1 Support Section' started by francky06l, Aug 14, 2013.

  1. francky06l

    francky06l Premium Member Advanced User Premium Member

    Messages:
    1,963
    Likes Received:
    1,937
    Joined:
    Jul 4, 2013
    Hi All,

    This going to be a long thread, many time edited and amended. I will try to explain the YaV1 features with screen shots and text, Please feel free to correct the wording / terminology (my mother tongue not being English) ..
    I suggest to have this main thread edited and amended, but maybe better to have different threads for specialization ? You to tell :)
    I will renew the top link to the application on top of the thread, when needed.
    I hope you will have suggestion for the wording / terminology. If some of you have skills in designing button / images (PNG) you are welcome. The navigation can also be better, let me know, but the first thing I wish is functionality being there for covering most of wishes.

    you can download the file here:
    LAST BUILD 2013-08-30 09:50:00 (Madrid / Paris / Brussels time):
    https://www.dropbox.com/s/boe8y7ta7uqr9pe/YaV1-release.apk


    CHAPTER I, how to start:

    First you download the app, then you install with one of the many APK installer application available in Google play.

    When it's first time you start the application ever, it will be asking to choose the Valentine device without scanning for it. This means you have to pair your phone with V1 before to start the app (bleutooth -> pair -> code 1234 on your phone), this will occurs only once and will look like this :

    Screenshot_2013-08-14-12-46-57.png

    You can choose in this sample the V1-connection-xxx .. and let the app finding device, it might take 1 minute when trying to connect to V1, depends also if V1 is already started or not. Anyway after this first phase, you V1 bluetooth is recorded and will be the default one. However you can change afterward if needed.

    THE BASIC 2 VIEWS OF YAV1

    When starting YAV1, the first view is the following and this will be referred in the tutorial as the "Main view"

    Screenshot_2013-08-13-11-50-50.png

    This the basic view for all the settings, by clicking the left button of the PHONE, you get access to the menu:

    Screenshot_2013-08-13-11-50-59.png


    • Settings - settings of YAV1
    • Custom sweeps - settings and custom sweeps definition / management
    • V1 settings, the settings of Valentine one, or can be said "User profiles"
    • Devices, if ever you have change bluetooth adapter, this comes back to the same screen as first start
    • About, this give you a "dirty" view of version and other information (detailed later)
    • Demo mode, this plays some "recorded" alerts and let you have a view of the look. There 4 demo "scenario" available, when clicking "demo" one is choosen randomly and it last for about 1 minute. When finished it comes back to the Main screen "YAV1".
    • Quit is a new option that closes every services and just leave the application.

    From the Main view, by clicking on the big Green central button you access to the "Alert view", the first time you click on Alert view, the application will try to connect to V1, but not only the V1C adapter but the V1 itself (indeed you can have everything powered, but V1 stopped, the V1C will respond ... but not the V1), this will look like this ..

    Screenshot_2013-08-13-11-57-30.png

    There you can wait few seconds (about 5) to have the V1 connected, and the services starting up. What happen is that the first time you start the Alert view, the app starts the V1 alert service, optionally the Gps Service. The service once started they will remain running in background, next time you switch to the Main view and click the Alert view button again, they will be not waiting .. since the service are started. The alerts, and Gps, are in background and they will run as long as the Application is running.
    Note: Gps part will be only visible if you enable GPS in the settings (explained latter).

    When V1 is found the Alert view is this:

    Screenshot_2013-08-13-11-57-01.png

    Now, once the services are started and found the V1 running, if you press "back" on your Phone, the same way your press back in your phone settings to switch back from "wifi" to the settings global view, you will see this (depends of the current settings on V1):

    Screenshot_2013-08-13-11-56-50.png

    This view, shows you that V1 is connected and display the "Euro" or "Usa" mode, custom sweeps or not and the buttons to change the logic mode.
    In Usa mode, you will get 3 buttons "All" (All bogeys) "Logic" (Logic Mode) "Adv" for "Advance Logic",
    In euro mode without custom sweeps K/Ka (P) for K/Ka Photo, Ka (P) for Ka only Photo
    in Euro mode with custom sweeps K/Ka (C) for K/Ka Custom Sweeps, Ka (C) for Ka only custom sweeps ..

    The red label shows you the current mode, by clicking one of the button, the mode will change and the "Alert view" will be displayed. You can "back./esc" on the phone and see that the mode has changed and you can select another mode if you wish.

    IMPORTANT: The main view is the view to access all the menu options, so when in alert view, you have to click "back" from phone (usually the right bottom phone touch) and you will be back to the "Main View" ..

    CHAPTER II, YaV1 settings

    I will detail all the settings for the YaV1 application (not the V1 itself)
    First to access the Setting you select "Settings" from the menu, accessible from the Main view. This should look like this:

    Screenshot_2013-08-13-11-51-15.png

    There different screens to set up the features of the application.
    - General settings, for the global settings
    - The box definition, boxes are frequency range per band that you can parameter to distinguish them (or filter them) in the Alert List.
    - GPS parameters, using gps allow to use the lockouts / mute under speed feature.
    - Muting phone alerts, if ever you use the phone "sound notification" for alerts, you can set up muting phone.
    - Filter view, you can define what alert you want to filter, if ever you wish to have a filtered alert view.
    - Frequency recording if you want to be able to record frequency (nothing else, such as location etc ..)
    - Lockout on K Band lets you define the behaviors of lockouts.

    General settings, the screen looks as follow:

    Screenshot_2013-08-13-11-51-25.png

    - Alert theme, by default it will the "Red dot" theme, you can switch to the arrow theme, but I think, in general users prefers the dot one.
    - Start looking for V1 on start, when checked the application will start the "Alert view" as soon as started, bypassing the Main view and avoiding you to "click" the green button. I suggest, for beginners, to leave it unchecked until you have defined your parameters. In any case, when pressing "back" / "esc" button of the phone you will come back to the "Main view".
    - Priority alert on top of the list (default is checked). When the application receives alerts from the V1C, it can be by packets of N alerts, V1C has a flag to mark an alert as priority but the alert might not be the first one of the "packet" received. By default, and when the option is checked, the priority alerts will be places at the top the alerts in the alert view, also the name of the band will be in "Red".
    - Laser alert on top, default is checked is based on same approach as the priority except that laser are also detected by the packet that described the "screen on V1", when a laser alert arrived there is a special "arrow and sound" on the V1 itself. When this is detected a laser alert will be placed on top of the list with an 8 strength. The laser alert will always placed in the alert list, but with this option it will be places on top, even before the priority one.
    Note: the fact of reordering the alert can be a problem, in case of many alerts when users want to lockout, because it may change the order of an alert on K band that was already displayed. By un checking these options you have a greater chance that the order will not change.

    - Alert sound on phone, with this you decide if the phone sound (notifications sound) will be used or not.
    Note: the Android version prior to Honey Comb (3.0.x) have a check box here instead of the switch on/off box. Indeed switch box have been introduced with Honey Comb.

    - Default alert sound, you can choose here a sound from your phone as a default alerts sound. This sound will be "played", if not muted (see later muting settings), if any other sound with higher priority are played.

    - High priority alert sound, again here you choose a sound from your phone (you can even record some sounds and place the file in /media/sound/notifications folder, note that the place to store them can change depending on the android version/Rom etc ..). This sound will be played if an alert has it's frequency in a box that you have defined OR if there is no box defined for the band and the signal is > 4.

    - Laser sound, you can choose also a special sound for laser alert.
    Note: the priority order is Laser, High priority and default. Indeed the phone can play one sound at a time, so the top priority is played and if, because of new alerts, an higher priority sound should be play, the current sound will be stopped and the new played.

    - Early laser sound on, this let the application to play the laser as soon as a laser is detected (through the display information) wihtout having to process the packet of alerts. Basically you will hear the sound few milliseconds before seeing the laser alert. It's very hard to evaluate how "soon", since it's a story of milliseconds.

    All the sound comes with the "default notification sound" of the phone. Indeed I can't use other sounds since it depends of the android version, custom Rom or self made sounds.
    In a future release we might be to able to define sounds per band or even per "box", we will see in future, but the concept will remain the same ..

    Second screen for general settings (could not fit in one view):

    Screenshot_2013-08-13-11-51-34.png

    - Sound on service/start stop. You can define a sound that will be played when the Alert service starts or stops. When starting it really means that the application is connected to V1 itself, not only to the V1C. I realize that you can have V1C running, and V1 stopped, so this sound means that the application has received some "packets" from V1 and the Alert service is really active. You will get the same sound when you stop the application, meaning the Alert service stop. You can also have this sound if you stop the V1, after few seconds (see below) the sound will be played and the "Waiting for V1" screen will pop up.

    - Valentine timeout. The application receives continuously data from V1. Passed this number of second without receiving any data, we can consider of an error or most likely the V1 has been switch off. In such case, the V1 wait screen will appear and try to restart the Alert service. 3 seconds is the default value, that was used in the simple sample app from VR, if you get too many "V1 drop" you can try to increase by 1 or 2 seconds, but it should not need any other value.

    - Record success sound, this sound is used to indicate success on a lockout or frequency recording (if you enabled these features)
    - Record failed sound, this is the opposite as the above one.

    The other options are switch that you can use to turn on/off features. I am actually thinking to remove them since they are also available in the feature settings screens.

    To be continued ...
     

    Attached Files:

    Last edited: Aug 30, 2013
  2. francky06l

    francky06l Premium Member Advanced User Premium Member

    Messages:
    1,963
    Likes Received:
    1,937
    Joined:
    Jul 4, 2013
    Re: YaV1, tutorial, design, functionaly suggestion - BOX definition

    Let's detail the "Boxes definition".

    Boxes are range of frequency per band you can define, up to 3 "boxes" per band. The initial idea was to define the real threat frequency, according to your local LEO equipment.

    Boxes VS Sweep:

    Box have nothing to do with custom sweeps, custom sweeps affects the V1 scanning on Ka band only and make the V1 focusing the detection on the sweeps you define. Boxes do not affect the V1 at all, they are just useful for viewing / muting / filter the alerts.

    When an alert is "in a box", the high priority sound will be used (if enabled of course), you can also "mute" / "filter" the alerts that are NOT in a box. When defining a background color per frequency, it's easier to see them on the Alert View.

    Screenshot_2013-08-13-11-51-41.png
    .

    You can define up to 3 boxes per frequency by "clicking" the name of the box. Then you can enter the lower and upper edge frequencies, as well as a custom background color.

    Screenshot_2013-08-13-11-51-48.png

    The frequencies entered are checked according to the band. The app verifies that the upper edge is >= lower edge and the edges are in the V1 covered range.
    However the app does not check if a box is "contained" in another one, if K 1 covers 24100 to 24250 and K 2 covers 24150 - 24200 the app will not complain, but of course the K 2 is useless in this case, it will never be hit.
    In box are checked sequentially from first to last.

    POSSIBLE changes: have a sound per "in band" box ?
     
  3. francky06l

    francky06l Premium Member Advanced User Premium Member

    Messages:
    1,963
    Likes Received:
    1,937
    Joined:
    Jul 4, 2013
    Re: YaV1, tutorial, design, functionaly suggestion

    GPS Settings.

    Having Gps and allowing the app to use it is the real difference with V1 Connection. Indeed with Gps you can have lockouts, in future release, Loging alerts with location .. Gps also give you speed and direction on the Alert View.

    Screenshot_2013-08-13-11-52-14.png


    You have a switch to turn on/off Gps, of course turning off will turn off all the settings for Gps.

    Gps timeout: when this number of seconds is elapsed without new Gps position, the "red dot" in the Gps view will appear and it means the speed and direction are the last "known", but also means your current position is not accurate and you can't record lockout for example. You can play with this, in the best conditions you can set it to 3 seconds, you will get a better accuracy when recording lockouts.

    Speed unit: no need to details, KM/H is default though..

    Speed display: there are 4 different options, default one must be the moist accurate.
    Gps is giving you speed, I always compute speed as well between 2 gps positions. You can choose to display the GPS speed or the computed speed if Gps speed is not given. You can also choose the computed speed, the speed might be surprising then especially when having tunnels, or very curvy roads .. it's actually accurate in long distance straight roads. Then you can choose the maximum or minimum of Gps / Computed.

    Mute V1 under speed: the speed under which to mute in under (actually I have to review this, since is redundant), the idea was to have SAVVY like but using the Gps. It means that under the speed set after, the app will mute the V1. Note that if the GPS position becomes unavailable or "timed out", the V1 will be un muted.

    Display off when muted: just when muting V1 the display will turn off, at first was for me to check that the muting was matching the speed just looking at V1 display. My V1 is "very" concealed and I can't see it anyway now ..

    Bearing tied to accuracy: the bearing is the "direction" you heading on, it's in degrees to the North with is 0, so a value between 0 - 360. The Gps can also give you accuracy, a good one is <= 15 meters a "common" one is 30 - 50 meters. When tieding up the bearing to the accuracy, it means that if the distance since last position is not at least the "accuracy", the app display the last direction. For lockout is better to turn it off, since in curvy place, you can direction changing in 20 meters.

    Muting maximum speed: this works with the above setting "Mute V1 under speed". Here you choose the speed, under which the app will mute the V1. Again this is a bit redundant since it could be only the only setting, having "never mute V1" will be same as unchecked the previous setting. Something to do change obviously.
    This act as Savvy based on Gps.

    Enable Gps reset: this was done for my own usage. As I use an external GPS device (Bleutooth), I need an application that "replaces" the phone GPS by the external one. However, sometimes, after few hours the Gps is lost, so using this option you can click on the Gps view to "restart" the Gps service. It does not work "always" though, for people having a good Gps phone, do not check this option.

    next chapter soon
     
    Last edited: Aug 21, 2013
    Higado de Acero and Windstrings like this.
  4. francky06l

    francky06l Premium Member Advanced User Premium Member

    Messages:
    1,963
    Likes Received:
    1,937
    Joined:
    Jul 4, 2013
    Re: YaV1, tutorial, design, functionaly suggestion

    Muting parameters.

    This section describe the "muting" of the Application, not the muting of V1. I did remove the V1 muting here, but might add it back as Youthan suggested.
    Again this will mute only the sound of the Phone, not the V1.

    Screenshot_2013-08-13-11-52-20.png

    There is on top a global switch that allow you to use or not the phone sound, If you turn it off, then all other options are disabled.

    Mute lockout: checked by default, and of course if you enable lockout no sound will be played when an alert is in the lockout list, this applies also when the GPS has a valid position.
    Mute out of box: alert will not sound if the they are not in a "Box". Of course if you do not have any box defined for the current band, sound will be available.
    Mute recorded frequency: it's self explained, but I think the frequency recording will be changed to "logging", then this setting will disappear.
    Mute all under Gps speed: if you have defined a speed in the GPS settings, then under this speed no sound will be played, of course Gps must be available and have a valid position

    Enable K muting: when this is checked or ON, you have a left button in the alert view, by clicking on it, all the K alerts will be muted, if not enabled the button is not present.

    EVOLUTION: restore the V1 muting as it was in a previous release .. what you guys think ?
    .
     
  5. Windstrings

    Windstrings Premium Member Advanced User Premium Member

    Messages:
    8,312
    Likes Received:
    4,099
    Country:
    United States
    Joined:
    Jun 18, 2013
    Location:
    Central Texas
    Re: YaV1, tutorial, design, functionaly suggestion

    Ok, I'm dizzy now... Your a genius! This site going to revolutionize the RD world "especially the V1" as we know it.

    We all really appreciate you sharing with us as this evolves. I'm sure you will be handsomely rewarded as this is quite a project!

    I was afraid the bombardment of so many requests and particulars "we are a hard crowd to please!" would be overwhelming and prompt you to quit saying "you just can't please them all!" but instead you have and are marvelously tackling everything presented!

    This is so refreshing after pulling teeth for months and years for updates have been unfruitful!

    I am humbled to be in the presence of technical greatness!
    While so many others beat their chest and are all mouth and hot air, you Sir are producing the goods!!! :thumbup:

    Way to go! Keep up the good work!
    As this unfolds and begins to all make sense, people will be behind you in droves.

    This app literally makes the difference between which RD people will purchase.
    This makes your work very valuable my friend!
    As you know, hardware is only as good as the software behind it! And vice versa of course.

    I wouldn't surprised if someone doesn't try to discourage you as you are a threat to companies with simple minds and simple vision!

    _____________________________________
    Alan - The best things in the world are free --- and worth every penny of it.
     
    Last edited: Aug 26, 2013
  6. Youthan

    Youthan PSL +5 Intermediate User

    Messages:
    280
    Likes Received:
    171
    Country:
    Poland
    Joined:
    Feb 21, 2012
    Location:
    Silesia / PL / EU
    Re: YaV1, tutorial, design, functionaly suggestion

    Ready to test and thanks for restore this setting ;)
     
  7. francky06l

    francky06l Premium Member Advanced User Premium Member

    Messages:
    1,963
    Likes Received:
    1,937
    Joined:
    Jul 4, 2013
    Re: YaV1, tutorial, design, functionaly suggestion

    Hello Youthan,

    I will restore this, and email it to you ..
    Can you email me the avatar ?

    Thanks
    F.
     
  8. Youthan

    Youthan PSL +5 Intermediate User

    Messages:
    280
    Likes Received:
    171
    Country:
    Poland
    Joined:
    Feb 21, 2012
    Location:
    Silesia / PL / EU
    Re: YaV1, tutorial, design, functionaly suggestion

    Yeah
     
  9. francky06l

    francky06l Premium Member Advanced User Premium Member

    Messages:
    1,963
    Likes Received:
    1,937
    Joined:
    Jul 4, 2013
    Re: YaV1, tutorial, design, functionaly suggestion

    That's indeed the hardest part, and to know what is the essential ... I have a full time job, so I work only on this in evening and week end, unfortunately only 24 hours per day so far :)

    Thanks for your post, it makes me feel better ..

    F.
     
  10. Windstrings

    Windstrings Premium Member Advanced User Premium Member

    Messages:
    8,312
    Likes Received:
    4,099
    Country:
    United States
    Joined:
    Jun 18, 2013
    Location:
    Central Texas
    Re: YaV1, tutorial, design, functionaly suggestion

    For now, you may have to draw a line in sand and limit features... Perfect them, then release it as a "non beta" app otherwise it may never get finished.

    You've heard the term "Jack of all trades and master of none".

    There's wisdom in perfecting a smaller format, expanding it another date with a newer version rather than trying to tackle too much at once in the first version at the risk of increasing issues of cross compatibility and feature clashes.

    I'm amazed you've kept up with it so far.. It's all so far above my head.

    Your one sharp cookie to Do this and a full time job!

    Makes me wonder what the hecks wrong with some of the other software "teams" we gave that can't seem to produce an update or fix simple issues. Your just one guy.

    Your making hem look bad! :D

    That approach is possibly more rewarding too.

    _____________________________________
    Alan - The best things in the world are free --- and worth every penny of it.
     
  11. francky06l

    francky06l Premium Member Advanced User Premium Member

    Messages:
    1,963
    Likes Received:
    1,937
    Joined:
    Jul 4, 2013
    Re: YaV1, tutorial, design, functionaly suggestion

    My BIG problem is testing .. I am in a country where having a V1 can drive to very big problems .. It's very concealed and I do not see neither hear it .. I rely on the phone ..
    Best testing team is you guys !!! Where I am we do not have X band, but we have Ku ... Not so many pop guns on Ka etc .... that makes big difference, and I can't test all cases just because of the miss of "real cases" around me :)

    Thanks for comment, and indeed I need to draw a line .... Just let me know about the wordings in settings etc .. that will be a start "cleaning up" the app.

    Too bad that I can't make a survey here to know what people like (or dislike) the most (Custom sweep ? User profile ? lockout ? boxes) .... Also, I have absolutely no idea about the number of user running YaV1 ..

    Thanks again
    F.
     
  12. Youthan

    Youthan PSL +5 Intermediate User

    Messages:
    280
    Likes Received:
    171
    Country:
    Poland
    Joined:
    Feb 21, 2012
    Location:
    Silesia / PL / EU
    Re: YaV1, tutorial, design, functionaly suggestion

    I didn't know. I will try to help in this case in close future ;)

    At least you have one :D

    Please others to do some "coming out" with YaV1 :D

    Thanks,
    Regards,
    Youthan
     
  13. codesplice

    codesplice Flighting through Traffic Advanced User Premium Member

    Messages:
    699
    Likes Received:
    305
    Joined:
    Mar 21, 2013
    Location:
    Huntsville, AL
    Re: YaV1, tutorial, design, functionaly suggestion

    Another good reason to get this thing on Google Play STAT! ;)

    PS - I've disabled the K-band automuting on my V1, but YaV1 still isn't 100% reliable with muting alerts under the defined speed threshold. When it works, it's great; but there are still a lot of times when it just doesn't mute when I think it should. I'll keep testing and see if I can figure out any pattern.
     
  14. francky06l

    francky06l Premium Member Advanced User Premium Member

    Messages:
    1,963
    Likes Received:
    1,937
    Joined:
    Jul 4, 2013
    Re: YaV1, tutorial, design, functionaly suggestion

    you are right about first version on google play ..
    Concerning the muting, maybe this has to do with the K Muting settings, I was woundering about a simple test, manually mute V1, and check if it sounds when having an alert on K > 3 on first threat or >= 6 ...
    This would mean that V1 override the "manual muting" ...
    I just compile a version that Youthan will test, this one should be able to check the muting status of V1 as soon as it changes .. I did remove the record frequency also, I think this is confusing users ... but will turn them to logging as csv file that you can put on excel and check (was thinking to make this also enabled to a website where you can see them on google map, but again 24 hours only per day) :)

    I will draw a line soon :) This has to be done in order to progress, thanks all of you !!
    F.
     
  15. Youthan

    Youthan PSL +5 Intermediate User

    Messages:
    280
    Likes Received:
    171
    Country:
    Poland
    Joined:
    Feb 21, 2012
    Location:
    Silesia / PL / EU
    Re: YaV1, tutorial, design, functionaly suggestion


    Wow. That would be great. I was trying to do it by my self, but couldn't find a way (not to good in converting a file and content) Just another awsome option for YaV1 :D I like that !

    With muting V1 I think, we will find a problem. It's just a matter of time . . .

    Sorry. But we have now 10pm now in EU. See you all later ;)

    Don't worry . . .
     
    Last edited: Aug 26, 2013
  16. PointerCone

    PointerCone M3 Kng Advanced User Premium Member

    Messages:
    22,471
    Likes Received:
    21,201
    Country:
    United States
    Joined:
    Aug 5, 2011
    Re: YaV1, tutorial, design, functionaly suggestion

    the settings that you don't need a phone for, can these be saved to the V1 for use with Savvy in lieu of the phone. frankly, this is great stuff and you're to be commended for it! Great job Franky!
     
    Last edited: Aug 26, 2013
  17. francky06l

    francky06l Premium Member Advanced User Premium Member

    Messages:
    1,963
    Likes Received:
    1,937
    Joined:
    Jul 4, 2013
    Re: YaV1, tutorial, design, functionaly suggestion

    V1 is not a storage device and, I guess as limited capacity for this.
    The only thing you "save" (actually it's not really saving, but settings) is the current settings (only 1 set), the sweeps and few parameters such as the the mode and the Savvy behavior.
     
  18. Porcfat

    Porcfat Learning to Fly Beginner User

    Messages:
    60
    Likes Received:
    48
    Joined:
    Jul 25, 2013
    Location:
    North Kakelacky
    Re: YaV1, tutorial, design, functionaly suggestion

    This is truly an incredible development. I tip my hat for you! On to the iV1 app next??!! This is one of those moments when it pays off to be a Droid user.... sigh...
     
  19. francky06l

    francky06l Premium Member Advanced User Premium Member

    Messages:
    1,963
    Likes Received:
    1,937
    Joined:
    Jul 4, 2013
    Re: YaV1, tutorial, design, functionaly suggestion

    Filter view.

    When enabled, on the bottom of the Alert view a button "Filter" will appear, when click the view will show the alerts that remain after filtering (you come back to the "normal alert view", by clicking again on the button).
    The following settings let you define what you want to "filter", meaning which alerts will not be visible.

    Screenshot_2013-08-05-15-44-06.png

    Filter view: this a global switch, when OFF the "filter view" is disabled, no button will appear at the bottom of the "Alert view".
    Filter K alerts: that is a bit tricky, but it;s link to the "Mute K" button of the alert view. When muted, then the K alert will not be visible because they are muted.
    Filter lockout: if an alert is "locked out" it will not appear in the filter view.
    Filter recorded: this will be obsolete very soon.
    Filter out of box K: if you have defined at least one box on the K band and the alert frequency is not falling in one box range, it will be filtered.
    Filter out of box Ka, Ku, X: same as above for the respective bands.
    Filter under speed: if you have defined a speed in the GPS section, and the GPS is available and speed under or equal to the defined speed, then all alert will be filtered. In other words, when the speed is lower than the defined one, the filter view should be empty.

    Mute V1 if all filtered: this affects the V1 sound, if all the alerts have been filtered (filter view empty), the app will mute the V1. I still have to check the muting, sometimes I think it conflicts with the K Muting of the V1 settings.
     
    Windstrings likes this.
  20. francky06l

    francky06l Premium Member Advanced User Premium Member

    Messages:
    1,963
    Likes Received:
    1,937
    Joined:
    Jul 4, 2013
    Re: YaV1, tutorial, design, functionaly suggestion

    Lockout, what's that ?
    Lockout allow you to mark some alerts on K band (soon on X band also) as FALSE according to a GPS position. Of course you need to have a GPS and also a valid position, you will not be able to lockout alerts in a tunnel or in an underground parking.
    The lockout occurs when you "click" on an alert, if successfully recorded the alert should appear with the choosen background color and a "sound" of success recording should be played (if enabled in the sound definition).
    The following settings are used to define the lockout behavior.

    Screenshot_2013-08-27-17-43-20.png

    Note that this release is not yet available (note the change of the icon), but will be soon ..

    Use Gps: as you need Gps to apply lockout, the switch is present here in order to turn it on if ever is not done yet.
    Lockout on K Band: this is mandatory, a new option has been added to allow lockout on X band, but K band is mandatory to have X band.
    Lockout by group: this will show, on top of the alert screen, a "red circle" button that you can press to lockout all the alerts that are currently visible. This will record the K and X alerts if enabled.

    Important tips on lockout:

    The app will record a lockout for an alert if the alert frequency is not already covered by an existing lockout (+/- drift) within 100 meters distance (109 yards), regardless the direction. Now if you want to consider direction, meaning you want to lockout alert when driving South to North but NOT when driving North to South, then you can enable "Record direction", this will allow you to record the same place, if the angle from an existing lockout is at least 120 degrees.
    In other word you could see lockout alerts going North but not going South, this is also linked to the "Direction max angle" search in the parameters.

    Best way to record a lockout ? Being in the middle of the area you want to lockout !!! Indeed when searching for lockout, we give a distance, this distance is actually the radius of a circle around the car that should contain a recorded lockout locationt.
    Being in the middle WHEN you record, it's then more efficient , otherwise, in case of strong/long alert, you could get out of the area given by the search distance.

    Record direction:: as said before, this allow you to record lockout more than once and thus having the capability to distinguish your direction compared to the recorded direction when you did record the lockout. Note that the direction is ALWAYS recorded anyway, but when this option is checked this allow you to record same area more than once (angle in direction >= 120 degrees).

    Initial lockout drift: you can set the drift of the frequency, initially it's 5 MHz. This avoid recording many lockout for frequency that are "close" to each other.
    Record min signal: you can define a minimum signal strength of an alert to be "lockout" candidate, default is 1 (meaning all).
    Search Maximum Distance: this is the "circle radius" of your car where the lockout for the given alert will be searched.
    Direction Max Angle: by default the search is done regardless the direction, but you can define also a maximum angle to consider, as explained before, you might want to lockout alerts in an area only when driving in the "same direction" as the recorded lockout.

    Another screen to complete the lockouts:

    Screenshot_2013-08-27-17-43-41.png

    Enable remove lockout: when enable this allow you to "remove" a lockout area for the alert, by clicking on it.
    Background color, the background color used to show the alert when it's a lockout. You know that, if you have a valid Gps position, and the background color is the default one you can potentially "lockout" it, when the color is the "lockout" one, you can remove the lockout if you enabled this ..

    EVOLUTION: have a lockout list view, to able to remove / change the drift and optionally to show them on google map.
     
    Last edited: Aug 27, 2013
    hiddencam, Vortex and Windstrings like this.