RAM Buffer is fall

[marauder-11]

I could install the software. When I run the default settings, i.e. rfexplorerDetailedScan -v ~/test.csv, it prints "RAM Buffer is full" and the program looks like it stalled and nothing happens.

What does this mean? and how do I overcome this? Thanks.

[tweeter103]

Interesting, I've been seeing that too. I've installed on several older but identical laptops mostly it runs ok, sometimes I get RAM buffer is full. I've had some running for more than a week unattended with no problem. If it is going to do it, it is generally the first scan. I've been scanning 450-700MHz which take (and outputs) a csv every 10 minutes. mkupferman, are you interested in revisiting this project, given the increased resolution available now from RF Explorer. Even 4096 data points is not enough to get 25k steps across 450-700MHz

[mkupferman]

I encountered this once when my starting and ending frequencies were beyond the capabilities of the selected radio on my RF Explorer, and the scanner seemed to get stuck, never advancing frequencies and filling up the available heap space. I'll take a look and see if there's a way to detect and trap this condition.

@tehleaf can you check the frequency boundaries you're using (--start-freq and --end-freq) and make sure they're safely within the operating range of your radio, and let me know if that fixes it?

@tweeter103 I'll take a look at some better memory management options for large scans.

[tweeter103]

Hi, Thanks so much for taking interest in this. Let me know if there is anything that I can assist with.

BTW, while you are digging in the code, a great enhancement would be it include support for RF Explorer’s addition of the number of steps. Originally this was 112, and still is on the handheld screen. But now from a laptop it can be set to 512, 1024, 2048 or 4096. As you correctly point out steps of 25k are ideal for Shure’s Wireless Workbench. Even with 4096 points at 25k it is only 100MHz of spectrum covered, so your concatenating of successive scans is still beneficial. But it would mean that fewer scan blocks are required if each scan is for example 25MHz at 1024 points.

Anyway, thanks for your work.

Cheers Peter

@. W. Peter Twartz Profiles Resource Management Sydney, Australia Phone: +61 (0) 424 411 747 Web www.prm.com.au/https://www.prm.com.au/ Facebook: www.facebook.com/prmaushttps://www.facebook.com/prmaus Email @*.**@*.***>

From: mkupferman @.> Sent: Friday, 6 August 2021 07:36 To: mkupferman/rfexplorer-detailed-scan @.> Cc: Peter Twartz @.>; Mention @.> Subject: Re: [mkupferman/rfexplorer-detailed-scan] RAM Buffer is fall (#2)

I encountered this once when my starting and ending frequencies were beyond the capabilities of my the selected radio on my RF Explorer, and the scanner seemed to get stuck, never advancing frequencies and filling up the available heap space. I'll take a look and see if there's a way to detect and trap this condition.

@tehleafhttps://github.com/tehleaf can you check the frequency boundaries you're using (--start-freq and --end-freq) and make sure they're safely within the operating range of your radio, and let me know if that fixes it?

@tweeter103https://github.com/tweeter103 I'll take a look at some better memory management options for large scans.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/mkupferman/rfexplorer-detailed-scan/issues/2#issuecomment-893824788, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUW7OPQEQUYU3JBO5PMJX73T3L75DANCNFSM42TXHMYQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.