jks-prv / beagle_sdr_gps Goto Github PK

KiwiSDR: BeagleBone web-accessible shortwave receiver and software-defined GPS

Makefile 0.49% C 33.19% C++ 50.39% Assembly 0.26% Shell 1.08% OpenEdge ABL 0.01% JavaScript 11.05% HTML 0.11% CSS 0.74% Verilog 0.95% SystemVerilog 0.19% sed 0.01% Perl 0.39% Tcl 0.21% MATLAB 0.10% Less 0.35% SCSS 0.36% PHP 0.01% CMake 0.06% BitBake 0.06%

sdr gps beagle cape vlf hf shortwave verilog fpga pcb

beagle_sdr_gps's People

Stargazers

Watchers

Forkers

periloso yangkkokk mfkiwl liubingzsd donzelot diyjack n5fpp murat-sever rbarraud fourks wanming2008 vtpp tomgaussiran elfchief yangquan3 stargo icm7216 kkndyu rikvanriel sherckuith sonvoque slepp misterdevil huleg barmallini linkfanel kdfuqixiang sinantie orloff2 idaohang rtsys2020 thewyliestcoyote lazywalker roice ecoblockchain bemnetadefis marsystech bi7jta-hamradio tvikneshwar tdautc19841202 hb9fxq dish-eme-sdr hcab14 weissbier herrfeuer gnss-hpsdr geonomad lordleid hjcya99 navy2609 jasonj99 jgamage91 doyke kk2018 cjsatuforc corerc zebrahippo vu2lid junaidnaseer 3v4l langxj compass42 sq5alq st0ne xinghuaman ringof circuit-killer zhu163bing alonso48f px2ku ymz000 yellowsdr liangjw tomn46037 5l1v3r1 jellokang mahuixun jonathonmh howard0su yo3ibz cql1983 hg2ecz qyon ammarnoman lb425 andromem tubbz-alt hitanvil metroson88 gaybro8777 gm4sfw srgkmv pdeforge belmy mibatu mcogoni fullstackfpga trigrass2 mgrennan j3ster2019

beagle_sdr_gps's Issues

Suggestion for IBP beacon / WSPR propagation monitoring extension / new function

Hi,

I was thinking about how to maximise the use of the limited four receiver resources in each KiWi, especially when not being used by remote listeners.

I note that the KiWi currently has the IBP beacon tags changing in sequence with the beacon transmission schedule.

How feasible would it be to have the Kiwi scan the various IBP beacons on different bands and logging the results whenever there is a spare receiver that is not being used for other purposes.

Maybe the WSPR extension could also scan following the WSPR hopping schedule when there is spare capacity on the Kiwi ? This would free up capacity in real time as it would not have individual users logged on for long periods of time just to run a WSPR session.

The IBP results could then be displayed on the individual KiWi as a form of real time propagation indicator.

Something like FAROS

http://www.dxatlas.com/faros/

Regards,

Martin - G8JNJ

move WF min / WF max sliders to "more" menu?

Would it make sense to move the WF max & WF min sliders from the normal menu to the "more" menu, so these sliders are not always taking up screen space?

This make make it a little easier to use kiwisdr on a smaller screen, and will leave a slightly larger amount of the waterfall visible.

If people think this is a good idea, I am willing to implement that change in the code and simply submit it as a pull request for John to integrate. However, before doing that kind of thing I would like people's opinions :)

Hide mode, freq, s-meter panel?

Is it possible to add a triangle, hide option to the right hand mode, freq select & s-meter panel to push it off into the drawer on the right hand side of the display, similar to what is done on the left for user list and intro/help lists? It would be nice to see the entire display and be able to take screen shots without any blockage.

Thanks & 73

andyz - K1RA

Admin page password not letting me on. I'm on local network.

Docs say it doesn't require a password if you are on the local network, but mine is. Any ideas.

Chuck

Suggestion - keyword search for tags

Hi John,

I've now got a large number of tags setup on my SDR, however I'm finding it difficult to keep track of them all and remember where a particular service or broadcaster was located.

