开云体育

Hi Bob... Very elegant solution.? dw-cron is working perfectly.? It appears my initial problem was the result of nano writing crontab out as a MSDOS file.? Not being a regular nano user, it took me

Crontab are used to run programs at specific time.This requires a specific layout within the crontab. So 2 things:1. I'd create a specific crontab bash script and call it only from crontab ???

Hi Rob My crontab file follows.? Still getting the same error. # Edit this file to introduce tasks to be run by cron. # # Each task to run has to be defined through a single line # indicating with

Doing a search on "cron bad fd number" shows that the issue is with the shell. " >& is the *csh* syntax (also supported by zsh and recent versions of bash ) to redirect both stdout and stderr to a

Hi Ian Here is the exact output I am receiving from cron: From: root@raspberrypi (Cron Daemon) To: pi@raspberrypi Subject: Cron <pi@raspberrypi> /home/pi/dw-start.sh 2>&1 MIME-Version: 1.0

Hi Ian Here is the output from your command (DW started normally): pi@raspberrypi:~ $ cat output.txt RealVNC found - defaults to connecting to the :0 root window Direwolf in GUI mode start up

76??? FM PKT PTT SELECT??? was? DTR. I changed that to RTS. Direwolf now beacons correctly. I don't know if the data is formatted correctly, but it is keying/unkeying. Thank you very much.

Look at menu items 074 through 079 Patrick (N3TSZ)

I just stumbled on something else. Using PTT /dev/ttyUSB1 RTS does key and unkey the 991, but only on sideband, LSB or USB, not FM or AM.

Does RIG 135 refer to the 991a. Is Direwolf addressing hamlib? I will give it a try. This is how the 991a is set up for WSJT-X. WSJT-X will key the radio in 2 meters, and HF. T

I think this discussion has been swirling around some vagueness but the way I read it, you are using CAT-based PTT control with Fldigi and WSJT-X and *not* a serial port's RTS signal for PTT. Having a

Hamlib 4.2. There are ferrites on both ends. The setup works fine with fldigi and wsjt-x

Joe, Run the exact command from a terminal (replacing /dev/null with a file) and see if you get the same error. i.e /home/pi/dw-start.sh >/home/pi/output.txt 2>&1 What is on line 1 of dw-start.sh? Ian

Hi Ian. The Direwolf documentation makes the recommendation as a fail safe for a hung or crashed system. I just took the default to see if I could get things running. I am more perplexed about that

Joe, Looks like you are starting dw-start.sh every minute. Is that the intent?? Ian VK1IAN

An easy check for RF is to dial down the power as low as possible.Most "big rigs" will go down to about 5 watts and ground as you say.If the PTT works okay at 5 watts, you know that is the problem. If

Hi Rob No...I was primarily directing my comments to Rick Hatton....sorry for any confusion. BTW, the FT991a is very easy to interface to, requiring only a usb cable.? So, while you can create a

Running pi os, dw 1.6 and dw-start 1.3 on a pi 4 I can start dw-start.sh from a terminal window. When running from crontab, the following shows up in an email: /bin/sh: 1: Syntax error: Bad fd number

Have a look at FLARQ http://www.w1hkj.com/FlarqHelpFiles/ Danny K5CG

Keith,Are you asking me?Or are you just replting to the wrong part of the thread? I have never had an issue with PTT being stuck when using USB to TTL serial converters.I have used the DTech FTDI with