Re: Configuring PTT on Windows 10
The cm108-ptt feature for Windows is new to the v1.7 beta version
but if it behaves anything like the Linux version, it should
automatically associate the correct HID parameter for the specific
sound device you defined in ADEVICE (the sound device).? Looking at
your output below, it seems like Direwolf has found a port and
accepted it.? Is Direwolf NOT keying up your radio?? If you look at
section 9.2.9.5 in the User Guide, you should see more details on
getting this working.?
There is also another thread (though for Linux) on getting a DRA
device working:
??
/g/RaspberryPi-4-HamRadio/topic/getting_a_dra_30_to_work_with/75504791
--David
KI6ZHD
??
On 07/22/2021 09:51 AM, Jeffrey Komori
(KH6JUZ) via groups.io wrote:
toggle quoted message
Show quoted text
I am using two Masters Communications DRA-50 on a
Windows 10 Pro PC and using the following configs:
ADEVICE "USB 1 Mic" "USB 1 Speakers"
ARATE 48000
CHANNEL 0
MYCALL KH6JUZ-10
MODEM 1200 E+ /2
PTT CM108
When I startup DIREWOLF, here's what I get:
>direwolf -X 32
Dire Wolf DEVELOPMENT version 1.7 A (Mar 15 2021)
Includes optional support for: ?cm108-ptt
?
Reading config file direwolf.conf
There are multiple USB Audio Devices with GPIO capability.
Explicitly specify one of them for more predictable
results:
?
?"\\?\hid#vid_0d8c&pid_013a&mi_03#8&b470d0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
?
?"\\?\hid#vid_0d8c&pid_013a&mi_03#8&364f8d28&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
Run the "cm108" utility for more details.
Config file line 120: Found
"\\\\?\hid#vid_0d8c&pid_013a&mi_03#8&364f8d28&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
when expecting GPIO number or device name like /dev/hidraw1.
Available audio input devices for receive (*=selected):
? ? 0: Digital Audio (S/PDIF) (Cirrus
? ? 1: USB 2 Mic (2- USB PnP Sound Dev
?* ?2: USB 1 Mic (USB PnP Sound Device ? (channel 0)
Available audio output devices for transmit (*=selected):
? ? 0: Speakers (Cirrus Logic CS4206B
? ? 1: Digital Audio (S/PDIF) (Cirrus
? ? 2: USB 2 Speaker (2- USB PnP Sound
? ? 3: AMD HDMI Output (AMD High Defin
?* ?4: USB 1 Speakers (USB PnP Sound D ? (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 48000
sample rate / 2.
Using
\\?\hid#vid_0d8c&pid_013a&mi_03#8&364f8d28&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
GPIO 3 for channel 0 PTT control.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001
...
?
Now connected to IGate server noam.aprs2.net
(44.184.136.10)
Check server status here
I'm trying to figure out what I need to put on the "PTT" line
to specify the specific DRA-50.
Here's the output for CM108:
>cm108
? ? VID ?PID ? Product ? ? ? ? ? ? ? ? ? ? ? ? ?HID [ptt]
? ? --- ?--- ? ------- ? ? ? ? ? ? ? ? ? ? ? ? ?---------
? ? 248a 8514 ?Wireless Receiver ? ? ? ? ? ? ?
?\\?\hid#vid_248a&pid_8514&mi_00&col03#9&b8de63f&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
? ? 248a 8514 ?Wireless Receiver ? ? ? ? ? ? ?
?\\?\hid#vid_248a&pid_8514&mi_00&col04#9&b8de63f&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
? ? 04d9 1919 ?DasKeyboard ? ? ? ? ? ? ? ? ? ?
?\\?\hid#vid_04d9&pid_1919&mi_00#8&15dd3106&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
? ? 04d9 1919 ?DasKeyboard ? ? ? ? ? ? ? ? ? ?
?\\?\hid#vid_04d9&pid_1919&mi_01#8&39b46ec8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
? ? 05ac 820a ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
\\?\hid#vid_05ac&pid_820a#8&6324f3b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
? ? 248a 8514 ?Wireless Receiver ? ? ? ? ? ? ?
?\\?\hid#vid_248a&pid_8514&mi_00&col01#9&b8de63f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
? ? 248a 8514 ?Wireless Receiver ? ? ? ? ? ? ?
?\\?\hid#vid_248a&pid_8514&mi_01#9&1ebe027d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
** ?0d8c 013a ?USB PnP Sound Device ? ? ? ? ? ?
\\?\hid#vid_0d8c&pid_013a&mi_03#8&b470d0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
? ? 248a 8514 ?Wireless Receiver ? ? ? ? ? ? ?
?\\?\hid#vid_248a&pid_8514&mi_00&col02#9&b8de63f&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
? ? 05ac 8242 ?IR Receiver ? ? ? ? ? ? ? ? ? ?
?\\?\hid#vid_05ac&pid_8242#7&236c5da5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
** ?0d8c 013a ?USB PnP Sound Device ? ? ? ? ? ?
\\?\hid#vid_0d8c&pid_013a&mi_03#8&364f8d28&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
? ? 05ac 820b ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
\\?\hid#vid_05ac&pid_820b#8&c32dbd1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
?
** = Can use Audio Adapter GPIO for PTT.
?
-Jeffrey Komori, KH6JUZ
|
Configuring PTT on Windows 10
I am using two Masters Communications DRA-50 on a Windows 10 Pro PC and using the following configs:
ADEVICE "USB 1 Mic" "USB 1 Speakers"
ARATE 48000
CHANNEL 0
MYCALL KH6JUZ-10
MODEM 1200 E+ /2
PTT CM108
When I startup DIREWOLF, here's what I get:
>direwolf -X 32
Dire Wolf DEVELOPMENT version 1.7 A (Mar 15 2021)
Includes optional support for: ?cm108-ptt
?
Reading config file direwolf.conf
There are multiple USB Audio Devices with GPIO capability.
Explicitly specify one of them for more predictable results:
? ?"\\?\hid#vid_0d8c&pid_013a&mi_03#8&b470d0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
? ?"\\?\hid#vid_0d8c&pid_013a&mi_03#8&364f8d28&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
Run the "cm108" utility for more details.
Config file line 120: Found "\\\\?\hid#vid_0d8c&pid_013a&mi_03#8&364f8d28&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" when expecting GPIO number or device name like /dev/hidraw1.
Available audio input devices for receive (*=selected):
? ? 0: Digital Audio (S/PDIF) (Cirrus
? ? 1: USB 2 Mic (2- USB PnP Sound Dev
?* ?2: USB 1 Mic (USB PnP Sound Device ? (channel 0)
Available audio output devices for transmit (*=selected):
? ? 0: Speakers (Cirrus Logic CS4206B
? ? 1: Digital Audio (S/PDIF) (Cirrus
? ? 2: USB 2 Speaker (2- USB PnP Sound
? ? 3: AMD HDMI Output (AMD High Defin
?* ?4: USB 1 Speakers (USB PnP Sound D ? (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 48000 sample rate / 2.
Using \\?\hid#vid_0d8c&pid_013a&mi_03#8&364f8d28&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} GPIO 3 for channel 0 PTT control.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
?
Now connected to IGate server noam.aprs2.net (44.184.136.10)
Check server status here http://44.184.136.10:14501
I'm trying to figure out what I need to put on the "PTT" line to specify the specific DRA-50. Here's the output for CM108:
>cm108
? ? VID ?PID ? Product ? ? ? ? ? ? ? ? ? ? ? ? ?HID [ptt]
? ? --- ?--- ? ------- ? ? ? ? ? ? ? ? ? ? ? ? ?---------
? ? 248a 8514 ?Wireless Receiver ? ? ? ? ? ? ? ?\\?\hid#vid_248a&pid_8514&mi_00&col03#9&b8de63f&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
? ? 248a 8514 ?Wireless Receiver ? ? ? ? ? ? ? ?\\?\hid#vid_248a&pid_8514&mi_00&col04#9&b8de63f&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}
? ? 04d9 1919 ?DasKeyboard ? ? ? ? ? ? ? ? ? ? ?\\?\hid#vid_04d9&pid_1919&mi_00#8&15dd3106&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
? ? 04d9 1919 ?DasKeyboard ? ? ? ? ? ? ? ? ? ? ?\\?\hid#vid_04d9&pid_1919&mi_01#8&39b46ec8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
? ? 05ac 820a ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? \\?\hid#vid_05ac&pid_820a#8&6324f3b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
? ? 248a 8514 ?Wireless Receiver ? ? ? ? ? ? ? ?\\?\hid#vid_248a&pid_8514&mi_00&col01#9&b8de63f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
? ? 248a 8514 ?Wireless Receiver ? ? ? ? ? ? ? ?\\?\hid#vid_248a&pid_8514&mi_01#9&1ebe027d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd
** ?0d8c 013a ?USB PnP Sound Device ? ? ? ? ? ? \\?\hid#vid_0d8c&pid_013a&mi_03#8&b470d0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
? ? 248a 8514 ?Wireless Receiver ? ? ? ? ? ? ? ?\\?\hid#vid_248a&pid_8514&mi_00&col02#9&b8de63f&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
? ? 05ac 8242 ?IR Receiver ? ? ? ? ? ? ? ? ? ? ?\\?\hid#vid_05ac&pid_8242#7&236c5da5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
** ?0d8c 013a ?USB PnP Sound Device ? ? ? ? ? ? \\?\hid#vid_0d8c&pid_013a&mi_03#8&364f8d28&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
? ? 05ac 820b ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? \\?\hid#vid_05ac&pid_820b#8&c32dbd1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
?
** = Can use Audio Adapter GPIO for PTT.
?
-Jeffrey Komori, KH6JUZ
|
Re: dw-start.sh will not run from crontab
I think it must be only 4 asterisk. 5 makes the task be done twice per minute...
15,30 * * * * /home/.../some.sh
73, Mikel EA2CW
|
Re: dw-start.sh will not run from crontab
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 a couple of tries to figure out this was the problem.
Thanks much for the help and guidance.
73, Joe
|
Re: dw-start.sh will not run from crontab
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
??? We'll name it dw-cron.sh
??? In that script, you put the supplied code <see below>?
??? Make sure this file is executable
??? Assumption is that this file (dw-cron.sh) is in the home directory
2. In crontab file, follow the format so that the file in number 1 is called at a specific interval ??? In the example below, the dw-cron.sh script should be run 2x per hour at 15 and 45 minutes after the hour. ???
---------- dw-cron.sh --------------
#!/bin/bash # # file: dw-cron.sh #???? called from crontab to check if direwolf is running #???? if it is not running, it will restart #
if ! pgrep direwolf > /dev/null; then ?? /home/pi/dw-start.sh > /dev/null 2>&1 & fi
-------- end ---------------
----- crontab ----- # 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 different fields when the task will be run # and what command to run for the task # # To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').
15,45 * * * * * /home/pi/dw-cron.sh
-------- end ---------------
I have not tried these exact examples (never used pgrep before), but have used cron for other tasks where I have called scripts. The alternative would be to directly call the dw-start.sh script with ???? 15,45 * * * * * /home/pi/dw-start.sh
but if direwolf is already running, I am pretty sure it will start another instance and try to use the same settings.
|
Re: dw-start.sh will not run from crontab
On Wed, Jul 21, 2021 at 10:47 AM, Rob Giuliano wrote:
if ! pgrep direwolf > /dev/null; then
/home/pi/dw-start.sh > /dev/null 2>&1 &
fi
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 different fields when the task will be run # and what command to run for the task # # To define the time you can provide concrete values for # minute (m), hour (h), day of month (dom), month (mon), # and day of week (dow) or use '*' in these fields (for 'any'). # # Notice that tasks will be started based on the cron's system # daemon's notion of time and timezones. # # Output of the crontab jobs (including errors) is sent through # email to the user the crontab file belongs to (unless redirected). # # For example, you can run a backup of all your user accounts # at 5 a.m every week with: # 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/ # # For more information see the manual pages of crontab(5) and cron(8) # # m h? dom mon dow?? command if ! pgrep direwolf > /dev/null; then /home/pi/dw-start.sh > /dev/null 2>&1 & fi # # * * * * * /home/pi/dw-start.sh >/dev/null 2>&1
|
Re: dw-start.sh will not run from crontab
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 file." The listed fix was a bash script (which included a check to ensure the application was not already running).? Modified their script for 'direwolf':
if ! pgrep direwolf > /dev/null; then
/home/pi/dw-start.sh > /dev/null 2>&1 &
fi
So you may only be looking for /home/pi/dw-start.sh > /dev/null 2>&1 &See if that helps. Rob KB8RCO
|
Re: dw-start.sh will not run from crontab
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 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/home/pi> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=pi> Message-Id: <E1m6D51-0003RY-JQ@raspberrypi> Date: Wed, 21 Jul 2021 10:20:11 -0400 /bin/sh: 1: Syntax error: Bad fd number
|
Re: dw-start.sh will not run from crontab
On Tue, Jul 20, 2021 at 07:59 PM, VK1IAN wrote:
/home/pi/dw-start.sh >/home/pi/output.txt 2>&1
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 DISPLAY=:0 ----------------------- pi@raspberrypi:~ $ Line 1, dw-start.sh (first uncommented line): #? CLI mode is suited for say a Raspberry Pi running the Jessie LITE version #????? where it will run from the CLI w/o requiring Xwindows - uses screen RUNMODE=AUTO
|
Re: How configure 991a and direwolf for ISS
On Wed, Jul 21, 2021 at 06:53 AM, Patrick Connor wrote:
Look at menu items 074 through 079
?
Patrick (N3TSZ)
?
?
On Wednesday, July 21, 2021, 09:16:13 AM EDT, Rick Hatton <71topaz@...> wrote:
?
?
[Edited Message Follows]
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.
?
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.
|
Re: How configure 991a and direwolf for ISS
Look at menu items 074 through 079
Patrick (N3TSZ)
On Wednesday, July 21, 2021, 09:16:13 AM EDT, Rick Hatton <71topaz@...> wrote:
[Edited Message Follows]
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.
|
Re: How configure 991a and direwolf for ISS
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.
|
Re: How configure 991a and direwolf for ISS
On Tue, Jul 20, 2021 at 05:30 PM, David Ranch wrote:
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 mixture of CAT based PTT and serial port PTT could be creating your "hanging PTT" issue.
As a test... to do CAT based PTT with Direwolf, you would need something like the following in your direwolf.conf:
?? PTT RIG 135 /dev/ttyUSB0 4800
Btw.. if this works for you, I recommend you increase your serial port speed to something much faster.? I use 38400 on my FT950.? This change will be required to be made in a menu setting on your radio as well as this direwolf.conf line.
--David
KI6ZHD
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. Thanks
|
Re: How configure 991a and direwolf for ISS
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 mixture of CAT based PTT and serial port
PTT could be creating your "hanging PTT" issue.
As a test... to do CAT based PTT with Direwolf, you would need
something like the following in your direwolf.conf:
?? PTT RIG 135 /dev/ttyUSB0 4800
Btw.. if this works for you, I recommend you increase your serial
port speed to something much faster.? I use 38400 on my FT950.?
This change will be required to be made in a menu setting on your
radio as well as this direwolf.conf line.
--David
KI6ZHD
On 07/19/2021 06:02 PM, Rick Hatton
wrote:
toggle quoted message
Show quoted text
I have been doing HF. I want to do VHF to communicate
woth the ISS.
WSJTX and fldigi? alway use U SB.
I am most definitely NOT using flrig.
fldigi is using hamlib. I believe WSJTX does too.
PTT port is /dev/ttyUSB1
CAT port is /dev/ttyUSB0
PTT is via RTS in WSJTX.
4800. Data bits set to default. Stop bits 2
Hardware PTT is not set in fldigi. PTT via hamlib command. Stop
bits 1. RTS/CTS flow control.
The 991a is connected to the computer with one USB cable. In both
Windows and Linux 2 virtual serial ports are created. One
"Enhanced" used for cat and one "Standard".
|
Re: How configure 991a and direwolf for ISS
On Tue, Jul 20, 2021 at 12:31 PM, Keith wrote:
?
Hmmm...what HAMLIB version are you using?
?
Also, are you using feritte cores on your USB cables, rig properly grounded, etc?? If not, the RF from the rig can produce unpredictable operation.?
?
K
Hamlib 4.2. There are ferrites on both ends. The setup works fine with fldigi and wsjt-x
|
Re: dw-start.sh will not run from crontab
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
toggle quoted message
Show quoted text
On 21/7/21 9:37 am, Joe wrote: 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 error that keeps showing up when crontab runs dw-startup.
Joe
On Tue, Jul 20, 2021 at 19:19 VK1IAN <ibennett@... <mailto:ibennett@...>> wrote:
Joe,
? ? ? ? Looks like you are starting dw-start.sh every minute. Is that the intent??
Ian
VK1IAN
On 21/7/21 6:27 am, Joe wrote:
> [Edited Message Follows]
>
> 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
> These are the 2 modifications to crontab I have tried,both return error referenced above:
>
> # * * * * * /home/pi/dw-start.sh >/dev/null 2>&1
> * * * * * /home/pi/dw-start.sh 2>&1
>
>
> dw is running fine as a receive only APRS iGate out here in the panhandle of FL (K2EVK-10)
>
> I have not been able to find any message topics on this error.? My sw-start.sh only has
changes to
> mycall and my user path update.
>
> Are there some pi os dependencies I am overlooking?
>
> 73, Joe
>
--
Joe Dempster
+1 908 413 2889 (m)
|
Re: dw-start.sh will not run from crontab
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 error that keeps showing up when crontab runs dw-startup. ?
Joe
Joe,
? ? ? ? Looks like you are starting dw-start.sh every minute. Is that the intent??
Ian
VK1IAN
On 21/7/21 6:27 am, Joe wrote:
> [Edited Message Follows]
>
> 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
> These are the 2 modifications to crontab I have tried,both return error referenced above:
>
> # * * * * * /home/pi/dw-start.sh >/dev/null 2>&1
> * * * * * /home/pi/dw-start.sh 2>&1
>
>
> dw is running fine as a receive only APRS iGate out here in the panhandle of FL (K2EVK-10)
>
> I have not been able to find any message topics on this error.? My sw-start.sh only has changes to
> mycall and my user path update.
>
> Are there some pi os dependencies I am overlooking?
>
> 73, Joe
>
-- Joe Dempster
+1 908 413 2889 (m)
|
Re: dw-start.sh will not run from crontab
Joe,
Looks like you are starting dw-start.sh every minute. Is that the intent??
Ian
VK1IAN
toggle quoted message
Show quoted text
On 21/7/21 6:27 am, Joe wrote: [Edited Message Follows]
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
These are the 2 modifications to crontab I have tried,both return error referenced above:
# * * * * * /home/pi/dw-start.sh >/dev/null 2>&1
* * * * * /home/pi/dw-start.sh 2>&1
dw is running fine as a receive only APRS iGate out here in the panhandle of FL (K2EVK-10)
I have not been able to find any message topics on this error.? My sw-start.sh only has changes to mycall and my user path update.
Are there some pi os dependencies I am overlooking?
73, Joe
|
Re: dw-start.sh will not run from crontab
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 it still doesn't work, you may have to do more than a few ferrite beads.
On Tuesday, July 20, 2021, 5:22:48 PM EDT, Joe <joe.dempster@...> wrote:
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
dw is running fine as a receive only APRS iGate out here in the panhandle of FL (K2EVK-10)
I have not been able to find any message topics on this error.? My sw-start.sh only has changes to mycall and my user path update.
Are there some pi os dependencies I am overlooking?
73, Joe
|
Re: How configure 991a and direwolf for ISS
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 viable interface using GPIO pins, there's no need for
anything else with a Raspberry Pi and the FT991a.? Irregardless of
interface choice, however, ferrite cores and good grounding
methods are really good ideas.? I've seen the problem Rick is
having with the rig hanging in transmit due to rf getting into the
usb cable and causing problems. Not saying that this is what's
causing his issue, but it's a possibility.
73
Keith/KI5US
On 7/20/21 4:19 PM, Rob Giuliano via
groups.io wrote:
toggle quoted message
Show quoted text
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 the 6-pin header connector, several brands of the cheap
CP2102 boards, and most recently tried one of the USB to
UART/SPI/I2C boards (CH341A).? The board you choose must
have "at least" the RTS/CTS pins.?
I typcially make sure they
have all the serial interface pins so I have "lots of
options".
On my Linux machines (Pi I
use GPIO) I typically use /dev/ttyUSB# -RTS? where
# is the USB device number.
Most often I use a udev
rule to rename the device to make life easier.
On Tuesday, July 20, 2021, 3:31:20 PM EDT, Keith
<geek4096@...> wrote:
Hmmm...what
HAMLIB version are you using?
Also,
are you using feritte cores on your USB cables, rig
properly grounded, etc?? If not, the RF from the rig
can produce unpredictable operation.?
K
On
7/20/21 3:22 PM, Rick Hatton wrote:
On Tue, Jul 20, 2021 at 08:07 AM, Rob Giuliano
wrote:
Keith provided the specific line
for the radio and how it should be configured
for the virtual ports.
.
I was working off physical serial
port devices that I have used for PTT.?
I have used different USB to serial
TTL devices for PTT using FTDI or other chips.
?
I would go with Keith's advice!
PTT
/dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00C98A2F-if01-port0
does not key the radio.
PTT
/dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00C98A2F-if01-port0
RTS keys, but does not unkey the radio.
|
Mikel EA2CW
Joe
Patrick Connor
Keith/KI5US