开云体育

When I access the Wo-We from my Windows 10 PC with the Roadom monitor attached to the Wo-We via a USBC cable if comes up OK. Attaching the HDMI cable from the Wo-We to the monitor I get a little video during the boot process and then Black Screen. I think this may be a HDMI driver issue on Mint/Wo-We? Back the the USBC connection issue. Nomachine VNC works great and I get a display that is running 1920x1024 and the Nomachine app on my Windows PC looks great. Disconnect the monitor from the Wo-We to run headless and the Windows PC resolution is so large I can't see the bottom of the screen and Conky and a few Icons is all that displays. Does anyone know how to get Nomachine VNC to stay at 1920x1024 when no monitor is hooked to the Wo-We PC? Thanks Dave

I know this is Elecraft KX2 specific, but Jason suggested I post here for possible help. I am trying to get started on JS8Call, and am having problems. I set up FT8 a few years ago, made a couple contacts, and didn't go back to it. Today, I re-setup FT8 (new computer) and make contacts. I set JS8Call up with the same settings, but am getting this error: Rig Failure Hamlib Error: IO error while opening connection to rig. I am using a Sabrent sound card with the Mic, Phones and ACC all plugged into a USB splitter if that matters. I have very little experience with Digital modes. Any direction would be appreciated. Thx.

I am using an Icom IC-705 using the USB port for control and audio. I just did a clean build on my Evolve laptop to Mint 22 and everything appears to work except AX.25 with PAT. It will set the frequency OK and key the rig but it is producing no transmit audio as monitored on another radio. VARA FM creates transmit audio from PAT just no packet audio. On the 705 the transmit power is set to 50% I suspect something is wrong in direwolf but the config shows ADEVICE plughw:3.0 and the arecord -l command returns card 3: CODEC [USB Audio CODEC}, device 0: USB Audio [USB Audio] I am using FLRig for rig control. When I run direwolf -p from the command window it receives audio OK from other stations on the frequency. Just no transmit audio. Any ideas? Thanks, Dave - KD7UM

Read the comments before updating! https://www.raspberrypi.com/news/a-new-release-of-raspberry-pi-os Regards Jon

I ran into an issue and need some help, I am running this version of APRSdroid on a Revvl android tablet connected to an anytime at-5888uv. It’s connected via a digirig mobile using a dev version of APRSdroid https://github.com/bxlentpartyon/aprsdroid/releases/tag/digirig-test-release-1 It connects fine and transmits with no issue. I confirmed with aprs.fi and with my PC connected to an ht. However it will not decode any packets. I confirmed that the anytime is receiving audio but the tablet does not decode it. I probably have an APRSdroid setting or setting configured wrong. Any advice would be much appreciated.

Hi All! Im trying to build a 73Linux. Hardware is Pi 5, New Display touch 2, gps/glonas dongle. The Display is 720 × 1280 Portrait but in software I can switch it to Landscape 1280 x 720. I'm missing the lower part of the screen. It's a way to fix it? Thanks in advance Jorge VE3EAD

I have been having problems to make work my gps when I use my raspberry pi 4B connected to a external USB SSD hard disk. It seems to see few satellites status, but does not fixed. Different situation when I boot with a micro SD card, it get fixed with no problem. I have changed all USB ports to boot the SSD hd but it is the same, never get fixed and only with cgps -s only gets few 2 to 5 SATs but does not get fixed. I have tried Gps update tool, etc.. Any help is appreciated. HP1GDS / George

Hello. Anybody succeed in fixing the 403 error. I understand that the 7-day needs to change to a 5-day forecast. I tried to apply fixes per Elewin recommendations but did not work. Anyone make the fix? Thanks and 73.

I recently setup a new Evlove III laptop with Mint, loaded 73 Linux. I configured Yaac and my mobilinkd tnc 3 with a Yaesu FT70. It worked great, was able to transmit/Recieve packets. About a week later I decided to try and setup digirig with FT-817 to use for FT-8. No joy, could receive but no transmit....gave up and went back to yaac and mobilinkd.....when i do the terminal part, i get the above error I'm really just appliance operator and have not been able to get it back running..... Would appreciate any help to get aprs back up and running again. thanks in advance 73 frankie

Guys, I saw this on Kickstarter and I backed it since I think it is a cool and useful product. NZUP powerbank with 100W USB-C and 12v/24v barrel jack outputs I think this would be useful for some hams doing POTA or a mobile setup. It also allows for solar input up to 25 volts, so you can recharge the guy while using it at a campsite or wherever. No association with the company that makes it -- but as I said I pledged for it on Kickstarter and I think it will make a great product. KM4OCR

