1. APRSISCE@groups.io
  2. Messages
   Date   
Re: Filters. IS/RF RF/IS on various ports.

Rob Giuliano
 

XML
The XML with a date extension is from the last upgrade.  You should also have an EXE file with a date extension (the same date extensions).    This is for the case where something doesn't work, you can quickly go back to the previous working version by deleting the newer, and removing the date extension.

Filters
I believe you are correct, you cannot filter RF received.  Anything received on RF is handled (DIGI, etc.).  However, you can use the to ignore or limit hops by changing the response to WIDEn-N requests as shown on the wiki: http://aprsisce.wikidot.com/doc:digipeating

I think the general philosophy is that if it came in on RF it is safe to send on RF.  On the other hand, what you get from the internet, you need to ensure it meets amateur radio regulations.

Are you trying to filter RF data as in prevent your station from DIGI'ing a request just because of a callsign?
  Most TOCALLs are ALTNETs or just an indication of the APRS app in use.  Why would you block certain ones from being DIGI'ed?

Robert Giuliano
KB8RCO




From: "iulianp@... [aprsisce]"
To: aprsisce@...
Sent: Monday, June 25, 2018 4:08 PM
Subject: Re: [aprsisce] Filters. IS/RF RF/IS on various ports.

 
Filters.
I had a bit of a 'revelation' this morning. I came across a couple of similar unanswered questions somewhere else on the net. I believe the filters only apply to the RF IS / IS RF traffic and they do not interfere at all with the RF digipeater function in the APRSIS32 program. In other words, if I used APRSIS32 as a WIDEn-N RF digipeater and wanted to block a certain TOCALL, for example, the filter -u/TOCALL won't have any effect on the digipeated packet. That TOCALL won't go though the RF IS though in my APRSIS32. I am yet to do some experiments on this.

RF IS IS RF vs APRS-IS disabled/enabled.
I also need to experiment with the RF IS tick boxes on the RF port and APRS-IS port (enabled and disabled). See the outcome.

XML
Truly, I haven't seen many xml files in the programs folder! There is one more in my case. It has a date extension added to it. Probably another backup.

"Lynn's implementation of filters"
I have seen something in the manual, pg 38.

Any comments and suggestions on the above from pax who have already mastered APRSIS32, more than welcome.

73, J, YO3FCA M0IPU
Re: Filters. IS/RF RF/IS on various ports.

Julian
 

Filters.
I had a bit of a 'revelation' this morning. I came across a couple of similar unanswered questions somewhere else on the net. I believe the filters only apply to the RF IS / IS RF traffic and they do not interfere at all with the RF digipeater function in the APRSIS32 program. In other words, if I used APRSIS32 as a WIDEn-N RF digipeater and wanted to block a certain TOCALL, for example, the filter -u/TOCALL won't have any effect on the digipeated packet. That TOCALL won't go though the RF IS though in my APRSIS32. I am yet to do some experiments on this.

RF IS IS RF vs APRS-IS disabled/enabled.
I also need to experiment with the RF IS tick boxes on the RF port and APRS-IS port (enabled and disabled). See the outcome.

XML
Truly, I haven't seen many xml files in the programs folder! There is one more in my case. It has a date extension added to it. Probably another backup.

"Lynn's implementation of filters"
I have seen something in the manual, pg 38.

Any comments and suggestions on the above from pax who have already mastered APRSIS32, more than welcome.

73, J, YO3FCA M0IPU
Re: Filters. IS/RF RF/IS on various ports.

Michael Wright
 

From: "Rob Giuliano
I am not an expert, but specific questions can get great results as many people
your answers and other posts very educational and thanks for taking time to post.

In other APRSISCE news, last week was our Parachute Mobile Mission 31 and APRSISCE is a major component to track jumpers and log data.

couple weeks before that I setup a APRS demo at a city park along with other San Jose RACES members. There was a group near Lake Tahoe that responded to a QST message post, we messaged back and forth just like chat rooms on the internet but this was not the internet. See attached.

Mike K6MFW
Re: Filters. IS/RF RF/IS on various ports.

Rob Giuliano
 

beyond the map tiles, the only 2 files APRSIS32 uses are the execuatable (APRSIS32.exe) and XML (APRSIS32.XML).  There is a "safe file" backup of the xml (APRSIS32-safe.XML), but in theory, it isn't used (unless something is missed up in the working file).

The G and I filter functionality is still experimental.  Because a bad configuration could have a major impact on the RF channel load, the setting are not saved between starts. 

One reason is to ensure if you close APRSIS32 to quickly to stop an RF flood, it doesn't automatically re-flood when you start it.

Another reason is that there is still some experimentation and discussion on ways to ensure this feature doesn't flood the RF channel.  Right now it is up to the user to ensure their settings are "RF friendly".
 
Lynn's implementation of filters is a bit more capable than the standard, server side filters.  This includes additive filters for more control.  I am not an expert, but specific questions can get great results as many people on the list are much better with them.

Robert Giuliano
KB8RCO


From: "iulianpt@... [aprsisce]" To: aprsisce@...
Sent: Sunday, June 24, 2018 11:06 AM
Subject: [aprsisce] Filters. IS/RF RF/IS on various ports.

 
Hi. I have to admit I haven't read the APRSIS32 manual page by page; headlines plus few paragraphs here and there. Work and family commitments in the last few years have taken a heavy toll on my free time.


1.) I am not very sure whether I understand the filtering in APRSIS32. I don't think I have a clear mental picture of some of the APRSIS32 functions or structure, something like a flow diagram (logic chart).

  • If I set a filter in "Configure/General/Add Filter" I can see it in APRSIS32.xml as -b/M9XYZ 0
  •  If I set the same filter with Ctrl G it doesn't seem to be written in any APRSIS32 file (I did a search in every config file in the APRSIS32 folder).
  • Most importantly, the above filter (-b/M9XYZ) has no effect on the station, in other words, the station still gets digipeated by my WIDE1-1 digi (station M9XYZ heard over RF, digipeated over RF).
  • How do I setup multiple filters in "Configure/General/Add Filter" or the xml file? Are they comma etc separated? I have tried to add multiple ... lines in the xml file, but it doesn't seem to work.


2.) RF to IS, IS to RF on an RF port versus the APRSIS port.

  • If I enable RF to IS, IS to RF an AGW RF port for ex and have APRSIS disabled I assume the RF/IS RF/IS traffic won't take place?
  •  What is the purpose of the RF/IS IS/RF check boxes on the APRSIS port? How do they compete with the same checkboxes on a RF port?
  • In other words, if APRS-IS is disabled in the client, RF IS IS RF traffic can still take place? I in a bit of a logical mix-up here.

Much appreciated,
73, Julian, YO3FCA MØIPU
 
Filters. IS/RF RF/IS on various ports.

iulianpt@...
 

Hi. I have to admit I haven't read the APRSIS32 manual page by page; headlines plus few paragraphs here and there. Work and family commitments in the last few years have taken a heavy toll on my free time.



1.) I am not very sure whether I understand the filtering in APRSIS32. I don't think I have a clear mental picture of some of the APRSIS32 functions or structure, something like a flow diagram (logic chart).


  • If I set a filter in "Configure/General/Add Filter" I can see it in APRSIS32.xml as <!--CompanionCall--> <CompanionInterval>0</CompanionInterval> <Filter>-b/M9XYZ</Filter> <CommentInterval>0</CommentInterval>
  •  If I set the same filter with Ctrl G it doesn't seem to be written in any APRSIS32 file (I did a search in every config file in the APRSIS32 folder).
  • Most importantly, the above filter (-b/M9XYZ) has no effect on the station, in other words, the station still gets digipeated by my WIDE1-1 digi (station M9XYZ heard over RF, digipeated over RF).
  • How do I setup multiple filters in "Configure/General/Add Filter" or the xml file? Are they comma etc separated? I have tried to add multiple <Filter>...</Filter> lines in the xml file, but it doesn't seem to work.


2.) RF to IS, IS to RF on an RF port versus the APRSIS port.

  • If I enable RF to IS, IS to RF an AGW RF port for ex and have APRSIS disabled I assume the RF/IS RF/IS traffic won't take place?
  •  What is the purpose of the RF/IS IS/RF check boxes on the APRSIS port? How do they compete with the same checkboxes on a RF port?
  • In other words, if APRS-IS is disabled in the client, RF IS IS RF traffic can still take place? I in a bit of a logical mix-up here.

Much appreciated,
73, Julian, YO3FCA MØIPU
 
Re: D74 with APRSIS32 won't transmit

Rob Giuliano
 

I love those pants!  About the only pants and shorts I wear these days (never was much for jeans).
Yes, Docker.Lean more at: https://www.docker.com/what-docker Robert Giuliano KB8RCO

From: "Greg D ko6th.greg@gmail.com [aprsisce]" <aprsisce@yahoogroups.com>
To: aprsisce@yahoogroups.com
Sent: Friday, June 22, 2018 5:27 PM
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

  Docker?  The only Docker I know of has two legs and pockets...  :)

Greg  KO6TH


Rob Giuliano kb8rco@yahoo.com [aprsisce] wrote:

  I use a Bluetooth dongle and as luck would have it, VirtualBox has provisions for USB pass-through. I haven't done that in some time though.  Since Docker came around, I stopped using VirtualBox on Linux.   Robert Giuliano KB8RCO

From: "Greg D ko6th.greg@gmail.com [aprsisce]" <aprsisce@yahoogroups.com>
To: aprsisce@yahoogroups.com
Sent: Thursday, June 21, 2018 4:38 PM
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

  Running VBox or VMware might work, but I don't know how it would have proper access to the BT hardware.  Usually these sorts of things depend on the host PC to provide support to the device file level, and that lower level is where the trouble is.  USB is working now, so I'm good.  Getting BT to work that way would be WAY more trouble than it's worth at this point.  But thanks for the suggestion.

Greg  KO6TH


Rob Giuliano kb8rco@yahoo.com [aprsisce] wrote:

  I prefer an virtual machine running a very limited install of Windows XP for such occasions. XP can be stripped down pretty easily to not much more than the operating system for a small virtualbox drive. That is if you have an XP compatible Windows app.  Save the reboot time.   Option 2 would be run Windows and use Virtualbox for Linux.
Robert Giuliano KB8RCO

From: "Greg D ko6th.greg@gmail.com [aprsisce]" <aprsisce@yahoogroups.com>
To: aprsisce@yahoogroups.com
Sent: Thursday, June 21, 2018 4:26 PM
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

  I don't think the Bluetooth issue is with APRSIS32 or Wine.  The device seems to connect as displayed on the Linux side, but I never see the BT symbol on the D74 light up, and a few seconds later Linux shows the device as not connected.  So, I think something's not matching up in their respective BT stacks, causing an error.  The D74's BT stack is known for being a bit quirky, so this isn't totally unexpected as Linux isn't an operating system that Kenwood supports. 

I tried configuring a BT port for APRSIS32, hoping perhaps the connection would stay up if there was something to talk to, but that didn't work.

I'll just leave things as they are for now, and revisit this perhaps later.  The original plan for Field Day was to take the Netbook (running Win 7), as it's more portable, has its own SIM for Internet connections, and is less valuable, but the issue with gpredict forced the use of my full-sized laptop.  It dual-boots with Win 10, but I strongly prefer to leave it running Linux.

Greg  KO6TH


