开云体育

Thanks Dave. ?I've got Digital Gain (Menu 37) at 75, and put Dig Vox (Menu 40) at 30. ?I tried to turn on "VOX" on the front menu, but it won't let me in packet mode.

Yes, menu 40 you might need to mess about with levels as well. I use a Signalink but have just swapped to a Sound Card just to check my advice works. Connected to Winkink no issues with menu 40 set at

Rather, do I need VOX turned on on the 857 with the Sabrent?

I ended up ditching the SignaLink and went to the Sabrent sound card - much better and easier. ?I'm getting tones out, and was connected for almost 90 seconds to a local EOC, but didn't get emails to

There's no need to be root so you shouldn't use "sudo bash" Make sure you are the pi user and run rm -rf ~/pi-build The above command will remove any previous downloads. Now run git clone

Did you enable VNC? From the main pi menu->preferences->raspberry pi configuration. Look under the interfaces tab. Is VNC set to enable? -- 73, de KM4ACK YouTube ( https://youtube.com/km4ack ) | Tip

pi@house:~ $ sudo bashroot@house:/home/pi#? git clone https://github.com/km4ack/pi-build.git $HOME/pi-build && bash $HOME/pi-build/build-a-pifatal: destination path '/root/pi-build' already exists

It seems that there is some problem with the ftdi drivers and Linux -- 73 de Eugene / ZR4EM

@ KN4VXP Maybe its the port you are connecting to. Perhaps you should try another available port. Look for a similar description or try entering the command lsusb in terminal to see the port. It is

Well, maybe... I can run build-pi, but when I check flrig, it does not install. (it does install PAT... and RTC OK) I am also NOT getting VNC showing on the upper bar (top right). I can NOT check the

Nope it seems to be a USB hickup with the Linux core. So no, its maybe a collection of stuff and its frustrating. The other stuff is when the baud rate (not in your case) is fine for an instant but

The guys that build/maintain FLRIG might be able to give you specifics on the errors you are seeing. /g/linuxham/topics -- 73, de KM4ACK YouTube ( https://youtube.com/km4ack ) | Tip

What error are you seeing? -- 73, de KM4ACK YouTube ( https://youtube.com/km4ack ) | Tip Jar ( https://www.paypal.me/km4ack ) Twitter ( https://twitter.com/km4ack ) | Store (

Not an answer as to why your Signalink doesn’t key the radio but the FT857 has data VOX built in that will get you up and running. * menu 40 Dig VOX 95

Has anyone a issue after they updated buster of the build a pi not wanting to install

Also, JS8CALL works perfect connects the first try every try. I don't get it?

I don't know if anyone can take a look at this error report from flrig and advise? I'm not sure what I'm looking at. I was able to connect to the radio all day yesterday and can't connect for anything

My setup: 1. BAP v2.0 2. Pi4 3. TS-590S on USB 2.0 4. U-Blox GPS on USB 2.0 5. Boot Device: SD Card I plugged in a spare CM108 based USB sound card directly into the back of the Pi's USB 3.0 and boom,

Dafcho's answer is the right one. After lots of trial and error testing, I came to the same conclusion. Video coming soon. -- 73, de KM4ACK YouTube ( https://youtube.com/km4ack ) | Tip Jar (

I have a similar problem with a Kenwood D74 used as a KISS modem, If the D74 was on at boot up the GPS would fail. I eventually worked out that the D74 could boot up as ttyACM0, 1 or 2 and sometimes