Date   

Re: GPS has been working but not since Saturday #gpsd

KI5EVJ - Richard
 

Something is still off. Gpsmon shows current time but if I enter "date" in a terminal window I get yesterday evening (correct time zone). I am connected by WIFI to our LAN but I'm not getting updates from either the gps or WIFI.  Reboots don't help.
Richard


Re: GPS has been working but not since Saturday #gpsd

Basil Gunn
 

Richard,

Found it Extra " at end of DEVICES line
Glad you found the solution straight away.

# Configure gpsd
START_DAEMON="true"
DEVICES="/dev/ttySC0 /dev/pps0"<========
GPSD_OPTIONS="-n"

Time for new glasses :-)


Re: GPS has been working but not since Saturday #gpsd

KI5EVJ - Richard
 

Basil,

Found it Extra " at end of  DEVICES line

# Configure gpsd
START_DAEMON="true"
DEVICES="/dev/ttySC0 /dev/pps0"<========
GPSD_OPTIONS="-n"

Time for new glasses :-)
 


Re: GPS has been working but not since Saturday #gpsd

Basil Gunn
 

Clock not updating , gpsmon either gives nothing or won't open or
display. I went through the configure steps in the wiki and all was in
order till I got to restart the daemon
Initial config using scripts creates an /etc/default/gpsd file that
looks like this:

# Configure gpsd
START_DAEMON="true"
DEVICES="/dev/ttySC0 /dev/pps0"
GPSD_OPTIONS="-n"

Either you or some other program installed on your RPi has mucked with
this file. Make sure it looks exactly as above then:

sudo su
systemctl restart gpsd

# Then post the console output of:

systemctl status gpsd

# If it still doesn't work then also post the output of:

cat /etc/default/gpsd