Rob Giuliano kb8rco@yahoo.com [aprsisce] wrote:

  I have found that with APRSIS32 under WINE, you are always better off linking to COMM ports. Most Bluetooth devices are listed as /dev/rfcomm# (I think that is how it gets listed).  I can double check when I get home
from within /home/{username}/.wine/dosdevices ln -s /dev/rfcomm0 com8 
Then connect to Com8 in APRSIS32. 
Again, I do not use a D74, but this works with all my Bluetooth devices I use to connect to the TNCs
Robert Giuliano KB8RCO

From: "Greg D ko6th.greg@gmail.com [aprsisce]" <aprsisce@yahoogroups.com>
To: aprsisce@yahoogroups.com
Sent: Thursday, June 21, 2018 4:05 PM
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

  Thanks, Rob. 

Not sure what it was, but it's working now.  I was already in Dialout, but added Modem and UUCP to the groups.  Logged out and back in and it's working.  What's odd is that I could write to the serial device just fine from putty (sending the ID command to the D74), and receive just fine with APRSIS32, but not send.  {Shrug}

So, for field day I don't have to switch between Linux and Windows to run the various apps that I need.  I only wish I could get the D74's Bluetooth connection to link up with Linux.  Works fine in Windows with APRSIS32, but then I'm, blocked when I try to run gpredict.  The Doppler tracking isn't working under Windows, and I'm really hoping to snag 100 pts with AO-92 mode L/v.  Perfect pass at 11:09 am local on Saturday.

Greg  KO6TH


Rob Giuliano kb8rco@yahoo.com [aprsisce] wrote:

  Although I am not a D74 user, I have worked with various serial interfaces on Windows, Linux, and other operating systems.
A couple additional things to consider: * Could be that the radio is expecting hardware flow control (common with KISS mode TNCs to ensure buffers don't fill)    This should be a setting in the radio and the Linux system.  Linux uses stty to control the port settings.  * If the D74 is using Hayes AT commands, you typically go between "command mode" and "use mode" with by sending +++   I'd be surprised if Kenwood is using the Hayes command set though.   Robert Giuliano KB8RCO


First thing to check is whether you have write permission for /dev/ttyACMo. Most serial devices belong to the "dialout" group (/etc/groups).  Have you added your username to that group?
If that isn't it, answer these questions:    What does the "port log" in APRSIS32 say when you transmit?
   What happens if you leave PuTTY (under WINE or compiled fro Linux) connected for awhile?       Does it show KISS packets or clear text?   The ACM# means that Linux thinks it is a modem (rather than a RAW serial device).  This typically isn't a problem, but can be if the modem state is "awaiting AT commands".  You can lookup an AT command to put in the OpenCmd are to ensure it isn't in a "command mode" (could explain the response to "id" as opposed to sending "id" out the TNC portion).
Robert Giuliano KB8RCO

From: "Greg D ko6th.greg@gmail.com [aprsisce]" <aprsisce@yahoogroups.com>
To: aprsisce@yahoogroups.com
Sent: Thursday, June 21, 2018 2:55 PM
Subject: [aprsisce] D74 with APRSIS32 won't transmit

  Hi folks,

Not sure if this is particular to the D74 or APRSIS32... I have the
Kenwood TH-D74 configured for KISS 12, and the Interface for KISS is
USB. USB is configured for COM use. The whole lot is hooked via USB to
my laptop which is running Linux. 'dmesg' on Linux shows the radio
serial port as /dev/ttyACM0, as expected. The device files under
dosdevices show this as COM33.

APRSIS32 is running under Wine, and it properly displays RF traffic
received by the radio. I can also fire up Putty (instead of APRSIS32,
so no com port fighting), and talk to the radio (send "id" and the radio
responds "TH-D74". So I know that the USB connection is working and
that I can both send and receive. The port type is SimplyKISS, COM port
set to COM33. I've even done the system.reg hack for COM33, just in
case, though all the com ports seem to show up when configuring the
device port. The Transmit Enabled box is checked.

I have turned off Enable / Internet access and APRS-IS, to force using
the radio.

But when I hit the Transmit button on APRSIS32, nothing happens. No
transmit. What am I missing?

Greg KO6TH



















#yiv6630333356 #yiv6630333356 -- #yiv6630333356ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv6630333356 #yiv6630333356ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv6630333356 #yiv6630333356ygrp-mkp #yiv6630333356hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv6630333356 #yiv6630333356ygrp-mkp #yiv6630333356ads {margin-bottom:10px;}#yiv6630333356 #yiv6630333356ygrp-mkp .yiv6630333356ad {padding:0 0;}#yiv6630333356 #yiv6630333356ygrp-mkp .yiv6630333356ad p {margin:0;}#yiv6630333356 #yiv6630333356ygrp-mkp .yiv6630333356ad a {color:#0000ff;text-decoration:none;}#yiv6630333356 #yiv6630333356ygrp-sponsor #yiv6630333356ygrp-lc {font-family:Arial;}#yiv6630333356 #yiv6630333356ygrp-sponsor #yiv6630333356ygrp-lc #yiv6630333356hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv6630333356 #yiv6630333356ygrp-sponsor #yiv6630333356ygrp-lc .yiv6630333356ad {margin-bottom:10px;padding:0 0;}#yiv6630333356 #yiv6630333356actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv6630333356 #yiv6630333356activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv6630333356 #yiv6630333356activity span {font-weight:700;}#yiv6630333356 #yiv6630333356activity span:first-child {text-transform:uppercase;}#yiv6630333356 #yiv6630333356activity span a {color:#5085b6;text-decoration:none;}#yiv6630333356 #yiv6630333356activity span span {color:#ff7900;}#yiv6630333356 #yiv6630333356activity span .yiv6630333356underline {text-decoration:underline;}#yiv6630333356 .yiv6630333356attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv6630333356 .yiv6630333356attach div a {text-decoration:none;}#yiv6630333356 .yiv6630333356attach img {border:none;padding-right:5px;}#yiv6630333356 .yiv6630333356attach label {display:block;margin-bottom:5px;}#yiv6630333356 .yiv6630333356attach label a {text-decoration:none;}#yiv6630333356 blockquote {margin:0 0 0 4px;}#yiv6630333356 .yiv6630333356bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv6630333356 .yiv6630333356bold a {text-decoration:none;}#yiv6630333356 dd.yiv6630333356last p a {font-family:Verdana;font-weight:700;}#yiv6630333356 dd.yiv6630333356last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv6630333356 dd.yiv6630333356last p span.yiv6630333356yshortcuts {margin-right:0;}#yiv6630333356 div.yiv6630333356attach-table div div a {text-decoration:none;}#yiv6630333356 div.yiv6630333356attach-table {width:400px;}#yiv6630333356 div.yiv6630333356file-title a, #yiv6630333356 div.yiv6630333356file-title a:active, #yiv6630333356 div.yiv6630333356file-title a:hover, #yiv6630333356 div.yiv6630333356file-title a:visited {text-decoration:none;}#yiv6630333356 div.yiv6630333356photo-title a, #yiv6630333356 div.yiv6630333356photo-title a:active, #yiv6630333356 div.yiv6630333356photo-title a:hover, #yiv6630333356 div.yiv6630333356photo-title a:visited {text-decoration:none;}#yiv6630333356 div#yiv6630333356ygrp-mlmsg #yiv6630333356ygrp-msg p a span.yiv6630333356yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv6630333356 .yiv6630333356green {color:#628c2a;}#yiv6630333356 .yiv6630333356MsoNormal {margin:0 0 0 0;}#yiv6630333356 o {font-size:0;}#yiv6630333356 #yiv6630333356photos div {float:left;width:72px;}#yiv6630333356 #yiv6630333356photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv6630333356 #yiv6630333356photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv6630333356 #yiv6630333356reco-category {font-size:77%;}#yiv6630333356 #yiv6630333356reco-desc {font-size:77%;}#yiv6630333356 .yiv6630333356replbq {margin:4px;}#yiv6630333356 #yiv6630333356ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv6630333356 #yiv6630333356ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv6630333356 #yiv6630333356ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv6630333356 #yiv6630333356ygrp-mlmsg select, #yiv6630333356 input, #yiv6630333356 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv6630333356 #yiv6630333356ygrp-mlmsg pre, #yiv6630333356 code {font:115% monospace;}#yiv6630333356 #yiv6630333356ygrp-mlmsg * {line-height:1.22em;}#yiv6630333356 #yiv6630333356ygrp-mlmsg #yiv6630333356logo {padding-bottom:10px;}#yiv6630333356 #yiv6630333356ygrp-msg p a {font-family:Verdana;}#yiv6630333356 #yiv6630333356ygrp-msg p#yiv6630333356attach-count span {color:#1E66AE;font-weight:700;}#yiv6630333356 #yiv6630333356ygrp-reco #yiv6630333356reco-head {color:#ff7900;font-weight:700;}#yiv6630333356 #yiv6630333356ygrp-reco {margin-bottom:20px;padding:0px;}#yiv6630333356 #yiv6630333356ygrp-sponsor #yiv6630333356ov li a {font-size:130%;text-decoration:none;}#yiv6630333356 #yiv6630333356ygrp-sponsor #yiv6630333356ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv6630333356 #yiv6630333356ygrp-sponsor #yiv6630333356ov ul {margin:0;padding:0 0 0 8px;}#yiv6630333356 #yiv6630333356ygrp-text {font-family:Georgia;}#yiv6630333356 #yiv6630333356ygrp-text p {margin:0 0 1em 0;}#yiv6630333356 #yiv6630333356ygrp-text tt {font-size:120%;}#yiv6630333356 #yiv6630333356ygrp-vital ul li:last-child {border-right:none !important;}#yiv6630333356
Re: D74 with APRSIS32 won't transmit

Greg D
 

Docker?  The only Docker I know of has two legs and pockets...  :)

Greg  KO6TH

Rob Giuliano kb8rco@yahoo.com [aprsisce] wrote:



I use a Bluetooth dongle and as luck would have it, VirtualBox has
provisions for USB pass-through.
I haven't done that in some time though.  Since Docker came around, I
stopped using VirtualBox on Linux.

Robert Giuliano
KB8RCO



*From:* "Greg D ko6th.greg@gmail.com [aprsisce]" ( aprsisce@yahoogroups.com
)
*To:* aprsisce@yahoogroups.com
*Sent:* Thursday, June 21, 2018 4:38 PM
*Subject:* Re: [aprsisce] D74 with APRSIS32 won't transmit


Running VBox or VMware might work, but I don't know how it would have
proper access to the BT hardware.  Usually these sorts of things depend on
the host PC to provide support to the device file level, and that lower
level is where the trouble is.  USB is working now, so I'm good.  Getting
BT to work that way would be WAY more trouble than it's worth at this
point.  But thanks for the suggestion.

Greg  KO6TH



Rob Giuliano kb8rco@yahoo.com [aprsisce] wrote:



I prefer an virtual machine running a very limited install of Windows XP
for such occasions. XP can be stripped down pretty easily to not much more
than the operating system for a small virtualbox drive. That is if you
have an XP compatible Windows app.  Save the reboot time.

Option 2 would be run Windows and use Virtualbox for Linux.


Robert Giuliano
KB8RCO



*From:* "Greg D ko6th.greg@gmail.com [aprsisce]" ( aprsisce@yahoogroups.com
)
*To:* aprsisce@yahoogroups.com
*Sent:* Thursday, June 21, 2018 4:26 PM
*Subject:* Re: [aprsisce] D74 with APRSIS32 won't transmit


I don't think the Bluetooth issue is with APRSIS32 or Wine.  The device
seems to connect as displayed on the Linux side, but I never see the BT
symbol on the D74 light up, and a few seconds later Linux shows the device
as not connected.  So, I think something's not matching up in their
respective BT stacks, causing an error.  The D74's BT stack is known for
being a bit quirky, so this isn't totally unexpected as Linux isn't an
operating system that Kenwood supports.

I tried configuring a BT port for APRSIS32, hoping perhaps the connection
would stay up if there was something to talk to, but that didn't work.

I'll just leave things as they are for now, and revisit this perhaps
later.  The original plan for Field Day was to take the Netbook (running
Win 7), as it's more portable, has its own SIM for Internet connections,
and is less valuable, but the issue with gpredict forced the use of my
full-sized laptop.  It dual-boots with Win 10, but I strongly prefer to
leave it running Linux.

Greg  KO6TH



Rob Giuliano kb8rco@yahoo.com [aprsisce] wrote:



I have found that with APRSIS32 under WINE, you are always better off
linking to COMM ports.
Most Bluetooth devices are listed as /dev/rfcomm# (I think that is how it
gets listed).  I can double check when I get home