Would it be possible to include a simple keyword search with a next and back option that would sort the tags.

Regards,

Martin

Waterfall frequency ruler fault

Hi,

It seems that at maximum waterfall zoom the frequency "ruler" at the top of waterfall shows potatoes, when the frequency is 1 MHz or more, and browser window is wide enough (> ~1880 pixels). Zooming one step back reverts proper display.

Best 73,
-petri OH1BDF

Allow listening when all four RXs in use

The number of unique streams leaving the KiwiSDR is limited by the processing power available to generate them, but sending the same stream out to multiple people should require almost no extra overhead. It would be very nice if, when all four RXs are in use, you were given the option to listen to an existing stream rather than being blocked completely.

kiwid stalls on sdr.hu registration

I have noticed occasional stalls of the waterfall and audio. I finally managed to grab a backtrace, and it turns out to be the sdr.hu registration that can take several seconds, stalling the kiwid process while waiting for the sdr.hu http request to complete (or the connection to be made?).

gdb --batch -p `pidof kiwid` -ex "bt" -ex "quit"

__libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:43
43 ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file or directory.
#0 __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:43
#1 0xb6c1650a in _IO_new_proc_close (fp=0x495d7d8) at iopopen.c:345
#2 0xb6c1d1c4 in _IO_new_file_close_it (fp=fp@entry=0x495d7d8) at fileops.c:171
#3 0xb6c1514c in _IO_new_fclose (fp=0x495d7d8) at iofclose.c:59
#4 0x0002ea98 in non_blocking_cmd (cmd=, reply=0x49ea468 "<!doctype html>\n\n\n\t<title>SDR.hu</title>\n\t<meta charset="utf-8" />\n\t<meta http-equiv="X-UA-Compatible" content="IE=edge">\n\t<!--<meta name="viewport" content="width=1000, initial-scale=1" >"..., reply_size=16384, status=0x0) at support/misc.c:318
#5 0x00023b38 in reg_SDR_hu (param=0x0) at web/services.c:137
#6 0x00048dda in trampoline () at support/coroutines.cpp:451
#7 0x00048dc4 in TaskRemove (id=) at support/coroutines.cpp:653

Frequency input: accept also comma as a decimal separator

Some countries use comma as a decimal separator (for instance Nordic ones, DK/SV/NO/FI). This is often effective in numeric keypad mapping, where decimal separator reflects to system locale.

