# Logic 2.4.46 frequency missing from range measurement on analog tracks **URL:** \ **Category:** Logic 2 Software\ **Created:** [August 3, 2026, 5:43am UTC](https://discuss.saleae.com/t/logic-2-4-46-frequency-missing-from-range-measurement-on-analog-tracks/3791 "2026-08-03T05:43:38Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![robin](https://avatars.discourse-cdn.com/v4/letter/r/e5b9ba/32.png) [@robin](https://discuss.saleae.com/u/robin)\ **Post date:** [August 3, 2026, 5:43am UTC](https://discuss.saleae.com/t/logic-2-4-46-frequency-missing-from-range-measurement-on-analog-tracks/3791/1 "2026-08-03T05:43:38Z")
_As per title:_ Logic 2.4.46 frequency missing from range measurement on analog tracks, gone back to 2.4.44 to continue work. ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [August 6, 2026, 12:23am UTC](https://discuss.saleae.com/t/logic-2-4-46-frequency-missing-from-range-measurement-on-analog-tracks/3791/2 "2026-08-06T00:23:03Z")
@robin Sorry for the trouble with that! Can you check to see if Frequency measurement is enabled? You can enable/disable it via the “Add” button like in the images below. ![Screenshot 2026-08-05 182024](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/7/7861166852357d9ddf2e62e90c42fa66a6f75c62.png) ![Screenshot 2026-08-05 182230](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/9/999370c7986fdf8aea7aaa6ff79a570d17fe2373.png) ---
**Author:** ![robin](https://avatars.discourse-cdn.com/v4/letter/r/e5b9ba/32.png) [@robin](https://discuss.saleae.com/u/robin)\ **Post date:** [August 6, 2026, 3:03am UTC](https://discuss.saleae.com/t/logic-2-4-46-frequency-missing-from-range-measurement-on-analog-tracks/3791/3 "2026-08-06T03:03:28Z")
![Range_window](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/8/81e3eb58c1eb6bdb2ed58e99ee74444cc54e1d91.jpeg) I can’t find a popup that looks like either of those Note that control-G gives me a Measurement window (M0) not a Range (R0). Perhaps that’s why some of the options are missing Details: {“ReleaseChannel”:“stable”,“Branch”:“HEAD”,“Commit”:“116af78e00dda39f1c1b6b4f69c5b354b1ade5f2”,“Version”:“2.4.46”,“AutomationVersion”:“1.0.0”,“MachineID”:“dc8d59b7-9454-4108-a616-08e674b8bc61”,“PID”:970245,“LaunchId”:“77ec3378-69d5-43c2-b6a5-4f9176f8c4a5”,“Architecture”:“x64”} For reference, this is what 2.4.44 shows: ![Range_2.4.44](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/9/9810bd6d8d6d30d7b3992859f1abbdc9740a067f.jpeg) It has an extra ‘+’ in top right that is missing from 2.4.46 which allows all those extra measurements!! ---
**Author:** ![markgarrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/markgarrison/32/23_2.png) [@markgarrison](https://discuss.saleae.com/u/markgarrison)\ **Post date:** [August 6, 2026, 7:34pm UTC](https://discuss.saleae.com/t/logic-2-4-46-frequency-missing-from-range-measurement-on-analog-tracks/3791/4 "2026-08-06T19:34:57Z")
Hi @robin, looks like you have V2 measurements enabled in Logic 2.4.44 but not the newer version! Normally that “+” button is only visible when the environment variable `ENABLE_MEASUREMENTS_V2` is set, e.g.: `set ENABLE_MEASUREMENTS_V2=1` It’s possible you edited a shortcut to our software to add that variable, or have the variable set on your system. Logic 2.2.46 still works the same way with the same variable, so I’m not sure why it’s not working for you. However the behavior is not default on the older software either, so some change was made somewhere on your machine to set that environment variable, and for some reason that only seems to apply to the older version. We released Measurements V2 a long time ago, and never finished switching over to it for existing products. (We were diving into Logic MSO soon after that. Logic MSO always uses the V2 system, but we never finished approving the API for general use, which blocked switching everyone over to it) We really need to get back to that… Details here: > [@Logic 2.3.48](https://discuss.saleae.com/t/logic-2-3-48/1533): > > Download Links [Windows](https://downloads.saleae.com/logic2/Logic+Setup+2.3.48-master.exe) - [Linux](https://downloads.saleae.com/logic2/Logic-2.3.48-master.AppImage) - [MacOS](https://downloads.saleae.com/logic2/Logic-macOS-2.3.48-master.zip) Check out the Saleae Logic 2 Extension Marketplace! - Read more about the Marketplace on the [Saleae blog](https://blog.saleae.com/introducing-logic-2-marketplace/)! What’s New Measurement API We’ve expanded the capabilities of the Measurement API with a focus on Analog channels as part of a longer term product development plan to help our customers verify, debug and test analog problems such as signal integrity issues and much more. Please keep in mind that this API is a preview-release, and we’re planning on mak… and here: > **[GitHub - saleae/saleae-measurements-v2](https://github.com/saleae/saleae-measurements-v2)** > > Contribute to saleae/saleae-measurements-v2 development by creating an account on GitHub. ---
**Author:** ![robin](https://avatars.discourse-cdn.com/v4/letter/r/e5b9ba/32.png) [@robin](https://discuss.saleae.com/u/robin)\ **Post date:** [August 6, 2026, 10:00pm UTC](https://discuss.saleae.com/t/logic-2-4-46-frequency-missing-from-range-measurement-on-analog-tracks/3791/5 "2026-08-06T22:00:29Z")
Exactly the issue - 2.4.44 I was starting from a KDE Plasma icon with “ENABLE\_MEASUREMENTS\_V2=1” set in the environmental variables but 2.4.46 I was starting from the command line ‘barefoot’. Many thanks for your time in helping me determine the issue.