¿ªÔÆÌåÓý

Date

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

Rick Hatton
 

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

Rick Hatton
 
Edited

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

Rick Hatton
 

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:

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

Rick Hatton
 

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

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

On Tue, Jul 20, 2021 at 19:19 VK1IAN <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

 

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


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.

Robert Giuliano
KB8RCO



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:

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.

Robert Giuliano
KB8RCO



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!

Robert Giuliano
KB8RCO


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.




dw-start.sh will not run from crontab

 
Edited

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: Toy example text <-> audio?

 

Have a look at FLARQ

http://www.w1hkj.com/FlarqHelpFiles/

Danny
K5CG


From: "David Ranch" <direwolf-groupsio@...>
To: [email protected]
Sent: Monday, July 19, 2021 3:32:45 PM
Subject: Re: [direwolf] Toy example text <-> audio?

Hello Yishuai,

>When you say RF, are you talking about FM over VHF? Maybe SSB over HF? The transport details really matters here

I currently have FM over VHF/UHF. I suppose the modulation and frequency limit the transmission rate. Are there other factors that are affected?


There are lots of factors for sure including the robustness of the mode, noise floor of the frequency, width of the passband, the regional legality of symbols/sec of the transmitter, etc.? it goes on and on.


>What kind of speed is required here? Do you want to do everything via AX.25 or are you looking for something far simplier like minimodem?

I plan to start with RTTY, typing on one computer and printing on another, without packeting. After that I want to build a server that speaks HTTP, maybe over Bell 103.


Personally, I personally wouldn't bother with RTTY as it's not 8bit clean (if you need to send binary data), it's not very robust, it's quite slow (especially for a medium like FM over VHF), etc.



What operating system are you looking to run this "application" on? Windows, Linux, Mac, something else?

I have Windows, Linux, Mac, Android, and iOS. I'll start with Linux, which seems to have the most tools available. I'll then port to more platforms, so that all my devices can open up a browser and interact with the server.


Is your goal to send arbitrary strings?? Maybe you want to send files?? Is this all point to point or is there any in-between infrastructure being used (digipeaters, etc)?? How are you intending to interface to these modems?? For example, ARDOP has a very robust API for sending both FEC and ARQ protected strings.?

--David


Re: How configure 991a and direwolf for ISS

 

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.

Robert Giuliano
KB8RCO



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!

Robert Giuliano
KB8RCO


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.



Re: How configure 991a and direwolf for ISS

Rick Hatton
 

On Tue, Jul 20, 2021 at 12:03 PM, Keith wrote:
?
Also, since you're wanting to use this for ISS, Gpredict has a really nice feature for tracking lots of satellites, including the ISS.? I've used it to constantly adjust the downlink frequency to compensate for the doppler shift.? It supports the FT991a in split frequency mode and works great.? Click on the small arrow at the upper-right of the main Gpredict screen to access the Radio Control feature.? Nice program...it lists lots of satellites, their orbital parameters, and their known transponder details (be sure to update TLE and transponder data under the Edit menu).? If you have compatible hardware, Gpredict will also control AZ/EL for your antenna.? Best of all, it's free.
?
I haven't tried using direwolf with Gpredict, but perhaps you can tell us how well that works?
I use Gpredict to track the ISS and a couple of other satellites. My version doesn't seem to support the 991a. I'll look into that once I have the radio keying properly.
Using PTT /dev/ttyUSB1 RTS or PTT /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00C98A2F-if01-port0 RTS will key the radio, but won't unkey.


Re: How configure 991a and direwolf for ISS

 

¿ªÔÆÌåÓý


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!

Robert Giuliano
KB8RCO


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.



Re: How configure 991a and direwolf for ISS

Rick Hatton
 
Edited

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!

Robert Giuliano
KB8RCO


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.
stty -crtscts -F /dev/ttyUSB1... USB01 keys but won't unkey after this.


Re: How configure 991a and direwolf for ISS

 

¿ªÔÆÌåÓý


Also, since you're wanting to use this for ISS, Gpredict has a really nice feature for tracking lots of satellites, including the ISS.? I've used it to constantly adjust the downlink frequency to compensate for the doppler shift.? It supports the FT991a in split frequency mode and works great.? Click on the small arrow at the upper-right of the main Gpredict screen to access the Radio Control feature.? Nice program...it lists lots of satellites, their orbital parameters, and their known transponder details (be sure to update TLE and transponder data under the Edit menu).? If you have compatible hardware, Gpredict will also control AZ/EL for your antenna.? Best of all, it's free.

I haven't tried using direwolf with Gpredict, but perhaps you can tell us how well that works?

Enjoy chasing the ISS...
73
Keith/KI5US



On 7/20/21 11:05 AM, Rick Hatton wrote:

On Tue, Jul 20, 2021 at 07:44 AM, Keith wrote:
PTT RIG 135 /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00A06B06-if00-port0
Works. (check your port ID on your system and change if needed).
Just curious....You emphasized NOT using flrig.? Why?? Works very well with the 991a. But the line above, in direwolf.conf, does work on mine.? You might want to confirm the device port info (i.e., 00A06B06) in your /dev/serial/by-id directory.? Also be sure to add your user and direwolf to the /etc/group dialout group, if you haven't already done so.
?
Hope that helps.
?
73
Keith
Seems to be? usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00C98A2F-if01-port0 for tty/USB1. I have used /dev/serial/by-id before when I was using an IC-718.
I don't use flrig because, for me, seems to be an added level of complexity... running another program when fldigi and wsjtx both will control the 991a. Still, I suppose if I set up flrig correctly,? might not have to worry anout the setup differences in other programs. I'll give it another look.