Hi,
Is there anybody who can tell me what’s the format of output file resulted from running spectral-scan ?
I wrote a command like this in winbox terminal:
Hey normis could you please tell me how could I save the result of spectral-scan on remote radio? by means of duration parameter I can limit the running time of this command but when I login back to that radio, everything is cleared and I have no idea how to scan the remote environment.
Being able to read it would be great to diagnose remote PTP stations… No need for an external viewer though! Why not make routeros itself to be able to “replay” or read that file? i.e. a spectral-scan is ran on the remote end and saved to a file, then after it ends and we are able to login in again, and view or replay that file. CLI mode would be more than fine…
That way it would be a win-win situation: It would be more practical for admins (much better than having to transfer the file and open it in a PC), and better for Mikrotik as everything would be self-contained in routeros so no worries for the proprietary format/coding.
I guess also it would be faster and simpler to program as all the functions are already developed in RouterOS…
Hi Normis, can you let us know if someone will be working on finishing the viewer soon?
As suggested this could be as simple as having routeros “play back” the saved file.
So I have emailed Mikrotik asking for the file format, with the aim of creating a tool to automate the collection and parsing of spectral scans from our AP deployment. We are having bad noise issues so we want to see if there are patterns, wether it’s constrained to certain locations, etc.
Our topology doesn’t allow us to use Dude for this, so we are limited to save file & collect. I have even offered to give the tool I create back to Mikrotik so they can scratch the “Develop tool when we get around to it eventually sometime” from their backlog - this has been asked about for the last few years - but the reply has been “we cannot give any info”.
Thus, I’ve started to attempt reverse-engineering, and have already identified the RSSI readings, but how they map out to frequencies I’m stuck on.
I was fully aware of that URL and the posts pointing to it. However, after asking said forum member, I was told I could get 5 API calls per day and anything higher it would be paid-for. I need to process hourly readings from 55 APs, so it was going to get expensive fast. It became cheaper for me to dig into the binary file.
My offer to Mikrotik to write a tool for it & release it back the community was free, no strings attached. I will publish my findings on the file format in case anyone wants to extend them - they are limited to my bare needs, so I just mapped readings to file byte positions, there is no decoding of frequency bands, wether there is a mapping table of reading/frequency pairs, etc.
So, I finally managed to reverse-engineer the file format, to the extent that I can consistently read and interpret the results of spectral scans. I’ve now deployed on our network via a custom-made tool, which connects to each AP once an hour, runs the scan for 5 seconds, downloads the file, and processes & stores the result.
The tool then allows us to see the individual scan results, and a time-based waterfall of all results in a heatmap fashion.
This has allowed us to see things like:
APs with high levels of background noise across the 11 WiFi channels will fail to re-select quieter frequencies, and remain “stuck” on higher-noise channels that may be available.
APs with failed antennas systems are easy to spot - the background noise is almost gone!
On the tool itself, not likely to go on Github as it’s internal to our company, but I can post a file format description & and example on how to read it. The file itself is not completely reverse-engineered, I was only interested in reading the RSSI samples, so anything such as frequency mapping of readings, timestamps, device info, etc. is not done. To be clear, I just took scans of the whole 2.4GHz spectrum, and decoded the readings out of the resulting files - same work would be needed for 5GHz for example, which I have not done.
On the reselection issue, I’m preparing an email to support, I just wanted to have more historical data to see if the pattern is clear.
That’s understandable, would you mind sharing? I’m willing to take a stab at something more standalone, maybe we will finally get the tool we’ve been waiting years for
This is a really good job.
It is something really interesting that mikrotik should pay attention about it.
This kind of features cant be left away without any kind of explanation.
-1 to mikrotik.
If u can share any kind of information about it I (and a lot of people I guess) will be really gracefully.
Thanks my friend and good job again.
The range frequency is beetween 140a (= 5130) and 14c8 (=5320).
I don’t understand how to interpret the values in blue.
I ask for help.
Can you share your information?
Thanks,
Fabio