When you configure the SERIALKISS parameter in each of the "channel"
areas, are you specifying unique serial ports or are you assuming
the data from both Direwolf channel 0 and channel 1 will be mux'ed
into the same serial port?? As an experiment, gave you tried just
configuring the SERIALKISS parameter for channel 1 only and see if
you now receive the 9600bps traffic on the configured serial port?
--David
KI6ZHD
On 12/05/2021 10:15 AM, Douglas Pervine
wrote:
toggle quoted message
Show quoted text
I have two RPi 4's both have Audio Injector Zero sound
cards. Both are running DW 1.7B. Both are configured with Channel
0 at 1200 baud and Channel 1 at 9600 baud.
The two RPi 4's communicate perfectly.
I have one RPi 4 configured with "SERIALKISS /dev/ttyUSB0 115200"
as described in the User Guide, para 9.4.3 on page 85.? I then
attached a
null-modem cable to a WIN-10 machine running YAAC as described in
the User Guide, para 4.4.3 on page 16.
My problem is this:? DW will only listen to/communicate with
Channel 0.? Any activity on Channel 1 is ignored.
I have verified this by using a Kenwood TH-D74A.? When I beacon at
1200 baud, the both RPi's receive it and the one that has a
SERIALKISS null-modem cable to?
YAAC also receives the beacon.? However, when I beacon at 9600
baud, only the RPi's receive the beacon.? The beacon isn't passed
to YAAC over the null-modem cable.
Any assistance would be greatly appreciated.
?
