jks

About

Username
jks
Joined
Visits
32,324
Last Active
Roles
Member, Administrator, Moderator
Points
331

Reactions

589Helpful509Awesome

  • My unit does not seem to be powering up

    jksjks
    Happy to hear that.

    Even though you plug power into the Kiwi board it is first routed to the Beagle and its power management chip (PMIC) for monitoring, protection and switching. From there it goes on to power the Beagle and then back over to the Kiwi board. The PMIC has an absolute maximum input voltage spec of +20 VDC. It won't power-on at that voltage (5.8V is the limit) but it's supposed to withstand it. So that's why you got away with applying 9V.

    However we have had a couple Kiwi/Beagles expire when reverse input voltage was applied.
    PowernumptyG8JNJ

  • Feature request - receiver info on status page [trial in v1.334]

    jksjks
    Okay, there is a trial of this in today's v1.334, e.g. "kiwi:8073/users" Only responds to connections from the local network.
    Response is JSON with a couple of the fields URI encoded. This mostly because it already existed as a protocol with the Kiwi Javascript and I've been trying to move everything to JSON anyway.

    Example: 
    [{"i":0,"n":"ZL%2fKF6VO","g":"Tauranga,%20New%20Zealand","f":518000,"m":"cw","z":11,"t":"0:00:15","rt":0,"rs":"0:00:00","e":"","a":"192.168.1.2"},{"i":1},{"i":2},{"i":3}]
    So a JSON array with as many objects as there are rx channels. Many of the fields can be an empty string value if there is no info.
    • i: channel index
    • n: name/callsign field, URI encoded
    • g: geolocation, URI encoded
    • f: freq Hz
    • m: mode
    • z: zoom level 0-14
    • t: connect time h:mm:ss
    • rt: time remaining type: 0 = no limit, 1 = inactivity limit will expire first, 2 = /24 hr limit will expire first
    • rs: time remaining h:mm:ss (inactivity or /24 hr)
    • e: extension in use
    • a: user's ip address (as you would see on admin status tab)
    PowernumptyHB9TMCrz3dvp

  • "Cannot use extensions while another channel is in DRM mode." - but no other DRM mode in use..

    jksjks
    Okay, I got what I needed, thanks.
    Until there is a fix (won't be anytime soon) just disable DRM to keep this from happening.
    cathalferris

  • New links: rx.kiwisdr.com, map.kiwisdr.com, snr.kiwisdr.com, forum.kiwisdr.com

    jksjks
    You can also use these links which might be slightly easier to remember:
    johnk5mo

  • Kiwid can't start on BB-AI after update [spidev issue, problem disappeared with reinstall]

    jksjks
    Neat. I did not know that would work. After a kernel upgrade you can also do: 
    root@ai:~# cdp
root@ai:~/Beagle_SDR_GPS# make install_kiwi_device_tree
install Kiwi device tree to configure GPIO pins
4.14 4.14.108-ti-r123
cp platform/beaglebone_AI/am5729-beagleboneai-kiwisdr-cape.dts /opt/source/dtb-4.14-ti/src/arm
(cd /opt/source/dtb-4.14-ti; make)
make[1]: Entering directory '/opt/source/dtb-4.14-ti'
  DTC     src/arm/am5729-beagleboneai-kiwisdr-cape.dtb
make[1]: Leaving directory '/opt/source/dtb-4.14-ti'
cp /opt/source/dtb-4.14-ti/src/arm/am5729-beagleboneai-kiwisdr-cape.dtb /boot/dtbs/4.14.108-ti-r123
cp /opt/source/dtb-4.14-ti/src/arm/am5729-beagleboneai-kiwisdr-cape.dtb /boot/dtbs/4.14.108-ti-r123/am5729-beagleboneai.dtb
    Where all references to 4.14.108-ti-r123 above will be 4.14.108-ti-r124 in your case (it gets it from doing a "uname --r"). Restart after doing this.
    rz3dvp