Date
1 - 20 of 27
Split Channel
|
Hi All and Happy New Year.
Basil, I believe I read on here somewhere that you were working on the split-channel operation of the Draws and making so that you could do HF and APRS/Packet with two different radios? If it was, please read on, if not, hopefully whomever it was will see this. Anyways, I got a chance to try it as the prospect intrigued me. To be able to have local packet traffic and be able to do HF, in my mind, primarily JS8 with one RPi seems the dream. So I tried running your scripts which seemed to work excellent. Easy to turn on and off, works as expected in my books, almost. I've verified, when running the ax25-start, without the split-channel, I'm decoding local APRS traffic in dire wolf. My volume is a little lower than I'd like, so I do need to experiment with a different 2m rig, but the point is that I do decode packets. Then when I enable the split channel and then re-enable ax25-start and start listening for APRS traffic, I decode none. I'm using the left mini-din for both split and non-split APRS work. I confess, pulse audio is very new to me. I think I roughly understand it, but not definitively, and configuring it within linux is not in my tools yet. Any thoughts? I'm going to try a different 2m rig to see if that makes a difference. I have verified that the right din works as expected. Thanks for this! Jim VA7SHG/VE7TGZ 73
|
|
|
|
Jim,
toggle quoted messageShow quoted text
First, thanks for trying out split-channels! Some back ground. Anna made a repo & got split-channels working around last April. I picked it up last November & made some install scripts to configure things a little differently. If you follow the README.md file from https://github.com/nwdigitalradio/split-channels you will end up with the left mDin6 connector controlling an HF radio & the right a VHF/UHF radio. What that does is make the right connector device udr0 when it used to be udr1. If you use the split_install.sh script from n7nix/splitchan it will keep the left mDin6 connector for VHF/UHF which means it remains device udr0 and the right connector will be used by pulse audio for HF. So November turned into December and I spent less time doing NW Digital Radio stuff as the holidays started sucking up more of my time. This is just to rationalize my excuse for what works & what doesn't. The install script (split_install.sh) works OK. The status script (split_status.sh) mainly used for debugging works OK. The toggle script has never been tested but seemed like a good idea at the time. As it happened the split channel stuff worked well enough right away that I started playing more with HF modes with packet happening on the other channel. Seemed cool and I stopped script testing and did more Hammy things. I have not tried what you are describing which I think is: Install split chan - which has ax.25 running on udr0, left mDin6 & HF on right mDin6 Run ax25-start when split chan is running - shouldn't have to do this and needs testing - pretty sure this will mess with the split chan config - you can run split_status.sh to confirm I need to finish testing split_toggle.sh which will go from split chan to both chans either config'ed for ax.25/direwolf or both ready for HF. Will get back to you in a bit as I finish testing with a clean image. /Basil n7nix
Anyways, I got a chance to try it as the prospect intrigued me. To be I've verified, when running the
|
|
|
|
Thanks Basil and I understand this time of year. I’ve had trying the split chan on my list to try for quite awhile but just haven’t found the time, even with time off. I finally decided to give it a try yesterday, at the end of my vacation.
toggle quoted messageShow quoted text
I don’t know that I have a specific workflow in mind. I tried this on an already setup image that has had the core_install run. I imagined that I would have to stop ax25, then run the split_toggle (which would have to change the dire wolf config) and the restart ax25. I’ve taken a look at the resulting direwolf.conf and I think I’ve discovered what the issue was. It’s pointing to draws-capture-right and draws-playback-right. Should be left, which I’ve switched, and now I’m decoding packets! This is a super radio workstation now. I can have 2m/70cm packet on one mini din and HF/JS8 on the other. Brilliant!! ------ 73, Jim VA7SHG - Phone VE7TGZ/VA7TGZ - Other
|
|
|
|
John Spoonhower
Basil and others,
I am trying to create a split channel system using my DRAWS board but not having success. I am running the current NW16 image on a Pi3. I have installed pulseaudio as per the github page. https://github.com/nwdigitalradio/split-channels. Also copied the supplied files from the master /etc directory to their appropriate /etc points. /etc/direwolf.conf has been edited to appear as: ADEVICE plughw:CARD=udrc,DEV=0 plughw:CARD=udrc,DEV=0ACHANNELS 2ARATE 48000CHANNEL 0#MYCALL N0CALL-1MYCALL NX2I-1MODEM 1200PTT GPIO 12
|
|
|
|
John, I’m not going to be a lot of help with figuring out your situation, but I’ll tell you my experience with spilt channel was really simple. I only ran the scripts of Basil’s. I didn’t hand edit much, nor did I manually install much. If I remember, pulse audio got installed by the script, direwolf got edited, exports, etc.. I haven’t tried from scratch again, though that is my intention with the new RPi 4 8Gb version, once I move my Hat over.
toggle quoted messageShow quoted text
------ 73, Jim VA7SHG - Phone VE7TGZ/VA7TGZ - Other
|
|
|
|
John,
toggle quoted messageShow quoted text
I will document what we do to get you going and check it in to github - The split channel scripts in the n7nix repo are not compatible with the documentation in the split-channels repo. I set up the n7nix scripts to be able to choose which connector is used for HF & which is controlled by Direwolf ... and then only tested LEFT direwolf, RIGHT hf which is different from the split-channels repo. I did this so that the port name udr0 is always on the left connector and does not move to the right connector. So left connector direwolf vhf/uhf and right connector for HF radio. - I will remove the split_chan.sh script sometime soon. Please use ./split_ctrl.sh (Do not run as root) Usage: split_ctrl.sh [-c <connector>][-s][-d][-h][left|right|off] No args will show status of Direwolf, pulseaudio & asound left ENable split channel, direwolf uses left connector right ENable split channel, direwolf uses right connector NOT IMPLEMENTED off DISable split channel -c right | left ENable split channel, use either right or left mDin6 connector. -s Display verbose status -d Set DEBUG flag -h Display this message. - I need to make a custom setalsa script for which 2 radios you are using. Look at n7nix/bin/setalsa-ic706_tmv71a.sh to see what I'm talking about. I tested split channels with a TM-V71a & an Icom ic-706mkIIG. So which 2 radios are you using? - To make things a little cleaner I pulled some variables out of the scripts and put them in file /etc/ax25/ports.conf. After you run the split_ctrl.sh script you can confirm that split channels is configured by checking that the packet speed parameter for port 1 (right connector, HF radio) is "off". I am pretty busy this week so please be patient with me. /Basil John Spoonhower <jpspoonhower@...> writes:
Basil and others,
|
|
|
|
John Spoonhower
Hi Basil,
my plan is to run a Yaesu FT-7900R on the VHF Channel and an Icom IC-7300 on HF. Here is some output from the split_ctrl.sh command script: pi@draws:~/n7nix/splitchan $ ./split_ctrl.sh Detected pulseaudio package. == Pulse Audio is NOT RUNNING. split-channels repo does NOT exist asound config file DOES exist Pulseaudio configuration directory DOES exist Service: pulseaudio is enabled and NOT running Direwolf is running with pid: 23683 and controls both channels Check: ADEVICE plughw:CARD=udrc,DEV=0 plughw:CARD=udrc,DEV=0 Check: ARATE parameter already set to 48000 in direwolf config file. Number of direwolf channels: 2 Detected pulseaudio package. No split-channels source directory found (/home/pi/dev/github/split-channels) pi@draws:~/n7nix/splitchan $ ./split_ctrl.sh -c left -s Set connector to: left Detected pulseaudio package. == Pulse Audio is NOT RUNNING. split-channels repo does NOT exist asound config file DOES exist Pulseaudio configuration directory DOES exist Service: pulseaudio is enabled and NOT running Direwolf is running with pid: 23683 and controls both channels Check: ADEVICE plughw:CARD=udrc,DEV=0 plughw:CARD=udrc,DEV=0 Check: ARATE parameter already set to 48000 in direwolf config file. Number of direwolf channels: 2 Detected pulseaudio package. No split-channels source directory found (/home/pi/dev/github/split-channels) I will lay-low until I hear back from you. I have plenty of other irons in the fire at this point....so please do not rush on my behalf. 73, John
|
|
|
|
John Spoonhower
Basil,
one more thing. here is the current state of /etc/ax25/port.conf; I do not see a ports.conf.... 73, John pi@draws:/etc/ax25 $ more port.conf # Configuration for each sound card port # version: 1.1 # # speed is the modulator baud rate and can be: # 1200 # 9600 # off (for split channel) # # receive_out (from radio) can be: # disc (for discriminator) or # audio (for preemphasis/deemphasis) # # You can run 1200 baud with receive signal from discriminator # You can NOT run 9600 baud with receive signal from audio [port0] speed=1200 ip_address="192.168.255.2" receive_out=audio [port1] speed=1200 ip_address="192.168.255.3" receive_out=audio [baud_1200] slottime=200 txdelay=500 t1_timeout=3000 t2_timeout=1000 [[baud_9600] slottime=10 txdelay=150 t1_timeout=2000 t2_timeout=100
|
|
|
|
Yep. /etc/ax25/port.conf
my plan is to run a Yaesu FT-7900R on the VHF Channel and an Icom IC-7300 on HF.The IC-7300 has an internal sound card so you will not need to run in split-channel mode. You will need to know the serial device name of the CAT port and which audio card number is assigned to the each of DRAWS & IC-7300 Do an ls /dev/ttyU* before & after you plug in your cat cable so you know the device name assigned to it. ## For an IC-7300 which has an internal sound card * This config does NOT use a udrc/DRAWS hat * IC-7300 sound card PCM connects to RPi via USB cable * When you plug in the USB cable to the RPI from the IC-7300 it becomes audio card 1, the udrc/DRAWS hat becomes card 2 and the RPi internal sound card remains as card 0. * _CODEC_ is the name of the IC-7300 sound card device To get a list of playback devices: aplay -l ``` Playback Device list example. # Internal RPi audio device Card 0, ID `ALSA', name `bcm2835 ALSA' Device hw:0,0 ID `bcm2835 ALSA', name `bcm2835 ALSA', 7 subdevices (7 available) # IC-7300 audio device Card 1, ID `CODEC', name `USB Audio CODEC' Device hw:1,0 ID `USB Audio', name `USB Audio', 1 subdevices (0 available) # UDRC/DRAWS hat audio device Card 2, ID `udrc', name `udrc' Device hw:2,0 ID `bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0', name `', 1 subdevices (1 available) ``` John Spoonhower <jpspoonhower@...> writes: Basil,
|
|
|
|
John Spoonhower
Hi Basil,
bear with me ...... I just purchased the IC-7300, so I am just starting to learn the intricacies. Parenthetically, it's the my first brand-new out of the box HF rig in 58 years of hamming. According to the manual, the USB port can be used for PC control, and sending received audio to the PC. It also states that decoded RTTY output can be directed to a PC. I haven't had a chance to look over the schematics, so I am unclear just what is being sent (analog, digital, both, etc.) . Additionally, there is a an ACC socket where there is the option to direct audio (analog) from the radio to a PC either from the AF detector or the rcvr IF. Because I enjoy experimenting I am very much still interested in a configuration where the DRAWS board is used in SPLIT mode. I can be patient . Thanks for your guidance relating to the USB port. 73, John, NX2I
|
|
|
|
Hi John, The IC-7300 has a built in sound card available via the USB port, this is good for Direwolf, Fldigi, WSJT-X, and other digital soundcard modems. It also presents a serial port via USB for control of the radio operating parameters and PTT. You can, of course, use the accessory port connected to the DRAWS™ port as an alternative.
On Wed, Jun 24, 2020 at 9:53 AM John Spoonhower <jpspoonhower@...> wrote: Hi Basil, --
John D. Hays Kingston, WA K7VE
|
|
|
|
John Spoonhower
John, thanks for the info. It makes sense that the soundcard output is not just RTTY. For the ACC socket on the IC-7300, is there both digital (soundcard) and analog capability? Or am I misunderstanding the cryptically worded users manual.. To me it seems you can select either AF or IF data but the format (digital vs. analog) is unclear. 73, John
|
|
|
|
John, I have a 7300 but haven't been able to exercise it yet. I have been living in an apartment for the last year with no antennas :( Most of these applications are looking for AF which the USB soundcard should provide.
On Wed, Jun 24, 2020 at 10:36 AM John Spoonhower <jpspoonhower@...> wrote:
--
John D. Hays Kingston, WA K7VE
|
|
|
|
John and John,
Have the 7300 here and have been using it for several years (yes – early adopter). Everything available over USB depending on rig settings and mode of operation are: Audio Out (analog), Audio In (digital control of rig’s “DAC”), data for C-IV rig control, data RTTY decode, limited IQ for SDR program (including ICOM’s RS-BA1 and HRD) *if* you use the remote and serial control for C-IV).
Unfortunately my test bed DRAWS unit suffered a somewhat mysterious issue and demise, so pending a replacement, I have not continued to experiment with it to any degree.
Jack Spitznagel – KD4IZ Trustee for NR3DT The Museum Ship USCGC Taney WHEC-37 Amateur Radio Group
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of John D Hays - K7VE
Sent: Wednesday, June 24, 2020 13:47 To: udrc@nw-digital-radio.groups.io Subject: Re: [draws and udrc] Split Channel
John,
I have a 7300 but haven't been able to exercise it yet. I have been living in an apartment for the last year with no antennas :(
On Wed, Jun 24, 2020 at 10:36 AM John Spoonhower <jpspoonhower@...> wrote:
-- John D. Hays K7VE
|
|
|
Which would be helpful if you were doing 9600 baud packet or higher bandwidth voice modulations. Probably not an issue on the HF 7300 like it is on the all-band all-mode IC-7100.
|
|
|
|
Hi Basil: I've recently received a fresh DRAWS Hat and am setting it up fresh again. It's been so long, my other DRAWS hat just runs as a message only Igate on one channel and an RMS/BPQ Node on the other channel. I haven't touched it in a year or two. So I'm starting out fresh again. Most things I've gotten working as expected (including qsstv using gpio for ptt), but not Split Channel.
I'm only using the split_ctrl.sh script for trying to enable and disable split mode. It appears to me that split mode is never properly enabled. Direwolf is changed appropriately as is port.conf where port1 is changed to off. But it doesn't appear that pulseaudio is getting setup correctly. The error I get in Direwolf is that the sound device draws-capture-left can't be opened, pointless to continue. I am able to run split_ctrl.sh off which reverts the direwolf.conf and port.conf changes back and I end up with udr0 and udr1 for packet again or udrc for sound cards. If I remember last time I had this working, I end up with two sound "devices", draws-left and draws-right, or something along those lines. Is that they way Split Channel is still working? Is there something else I'm doing or not doing? 73, Jim
|
|
|
|
Jim,
toggle quoted messageShow quoted text
I will have to take a look at the split channel script. I know pulse audio has had a lot of changes since I last played around with split channel. The Raspberry Pi OS systemd service files for pulseaudio changed from system to user files and I think that is what is causing your problem. I folded the split_status.sh, split_uninstall.sh & split_chan.sh scripts into the split_ctrl.sh script so you are correct in only using split_ctrl.sh Also I have only tested using packet/direwolf on the left channel (udr0) and HF on the right channel. I'll look at it this weekend. /Basil Jim VA7SHG/VE7TGZ <jim@...> writes:
Hi Basil: I've recently received a fresh DRAWS Hat and am setting it up fresh again. It's been so long, my other DRAWS hat just runs as a message only Igate on one channel and an RMS/BPQ Node on the other channel. I haven't touched it in a year or two. So I'm starting out fresh again. Most things I've gotten working as expected (including qsstv using gpio for ptt), but not Split Channel.
|
|
|
|
Crap Basi, I got it working but not sure of the exact steps. Here's what I recall, I'll try to replicate on a fresh install.
I copied the pulse directory from ~/dev/github/split-channels/etc/ to /etc/, ~/dev/github/split-channels/etc/asound.conf to /etc/ and I turned pulseaudio into a service. I did these steps by hand. Then I run the split_ctrl.sh script with left as the argument. Direwolf complains on restart about not finding the draws-left-capture sound device. I reboot my pi and then start direwolf manually (ax25-start) and it works fine. I have access to the right din for SSTV/JS8/FLDigi and left does packet. I notice that the script though doesn't correctly comment or uncomment the direwolf.conf file for channel 1, though direwolf still appears to work, so I'm not sure it's needed? So for now, it's working fine for me, not completely automated, but good enough for my purposes. 73, Jim
|
|
|
|
Hey Jim,
So for now, it's working fine for me, not completely automated, butGood work! You probably want to ignore the following. I think I have a handle on what has been going on with pulseaudio. It used to default to being a 'system' app but now defaults to a being a 'user' app which has implications for the systemd service files. I spent the day yesterday modifying splitchan/split_ctrl.sh to start up with systemd 'user' service files. I found that direwolf could not find the virtual device names (draws-capture-left draws-playback-left) by doing that. Switched back to 'system' service files and direwolf could connect to the virtual device names. So that's were I'm leaving it. I have been doing a lot of testing with 9600 baud packet and I found that the parameters I have when direwolf connects to ALSA devices (NOT split channel) works really well and when using the pulseaudio devices things really slow down. I haven't mucked with this too much so just an observation at this point. Notes on using the (heavily) modified split_ctrl.sh script After bringing up a regular 2 channel packet config: cd cd n7nix/splitchan # This will create a packet port on the left mDin6 connector and leave the right connector available for HF ./split_ctrl.sh left # This will give you some status info. ./split_ctrl.sh -s # This will revert back to a two port packet device ./split_ctrl.sh off Look at the last few lines of the split_ctrl.sh script to get an idea of what is going on. /Basil n7nix Jim VA7SHG/VE7TGZ <jim@...> writes: Crap Basi, I got it working but not sure of the exact steps. Here's
|
|
|
|
That’s great Basil, thanks for the insight. And very interesting about the difference between the sound quality of ALSA vs Pulse. Anecdotally, I may have also noticed that difference, but it was only my ears. I’ll pay more attention as I’m experimenting.
toggle quoted messageShow quoted text
73, Jim
On Mar 21, 2021, at 16:23, Basil Gunn <basil@...> wrote:
|
|
|