Would it be a big effort to accept both period and comma as decimal separators? Additionally, if system locale is available at browser / JS level, maybe it could be used to parse the F input (and when presenting frequencies, though this isn't that important..) correct way?

73
-petri OH1BDF

PANIC: "jsmn_parse" (cfg.c, line 496)

After occasionally adding stations to the dx.json file the reload crashed with:
Nov 17 23:55:01 kiwisdr kiwid: 0:00:00 .... compiled: Nov 9 2016 04:28:49
Nov 17 23:55:01 kiwisdr kiwid: 0:00:00 .... reading configuration from file /root/kiwi.config/kiwi.json
Nov 17 23:55:01 kiwisdr kiwid: 0:00:01 .... serial number from EEPROM: 1361
Nov 17 23:55:01 kiwisdr kiwid: PANIC: "jsmn_parse" (cfg.c, line 496)
Nov 17 23:55:13 kiwisdr kiwid: 0:00:00 .... KiwiSDR v1.22

The last line entered that seems to have generated the error is shown in bold below. I cut the newly added stations list as shown below, rebooted, and all is well again. I pasted it back in and it crashed again. Took it out and all is well. How do you restart kiwisdr from the command line?

,[580.00,"AM","KIDO","5KW,Nampa,ID",{"WL":1}]
,[610.00,"AM","KONA","5KW,Richland,Pasco,Kennewick,WA",{"WL":1}]
,[630.00,"AM","KFXD","5KW,Boise,ID",{"WL":1}]
,[670.00,"AM","KBOI","50KW,Boise,ID",{"WL":1}]
,[710.00,"AM","KIRO","50KW,Seattle,WA",{"WL":1}]
,[730.00,"AM","KNFL","15KW-D,500W-N,Boise,ID",{"WL":1}]
,[760.00,"AM","KDSP",50KW-D,1KW-N,Thornton,CO",{"WL":1}]
,[770.00,"AM","CHQR","50KW,Calgary,Alberta",{"WL":1}]
,[770.00,"AM","KTTH","50KW-D,5KW-N,Seattle,WA",{"WL":1}]
,[780.00,"AM","KKOH","50KW,Reno,NV",{"WL":1}]
,[790.00,"AM","KSPD","1KW-D,61W-N,Boise,ID",{"WL":1}]
,[890.00,"AM","KYWN","50KW-D,250W-N,Meridian,ID",{"WL":1}]
,[1060.00,"AM","KBGN","10KW,Caldwell,ID",{"WL":1}]
,[1140.00,"AM","KGEM","10KW,Boise,ID",{"WL":1}]
,[1350.00,"AM","KTIK","5KW-D,600W-N,Nampa,ID",{"WL":1}]
,[1380.00,"AM","KKOO","15KW-D,1KW-N,Ontario,OR",{"WL":1}]
,[1490.00,"AM","KCID","1KW, Caldwell,ID",{"WL":1}]
,[1650.00,"AM","Weiser Highway Advisor","10W,Ontario,OR",{"WL":1}]

Startup frequency

The default start up frequency can only be defined in 1KHz steps. Could smaller values be permitted ?

Regards,

Martin - G8JNJ

Possible bug LORAN_C extension

I've noticed that the Loran_C extension doesn't always sync to the correct time slot.

Stopping and restarting the extension a few times usually fixes it, but if the signal is not known it isn't really possible to tell if the timing is correct (or not).

Regards,

Martin - G8JNJ

Suggestion for click to frequency dependent upon zoom level

I find that when zoomed out and tuning by clicking on the waterfall, I very often don't tune to the correct frequency.

Would it be possible to change the resolution of the tuning step that the SDR snaps to depending upon what level of zoom is being used.

For example most transmissions tend to be on frequencies that are multiples of whole KHz.

When clicking on the waterfall at zoom level 0 to 2 1KHz resolution is OK, zoom level 3 to 4 500Hz, zoom level 5 to 6 10Hz and 1Hz steps at higher zoom levels.

Tuning using the + and - buttons and by direct frequency entry would continue to operate as before.

Regards,

Martin - G8JNJ

Set number of public recievers

This is applicable if the suggestion of being able to permit multiple users to listen to existing receivers is implemented as per issue #2

Would it be possible to somehow set password protection or some sort of priority use per receiver in the admin menu ?

Would it also be possible to set a default frequency and mode to individual password protected receivers ?

This would allow authorised users priority over other casual users on one or more receivers if required.

My thinking is that if a radio club operates a KiWi SDR they may wish to leave one receiver permanently set on their local net frequency.

Regards,

Martin - G8JNJ

Feature request: Listener IP-address privacy mode

I'd like to see possibility to enable privacy mode that hides listener IP-address from KiwiSDR WebUI. Currently default behavior is to display other listeners IP-address on WebUI.

Listener IP-privacy mode should be able to turn on from admin panel. If IP-privacy mode is Enabled, KiwiSDR ui should

a) display salted hash of listener's IP-address instead of actual IP on WebUI.

b) Display text Anonymous instead of listener's actual IP on WebUI.

Saving AGC settings

Would it be possible to save the AGC settings as cookies ?

I find that setting the AGC is very beneficial in reducing the background noise level especially on the LF bands.

However the settings do not seem to be saved from session to session.

Also could the AGC defaults be set to something mid range. The default slope setting seems to be 0dB which means that the AGC doesn't do anything when initially enabled

My suggestion for default values would be:-

Threshold of -90dBfs
Slope 6dB slope
Decay 1000mS

Regards,

Martin - G8JNJ

I'd like to be able to send spots to PSK reporter right within KiwiSDR.

https://www.pskreporter.info/pskmap.html

If this isn't possible, I'm guessing I might be able to get it send the audio to something like FL-DIGI, but might need to send some rig control signals to make FL-digi be in sync so far as freq.