Hello After installing 73 Linux package on Raspberry Pi 5 I can’t use HAM Clock. Any time I open that app I’m getting a message - RESTful server is using same port 8080. Where and how I can update port settings? Thanks! 73 De AA1SL

I noticed in Jason's latest newsletter he mentioned Meshtastic devices he saw at the Dayton Hamvention. I've been playing with these things for a couple months and thought I'd share some of my learnings. None of what follows is intended to dissuade anyone from playing around or running their own experiments, they are neat toys, but (jumping to the bottom line real quick) Meshtastic is not ready for prime-time as a reliable comms mechanism in a disaster scenario in a way that APRS or even VARAC might be (my opinion). There are alot of Youtube videos and Internet articles explaining what Meshtastic is and how to get started with it, so I'll not cover that part. I'll just cover some conclusions I've drawn. There are many device makers, but two primary (most common) ones: Heltec and RAK WISBlock. Heltec have many models and are generally cheaper, but draw more power due to the chips used. People who want to build a solar-powered unit, for example, usually go with the RAK WISblock units as many have had success keeping them running for days/weeks in decent solar locations with just a 3K amp-hour battery as backup. The Heltec's, with the same battery, run down in 1-2 days (although you can power down several of the functions such as GPS and extend this to maybe 3-4 days, see this article for more about that: https://meshtastic.discourse.group/t/heltec-tracker-v1-and-v1-1-power-config/12016. If you don't care about location tracking of your Meshtastic node (and I'll dare say for most home-based use this isn't needed) you can skip the GPS and save money and power. This is not like FT8 or other digital modes where an accurate time is required -- GPS is mostly not necessary unless you are actually using the Meshtastic node as a tracking device. As a beginner selecting a device to purchase, go to https://flasher.meshtastic.org/, drop down the "Select Target Device" list and make sure the device you intend to buy is on that list. There are hundreds of other LoRa devices that will not run the Meshtastic software/firmware and are not listed there. Flashing your new device with Meshtastic using that Flasher website is the first step once you have the device in hand. After that refer to the meshtastic.org website for configuration guidance. The factory default config will work without tweaking to start. There are ALOT of config options, and lots of ways to make your device not work -- but you can always reflash back to "factory". The antenna you choose also plays a huge part, as in most radio comms. After testing a couple dozen of the stubby antennas that come with the Lora boards from Heltec and RAK, only about 10% of them actually had decent SWR (below 3:1) -- even when they physically appeared identical. I've decided to build my own antennas for 915MHz (for USA use). I'm skimming over a very few high points of a topic where there is alot to learn. I'll leave most of that fun up to you. But why do I say "Meshtastic is not ready for prime-time as a reliable comms mechanism"? Because in areas where there are few Meshtastic nodes, messages do not get passed. And in areas where there are many Meshtastic nodes, congestion occurs and messages do not get passed (examples are England and Sweden, with other European countries rapidly approaching the congestion level). There seems to be a narrow sweet spot where Meshtastic works nicely. There is also a contentious Meshtastic feature called MQTT. This feature uses the Internet to pass messages if the radio-radio connections cannot be made. It is contentious because in practice it causes congestion if many nodes in an area use it. It is turned off by default and best practice calls for it to stay turned off. A bad actor could also use a bunch of MQTT-enabled Meshtastic nodes to disrupt communications -- there isn't any protection against this as of now. So, again, the above is my take on things to date. New firmware may modify some of the concerns above in the future. The little Meshtastic nodes are fun to tinker with are are still relatively inexpensive, and there is alot of information availabl

I just installed Direwolf and LinBPQ configured as an RMS for 1200 baud Packet following the video "Winlink Gateway on a Raspberry Pi LinBPQ". The install is on a fresh Pi 3B with Debian Bookworm. Everything seems to be running correctly but when I try to connect with either Winlink Express or Pat from Windows (don't have Pat on a PI). It connects but I only get the prompt for a BPQ node (Type ? for list of available commands.) instead of the message in the Outbox being transmitted. I have been approved as a Sysop. I have successfully been working with Winlink Express and Pat using both Vara HF and ARDOPC but don't have a VHF Packet station within range of my system so I'm not sure if this is a client setup problem or a setup for Pi and RMS. Any help is appreciated. 73 Dave WB9TEN

Hi I have been experimenting to send APRS HF via JS8 call message to and vhf APRS stations receiving good for VHF. I would like to know if is it possible to receive a message on JS8 call HF via APRS, from an station on VHF using YAAC? What should the JS8 all station Hf have to do to listen or request a message send to the HF station. In other words is there a command on JS8 call to request any pending message that was send via APRS? thanks George/HP1GDS