from within */home/{username}/.wine/dosdevices*
*ln -s /dev/rfcomm0 com8*


Then connect to Com8 in APRSIS32.


Again, I do not use a D74, but this works with all my Bluetooth devices I
use to connect to the TNCs


Robert Giuliano
KB8RCO



*From:* "Greg D ko6th.greg@gmail.com [aprsisce]" ( aprsisce@yahoogroups.com
)
*To:* aprsisce@yahoogroups.com
*Sent:* Thursday, June 21, 2018 4:05 PM
*Subject:* Re: [aprsisce] D74 with APRSIS32 won't transmit


Thanks, Rob.

Not sure what it was, but it's working now.  I was already in Dialout, but
added Modem and UUCP to the groups.  Logged out and back in and it's
working.  What's odd is that I could write to the serial device just fine
from putty (sending the ID command to the D74), and receive just fine with
APRSIS32, but not send.  {Shrug}

So, for field day I don't have to switch between Linux and Windows to run
the various apps that I need.  I only wish I could get the D74's Bluetooth
connection to link up with Linux.  Works fine in Windows with APRSIS32,
but then I'm, blocked when I try to run gpredict.  The Doppler tracking
isn't working under Windows, and I'm really hoping to snag 100 pts with
AO-92 mode L/v.  Perfect pass at 11:09 am local on Saturday.

Greg  KO6TH



Rob Giuliano kb8rco@yahoo.com [aprsisce] wrote:



Although I am not a D74 user, I have worked with various serial interfaces
on Windows, Linux, and other operating systems.