pi@draws:~ $ gpsmon
Read error from device
pi@draws:~ $ sudo nano /etc/default/gpsd
pi@draws:~ $ sudo systemctl enable gpsd && sudo systemctl restart gpsd
Synchronizing state of gpsd.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable gpsd
Job for gpsd.service failed because the control process exited with error code.
See "systemctl status gpsd.service" and "journalctl -xe" for details.
pi@draws:~ $ systemctl status gpsd.service
\u25cf gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2021-07-11 08:49:26 EDT; 28s ago
Process: 2819 ExecStart=/usr/sbin/gpsd $GPSD_OPTIONS $DEVICES (code=exited, status=1/FAI

Jul 11 08:49:26 draws systemd[1]: Starting GPS (Global Positioning System) Daemon...
Jul 11 08:49:26 draws gpsd[2819]: gpsd:ERROR: too many devices on command line
Jul 11 08:49:26 draws systemd[1]: gpsd.service: Control process exited, code=exited, statu
Jul 11 08:49:26 draws systemd[1]: gpsd.service: Failed with result 'exit-code'.
Jul 11 08:49:26 draws systemd[1]: Failed to start GPS (Global Positioning S


GPS has been working but not since Saturday #gpsd

KI5EVJ - Richard
 

Clock not updating , gpsmon either gives nothing or won't open or display. I went through the configure steps in the wiki and all was in order till I got to restart the daemon 

pi@draws:~ $ gpsmon
Read error from device
pi@draws:~ $ sudo nano /etc/default/gpsd
pi@draws:~ $ sudo systemctl enable gpsd && sudo systemctl restart gpsd
Synchronizing state of gpsd.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable gpsd
Job for gpsd.service failed because the control process exited with error code.
See "systemctl status gpsd.service" and "journalctl -xe" for details.
pi@draws:~ $ systemctl status gpsd.service
\u25cf gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2021-07-11 08:49:26 EDT; 28s ago
  Process: 2819 ExecStart=/usr/sbin/gpsd $GPSD_OPTIONS $DEVICES (code=exited, status=1/FAI
 
Jul 11 08:49:26 draws systemd[1]: Starting GPS (Global Positioning System) Daemon...
Jul 11 08:49:26 draws gpsd[2819]: gpsd:ERROR: too many devices on command line
Jul 11 08:49:26 draws systemd[1]: gpsd.service: Control process exited, code=exited, statu
Jul 11 08:49:26 draws systemd[1]: gpsd.service: Failed with result 'exit-code'.
Jul 11 08:49:26 draws systemd[1]: Failed to start GPS (Global Positioning S

Richard
KI5EVJ


Re: Pat ARDOP configure issues #rigctld #pat

 

Richard,

As you are discovering.  The 6 pin socket on the DRAWS™ carries audio in/out as well as PTT (and SQL, but the SQL pin can be a problem on Yaesu radios) to the matching data port (4).  To do computer control of the radio, eg. set frequency, command style PTT, etc. you use the accessory port (5) with a USB cable. From page 15 of the Yaesu manual.

image.png
image.png

On the 'Data' jack.  The data out 1200bps is de-emphasized audio (like speaker audio) from the radio, the data out 9600bps is raw output from the discriminator (in FM/Packet mode).  Data in goes straight to the modulator. 

On Sun, Jul 11, 2021 at 12:55 PM Richard Gilbert via groups.io <rpgilbert1=verizon.net@groups.io> wrote:
/dev/tyyUSB* no such file or directory
> On Jul 11, 2021, at 2:53 PM, RICHARD GILBERT <rpgilbert1@...> wrote:
>
> I am using the 6-pin cable that came with the DRAWS plugged into the right socket on the hat and the data port on the 818.
>
> Sent from my iPhone
>
>> On Jul 11, 2021, at 2:02 PM, Basil Gunn <basil@...> wrote:
>>
>> 
>>
>>> Trying to set up Pat following the KM4ACK videos and descriptions
>>> listed here
>>> . ARDOP loads, rigctld gives the error below
>>> port_open: serial_open status=-6
>>
>> errno 6 is No such device or address
>>
>>> Pat http loads but says it can't get the frequency from rigctld.
>>
>> Because rigctld is not running
>>
>>> I'm using a FT-818ND. Hardware id is 1041. There is no ttyUSB0 in the
>>> /dev/ folder so I must have missed something somewhere.
>>
>> Do this to see if the device is enumerated at some other USB number
>>
>> ls /dev/ttyUSB*
>>
>> Either you are using the wrong device name (ie. could be /dev/ttyUSB1)
>> OR you don't have the CAT cable for your FT-818ND plugged into the radio
>> or RPi.
>>
>> If the above command comes back like this:
>> ls /dev/ttyUSB*
>> ls: cannot access '/dev/ttyUSB*': No such file or directory
>>
>> then you don't have a CAT cable for your radio.
>>
>> Yaesu USB FTDI CT-62 CAT Cable FT-818,
>> https://www.amazon.com/gp/product/B0035DV1ZM/ref=ask_ql_qh_dp_hza
>>
>>> pi@draws:~ $ rigctld -m 1041 -r /dev/ttyUSB0 -s 4800
>>> rig_open: error = IO error
>>> port_open: serial_open status=-6
>>> iofunc.c(80):port_open return(-6)
>>> rig.c(773):rig_open return(-6)
>>
>>
>>
>>
>>








--
John D. Hays
Kingston, WA
K7VE / WRJT-215

 


Re: Pat ARDOP configure issues #rigctld #pat

KI5EVJ - Richard
 

Ok so rigctld worked but when I started Pat http it came back with “818NDready. Dial frequency is 145.000.00. Does Ardop work on 2m?
Then “bind: address already in use”
Not sure what is happening here.
Richard

On Jul 11, 2021, at 3:06 PM, Richard Gilbert via groups.io <rpgilbert1=verizon.net@groups.io> wrote:

Viola! Helps to used the correct cable. USB0 is there 😂😋
Thanks
Richard
On Jul 11, 2021, at 2:55 PM, Richard Gilbert via groups.io <rpgilbert1=verizon.net@groups.io> wrote:

/dev/tyyUSB* no such file or directory
On Jul 11, 2021, at 2:53 PM, RICHARD GILBERT <rpgilbert1@verizon.net> wrote:
I am using the 6-pin cable that came with the DRAWS plugged into the right socket on the hat and the data port on the 818.

Sent from my iPhone

On Jul 11, 2021, at 2:02 PM, Basil Gunn <basil@pacabunga.com> wrote:


Trying to set up Pat following the KM4ACK videos and descriptions
listed here
. ARDOP loads, rigctld gives the error below
port_open: serial_open status=-6
errno 6 is No such device or address

Pat http loads but says it can't get the frequency from rigctld.
Because rigctld is not running

I'm using a FT-818ND. Hardware id is 1041. There is no ttyUSB0 in the
/dev/ folder so I must have missed something somewhere.
Do this to see if the device is enumerated at some other USB number

ls /dev/ttyUSB*

Either you are using the wrong device name (ie. could be /dev/ttyUSB1)
OR you don't have the CAT cable for your FT-818ND plugged into the radio
or RPi.

If the above command comes back like this:
ls /dev/ttyUSB*
ls: cannot access '/dev/ttyUSB*': No such file or directory

then you don't have a CAT cable for your radio.

Yaesu USB FTDI CT-62 CAT Cable FT-818,
https://www.amazon.com/gp/product/B0035DV1ZM/ref=ask_ql_qh_dp_hza

pi@draws:~ $ rigctld -m 1041 -r /dev/ttyUSB0 -s 4800
rig_open: error = IO error
port_open: serial_open status=-6
iofunc.c(80):port_open return(-6)
rig.c(773):rig_open return(-6)












Re: Pat ARDOP configure issues #rigctld #pat

KI5EVJ - Richard
 

Viola! Helps to used the correct cable. USB0 is there 😂😋
Thanks
Richard

On Jul 11, 2021, at 2:55 PM, Richard Gilbert via groups.io <rpgilbert1=verizon.net@groups.io> wrote:

/dev/tyyUSB* no such file or directory
On Jul 11, 2021, at 2:53 PM, RICHARD GILBERT <rpgilbert1@verizon.net> wrote:

I am using the 6-pin cable that came with the DRAWS plugged into the right socket on the hat and the data port on the 818.

Sent from my iPhone

On Jul 11, 2021, at 2:02 PM, Basil Gunn <basil@pacabunga.com> wrote:


Trying to set up Pat following the KM4ACK videos and descriptions
listed here
. ARDOP loads, rigctld gives the error below
port_open: serial_open status=-6
errno 6 is No such device or address

Pat http loads but says it can't get the frequency from rigctld.
Because rigctld is not running

I'm using a FT-818ND. Hardware id is 1041. There is no ttyUSB0 in the
/dev/ folder so I must have missed something somewhere.
Do this to see if the device is enumerated at some other USB number

ls /dev/ttyUSB*

Either you are using the wrong device name (ie. could be /dev/ttyUSB1)
OR you don't have the CAT cable for your FT-818ND plugged into the radio
or RPi.

If the above command comes back like this:
ls /dev/ttyUSB*
ls: cannot access '/dev/ttyUSB*': No such file or directory

then you don't have a CAT cable for your radio.

Yaesu USB FTDI CT-62 CAT Cable FT-818,
https://www.amazon.com/gp/product/B0035DV1ZM/ref=ask_ql_qh_dp_hza

pi@draws:~ $ rigctld -m 1041 -r /dev/ttyUSB0 -s 4800
rig_open: error = IO error
port_open: serial_open status=-6
iofunc.c(80):port_open return(-6)
rig.c(773):rig_open return(-6)








Re: Pat ARDOP configure issues #rigctld #pat

KI5EVJ - Richard
 

/dev/tyyUSB* no such file or directory

On Jul 11, 2021, at 2:53 PM, RICHARD GILBERT <rpgilbert1@verizon.net> wrote:

I am using the 6-pin cable that came with the DRAWS plugged into the right socket on the hat and the data port on the 818.

Sent from my iPhone

On Jul 11, 2021, at 2:02 PM, Basil Gunn <basil@pacabunga.com> wrote:



Trying to set up Pat following the KM4ACK videos and descriptions
listed here
. ARDOP loads, rigctld gives the error below
port_open: serial_open status=-6
errno 6 is No such device or address

Pat http loads but says it can't get the frequency from rigctld.
Because rigctld is not running

I'm using a FT-818ND. Hardware id is 1041. There is no ttyUSB0 in the
/dev/ folder so I must have missed something somewhere.
Do this to see if the device is enumerated at some other USB number

ls /dev/ttyUSB*

Either you are using the wrong device name (ie. could be /dev/ttyUSB1)
OR you don't have the CAT cable for your FT-818ND plugged into the radio
or RPi.

If the above command comes back like this:
ls /dev/ttyUSB*
ls: cannot access '/dev/ttyUSB*': No such file or directory

then you don't have a CAT cable for your radio.

Yaesu USB FTDI CT-62 CAT Cable FT-818,
https://www.amazon.com/gp/product/B0035DV1ZM/ref=ask_ql_qh_dp_hza

pi@draws:~ $ rigctld -m 1041 -r /dev/ttyUSB0 -s 4800
rig_open: error = IO error
port_open: serial_open status=-6
iofunc.c(80):port_open return(-6)
rig.c(773):rig_open return(-6)




Re: Pat ARDOP configure issues #rigctld #pat

KI5EVJ - Richard
 

I am using the 6-pin cable that came with the DRAWS plugged into the right socket on the hat and the data port on the 818.

On Jul 11, 2021, at 2:02 PM, Basil Gunn <basil@pacabunga.com> wrote:



Trying to set up Pat following the KM4ACK videos and descriptions
listed here
. ARDOP loads, rigctld gives the error below
port_open: serial_open status=-6
errno 6 is No such device or address

Pat http loads but says it can't get the frequency from rigctld.
Because rigctld is not running

I'm using a FT-818ND. Hardware id is 1041. There is no ttyUSB0 in the
/dev/ folder so I must have missed something somewhere.
Do this to see if the device is enumerated at some other USB number

ls /dev/ttyUSB*

Either you are using the wrong device name (ie. could be /dev/ttyUSB1)
OR you don't have the CAT cable for your FT-818ND plugged into the radio
or RPi.

If the above command comes back like this:
ls /dev/ttyUSB*
ls: cannot access '/dev/ttyUSB*': No such file or directory

then you don't have a CAT cable for your radio.

Yaesu USB FTDI CT-62 CAT Cable FT-818,
https://www.amazon.com/gp/product/B0035DV1ZM/ref=ask_ql_qh_dp_hza

pi@draws:~ $ rigctld -m 1041 -r /dev/ttyUSB0 -s 4800
rig_open: error = IO error
port_open: serial_open status=-6
iofunc.c(80):port_open return(-6)
rig.c(773):rig_open return(-6)




Re: Pat ARDOP configure issues #rigctld #pat

Basil Gunn
 

Trying to set up Pat following the KM4ACK videos and descriptions
listed here
. ARDOP loads, rigctld gives the error below
port_open: serial_open status=-6
errno 6 is No such device or address

Pat http loads but says it can't get the frequency from rigctld.
Because rigctld is not running

I'm using a FT-818ND. Hardware id is 1041. There is no ttyUSB0 in the
/dev/ folder so I must have missed something somewhere.
Do this to see if the device is enumerated at some other USB number

ls /dev/ttyUSB*

Either you are using the wrong device name (ie. could be /dev/ttyUSB1)
OR you don't have the CAT cable for your FT-818ND plugged into the radio
or RPi.

If the above command comes back like this:
ls /dev/ttyUSB*
ls: cannot access '/dev/ttyUSB*': No such file or directory

then you don't have a CAT cable for your radio.

Yaesu USB FTDI CT-62 CAT Cable FT-818,
https://www.amazon.com/gp/product/B0035DV1ZM/ref=ask_ql_qh_dp_hza

pi@draws:~ $ rigctld -m 1041 -r /dev/ttyUSB0 -s 4800
rig_open: error = IO error
port_open: serial_open status=-6
iofunc.c(80):port_open return(-6)
rig.c(773):rig_open return(-6)


Re: Pat ARDOP configure issues #rigctld #pat

 

What are you using as your CAT control cable?   Usually something like


On Sun, Jul 11, 2021, 11:30 Richard Gilbert via groups.io <rpgilbert1=verizon.net@groups.io> wrote:
Trying to set up Pat following the KM4ACK videos and descriptions listed here. ARDOP loads, rigctld gives the error below Pat http loads but says it can't get the frequency from rigctld. I'm using a FT-818ND. Hardware id is 1041. There is no ttyUSB0 in the /dev/ folder so I must have missed something somewhere.

pi@draws:~ $ rigctld -m 1041 -r /dev/ttyUSB0 -s 4800
rig_open: error = IO error
port_open: serial_open status=-6
iofunc.c(80):port_open return(-6)
rig.c(773):rig_open return(-6) 
pi@draws:~ $ 

Suggestions, please
Richard KI5EVJ


Pat ARDOP configure issues #rigctld #pat

KI5EVJ - Richard
 

Trying to set up Pat following the KM4ACK videos and descriptions listed here. ARDOP loads, rigctld gives the error below Pat http loads but says it can't get the frequency from rigctld. I'm using a FT-818ND. Hardware id is 1041. There is no ttyUSB0 in the /dev/ folder so I must have missed something somewhere.

pi@draws:~ $ rigctld -m 1041 -r /dev/ttyUSB0 -s 4800
rig_open: error = IO error
port_open: serial_open status=-6
iofunc.c(80):port_open return(-6)
rig.c(773):rig_open return(-6) 
pi@draws:~ $ 

Suggestions, please
Richard KI5EVJ


Re: DRAWS power pigtail and UDRCII

TG9AOR
 

Thanks for the reply and information.


Re: DRAWS power pigtail and UDRCII

 

Thank you for the part numbers for barrel and JST connector. I don't need the barrel,  but I have broken my JST connector, and solered direct. I will return this back to normal now. 

I am also looking for the HDR 4×2 connector. If anyone can give me a part number to plug into DRAWS so I can use external devices better.

On Wed, Jul 7, 2021, 9:19 AM Bryan Hoyer <bhhoyer@...> wrote:
Budd Churchward manufactured acrylic cases for the UDRC and used the connectors listed to go from the board to a barrel jack and some UDRC users asked for the part numbers.

The parts could also be used on early DRAWS boards.

73,
Bryan K7UDR
NW Digital Radio









Re: DRAWS power pigtail and UDRCII

 

Budd Churchward manufactured acrylic cases for the UDRC and used the connectors listed to go from the board to a barrel jack and some UDRC users asked for the part numbers.

The parts could also be used on early DRAWS boards.

73,
Bryan K7UDR
NW Digital Radio


Re: DRAWS power pigtail and UDRCII

wrstrand
 

Sorry, but I do not understand the message about UDRC parts. 
Bill AG5ZN

On Wed, Jul 7, 2021 at 09:44 Bryan Hoyer <bhhoyer@...> wrote:
These are the parts that add Used on the UDRC Case:

JST Connector Plug and Cable
 
DC Power Jack Panel Mount

73,
Bryan K7UDR
NW Digital Radio



--


Re: DRAWS power pigtail and UDRCII

 

These are the parts that add Used on the UDRC Case:

JST Connector Plug and Cable
 
DC Power Jack Panel Mount

73,
Bryan K7UDR
NW Digital Radio




Re: DRAWS power pigtail and UDRCII

wrstrand
 

Since the DRAWS unit is powered by the 2.1 mm barrel connector, the USB-C jack is unused. 
Can this USB-C jack be accessed for power or data?
Thank you. 
Bill AG5ZN

On Tue, Jul 6, 2021 at 09:07 Bryan Hoyer <bhhoyer@...> wrote:
The UDRC-II is powered thru the HD15 Connector when attached to a Yaesu DR1-X.

There is a 0.1” header field behind the HD15 where you can attach power wires, which should be fused at the source (2A).

Budd made a pigtail using JST Connectors to a Barrel Jack for the Case he made.

73,
Bryan K7UDR
NW Digital Radio








--


Re: DRAWS power pigtail and UDRCII

 

The UDRC-II is powered thru the HD15 Connector when attached to a Yaesu DR1-X.

There is a 0.1” header field behind the HD15 where you can attach power wires, which should be fused at the source (2A).

Budd made a pigtail using JST Connectors to a Barrel Jack for the Case he made.

73,
Bryan K7UDR
NW Digital Radio

21 - 40 of 5764