Thanks for any ideas on this,

Chuck

added frequency offset when click a carrier frequency at waterfall. (on the LSB, USB, CW, CWN mode)

How to check this issue.

1: receive time signal.

freq = 10000.00 kHz
mode = AM

2: a dial to show carrier frequency is below.

  /-------------------|-------------------\ 
  |    |    |    |    |    |    |    |    |
(mode = AM)       10.000 MHz
                      | <= carrier frequency

3: change a mode to LSB. and then click a carrier frequency at waterfall.

         /----------\ | 
  |    |    |    |    |    |    |    |    |
(mode = LSB)      10.000 MHz
                      | <= click

4: received frequency is moved to the upper. display frequency is 10001.52 kHz.

                /----------\ | 
  |    |    |    |    |    |    |    |    |
(mode = LSB)      10.000 MHz
                      |

Why added frequency offset? It should not move the received frequency.
also USB, CW and CWN mode are similar problems.

I think that carrier frequency should be displayed as reception frequency.

Suggestion for 'Top Ten' frequencies

I find it quite interesting to see what other users are listening to.

Would it be possible to have a 'Top ten' list of frequencies displayed. This could be a rolling average generated from the total amount of time spent on specific frequencies by users over a suitable time scale.

Regards,

Martin - G8JNJ

Waterfall "logging"?

Hi,

first of all my most sincere thanks for this great project! In a nutshell: This little beast is absolutely super.

Say, what do you think of a feature similar to Twente's SDR: http://websdr.ewi.utwente.nl:8901/fullday/

That would be great in for instance trying to trace the nowadays far too frequent chinese SMPS QRM and similar, not mentioning the educational purposes: that would be nice to show people at local ham radio course, when the topic is radio propagation!

One proposal more over the Twente's display: how about adding "floating" time stamps? On Twente's implementation they disappear when this huge picture is scrolled to the right..

Thanks + 73,
-petri OH1BDF

Other users' frequencies should be clickable

In the panel where the current users are shown, the current frequency/mode shown for each user should be clickable, with a click setting your own RX's frequency/mode appropriately. This would make for a very nice "wonder what that person is listening to" kind of feature, with very little development effort.

Individual S-meter Calibration to Signal S9=-73dBm (if attenuators/pre-amps are used)

It would be nice, if the user could adjust the S-meter to always show correct levels being -73dbm = S9.
I found that a real input from a calibrated R&S source only shows S7-8 on the S-meter.
I also found it necessary to use additional 15db attenuation, to overcome overload with Megawatt broadcasters in the evening. So in my case a real S9 from the antenna becomes roughly S5 on the display.

I think the S-meter should always show S9 for a signal which comes down the antenna cable with -73dbm, no matter if the signal has been attenuated as part of the rx-hardware for linearity reasons of the rx or not. The received signal itself has not changed - so the signal strength indicator should not change either.

May be we should show a green botton next to the s-meter, if the user has followed a calibration routine, so others can see, that his SDR represents S9=73dBm or not.

Currently the KiwiSDR S-meter does NOT show S9 with direct connection to a -73dBm source - at least not with my unit.

Ulli, ON5KQ

P.S.
Currently testing my system in unfortunately very noisy location - if I can manage the noise, I will bring it online. But if it is of no added value at the current location I have to find a better location first before it will appear at SDR.hu. Thanks for your understanding

Saving and recalling config from admin menu [backing up Beagle to SD card]

Is it possible to add a "save to" and "load from" SD card option within the SDR admin pages ?

This would save having to modify files on the SD card then reload from scratch and await updates.

Regards,

Martin - G8JNJ

Suggestion - display local time on SDR WEB Page

Hi,

Whilst using other Kiwi SDR's on sdr.hu it sometimes surprises me that signals I'd expect to see are not present. Often this is simply because it's night time where the SDR is located.

Would it be possible to show the local time somewhere on the Kiwi header ?

