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 around 30. You have have to adjust menu 34 Digial Gain.

Good luck 73 de Dave G7HJX?

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 transmit. ?I've tried my three local gateways, and no joy on any of them. ?Do I need to have VOX turned on for Sabrent sound card?

On Fri, Jul 3, 2020 at 08:32 AM, Scott Reutter wrote:

pi@house:~ $ sudo bash

root@house:/home/pi#? git clone $HOME/pi-build && bash $HOME/pi-build/build-a-pi

fatal: destination path '/root/pi-build' already exists and is not an empty directory.

root@house:/home/pi#?

?

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 https://github.com/km4ack/pi-build.git $HOME/pi-build && bash $HOME/pi-build/build-a-pi

?
--

On Fri, Jul 3, 2020 at 07:41 AM, stephen shearer wrote:

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 box in "interfaces" - it is gray...

Did you enable VNC? From the main pi menu->preferences->raspberry pi configuration. Look under the interfaces tab. Is VNC set to enable?
?
--

开云体育

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 usually something with either ttyUSB[and either 1 or 0 or some number)?or something similar. The directory you are linking with is constantly changing. It also seems from??that according to a post by?? on?? that?

post 10??suggests that the ftdi drivers are not ARM compatible which the driver page??does back up, if that is the case then this is going nowhere until we have new drivers?

So its a problem again with the Linux core and USB
Also see??with the mention that

/dev/ttyS0?and?/dev/ttyAMA0?are inbuilt UARTS?/dev/ttyprintk?MAY be yours.

NOT all USB devices/drivers are "tty".

Unplug the device, list?/dev?then plug in and see what has changed.

--
73 de Eugene / ZR4EM

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 box in "interfaces" - it is gray...

73, steve WB3LGC

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 for continued use maybe a problem. When I program an ESP32 on 115k its fine, but if I want the continuous serial monitoring it drops the connection so slower is maybe better. I do not know anymore if USB and The RasPi is a good idea. Maybe using plain UART comms would be better but you have just so much UART TTL ports. I am now talking BS like my bosses in circles and confusing everyone. Its seems there is no short resolution for the problem that updating the core and firmware. And by that time we have a raspberry pi 10
--
73 de Eugene / ZR4EM

On Thu, Jul 2, 2020 at 09:44 PM, KN4VXP | Chad wrote:

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 today, I'm starting to wonder if I have an issue with the radio?

The guys that build/maintain FLRIG might be able to give you specifics on the errors you are seeing. /g/linuxham/topics

?
--

What error are you seeing?
--

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 today, I'm starting to wonder if I have an issue with the radio??

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, the GPS is no longer seen by the OS. Plug the sound card in via a 3' USB 2.0 extension cable into the USB 3.0 port, and so far, GPS is still there. Plug the sound card back in directly on the back of the Pi, and GPS is gone, but, disable WiFi, reboot, and it stays. Next test - remove sound card, plug in a M.2 NVMe external drive (Samsung EVO 960 in a QNine Case) into the Pi's USB 3.0 port and GPS is gone. Put a snap-on ferrite bead onto the 1' long USB 3.0 cable at the NVMe drive end, and GPS is still there.

Not sure at this point if USB 3.0 is causing it, and how WiFi fits in, but I suspect 2.4 GHz jamming. At any rate, the ferrite bead on the USB 3.0 cable going to the NVMe drive keep the GPS connected. I will leave it connected to see if the GPS stays or falls off, but by all means, if anyone with the problem has some ferrite beads to snap onto the USB 3 cable, please do, and share your results. UPDATE: after 4 hours and the GPS is still there.
73,
Joe - AD2DX

Dafcho's answer is the right one. After lots of trial and error testing, I came to the same conclusion. Video coming soon.
--

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 ‘steal’ the port that GPSD uses I.e. ACM0. My point is could the drive be stealing the port in your setup? A total pain as I had to keep changing the KISS port in Xastir until I created a symlink to give the radio a unique port name. Next step is to do the same thing with the GPS and change the Port in GPSD to the symlink port. I realise if I change GPS modules I need to change the symlink as it’s based on vendor Id etc.