|
A followup to this:
You can't set the KISS channel number in YAAC until you have connected to the Direwolf instance. This is because the port behavior is different if you make a KISS connection to W1HKJ's fldigi program, where only channel 0 is supported, but it is possible to change fldigi software modems on-the-fly from the YAAC UI. If the remote KISS server is identified as _not_ fldigi (such as for DireWolf), then you can configure the KISS channel number for the YAAC port. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Andrew P. <andrewemt@...> Sent: Monday, December 6, 2021 1:35 PM To: [email protected] Subject: Re: [direwolf] KISS TNC emulation issue WB2OSZ asked me to answer this. YAAC actually looks at the KISS channel number in the received frame, and only consumes if it matches the configured channel number. Transmission also uses the configured channel number in the KISS header byte. The channel number defaults to zero and can be configured to any of the legal values (0 to 15). If one YAAC wants to listen to more than one channel from the same Direwolf, it will have to open more than one KISS-over-TCP connection to the same Direwolf instance. I probably should optimize that, since Direwolf's default maximum number of KISS connections is smaller than the total range of port numbers. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Douglas Pervine <douglas.pervine@...> Sent: Sunday, December 5, 2021 1:15 PM To: [email protected] Subject: [direwolf] KISS TNC emulation issue 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. |