Perhaps with a coloured background or a sun / moon symbol (or similar to quickly indicate the time of day or night or when it's in the Greyline.

Regards,

Martin

Suggestion for users to be able to tag frequencies.

I think it would be useful if users were able to tag interesting frequencies to bring them to the attention of other users.

However I suspect that this could lead to abuse if it was not moderated in some way by the SDR admin.

Would it be possible to allow users to tag frequencies and add comments in the same way as the admin, but only display something like a question mark on a bright background colour, until the admin has opened up the tag and verified the comments, then changed the status so that it can be displayed normally.

Regards,

Martin - G8JNJ

Kiwi software should send/receive over VCP/VSP to 3rd party applications

[This issue is from Ron, KA7U, that was originally submitted as part of another issue: https://github.com//issues/19 Added here as a new issue for better visibility]

This image shows Fldigi monitoring the CW audio from the KiwiSDR web interface on an openSUSE OS. Pulse Audio is directing the audio connections and so Fldigi is the "recorder". The same could be done using virtual audio cables in Windows. If there were virtual serial ports such as com0com.exe provides in windows or SoCat provides in Linux, moving frequency and mode data to and from 3rd party applications such as Fldigi, then the KiwiSDR could be tuned (frequency and mode) from the 3rd party application and the 3rd party application could be tuned (frequency and mode) from the KiwiSDR web-browser waterfall input. This would allow for a great diversity of commonly available 3rd party applications to compliment KiwiSDR. That would be any instance of any KiwiSDR displayed on a web-browser using about any OS. While I'm at it, this link has very good overview information. It is written for HDSDR but the usage is similar. https://sites.google.com/site/g4zfqradio/hdsdr_digi-modes

Question WRT WSPR bandwidth

Hi,

I notice that the WSPR extension defaults to a narrow CW bandwidth rather than the more usual 2.4KHz USB bandwidth.

WSPR has been optimised to expect a 2.4KHz wide block of signals and extract the WSPR signals from that block.

Has CW been chosen for any particular reason such as a need to reduce the processing required for WSPR decoding ?

Regards,

Martin - G8JNJ

How can we help out?

I just set up my KiwiSDR recently, and set it up for public access. I love that there is a nice SDR with completely open source software.

I have worked on some other ham radio software in the past, and see a lot of great feature ideas for KiwiSDR in this issue list.

My question is, how can other software developers help out?

Have you considered setting up a development mailing list, or some other way for developers from outside the core team to get involved with KiwiSDR development?

I would be interested in working on demodulators, antenna switch control, and who knows what else, once I get more familiar with the code...

Problem with AM reception

This issue was flagged up by one of my SDR users.

When using AM to listen to a plain carrier signal, if you offset the tuning by say 1KHz you can hear a 1KHz beat tone. This is problematic when listening to broadcast stations or NDB's

For example tune to a plain carrier using USB set it to produce an audio tone of say 500Hz. Then switch to AM and you can hear the same frequency tone. It's almost as if the AM detector is actually a DSB detector.

This should not happen when using AM. No tone should be heard.

I have tried the same experiment on an Openwebrx SDR and the problem doesn't seem to be present.

Regards,

Martin - G8JNJ

Tags and bands

Is it possible for SDR admins to customise / edit the bands ?

If not would it be possible to edit the band information by Shift click on band marker when logged in as admin.

Is there any documentation other than the quick start guide ?

Regards,

Martin - G8JNJ

Spectrum window fixed, waterfall dynamic, not visually in sync.

The spectrum window is great for coarse tuning over a wide band, just jump to the peaked signal, but when zoomed in closer, the spectrum scale does not zoom dynamically to fit in the browser window, while the waterfall does. So the spectrum peaks are not aligned with the waterfall unless you take time to manually set the browser window size to match the fixed width of the spectrum display.

Loading new photo

In which directory should the title photo reside ?

I've tried uploading my own picture which is the same size as the original pcb.jpg but it won't load.

As a test I have tried replacing root/Beagle_SDR_GPS/web/kiwi/pcb.jpg with a copy called pcb2.jpg and setting that as the default through the admin interface but the file can't be found.

Does a replacement photo need to go in another folder ?

Regards,

Martin - G8JNJ

5kHz Step Up and Down

Is it possible to add a 5kHz step buttons (5kHz step up & down in frequency) when in the AM modes?
Shortwave broadcast stations are at 5kHz spacing and the current 1kHz and 10kHz steps while great require additional key clicks to scan up or down the band by station channels.

Provide higher priority to local user

Hi,

My KiWi is being fully utilised this evening and I can't easily log in to test something.

Rather than dropping exiting users by restarting the SDR, would it be possible to give priority to users on the local network above those logging in via the internet ?

Regards,

Martin - G8JNJ

Suggestion for expansion of existing SDR's

My SDR is now proving to be quite popular and my thoughts are turning towards how I could support more users.

Would it be possible to build some capability into the SDR so that if more Kiwi's and Beagles were deployed at a site they could be 'stacked' so that from a users perspective it just appeared as if they were just using the one SDR but with more receiver's ?

Regards,

Martin - G8JNJ

Suggestion for display of antenna in use

Hi,

I notice that in the in the KiWi sdr / admin interface / sdr.hu page there is a text field for Antenna details.

This information doesn't seem to be used or get displayed anywhere.

This detail could provide a useful indication to users of which antennas are working well and which ones are poor performers.

Could this be shown somewhere on the web sdr, perhaps in the grey status pane.

Regards,

Martin - G8JNJ

Suggestion for possible extension - Morse / CW decoder / Skimmer

Hi,

I wondered if it would be possible to include a Morse / CW decoder / Skimmer as an extension ?

There's still a lot of it about, and it would be useful for identifying NDB's and suchlike.

Regards,

Martin - G8JNJ

Adding new DX labels with mode NBFM makes kiwisdr stop

I tried to add a DX Label, shift-click above the frequency scale. If the mode is set to NBFM the kiwsdr stops and does not recover. I can manually edit the /root/kiwi.config/dx.json file, and remove the new entry.

I first thought had to do with with the >30MHz frequency
,[31330.00,"NBFM","Jakt","Local%20hunters"]
But I get the same problem when trying on 20 meters. I think it is connected to the mode NBFM, but not 100% sure.

S-Meter scales

Hi,

Would it be possible to have the option to show the S-meter scale in dBm ? maybe this could be added below the S-meter ? The present S-meter calibration is too coarse for accurate comparisons.

Unlike other WEB SDR's the great advantage of the KiWi SDR is that it is all based on the same hardware and so calibration shouldn't vary too much from SDR to SDR.

Having a common reference level in dBm would be very useful when making comparisons between antennas and different receiver sites.

Regards,

Martin - G8JNJ

Adding frequency offset for down-convertors

Hi,

Would it be possible to add a frequency offset so that the SDR could be used with block down convertors to provide coverage of higher frequency bands ?

Regards,

Martin - G8JNJ

Band overlap

Hi,

Just noticed there is an overlap of band markers between 3900 and 4000KHz.

The coloured bar is purple (mix of red and blue) and the titles obscure each other.

Regards,

Martin

Waterfall stopped working on Firefox [i386 Linux]

I noticed today that the KiwiSDR waterfall no longer displays on my small laptop, an Acer Aspire One i386 running Firefox 43.0 under Mint Linux. None of the current KiwiSDRs listed on sdr.hu displays a waterfall. Both of the RTL-SDR RPI2 sites I tried from there work fine.

Seems to be a result of a change introduced in a recent KiwiSDR update.

External users and internal users on the KiwiSDR

Hi. IF I connect to my own KiwiSDR within my local network that receiver only shows my connection. If I connect by the external IP address (or dyndns redirector) those connections do not show up.

I am not shure if that is a problem, but I could connect 3 browsers locally to my KiwiSDR and still had 2 external connections, making a total of 5 reveicers

Thanks,
Ben

Audio FFT Extension - suggestion for timing adjustment

Hi John,

The audio FFT extension is very interesting.

I've tried using it to identify weak NDB's which transmit morse at regular intervals.

The tricky part is figuring out the correct repetition rate.

Would it be possible to click on the FFT waterfall at two points and use that information to set the timing interval.

e.g. I can see the start of the morse ID so I click on that point then wait for the same sequence to start again and click on the same point of the sequence. This determines the cycle time and sets the integration time.

Would it also be possible to vary the speed of the FFT waterfall in order to cater for shorter of longer sequences.

It would also be useful to be able to zoom in on the FFT waterfall in order to allow closer inspection.

Thanks,

Martin - G8JNJ

Restricting frequency ranges

Hi,

Would it be possible to add the option to restrict the tuning range to be within defined upper and lower limits ?

It would be useful if other blocked frequencies could also be defined by pairs of upper and lower limits.

This would help with regulatory requirements in some countries.

Regards,

Martin - G8JNJ

Link to external (IRC) chatroom

Chatting is nice, and I've taken notice of the wish list item:

Chat? (that's been kind of a mess on WebSDR hasn't it?)

I would like to point out a few thoughts about it.

I think your project is great, and the future of WebSDRs, but I don't think you should try to add every suggested feature into it. In my opinion you shouldn't try to do everything within KiwiSDR. You should keep a modular design for the core jobs of KiwiSDR, maybe implement an extension framework for peripheral jobs - that's ambitious :) - but let other separate tools handle what are clearly other jobs.

As you've pointed out, chat has been a mess on the utwente WebSDR. Probably because WebSDR administration is very different from chat administration, the operator doesn't have the time to do it correctly, the architecture, functionality and support behind the chat are subpar compared to what you would expect from real chatrooms, etc. In my opinion it should have never been attempted to begin with.

On KiwiSDR, these problems would be compounded with the fact that with only 4 users maximum, you wouldn't have many people to chat with.

Instead, I suggest that in the user panel, you simply add a link to an external chatroom, which would be configurable by the administrator. IRC sounds like a great option for that. It could just be IRC chatroom information, an irc:// URL if that's universally supported, and/or a link to a WebIRC in a new browser tab for those without an IRC client. It could also be configured to link to an XMPP chatroom or whatever else it is that people want to use to chat.

The link could point to a default KiwiSDR listening IRC chatroom, which would then be shared by KiwiSDR users from any instance, and would benefit from the network effect. Administrators could customize it to a regional chatroom too, or a personal one, or disable the link if they so desire.

The best about this approach, especially compared to a chatbox, is that it is very easy to implement; about a one-liner for a static link, not much more for a configurable one. You don't have to administrate the chatroom yourself, you could even point to an existing SWL one.

I hope this helps and we can see this soon!

Remove debug clutter from interface

It's nice that contrary to the utwente WebSDR software, KiwiSDR makes an attempt at maximizing the use of screen real estate for the waterfall. However at the same time, it makes it frustrating whenever the interface clutters the useful display :/

I'll talk personally but I expect plenty other people would feel the same. The thick, solid top bar feels cumbersome. The top left general information about the KiwiSDR instance are nice to have and read once, but don't warrant taking all that top bar space all the time. The logos don't, and the average user doesn't care about the CPU and network debug.

Same about the bottom left panel: the contact links are not useful to keep at hand all the time, and the average user doesn't care about the config, uptime, audio and network debug...

I think most people look at this bottom left panel only for the user slots. I think there should be a dedicated "user status" panel, with these user slots, and the callsign input field should be moved to it and free the top bar, and the external chatroom link I mention in #60 should be put there too. The debug from that panel, and in general everywhere, should be kept out of the way by default for average users. This would also help with the user experience on mobile devices while waiting for a dedicated interface.

web page at :8073 refuses to connect

I can ssh into the beaglebone and do ku or kd, but cannot get a web page.

Any hints?

Output of ms:

Nov 07 01:04:39 kiwisdr kiwid[2387]: DEBIAN 8 Nov 07 01:04:39 kiwisdr kiwid[2387]: USE_SPIDEV Nov 07 01:04:39 kiwisdr kiwid[2387]: LOAD_SPI = no Nov 07 01:04:39 kiwisdr kiwid[2387]: Starting kiwid Nov 07 01:04:40 kiwisdr kiwid[2387]: Start kiwid: OK Nov 07 01:04:40 kiwisdr kiwid[2387]: Mon Nov 7 01:04:40 UTC 2016 Nov 07 01:04:40 kiwisdr kiwid[2393]: 0:00:00 .... KiwiSDR v1.20 -------------------------------------------------------------------- Nov 07 01:04:40 kiwisdr kiwid[2393]: 0:00:00 .... compiled: Nov 7 2016 00:44:11 Nov 07 01:04:40 kiwisdr kiwid[2393]: 0:00:00 .... reading configuration from file /root/kiwi.config/kiwi.json Nov 07 01:04:40 kiwisdr kiwid[2393]: 0:00:01 .... serial number from EEPROM: 1389 Nov 07 01:04:40 kiwisdr kiwid[2393]: 0:00:01 .... reading configuration from file /root/kiwi.config/dx.json Nov 07 01:04:40 kiwisdr kiwid[2393]: 0:00:01 .... 883 dx entries Nov 07 01:04:40 kiwisdr kiwid[2393]: 0:00:01 .... listening on port 8073 for "openwebrx" Nov 07 01:04:40 kiwisdr kiwid[2393]: 0:00:01 .... webserver for "openwebrx" on port [::]:8073 Nov 07 01:04:41 kiwisdr kiwid[2393]: 0:00:01 .... ### using SPI_DEV Nov 07 01:04:42 kiwisdr kiwid[2393]: 0:00:02 .... FPGA version 1 Nov 07 01:04:42 kiwisdr kiwid[2393]: 0:00:02 .... CFG read /root/kiwi.config/kiwi.json: sdr_hu_register = false Nov 07 01:04:45 kiwisdr kiwid[2393]: 0:00:05 .... (0 users) Nov 07 01:04:45 kiwisdr kiwid[2393]: 0:00:05 .... UPDATE: scheduled Nov 07 01:04:45 kiwisdr kiwid[2393]: 0:00:06 .... UPDATE: checking for updates Nov 07 01:04:46 kiwisdr kiwid[2393]: 0:00:06 .... UPDATE: version 1.20 is current Nov 07 01:04:46 kiwisdr kiwid[2393]: 0:00:07 .... DDNS: private IPv4 <192.168.1.13> 0xc0a8010d /24 0xffffff00 Nov 07 01:04:46 kiwisdr kiwid[2393]: 0:00:07 .... DDNS: public ip 47.185.229.231

Feature request: IPv6 support to kiwid

kiwid listens only on IPv4 socket. It does not bind to IPv6 socket. It would be nice to have IPv6 support in kiwid.

Until kiwid has native support there is workaround to get IPv6 work. Install socat to beaglebone and make IPv6 -> IPv4 proxy.

socat TCP6-LISTEN:8073,reuseaddr,fork,bind=[2001:DB8::BEA6:73] TCP4:127.0.0.1:8073

then KiwiSDR seems to work fine with IPv6.

Peak signal S-Meter display and possibly peak hold

Hi,

I frequently use the SDR's to compare signal strengths of stations participating in nets or to compare antennas. This is tricky due to signal fading and other variations in propagation.

Would it be possible to add a variable decay time, or a peak hold button, to the peak reading on the S-Meter so that it could be used to register the maximum received level over a longer period of time such as 1 minute or more ?

I also wondered if it would be possible to add some sort of peak hold trace, possibly dots or a translucent line to the spectrum display ?

Regards,

Martin - G8JNJ

jks-prv / beagle_sdr_gps Goto Github PK

beagle_sdr_gps's People

Stargazers

Watchers

Forkers

beagle_sdr_gps's Issues

gdb --batch -p pidof kiwid -ex "bt" -ex "quit"

How to check this issue.

1: receive time signal.

2: a dial to show carrier frequency is below.

3: change a mode to LSB. and then click a carrier frequency at waterfall.

4: received frequency is moved to the upper. display frequency is 10001.52 kHz.

Recommend Projects

Recommend Topics

Recommend Org

gdb --batch -p `pidof kiwid` -ex "bt" -ex "quit"