A couple additional things to consider:
* Could be that the radio is expecting hardware flow control (common with
KISS mode TNCs to ensure buffers don't fill)
This should be a setting in the radio and the Linux system.  Linux uses
stty to control the port settings.
* If the D74 is using Hayes AT commands, you typically go between "command
mode" and "use mode" with by sending *+++*
I'd be surprised if Kenwood is using the Hayes command set though.

Robert Giuliano
KB8RCO





First thing to check is whether you have write permission for */dev/ttyACMo*
.
Re: D74 with APRSIS32 won't transmit

Rob Giuliano
 

I use a Bluetooth dongle and as luck would have it, VirtualBox has provisions for USB pass-through.I haven't done that in some time though.  Since Docker came around, I stopped using VirtualBox on Linux. Robert Giuliano KB8RCO

From: "Greg D ko6th.greg@gmail.com [aprsisce]" <aprsisce@yahoogroups.com>
To: aprsisce@yahoogroups.com
Sent: Thursday, June 21, 2018 4:38 PM
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

  Running VBox or VMware might work, but I don't know how it would have proper access to the BT hardware.  Usually these sorts of things depend on the host PC to provide support to the device file level, and that lower level is where the trouble is.  USB is working now, so I'm good.  Getting BT to work that way would be WAY more trouble than it's worth at this point.  But thanks for the suggestion.

Greg  KO6TH


Rob Giuliano kb8rco@yahoo.com [aprsisce] wrote:

  I prefer an virtual machine running a very limited install of Windows XP for such occasions. XP can be stripped down pretty easily to not much more than the operating system for a small virtualbox drive. That is if you have an XP compatible Windows app.  Save the reboot time.   Option 2 would be run Windows and use Virtualbox for Linux.
Robert Giuliano KB8RCO

From: "Greg D ko6th.greg@gmail.com [aprsisce]" <aprsisce@yahoogroups.com>
To: aprsisce@yahoogroups.com
Sent: Thursday, June 21, 2018 4:26 PM
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

  I don't think the Bluetooth issue is with APRSIS32 or Wine.  The device seems to connect as displayed on the Linux side, but I never see the BT symbol on the D74 light up, and a few seconds later Linux shows the device as not connected.  So, I think something's not matching up in their respective BT stacks, causing an error.  The D74's BT stack is known for being a bit quirky, so this isn't totally unexpected as Linux isn't an operating system that Kenwood supports. 

I tried configuring a BT port for APRSIS32, hoping perhaps the connection would stay up if there was something to talk to, but that didn't work.

I'll just leave things as they are for now, and revisit this perhaps later.  The original plan for Field Day was to take the Netbook (running Win 7), as it's more portable, has its own SIM for Internet connections, and is less valuable, but the issue with gpredict forced the use of my full-sized laptop.  It dual-boots with Win 10, but I strongly prefer to leave it running Linux.

Greg  KO6TH


Rob Giuliano kb8rco@yahoo.com [aprsisce] wrote:

  I have found that with APRSIS32 under WINE, you are always better off linking to COMM ports. Most Bluetooth devices are listed as /dev/rfcomm# (I think that is how it gets listed).  I can double check when I get home
from within /home/{username}/.wine/dosdevices ln -s /dev/rfcomm0 com8 
Then connect to Com8 in APRSIS32. 
Again, I do not use a D74, but this works with all my Bluetooth devices I use to connect to the TNCs
Robert Giuliano KB8RCO

From: "Greg D ko6th.greg@gmail.com [aprsisce]" <aprsisce@yahoogroups.com>
To: aprsisce@yahoogroups.com
Sent: Thursday, June 21, 2018 4:05 PM
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

  Thanks, Rob. 

Not sure what it was, but it's working now.  I was already in Dialout, but added Modem and UUCP to the groups.  Logged out and back in and it's working.  What's odd is that I could write to the serial device just fine from putty (sending the ID command to the D74), and receive just fine with APRSIS32, but not send.  {Shrug}

So, for field day I don't have to switch between Linux and Windows to run the various apps that I need.  I only wish I could get the D74's Bluetooth connection to link up with Linux.  Works fine in Windows with APRSIS32, but then I'm, blocked when I try to run gpredict.  The Doppler tracking isn't working under Windows, and I'm really hoping to snag 100 pts with AO-92 mode L/v.  Perfect pass at 11:09 am local on Saturday.

Greg  KO6TH


Rob Giuliano kb8rco@yahoo.com [aprsisce] wrote:

  Although I am not a D74 user, I have worked with various serial interfaces on Windows, Linux, and other operating systems.
A couple additional things to consider: * Could be that the radio is expecting hardware flow control (common with KISS mode TNCs to ensure buffers don't fill)    This should be a setting in the radio and the Linux system.  Linux uses stty to control the port settings.  * If the D74 is using Hayes AT commands, you typically go between "command mode" and "use mode" with by sending +++   I'd be surprised if Kenwood is using the Hayes command set though.   Robert Giuliano KB8RCO


First thing to check is whether you have write permission for /dev/ttyACMo. Most serial devices belong to the "dialout" group (/etc/groups).  Have you added your username to that group?
If that isn't it, answer these questions:    What does the "port log" in APRSIS32 say when you transmit?
   What happens if you leave PuTTY (under WINE or compiled fro Linux) connected for awhile?       Does it show KISS packets or clear text?   The ACM# means that Linux thinks it is a modem (rather than a RAW serial device).  This typically isn't a problem, but can be if the modem state is "awaiting AT commands".  You can lookup an AT command to put in the OpenCmd are to ensure it isn't in a "command mode" (could explain the response to "id" as opposed to sending "id" out the TNC portion).
Robert Giuliano KB8RCO

From: "Greg D ko6th.greg@gmail.com [aprsisce]" <aprsisce@yahoogroups.com>
To: aprsisce@yahoogroups.com
Sent: Thursday, June 21, 2018 2:55 PM
Subject: [aprsisce] D74 with APRSIS32 won't transmit

  Hi folks,

Not sure if this is particular to the D74 or APRSIS32... I have the
Kenwood TH-D74 configured for KISS 12, and the Interface for KISS is
USB. USB is configured for COM use. The whole lot is hooked via USB to
my laptop which is running Linux. 'dmesg' on Linux shows the radio
serial port as /dev/ttyACM0, as expected. The device files under
dosdevices show this as COM33.

APRSIS32 is running under Wine, and it properly displays RF traffic
received by the radio. I can also fire up Putty (instead of APRSIS32,
so no com port fighting), and talk to the radio (send "id" and the radio
responds "TH-D74". So I know that the USB connection is working and
that I can both send and receive. The port type is SimplyKISS, COM port
set to COM33. I've even done the system.reg hack for COM33, just in
case, though all the com ports seem to show up when configuring the
device port. The Transmit Enabled box is checked.

I have turned off Enable / Internet access and APRS-IS, to force using
the radio.

But when I hit the Transmit button on APRSIS32, nothing happens. No
transmit. What am I missing?

Greg KO6TH















#yiv1287637836 #yiv1287637836 -- #yiv1287637836ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv1287637836 #yiv1287637836ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv1287637836 #yiv1287637836ygrp-mkp #yiv1287637836hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv1287637836 #yiv1287637836ygrp-mkp #yiv1287637836ads {margin-bottom:10px;}#yiv1287637836 #yiv1287637836ygrp-mkp .yiv1287637836ad {padding:0 0;}#yiv1287637836 #yiv1287637836ygrp-mkp .yiv1287637836ad p {margin:0;}#yiv1287637836 #yiv1287637836ygrp-mkp .yiv1287637836ad a {color:#0000ff;text-decoration:none;}#yiv1287637836 #yiv1287637836ygrp-sponsor #yiv1287637836ygrp-lc {font-family:Arial;}#yiv1287637836 #yiv1287637836ygrp-sponsor #yiv1287637836ygrp-lc #yiv1287637836hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv1287637836 #yiv1287637836ygrp-sponsor #yiv1287637836ygrp-lc .yiv1287637836ad {margin-bottom:10px;padding:0 0;}#yiv1287637836 #yiv1287637836actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv1287637836 #yiv1287637836activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv1287637836 #yiv1287637836activity span {font-weight:700;}#yiv1287637836 #yiv1287637836activity span:first-child {text-transform:uppercase;}#yiv1287637836 #yiv1287637836activity span a {color:#5085b6;text-decoration:none;}#yiv1287637836 #yiv1287637836activity span span {color:#ff7900;}#yiv1287637836 #yiv1287637836activity span .yiv1287637836underline {text-decoration:underline;}#yiv1287637836 .yiv1287637836attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv1287637836 .yiv1287637836attach div a {text-decoration:none;}#yiv1287637836 .yiv1287637836attach img {border:none;padding-right:5px;}#yiv1287637836 .yiv1287637836attach label {display:block;margin-bottom:5px;}#yiv1287637836 .yiv1287637836attach label a {text-decoration:none;}#yiv1287637836 blockquote {margin:0 0 0 4px;}#yiv1287637836 .yiv1287637836bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv1287637836 .yiv1287637836bold a {text-decoration:none;}#yiv1287637836 dd.yiv1287637836last p a {font-family:Verdana;font-weight:700;}#yiv1287637836 dd.yiv1287637836last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv1287637836 dd.yiv1287637836last p span.yiv1287637836yshortcuts {margin-right:0;}#yiv1287637836 div.yiv1287637836attach-table div div a {text-decoration:none;}#yiv1287637836 div.yiv1287637836attach-table {width:400px;}#yiv1287637836 div.yiv1287637836file-title a, #yiv1287637836 div.yiv1287637836file-title a:active, #yiv1287637836 div.yiv1287637836file-title a:hover, #yiv1287637836 div.yiv1287637836file-title a:visited {text-decoration:none;}#yiv1287637836 div.yiv1287637836photo-title a, #yiv1287637836 div.yiv1287637836photo-title a:active, #yiv1287637836 div.yiv1287637836photo-title a:hover, #yiv1287637836 div.yiv1287637836photo-title a:visited {text-decoration:none;}#yiv1287637836 div#yiv1287637836ygrp-mlmsg #yiv1287637836ygrp-msg p a span.yiv1287637836yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv1287637836 .yiv1287637836green {color:#628c2a;}#yiv1287637836 .yiv1287637836MsoNormal {margin:0 0 0 0;}#yiv1287637836 o {font-size:0;}#yiv1287637836 #yiv1287637836photos div {float:left;width:72px;}#yiv1287637836 #yiv1287637836photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv1287637836 #yiv1287637836photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv1287637836 #yiv1287637836reco-category {font-size:77%;}#yiv1287637836 #yiv1287637836reco-desc {font-size:77%;}#yiv1287637836 .yiv1287637836replbq {margin:4px;}#yiv1287637836 #yiv1287637836ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv1287637836 #yiv1287637836ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv1287637836 #yiv1287637836ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv1287637836 #yiv1287637836ygrp-mlmsg select, #yiv1287637836 input, #yiv1287637836 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv1287637836 #yiv1287637836ygrp-mlmsg pre, #yiv1287637836 code {font:115% monospace;}#yiv1287637836 #yiv1287637836ygrp-mlmsg * {line-height:1.22em;}#yiv1287637836 #yiv1287637836ygrp-mlmsg #yiv1287637836logo {padding-bottom:10px;}#yiv1287637836 #yiv1287637836ygrp-msg p a {font-family:Verdana;}#yiv1287637836 #yiv1287637836ygrp-msg p#yiv1287637836attach-count span {color:#1E66AE;font-weight:700;}#yiv1287637836 #yiv1287637836ygrp-reco #yiv1287637836reco-head {color:#ff7900;font-weight:700;}#yiv1287637836 #yiv1287637836ygrp-reco {margin-bottom:20px;padding:0px;}#yiv1287637836 #yiv1287637836ygrp-sponsor #yiv1287637836ov li a {font-size:130%;text-decoration:none;}#yiv1287637836 #yiv1287637836ygrp-sponsor #yiv1287637836ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv1287637836 #yiv1287637836ygrp-sponsor #yiv1287637836ov ul {margin:0;padding:0 0 0 8px;}#yiv1287637836 #yiv1287637836ygrp-text {font-family:Georgia;}#yiv1287637836 #yiv1287637836ygrp-text p {margin:0 0 1em 0;}#yiv1287637836 #yiv1287637836ygrp-text tt {font-size:120%;}#yiv1287637836 #yiv1287637836ygrp-vital ul li:last-child {border-right:none !important;}#yiv1287637836
Re: Digest Number 3136

Randy Allen
 

Thanks for the reply.

I've never messed with filters much, so I'm not sure I have this. If I read the APRS-IS filters wiki-dot page correctly (http://aprsisce.wikidot.com/aprs-is-filters), then in the pop up box I get with Ctl+g I put the following in to get what I want?

t/n/30  for NWS weather and objects inside a 30km range?  Then the Ctl+i will then port them to RF?

I'll see what comes up in the filter test logs after we have some weather come through the area.

Thanks again and 73

Randy KAØAZS

1a. Re: Fwd: Porting WX Bulletins to RF
Posted by: "Greg Depew" goatherder_4891@hotmail.com goatherder_4891@rocketmail.com
Date: Wed Jun 20, 2018 1:23 pm ((PDT))

You would use the Ctl+g command to setup a filter, either a range or box to send all packets in that filter to RF. Or there is the possibility of using a buddy filter to only put out your local weather office, however that will transmit everything from that office even if its 100 miles away. You should then sit and watch the log that comes up with Ctl+g for a couple days to make sure everything that's in it is what you want. Then Ctl+i will send it to RF.



Greg KB3KBR Sent from my Verizon, Samsung Galaxy smartphone
Re: D74 with APRSIS32 won't transmit

Fred Hillhouse
 

It does provide frequencies!

 

 

You may be able to load 3.5 as well assuming it is available.

 

Best regards,

Fred N7FMH

 

 

 

From: aprsisce@... [mailto:aprsisce@...]
Sent: Thursday, June 21, 2018 5:17 PM
To: aprsisce@...
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

 

 

Yikes, I haven't used Orbitron in years.  Did it have a real-time Doppler display?

I just found out that I need to take the Netbook to FD after all.  It has Winlink Express loaded (lots of points for Radio Grams), and I can't get that to run on the Dell under either Wine or Win-10.  Claims it needs .NET 3.5 and I have 4.x.  Bad software.  No biscuit.

So, re-thinking the whole laptop scene...

Greg  KO6TH

'Fred Hillhouse' fmhillhouse@... [aprsisce] wrote:

 

Orbitron is still available. TLEs have to downloaded manually since it can’t download from https.

 

There is also a TLE Retriever 3 on the Celestrak site that will get the TLEs automatically.

 

I think the last time I connected a radio to anything, I used HRD.

 

Good luck!

 

Best regards,

Fred N7FMH

 

 

From: aprsisce@... [mailto:aprsisce@...]
Sent: Thursday, June 21, 2018 4:52 PM
To: aprsisce@...
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

 

 

Hi Fred,

I'm tuning it manually; I just wanted gpredict to tell me in realtime what frequency to tune to, but couldn't get it to do that without something to talk to.  On Linux, I'm opening the Rig Control window on gpredict and telling it to tune an RTL-SDR stick via gqrx.  That's enough to keep gpredict happy.  Even works with gqrx running without the RTL-SDR even plugged in (so no waterfall active)...  Gpredict just needed something on the other end of the IP socket to talk to.

Actual control of the rig would be nice, but it's a bit more complicated than it's worth.  The radio is a Yaesu FT-736R and so needs an RS232->TTL adapter in order to run the CAT system.  I have one, but it's built into some interconnect equipment in the shack that is not portable.  But all I need to know is what frequency to tune to, and that works with the "dummy" device.  Don't need to rag-chew here, just get that golden QSO for the points.

Under Windows I would need to have yet another set rig control utilities loaded, and I've given up trying to find and configure them.  No gqrx for Windows...  So, the netbook will stay home, and the Dell coming up the hill to the FD site.  Not a big deal.  And the battery runs longer, too, so I guess that's an advantage.

Greg  KO6TH


'Fred Hillhouse' fmhillhouse@... [aprsisce] wrote:

 

Are you using gpredict to control the radio frequency too?

 

Best regards,

Fred N7FMH

 

From: aprsisce@... [mailto:aprsisce@...]
Sent: Thursday, June 21, 2018 4:05 PM
To: aprsisce@...
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

 

 

Thanks, Rob. 

Not sure what it was, but it's working now.  I was already in Dialout, but added Modem and UUCP to the groups.  Logged out and back in and it's working.  What's odd is that I could write to the serial device just fine from putty (sending the ID command to the D74), and receive just fine with APRSIS32, but not send.  {Shrug}

So, for field day I don't have to switch between Linux and Windows to run the various apps that I need.  I only wish I could get the D74's Bluetooth connection to link up with Linux.  Works fine in Windows with APRSIS32, but then I'm, blocked when I try to run gpredict.  The Doppler tracking isn't working under Windows, and I'm really hoping to snag 100 pts with AO-92 mode L/v.  Perfect pass at 11:09 am local on Saturday.

Greg  KO6TH



Rob Giuliano kb8rco@... [aprsisce] wrote:

 

Although I am not a D74 user, I have worked with various serial interfaces on Windows, Linux, and other operating systems.

 

A couple additional things to consider:

* Could be that the radio is expecting hardware flow control (common with KISS mode TNCs to ensure buffers don't fill)

   This should be a setting in the radio and the Linux system..  Linux uses stty to control the port settings. 

* If the D74 is using Hayes AT commands, you typically go between "command mode" and "use mode" with by sending +++

  I'd be surprised if Kenwood is using the Hayes command set though.

 

Robert Giuliano

KB8RCO

 

 

First thing to check is whether you have write permission for /dev/ttyACMo.

Most serial devices belong to the "dialout" group (/etc/groups).  Have you added your username to that group?

 

If that isn't it, answer these questions:

   What does the "port log" in APRSIS32 say when you transmit?

 

   What happens if you leave PuTTY (under WINE or compiled fro Linux) connected for awhile?

      Does it show KISS packets or clear text?

 

The ACM# means that Linux thinks it is a modem (rather than a RAW serial device).  This typically isn't a problem, but can be if the modem state is "awaiting AT commands".  You can lookup an AT command to put in the OpenCmd are to ensure it isn't in a "command mode" (could explain the response to "id" as opposed to sending "id" out the TNC portion).

 

Robert Giuliano

KB8RCO

 

From: "Greg D ko6th.greg@... [aprsisce]"
To: aprsisce@...
Sent: Thursday, June 21, 2018 2:55 PM
Subject: [aprsisce] D74 with APRSIS32 won't transmit

 

 

Hi folks,

Not sure if this is particular to the D74 or APRSIS32... I have the
Kenwood TH-D74 configured for KISS 12, and the Interface for KISS is
USB. USB is configured for COM use. The whole lot is hooked via USB to
my laptop which is running Linux. 'dmesg' on Linux shows the radio
serial port as /dev/ttyACM0, as expected. The device files under
dosdevices show this as COM33.

APRSIS32 is running under Wine, and it properly displays RF traffic
received by the radio. I can also fire up Putty (instead of APRSIS32,
so no com port fighting), and talk to the radio (send "id" and the radio
responds "TH-D74". So I know that the USB connection is working and
that I can both send and receive. The port type is SimplyKISS, COM port
set to COM33. I've even done the system.reg hack for COM33, just in
case, though all the com ports seem to show up when configuring the
device port. The Transmit Enabled box is checked.

I have turned off Enable / Internet access and APRS-IS, to force using
the radio.

But when I hit the Transmit button on APRSIS32, nothing happens. No
transmit. What am I missing?

Greg KO6TH

 

 

 

 

Virus-free. www.avast.com

 

 
Re: D74 with APRSIS32 won't transmit

Greg D
 

Yikes, I haven't used Orbitron in years.  Did it have a real-time Doppler display?

I just found out that I need to take the Netbook to FD after all.  It has Winlink Express loaded (lots of points for Radio Grams), and I can't get that to run on the Dell under either Wine or Win-10.  Claims it needs .NET 3.5 and I have 4.x.  Bad software.  No biscuit.

So, re-thinking the whole laptop scene...

Greg  KO6TH


'Fred Hillhouse' fmhillhouse@... [aprsisce] wrote:

 

Orbitron is still available. TLEs have to downloaded manually since it can’t download from https.

 

There is also a TLE Retriever 3 on the Celestrak site that will get the TLEs automatically.

 

I think the last time I connected a radio to anything, I used HRD.

 

Good luck!

 

Best regards,

Fred N7FMH

 

 

From: aprsisce@... [mailto:aprsisce@...]
Sent: Thursday, June 21, 2018 4:52 PM
To: aprsisce@...
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

 

 

Hi Fred,

I'm tuning it manually; I just wanted gpredict to tell me in realtime what frequency to tune to, but couldn't get it to do that without something to talk to.  On Linux, I'm opening the Rig Control window on gpredict and telling it to tune an RTL-SDR stick via gqrx.  That's enough to keep gpredict happy.  Even works with gqrx running without the RTL-SDR even plugged in (so no waterfall active)...  Gpredict just needed something on the other end of the IP socket to talk to.

Actual control of the rig would be nice, but it's a bit more complicated than it's worth.  The radio is a Yaesu FT-736R and so needs an RS232->TTL adapter in order to run the CAT system.  I have one, but it's built into some interconnect equipment in the shack that is not portable.  But all I need to know is what frequency to tune to, and that works with the "dummy" device.  Don't need to rag-chew here, just get that golden QSO for the points.

Under Windows I would need to have yet another set rig control utilities loaded, and I've given up trying to find and configure them.  No gqrx for Windows...  So, the netbook will stay home, and the Dell coming up the hill to the FD site.  Not a big deal.  And the battery runs longer, too, so I guess that's an advantage.

Greg  KO6TH

'Fred Hillhouse' fmhillhouse@... [aprsisce] wrote:

 

Are you using gpredict to control the radio frequency too?

 

Best regards,

Fred N7FMH

 

From: aprsisce@... [mailto:aprsisce@...]
Sent: Thursday, June 21, 2018 4:05 PM
To: aprsisce@...
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

 

 

Thanks, Rob. 

Not sure what it was, but it's working now.  I was already in Dialout, but added Modem and UUCP to the groups.  Logged out and back in and it's working.  What's odd is that I could write to the serial device just fine from putty (sending the ID command to the D74), and receive just fine with APRSIS32, but not send.  {Shrug}

So, for field day I don't have to switch between Linux and Windows to run the various apps that I need.  I only wish I could get the D74's Bluetooth connection to link up with Linux.  Works fine in Windows with APRSIS32, but then I'm, blocked when I try to run gpredict.  The Doppler tracking isn't working under Windows, and I'm really hoping to snag 100 pts with AO-92 mode L/v.  Perfect pass at 11:09 am local on Saturday.

Greg  KO6TH


Rob Giuliano kb8rco@... [aprsisce] wrote:

 

Although I am not a D74 user, I have worked with various serial interfaces on Windows, Linux, and other operating systems.

 

A couple additional things to consider:

* Could be that the radio is expecting hardware flow control (common with KISS mode TNCs to ensure buffers don't fill)

   This should be a setting in the radio and the Linux system..  Linux uses stty to control the port settings. 

* If the D74 is using Hayes AT commands, you typically go between "command mode" and "use mode" with by sending +++

  I'd be surprised if Kenwood is using the Hayes command set though.

 

Robert Giuliano

KB8RCO

 

 

First thing to check is whether you have write permission for /dev/ttyACMo.

Most serial devices belong to the "dialout" group (/etc/groups).  Have you added your username to that group?

 

If that isn't it, answer these questions:

   What does the "port log" in APRSIS32 say when you transmit?

 

   What happens if you leave PuTTY (under WINE or compiled fro Linux) connected for awhile?

      Does it show KISS packets or clear text?

 

The ACM# means that Linux thinks it is a modem (rather than a RAW serial device).  This typically isn't a problem, but can be if the modem state is "awaiting AT commands".  You can lookup an AT command to put in the OpenCmd are to ensure it isn't in a "command mode" (could explain the response to "id" as opposed to sending "id" out the TNC portion).

 

Robert Giuliano

KB8RCO

 

From: "Greg D ko6th.greg@... [aprsisce]"
To: aprsisce@...
Sent: Thursday, June 21, 2018 2:55 PM
Subject: [aprsisce] D74 with APRSIS32 won't transmit

 

 

Hi folks,

Not sure if this is particular to the D74 or APRSIS32... I have the
Kenwood TH-D74 configured for KISS 12, and the Interface for KISS is
USB. USB is configured for COM use. The whole lot is hooked via USB to
my laptop which is running Linux. 'dmesg' on Linux shows the radio
serial port as /dev/ttyACM0, as expected. The device files under
dosdevices show this as COM33.

APRSIS32 is running under Wine, and it properly displays RF traffic
received by the radio. I can also fire up Putty (instead of APRSIS32,
so no com port fighting), and talk to the radio (send "id" and the radio
responds "TH-D74". So I know that the USB connection is working and
that I can both send and receive. The port type is SimplyKISS, COM port
set to COM33. I've even done the system.reg hack for COM33, just in
case, though all the com ports seem to show up when configuring the
device port. The Transmit Enabled box is checked.

I have turned off Enable / Internet access and APRS-IS, to force using
the radio.

But when I hit the Transmit button on APRSIS32, nothing happens. No
transmit. What am I missing?

Greg KO6TH

 

 

 

 

Virus-free. www.avast.com

 
Re: D74 with APRSIS32 won't transmit

Fred Hillhouse
 

Orbitron is still available. TLEs have to downloaded manually since it can’t download from https.

 

There is also a TLE Retriever 3 on the Celestrak site that will get the TLEs automatically.

 

I think the last time I connected a radio to anything, I used HRD.

 

Good luck!

 

Best regards,

Fred N7FMH

 

 

From: aprsisce@... [mailto:aprsisce@...]
Sent: Thursday, June 21, 2018 4:52 PM
To: aprsisce@...
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

 

 

Hi Fred,

I'm tuning it manually; I just wanted gpredict to tell me in realtime what frequency to tune to, but couldn't get it to do that without something to talk to.  On Linux, I'm opening the Rig Control window on gpredict and telling it to tune an RTL-SDR stick via gqrx.  That's enough to keep gpredict happy.  Even works with gqrx running without the RTL-SDR even plugged in (so no waterfall active)...  Gpredict just needed something on the other end of the IP socket to talk to.

Actual control of the rig would be nice, but it's a bit more complicated than it's worth.  The radio is a Yaesu FT-736R and so needs an RS232->TTL adapter in order to run the CAT system.  I have one, but it's built into some interconnect equipment in the shack that is not portable.  But all I need to know is what frequency to tune to, and that works with the "dummy" device.  Don't need to rag-chew here, just get that golden QSO for the points.

Under Windows I would need to have yet another set rig control utilities loaded, and I've given up trying to find and configure them.  No gqrx for Windows...  So, the netbook will stay home, and the Dell coming up the hill to the FD site.  Not a big deal.  And the battery runs longer, too, so I guess that's an advantage.

Greg  KO6TH

'Fred Hillhouse' fmhillhouse@... [aprsisce] wrote:

 

Are you using gpredict to control the radio frequency too?

 

Best regards,

Fred N7FMH

 

From: aprsisce@... [mailto:aprsisce@...]
Sent: Thursday, June 21, 2018 4:05 PM
To: aprsisce@...
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

 

 

Thanks, Rob. 

Not sure what it was, but it's working now.  I was already in Dialout, but added Modem and UUCP to the groups.  Logged out and back in and it's working.  What's odd is that I could write to the serial device just fine from putty (sending the ID command to the D74), and receive just fine with APRSIS32, but not send.  {Shrug}

So, for field day I don't have to switch between Linux and Windows to run the various apps that I need.  I only wish I could get the D74's Bluetooth connection to link up with Linux.  Works fine in Windows with APRSIS32, but then I'm, blocked when I try to run gpredict.  The Doppler tracking isn't working under Windows, and I'm really hoping to snag 100 pts with AO-92 mode L/v.  Perfect pass at 11:09 am local on Saturday.

Greg  KO6TH


Rob Giuliano kb8rco@... [aprsisce] wrote:

 

Although I am not a D74 user, I have worked with various serial interfaces on Windows, Linux, and other operating systems.

 

A couple additional things to consider:

* Could be that the radio is expecting hardware flow control (common with KISS mode TNCs to ensure buffers don't fill)

   This should be a setting in the radio and the Linux system.  Linux uses stty to control the port settings. 

* If the D74 is using Hayes AT commands, you typically go between "command mode" and "use mode" with by sending +++

  I'd be surprised if Kenwood is using the Hayes command set though.

 

Robert Giuliano

KB8RCO

 

 

First thing to check is whether you have write permission for /dev/ttyACMo.

Most serial devices belong to the "dialout" group (/etc/groups).  Have you added your username to that group?

 

If that isn't it, answer these questions:

   What does the "port log" in APRSIS32 say when you transmit?

 

   What happens if you leave PuTTY (under WINE or compiled fro Linux) connected for awhile?

      Does it show KISS packets or clear text?

 

The ACM# means that Linux thinks it is a modem (rather than a RAW serial device).  This typically isn't a problem, but can be if the modem state is "awaiting AT commands".  You can lookup an AT command to put in the OpenCmd are to ensure it isn't in a "command mode" (could explain the response to "id" as opposed to sending "id" out the TNC portion).

 

Robert Giuliano

KB8RCO

 

From: "Greg D ko6th.greg@... [aprsisce]"
To: aprsisce@...
Sent: Thursday, June 21, 2018 2:55 PM
Subject: [aprsisce] D74 with APRSIS32 won't transmit

 

 

Hi folks,

Not sure if this is particular to the D74 or APRSIS32... I have the
Kenwood TH-D74 configured for KISS 12, and the Interface for KISS is
USB. USB is configured for COM use. The whole lot is hooked via USB to
my laptop which is running Linux. 'dmesg' on Linux shows the radio
serial port as /dev/ttyACM0, as expected. The device files under
dosdevices show this as COM33.

APRSIS32 is running under Wine, and it properly displays RF traffic
received by the radio. I can also fire up Putty (instead of APRSIS32,
so no com port fighting), and talk to the radio (send "id" and the radio
responds "TH-D74". So I know that the USB connection is working and
that I can both send and receive. The port type is SimplyKISS, COM port
set to COM33. I've even done the system.reg hack for COM33, just in
case, though all the com ports seem to show up when configuring the
device port. The Transmit Enabled box is checked.

I have turned off Enable / Internet access and APRS-IS, to force using
the radio.

But when I hit the Transmit button on APRSIS32, nothing happens. No
transmit. What am I missing?

Greg KO6TH

 

 

 

 

Virus-free. www.avast.com

 
Re: D74 with APRSIS32 won't transmit

Greg D
 

Hi Fred,

I'm tuning it manually; I just wanted gpredict to tell me in realtime what frequency to tune to, but couldn't get it to do that without something to talk to.  On Linux, I'm opening the Rig Control window on gpredict and telling it to tune an RTL-SDR stick via gqrx.  That's enough to keep gpredict happy.  Even works with gqrx running without the RTL-SDR even plugged in (so no waterfall active)...  Gpredict just needed something on the other end of the IP socket to talk to.

Actual control of the rig would be nice, but it's a bit more complicated than it's worth.  The radio is a Yaesu FT-736R and so needs an RS232->TTL adapter in order to run the CAT system.  I have one, but it's built into some interconnect equipment in the shack that is not portable.  But all I need to know is what frequency to tune to, and that works with the "dummy" device.  Don't need to rag-chew here, just get that golden QSO for the points.

Under Windows I would need to have yet another set rig control utilities loaded, and I've given up trying to find and configure them.  No gqrx for Windows...  So, the netbook will stay home, and the Dell coming up the hill to the FD site.  Not a big deal.  And the battery runs longer, too, so I guess that's an advantage.

Greg  KO6TH


'Fred Hillhouse' fmhillhouse@... [aprsisce] wrote:

 

Are you using gpredict to control the radio frequency too?

 

Best regards,

Fred N7FMH

 

From: aprsisce@... [mailto:aprsisce@...]
Sent: Thursday, June 21, 2018 4:05 PM
To: aprsisce@...
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

 

 

Thanks, Rob. 

Not sure what it was, but it's working now.  I was already in Dialout, but added Modem and UUCP to the groups.  Logged out and back in and it's working.  What's odd is that I could write to the serial device just fine from putty (sending the ID command to the D74), and receive just fine with APRSIS32, but not send.  {Shrug}

So, for field day I don't have to switch between Linux and Windows to run the various apps that I need.  I only wish I could get the D74's Bluetooth connection to link up with Linux.  Works fine in Windows with APRSIS32, but then I'm, blocked when I try to run gpredict.  The Doppler tracking isn't working under Windows, and I'm really hoping to snag 100 pts with AO-92 mode L/v.  Perfect pass at 11:09 am local on Saturday.

Greg  KO6TH

Rob Giuliano kb8rco@... [aprsisce] wrote:

 

Although I am not a D74 user, I have worked with various serial interfaces on Windows, Linux, and other operating systems.

 

A couple additional things to consider:

* Could be that the radio is expecting hardware flow control (common with KISS mode TNCs to ensure buffers don't fill)

   This should be a setting in the radio and the Linux system.  Linux uses stty to control the port settings. 

* If the D74 is using Hayes AT commands, you typically go between "command mode" and "use mode" with by sending +++

  I'd be surprised if Kenwood is using the Hayes command set though.

 

Robert Giuliano

KB8RCO

 

 

First thing to check is whether you have write permission for /dev/ttyACMo.

Most serial devices belong to the "dialout" group (/etc/groups).  Have you added your username to that group?

 

If that isn't it, answer these questions:

   What does the "port log" in APRSIS32 say when you transmit?

 

   What happens if you leave PuTTY (under WINE or compiled fro Linux) connected for awhile?

      Does it show KISS packets or clear text?

 

The ACM# means that Linux thinks it is a modem (rather than a RAW serial device).  This typically isn't a problem, but can be if the modem state is "awaiting AT commands".  You can lookup an AT command to put in the OpenCmd are to ensure it isn't in a "command mode" (could explain the response to "id" as opposed to sending "id" out the TNC portion).

 

Robert Giuliano

KB8RCO

 

From: "Greg D ko6th.greg@... [aprsisce]"
To: aprsisce@...
Sent: Thursday, June 21, 2018 2:55 PM
Subject: [aprsisce] D74 with APRSIS32 won't transmit

 

 

Hi folks,

Not sure if this is particular to the D74 or APRSIS32... I have the
Kenwood TH-D74 configured for KISS 12, and the Interface for KISS is
USB. USB is configured for COM use. The whole lot is hooked via USB to
my laptop which is running Linux. 'dmesg' on Linux shows the radio
serial port as /dev/ttyACM0, as expected. The device files under
dosdevices show this as COM33.

APRSIS32 is running under Wine, and it properly displays RF traffic
received by the radio. I can also fire up Putty (instead of APRSIS32,
so no com port fighting), and talk to the radio (send "id" and the radio
responds "TH-D74". So I know that the USB connection is working and
that I can both send and receive. The port type is SimplyKISS, COM port
set to COM33. I've even done the system.reg hack for COM33, just in
case, though all the com ports seem to show up when configuring the
device port. The Transmit Enabled box is checked.

I have turned off Enable / Internet access and APRS-IS, to force using
the radio.

But when I hit the Transmit button on APRSIS32, nothing happens. No
transmit. What am I missing?

Greg KO6TH

 

 

 


Virus-free. www.avast.com

Re: D74 with APRSIS32 won't transmit

Greg D
 

Running VBox or VMware might work, but I don't know how it would have proper access to the BT hardware.  Usually these sorts of things depend on the host PC to provide support to the device file level, and that lower level is where the trouble is.  USB is working now, so I'm good.  Getting BT to work that way would be WAY more trouble than it's worth at this point.  But thanks for the suggestion.

Greg  KO6TH

Rob Giuliano kb8rco@yahoo.com [aprsisce] wrote:



I prefer an virtual machine running a very limited install of Windows XP
for such occasions. XP can be stripped down pretty easily to not much more
than the operating system for a small virtualbox drive. That is if you
have an XP compatible Windows app.  Save the reboot time.

Option 2 would be run Windows and use Virtualbox for Linux.


Robert Giuliano
KB8RCO



*From:* "Greg D ko6th.greg@gmail.com [aprsisce]" ( aprsisce@yahoogroups.com
)
*To:* aprsisce@yahoogroups.com
*Sent:* Thursday, June 21, 2018 4:26 PM
*Subject:* Re: [aprsisce] D74 with APRSIS32 won't transmit


I don't think the Bluetooth issue is with APRSIS32 or Wine.  The device
seems to connect as displayed on the Linux side, but I never see the BT
symbol on the D74 light up, and a few seconds later Linux shows the device
as not connected.  So, I think something's not matching up in their
respective BT stacks, causing an error.  The D74's BT stack is known for
being a bit quirky, so this isn't totally unexpected as Linux isn't an
operating system that Kenwood supports.

I tried configuring a BT port for APRSIS32, hoping perhaps the connection
would stay up if there was something to talk to, but that didn't work.

I'll just leave things as they are for now, and revisit this perhaps
later.  The original plan for Field Day was to take the Netbook (running
Win 7), as it's more portable, has its own SIM for Internet connections,
and is less valuable, but the issue with gpredict forced the use of my
full-sized laptop.  It dual-boots with Win 10, but I strongly prefer to
leave it running Linux.

Greg  KO6TH



Rob Giuliano kb8rco@yahoo.com [aprsisce] wrote:



I have found that with APRSIS32 under WINE, you are always better off
linking to COMM ports.
Most Bluetooth devices are listed as /dev/rfcomm# (I think that is how it
gets listed).  I can double check when I get home


from within */home/{username}/.wine/dosdevices*
*ln -s /dev/rfcomm0 com8*


Then connect to Com8 in APRSIS32.


Again, I do not use a D74, but this works with all my Bluetooth devices I
use to connect to the TNCs


Robert Giuliano
KB8RCO



*From:* "Greg D ko6th.greg@gmail.com [aprsisce]" ( aprsisce@yahoogroups.com
)
*To:* aprsisce@yahoogroups.com
*Sent:* Thursday, June 21, 2018 4:05 PM
*Subject:* Re: [aprsisce] D74 with APRSIS32 won't transmit


Thanks, Rob.

Not sure what it was, but it's working now.  I was already in Dialout, but
added Modem and UUCP to the groups.  Logged out and back in and it's
working.  What's odd is that I could write to the serial device just fine
from putty (sending the ID command to the D74), and receive just fine with
APRSIS32, but not send.  {Shrug}

So, for field day I don't have to switch between Linux and Windows to run
the various apps that I need.  I only wish I could get the D74's Bluetooth
connection to link up with Linux.  Works fine in Windows with APRSIS32,
but then I'm, blocked when I try to run gpredict.  The Doppler tracking
isn't working under Windows, and I'm really hoping to snag 100 pts with
AO-92 mode L/v.  Perfect pass at 11:09 am local on Saturday.

Greg  KO6TH



Rob Giuliano kb8rco@yahoo.com [aprsisce] wrote:



Although I am not a D74 user, I have worked with various serial interfaces
on Windows, Linux, and other operating systems.


A couple additional things to consider:
* Could be that the radio is expecting hardware flow control (common with
KISS mode TNCs to ensure buffers don't fill)
This should be a setting in the radio and the Linux system.  Linux uses
stty to control the port settings.
* If the D74 is using Hayes AT commands, you typically go between "command
mode" and "use mode" with by sending *+++*
I'd be surprised if Kenwood is using the Hayes command set though.

Robert Giuliano
KB8RCO





First thing to check is whether you have write permission for */dev/ttyACMo*
.
Most serial devices belong to the "dialout" group (/etc/groups).  Have you
added your username to that group?


If that isn't it, answer these questions:
What does the "port log" in APRSIS32 say when you transmit?


What happens if you leave PuTTY (under WINE or compiled fro Linux)
connected for awhile?
Does it show KISS packets or clear text?

The ACM# means that Linux thinks it is a modem (rather than a RAW serial
device).  This typically isn't a problem, but can be if the modem state is
"awaiting AT commands".  You can lookup an AT command to put in the
OpenCmd are to ensure it isn't in a "command mode" (could explain the
response to "id" as opposed to sending "id" out the TNC portion).


Robert Giuliano
KB8RCO



*From:* "Greg D ko6th.greg@gmail.com [aprsisce]" ( aprsisce@yahoogroups.com
)
*To:* aprsisce@yahoogroups.com
*Sent:* Thursday, June 21, 2018 2:55 PM
*Subject:* [aprsisce] D74 with APRSIS32 won't transmit


Hi folks,

Not sure if this is particular to the D74 or APRSIS32... I have the
Kenwood TH-D74 configured for KISS 12, and the Interface for KISS is
USB. USB is configured for COM use. The whole lot is hooked via USB to
my laptop which is running Linux. 'dmesg' on Linux shows the radio
serial port as /dev/ttyACM0, as expected. The device files under
dosdevices show this as COM33.
Re: D74 with APRSIS32 won't transmit

Rob Giuliano
 

I prefer an virtual machine running a very limited install of Windows XP for such occasions. XP can be stripped down pretty easily to not much more than the operating system for a small virtualbox drive. That is if you have an XP compatible Windows app.  Save the reboot time.
 
Option 2 would be run Windows and use Virtualbox for Linux.

Robert Giuliano
KB8RCO


From: "Greg D ko6th.greg@... [aprsisce]"
To: aprsisce@...
Sent: Thursday, June 21, 2018 4:26 PM
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

 
I don't think the Bluetooth issue is with APRSIS32 or Wine.  The device seems to connect as displayed on the Linux side, but I never see the BT symbol on the D74 light up, and a few seconds later Linux shows the device as not connected.  So, I think something's not matching up in their respective BT stacks, causing an error.  The D74's BT stack is known for being a bit quirky, so this isn't totally unexpected as Linux isn't an operating system that Kenwood supports. 

I tried configuring a BT port for APRSIS32, hoping perhaps the connection would stay up if there was something to talk to, but that didn't work.

I'll just leave things as they are for now, and revisit this perhaps later.  The original plan for Field Day was to take the Netbook (running Win 7), as it's more portable, has its own SIM for Internet connections, and is less valuable, but the issue with gpredict forced the use of my full-sized laptop.  It dual-boots with Win 10, but I strongly prefer to leave it running Linux.

Greg  KO6TH


Rob Giuliano kb8rco@... [aprsisce] wrote:
 
I have found that with APRSIS32 under WINE, you are always better off linking to COMM ports.
Most Bluetooth devices are listed as /dev/rfcomm# (I think that is how it gets listed).  I can double check when I get home

from within /home/{username}/.wine/dosdevices
ln -s /dev/rfcomm0 com8 

Then connect to Com8 in APRSIS32. 

Again, I do not use a D74, but this works with all my Bluetooth devices I use to connect to the TNCs

Robert Giuliano
KB8RCO


From: "Greg D ko6th.greg@... [aprsisce]" <aprsisce@...>
To: aprsisce@...
Sent: Thursday, June 21, 2018 4:05 PM
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

 
Thanks, Rob. 

Not sure what it was, but it's working now.  I was already in Dialout, but added Modem and UUCP to the groups.  Logged out and back in and it's working.  What's odd is that I could write to the serial device just fine from putty (sending the ID command to the D74), and receive just fine with APRSIS32, but not send.  {Shrug}

So, for field day I don't have to switch between Linux and Windows to run the various apps that I need.  I only wish I could get the D74's Bluetooth connection to link up with Linux.  Works fine in Windows with APRSIS32, but then I'm, blocked when I try to run gpredict.  The Doppler tracking isn't working under Windows, and I'm really hoping to snag 100 pts with AO-92 mode L/v.  Perfect pass at 11:09 am local on Saturday.

Greg  KO6TH


Rob Giuliano kb8rco@... [aprsisce] wrote:
 
Although I am not a D74 user, I have worked with various serial interfaces on Windows, Linux, and other operating systems.

A couple additional things to consider:
* Could be that the radio is expecting hardware flow control (common with KISS mode TNCs to ensure buffers don't fill)
   This should be a setting in the radio and the Linux system.  Linux uses stty to control the port settings. 
* If the D74 is using Hayes AT commands, you typically go between "command mode" and "use mode" with by sending +++
  I'd be surprised if Kenwood is using the Hayes command set though.
 
Robert Giuliano
KB8RCO



First thing to check is whether you have write permission for /dev/ttyACMo.
Most serial devices belong to the "dialout" group (/etc/groups).  Have you added your username to that group?

If that isn't it, answer these questions:
   What does the "port log" in APRSIS32 say when you transmit?

   What happens if you leave PuTTY (under WINE or compiled fro Linux) connected for awhile?
      Does it show KISS packets or clear text?
 
The ACM# means that Linux thinks it is a modem (rather than a RAW serial device).  This typically isn't a problem, but can be if the modem state is "awaiting AT commands".  You can lookup an AT command to put in the OpenCmd are to ensure it isn't in a "command mode" (could explain the response to "id" as opposed to sending "id" out the TNC portion).

Robert Giuliano
KB8RCO


From: "Greg D ko6th.greg@... [aprsisce]"
To: aprsisce@...
Sent: Thursday, June 21, 2018 2:55 PM
Subject: [aprsisce] D74 with APRSIS32 won't transmit

 
Hi folks,

Not sure if this is particular to the D74 or APRSIS32... I have the
Kenwood TH-D74 configured for KISS 12, and the Interface for KISS is
USB. USB is configured for COM use. The whole lot is hooked via USB to
my laptop which is running Linux. 'dmesg' on Linux shows the radio
serial port as /dev/ttyACM0, as expected. The device files under
dosdevices show this as COM33.

APRSIS32 is running under Wine, and it properly displays RF traffic
received by the radio. I can also fire up Putty (instead of APRSIS32,
so no com port fighting), and talk to the radio (send "id" and the radio
responds "TH-D74". So I know that the USB connection is working and
that I can both send and receive. The port type is SimplyKISS, COM port
set to COM33. I've even done the system.reg hack for COM33, just in
case, though all the com ports seem to show up when configuring the
device port. The Transmit Enabled box is checked.

I have turned off Enable / Internet access and APRS-IS, to force using
the radio.

But when I hit the Transmit button on APRSIS32, nothing happens. No
transmit. What am I missing?

Greg KO6TH
Re: D74 with APRSIS32 won't transmit

Greg D
 

I don't think the Bluetooth issue is with APRSIS32 or Wine.  The device seems to connect as displayed on the Linux side, but I never see the BT symbol on the D74 light up, and a few seconds later Linux shows the device as not connected.  So, I think something's not matching up in their respective BT stacks, causing an error.  The D74's BT stack is known for being a bit quirky, so this isn't totally unexpected as Linux isn't an operating system that Kenwood supports. 

I tried configuring a BT port for APRSIS32, hoping perhaps the connection would stay up if there was something to talk to, but that didn't work.

I'll just leave things as they are for now, and revisit this perhaps later.  The original plan for Field Day was to take the Netbook (running Win 7), as it's more portable, has its own SIM for Internet connections, and is less valuable, but the issue with gpredict forced the use of my full-sized laptop.  It dual-boots with Win 10, but I strongly prefer to leave it running Linux.

Greg  KO6TH


Rob Giuliano kb8rco@... [aprsisce] wrote:

 
I have found that with APRSIS32 under WINE, you are always better off linking to COMM ports.
Most Bluetooth devices are listed as /dev/rfcomm# (I think that is how it gets listed).  I can double check when I get home

from within /home/{username}/.wine/dosdevices
ln -s /dev/rfcomm0 com8 

Then connect to Com8 in APRSIS32. 

Again, I do not use a D74, but this works with all my Bluetooth devices I use to connect to the TNCs

Robert Giuliano
KB8RCO


From: "Greg D ko6th.greg@... [aprsisce]"
To: aprsisce@...
Sent: Thursday, June 21, 2018 4:05 PM
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

 
Thanks, Rob. 

Not sure what it was, but it's working now.  I was already in Dialout, but added Modem and UUCP to the groups.  Logged out and back in and it's working.  What's odd is that I could write to the serial device just fine from putty (sending the ID command to the D74), and receive just fine with APRSIS32, but not send.  {Shrug}

So, for field day I don't have to switch between Linux and Windows to run the various apps that I need.  I only wish I could get the D74's Bluetooth connection to link up with Linux.  Works fine in Windows with APRSIS32, but then I'm, blocked when I try to run gpredict.  The Doppler tracking isn't working under Windows, and I'm really hoping to snag 100 pts with AO-92 mode L/v.  Perfect pass at 11:09 am local on Saturday.

Greg  KO6TH


Rob Giuliano kb8rco@... [aprsisce] wrote:
 
Although I am not a D74 user, I have worked with various serial interfaces on Windows, Linux, and other operating systems.

A couple additional things to consider:
* Could be that the radio is expecting hardware flow control (common with KISS mode TNCs to ensure buffers don't fill)
   This should be a setting in the radio and the Linux system.  Linux uses stty to control the port settings. 
* If the D74 is using Hayes AT commands, you typically go between "command mode" and "use mode" with by sending +++
  I'd be surprised if Kenwood is using the Hayes command set though.
 
Robert Giuliano
KB8RCO



First thing to check is whether you have write permission for /dev/ttyACMo.
Most serial devices belong to the "dialout" group (/etc/groups).  Have you added your username to that group?

If that isn't it, answer these questions:
   What does the "port log" in APRSIS32 say when you transmit?

   What happens if you leave PuTTY (under WINE or compiled fro Linux) connected for awhile?
      Does it show KISS packets or clear text?
 
The ACM# means that Linux thinks it is a modem (rather than a RAW serial device).  This typically isn't a problem, but can be if the modem state is "awaiting AT commands".  You can lookup an AT command to put in the OpenCmd are to ensure it isn't in a "command mode" (could explain the response to "id" as opposed to sending "id" out the TNC portion).

Robert Giuliano
KB8RCO


From: "Greg D ko6th.greg@... [aprsisce]"
To: aprsisce@...
Sent: Thursday, June 21, 2018 2:55 PM
Subject: [aprsisce] D74 with APRSIS32 won't transmit

 
Hi folks,

Not sure if this is particular to the D74 or APRSIS32... I have the
Kenwood TH-D74 configured for KISS 12, and the Interface for KISS is
USB. USB is configured for COM use. The whole lot is hooked via USB to
my laptop which is running Linux. 'dmesg' on Linux shows the radio
serial port as /dev/ttyACM0, as expected. The device files under
dosdevices show this as COM33.

APRSIS32 is running under Wine, and it properly displays RF traffic
received by the radio. I can also fire up Putty (instead of APRSIS32,
so no com port fighting), and talk to the radio (send "id" and the radio
responds "TH-D74". So I know that the USB connection is working and
that I can both send and receive. The port type is SimplyKISS, COM port
set to COM33. I've even done the system.reg hack for COM33, just in
case, though all the com ports seem to show up when configuring the
device port. The Transmit Enabled box is checked.

I have turned off Enable / Internet access and APRS-IS, to force using
the radio.

But when I hit the Transmit button on APRSIS32, nothing happens. No
transmit. What am I missing?

Greg KO6TH
Re: D74 with APRSIS32 won't transmit

Fred Hillhouse
 

Are you using gpredict to control the radio frequency too?

 

Best regards,

Fred N7FMH

 

From: aprsisce@... [mailto:aprsisce@...]
Sent: Thursday, June 21, 2018 4:05 PM
To: aprsisce@...
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

 

 

Thanks, Rob. 

Not sure what it was, but it's working now.  I was already in Dialout, but added Modem and UUCP to the groups.  Logged out and back in and it's working.  What's odd is that I could write to the serial device just fine from putty (sending the ID command to the D74), and receive just fine with APRSIS32, but not send.  {Shrug}

So, for field day I don't have to switch between Linux and Windows to run the various apps that I need.  I only wish I could get the D74's Bluetooth connection to link up with Linux.  Works fine in Windows with APRSIS32, but then I'm, blocked when I try to run gpredict.  The Doppler tracking isn't working under Windows, and I'm really hoping to snag 100 pts with AO-92 mode L/v.  Perfect pass at 11:09 am local on Saturday.

Greg  KO6TH

Rob Giuliano kb8rco@... [aprsisce] wrote:

 

Although I am not a D74 user, I have worked with various serial interfaces on Windows, Linux, and other operating systems.

 

A couple additional things to consider:

* Could be that the radio is expecting hardware flow control (common with KISS mode TNCs to ensure buffers don't fill)

   This should be a setting in the radio and the Linux system.  Linux uses stty to control the port settings. 

* If the D74 is using Hayes AT commands, you typically go between "command mode" and "use mode" with by sending +++

  I'd be surprised if Kenwood is using the Hayes command set though.

 

Robert Giuliano

KB8RCO

 

 

First thing to check is whether you have write permission for /dev/ttyACMo.

Most serial devices belong to the "dialout" group (/etc/groups).  Have you added your username to that group?

 

If that isn't it, answer these questions:

   What does the "port log" in APRSIS32 say when you transmit?

 

   What happens if you leave PuTTY (under WINE or compiled fro Linux) connected for awhile?

      Does it show KISS packets or clear text?

 

The ACM# means that Linux thinks it is a modem (rather than a RAW serial device).  This typically isn't a problem, but can be if the modem state is "awaiting AT commands".  You can lookup an AT command to put in the OpenCmd are to ensure it isn't in a "command mode" (could explain the response to "id" as opposed to sending "id" out the TNC portion).

 

Robert Giuliano

KB8RCO

 

From: "Greg D ko6th.greg@... [aprsisce]"
To: aprsisce@...
Sent: Thursday, June 21, 2018 2:55 PM
Subject: [aprsisce] D74 with APRSIS32 won't transmit

 

 

Hi folks,

Not sure if this is particular to the D74 or APRSIS32... I have the
Kenwood TH-D74 configured for KISS 12, and the Interface for KISS is
USB. USB is configured for COM use. The whole lot is hooked via USB to
my laptop which is running Linux. 'dmesg' on Linux shows the radio
serial port as /dev/ttyACM0, as expected. The device files under
dosdevices show this as COM33.

APRSIS32 is running under Wine, and it properly displays RF traffic
received by the radio. I can also fire up Putty (instead of APRSIS32,
so no com port fighting), and talk to the radio (send "id" and the radio
responds "TH-D74". So I know that the USB connection is working and
that I can both send and receive. The port type is SimplyKISS, COM port
set to COM33. I've even done the system.reg hack for COM33, just in
case, though all the com ports seem to show up when configuring the
device port. The Transmit Enabled box is checked.

I have turned off Enable / Internet access and APRS-IS, to force using
the radio.

But when I hit the Transmit button on APRSIS32, nothing happens. No
transmit. What am I missing?

Greg KO6TH

 

 

 


Virus-free. www.avast.com

Re: D74 with APRSIS32 won't transmit

Rob Giuliano
 

I have found that with APRSIS32 under WINE, you are always better off linking to COMM ports.
Most Bluetooth devices are listed as /dev/rfcomm# (I think that is how it gets listed).  I can double check when I get home

from within /home/{username}/.wine/dosdevices
ln -s /dev/rfcomm0 com8 

Then connect to Com8 in APRSIS32. 

Again, I do not use a D74, but this works with all my Bluetooth devices I use to connect to the TNCs

Robert Giuliano
KB8RCO


From: "Greg D ko6th.greg@... [aprsisce]"
To: aprsisce@...
Sent: Thursday, June 21, 2018 4:05 PM
Subject: Re: [aprsisce] D74 with APRSIS32 won't transmit

 
Thanks, Rob. 

Not sure what it was, but it's working now.  I was already in Dialout, but added Modem and UUCP to the groups.  Logged out and back in and it's working.  What's odd is that I could write to the serial device just fine from putty (sending the ID command to the D74), and receive just fine with APRSIS32, but not send.  {Shrug}

So, for field day I don't have to switch between Linux and Windows to run the various apps that I need.  I only wish I could get the D74's Bluetooth connection to link up with Linux.  Works fine in Windows with APRSIS32, but then I'm, blocked when I try to run gpredict.  The Doppler tracking isn't working under Windows, and I'm really hoping to snag 100 pts with AO-92 mode L/v.  Perfect pass at 11:09 am local on Saturday.

Greg  KO6TH


Rob Giuliano kb8rco@... [aprsisce] wrote:
 
Although I am not a D74 user, I have worked with various serial interfaces on Windows, Linux, and other operating systems.

A couple additional things to consider:
* Could be that the radio is expecting hardware flow control (common with KISS mode TNCs to ensure buffers don't fill)
   This should be a setting in the radio and the Linux system.  Linux uses stty to control the port settings. 
* If the D74 is using Hayes AT commands, you typically go between "command mode" and "use mode" with by sending +++
  I'd be surprised if Kenwood is using the Hayes command set though.
 
Robert Giuliano
KB8RCO



First thing to check is whether you have write permission for /dev/ttyACMo.
Most serial devices belong to the "dialout" group (/etc/groups).  Have you added your username to that group?

If that isn't it, answer these questions:
   What does the "port log" in APRSIS32 say when you transmit?

   What happens if you leave PuTTY (under WINE or compiled fro Linux) connected for awhile?
      Does it show KISS packets or clear text?
 
The ACM# means that Linux thinks it is a modem (rather than a RAW serial device).  This typically isn't a problem, but can be if the modem state is "awaiting AT commands".  You can lookup an AT command to put in the OpenCmd are to ensure it isn't in a "command mode" (could explain the response to "id" as opposed to sending "id" out the TNC portion).

Robert Giuliano
KB8RCO


From: "Greg D ko6th.greg@... [aprsisce]"
To: aprsisce@...
Sent: Thursday, June 21, 2018 2:55 PM
Subject: [aprsisce] D74 with APRSIS32 won't transmit

 
Hi folks,

Not sure if this is particular to the D74 or APRSIS32... I have the
Kenwood TH-D74 configured for KISS 12, and the Interface for KISS is
USB. USB is configured for COM use. The whole lot is hooked via USB to
my laptop which is running Linux. 'dmesg' on Linux shows the radio
serial port as /dev/ttyACM0, as expected. The device files under
dosdevices show this as COM33.

APRSIS32 is running under Wine, and it properly displays RF traffic
received by the radio. I can also fire up Putty (instead of APRSIS32,
so no com port fighting), and talk to the radio (send "id" and the radio
responds "TH-D74". So I know that the USB connection is working and
that I can both send and receive. The port type is SimplyKISS, COM port
set to COM33. I've even done the system.reg hack for COM33, just in
case, though all the com ports seem to show up when configuring the
device port. The Transmit Enabled box is checked.

I have turned off Enable / Internet access and APRS-IS, to force using
the radio.

But when I hit the Transmit button on APRSIS32, nothing happens. No
transmit. What am I missing?

Greg KO6TH
Re: D74 with APRSIS32 won't transmit

Greg D
 

Thanks, Rob. 

Not sure what it was, but it's working now.  I was already in Dialout, but added Modem and UUCP to the groups.  Logged out and back in and it's working.  What's odd is that I could write to the serial device just fine from putty (sending the ID command to the D74), and receive just fine with APRSIS32, but not send.  {Shrug}

So, for field day I don't have to switch between Linux and Windows to run the various apps that I need.  I only wish I could get the D74's Bluetooth connection to link up with Linux.  Works fine in Windows with APRSIS32, but then I'm, blocked when I try to run gpredict.  The Doppler tracking isn't working under Windows, and I'm really hoping to snag 100 pts with AO-92 mode L/v.  Perfect pass at 11:09 am local on Saturday.

Greg  KO6TH


Rob Giuliano kb8rco@... [aprsisce] wrote:

 
Although I am not a D74 user, I have worked with various serial interfaces on Windows, Linux, and other operating systems.

A couple additional things to consider:
* Could be that the radio is expecting hardware flow control (common with KISS mode TNCs to ensure buffers don't fill)
   This should be a setting in the radio and the Linux system.  Linux uses stty to control the port settings. 
* If the D74 is using Hayes AT commands, you typically go between "command mode" and "use mode" with by sending +++
  I'd be surprised if Kenwood is using the Hayes command set though.
 
Robert Giuliano
KB8RCO



First thing to check is whether you have write permission for /dev/ttyACMo.
Most serial devices belong to the "dialout" group (/etc/groups).  Have you added your username to that group?

If that isn't it, answer these questions:
   What does the "port log" in APRSIS32 say when you transmit?

   What happens if you leave PuTTY (under WINE or compiled fro Linux) connected for awhile?
      Does it show KISS packets or clear text?
 
The ACM# means that Linux thinks it is a modem (rather than a RAW serial device).  This typically isn't a problem, but can be if the modem state is "awaiting AT commands".  You can lookup an AT command to put in the OpenCmd are to ensure it isn't in a "command mode" (could explain the response to "id" as opposed to sending "id" out the TNC portion).

Robert Giuliano
KB8RCO


From: "Greg D ko6th.greg@... [aprsisce]"
To: aprsisce@...
Sent: Thursday, June 21, 2018 2:55 PM
Subject: [aprsisce] D74 with APRSIS32 won't transmit

 
Hi folks,

Not sure if this is particular to the D74 or APRSIS32... I have the
Kenwood TH-D74 configured for KISS 12, and the Interface for KISS is
USB. USB is configured for COM use. The whole lot is hooked via USB to
my laptop which is running Linux. 'dmesg' on Linux shows the radio
serial port as /dev/ttyACM0, as expected. The device files under
dosdevices show this as COM33.

APRSIS32 is running under Wine, and it properly displays RF traffic
received by the radio. I can also fire up Putty (instead of APRSIS32,
so no com port fighting), and talk to the radio (send "id" and the radio
responds "TH-D74". So I know that the USB connection is working and
that I can both send and receive. The port type is SimplyKISS, COM port
set to COM33. I've even done the system.reg hack for COM33, just in
case, though all the com ports seem to show up when configuring the
device port. The Transmit Enabled box is checked.

I have turned off Enable / Internet access and APRS-IS, to force using
the radio.

But when I hit the Transmit button on APRSIS32, nothing happens. No
transmit. What am I missing?

Greg KO6TH
Re: D74 with APRSIS32 won't transmit

Rob Giuliano
 

Although I am not a D74 user, I have worked with various serial interfaces on Windows, Linux, and other operating systems.

A couple additional things to consider:
* Could be that the radio is expecting hardware flow control (common with KISS mode TNCs to ensure buffers don't fill)
   This should be a setting in the radio and the Linux system.  Linux uses stty to control the port settings. 
* If the D74 is using Hayes AT commands, you typically go between "command mode" and "use mode" with by sending +++
  I'd be surprised if Kenwood is using the Hayes command set though.
 
Robert Giuliano
KB8RCO



First thing to check is whether you have write permission for /dev/ttyACMo.
Most serial devices belong to the "dialout" group (/etc/groups).  Have you added your username to that group?

If that isn't it, answer these questions:
   What does the "port log" in APRSIS32 say when you transmit?

   What happens if you leave PuTTY (under WINE or compiled fro Linux) connected for awhile?
      Does it show KISS packets or clear text?
 
The ACM# means that Linux thinks it is a modem (rather than a RAW serial device).  This typically isn't a problem, but can be if the modem state is "awaiting AT commands".  You can lookup an AT command to put in the OpenCmd are to ensure it isn't in a "command mode" (could explain the response to "id" as opposed to sending "id" out the TNC portion).

Robert Giuliano
KB8RCO


From: "Greg D ko6th.greg@... [aprsisce]"
To: aprsisce@...
Sent: Thursday, June 21, 2018 2:55 PM
Subject: [aprsisce] D74 with APRSIS32 won't transmit

 
Hi folks,

Not sure if this is particular to the D74 or APRSIS32... I have the
Kenwood TH-D74 configured for KISS 12, and the Interface for KISS is
USB. USB is configured for COM use. The whole lot is hooked via USB to
my laptop which is running Linux. 'dmesg' on Linux shows the radio
serial port as /dev/ttyACM0, as expected. The device files under
dosdevices show this as COM33.

APRSIS32 is running under Wine, and it properly displays RF traffic
received by the radio. I can also fire up Putty (instead of APRSIS32,
so no com port fighting), and talk to the radio (send "id" and the radio
responds "TH-D74". So I know that the USB connection is working and
that I can both send and receive. The port type is SimplyKISS, COM port
set to COM33. I've even done the system.reg hack for COM33, just in
case, though all the com ports seem to show up when configuring the
device port. The Transmit Enabled box is checked.

I have turned off Enable / Internet access and APRS-IS, to force using
the radio.

But when I hit the Transmit button on APRSIS32, nothing happens. No
transmit. What am I missing?

Greg KO6TH
3681 - 3700 of 36244