Date   

Beacon TX OK - no Message TX

w6dtw@...
 

Hi folks,


Experimenting with APRIS32 since late last night - very interesting software.  Having a bit of trouble with messages, in that they never trigger transmit.  The regular beaconing is fine, no issues.  Ran through the wiki section on messaging - I set RF ONLY and unset ACK, also confirmed the configure items for Port, etc.  I'm probably missing something really obvious - any suggestions?


...dtw



Re: Kenwood TM D710A to Windows 10 tablet in Vehicle

Dave Wickert
 

Ref: Charging the tablet

 

I do not know about the Toshiba Encore, but many low-end Windows tablets that are powered off the micro-USB port do not support OTG charging at the same time as using the micro-USB as an output USB.  Providing power onto the OTG micro-USB plug will disable the output USB capability. I have a NuVision TM800W560L tablet that has this “feature”. This is a well-documented limitation that applies to many Windows tablets. If anyone has a counter-example, i.e. a Windows tablet that support concurrent OTG power charging at the same time as using the micro-USB as an output USB, I’d love to hear it. I’ve searched but have not found one yet.

 

Ref: BT

Because of these power issues with the NuVision TM800W560L, my workaround is to use BT as a data interface instead of USB cable. In my case, I use a CT-165 RS232 data cable from my FTM-400XDR, to a serial Bluetooth converter to interface with my NuVision tablet. I dedicate the existing micro-USB on the tablet to keep the battery fully charged. The serial BT converter I use is:

http://www.usconverters.com/serial-bluetooth-adapter

Once the BT converter pairs with the tablet, you will see a mapped virtual COM port (Windows Device Manager) pops up, e.g. COM9 for example, that pops up. Then I configure APRSISCE to use that COM port. Here is a YouTube post that I found on something similar: https://www.youtube.com/watch?v=Q7oQYwurG8w  that uses this BT converter (to slightly different radio and computer, but it is very similar). Since then I’ve noticed that they have come out with http://www.usconverters.com/blutronium that appears to be an updated version with more configuration options.

Hope this helps.

 

73.

 

_-_-_ Dave, AE7TD

 

 

From: aprsisce@... [mailto:aprsisce@...]
Sent: Thursday, December 21, 2017 10:11 AM
To: aprsisce@...
Subject: Re: [aprsisce] Re: Kenwood TM D710A to Windows 10 tablet in Vehicle

 

 

Not sure if this will help, but have your tried:

 

$ 4.95

USB Mini Hub with Power Switch - OTG Micro-USB

By Adafruit Industries

Do you ever find yourself saying, "Gee whiz I wish I could plug in 4 more USB devices to my tablet, or micr...

 

 

This provides multiple USB ports and a port for power.

It doesn't come with a plug, but I have found Adafruit to be most helpful when asked.

They can properly point you to what will work.

 

Robert Giuliano

KB8RCO

 


From: "a_mascola@... [aprsisce]" <aprsisce@...>
To: aprsisce@...
Sent: Thursday, December 21, 2017 12:14 PM
Subject: [aprsisce] Re: Kenwood TM D710A to Windows 10 tablet in Vehicle

 

 

Hi All, thanks for the suggestions.   have acquired the Toshiba Encore WT8A32 and am successfully running APRSIS32 with my Kenwood TM-D710A.  As previously I am using the K6VHF GPS receiver and have the tablet connected to the Kenwood control head via the RT systems serial to USB cable.  I am using a USB OTG to micro USB adapter I got from Microcenter.  Not all of the OTG cables have worked for some reason unfortunately and I have had to try a few.  

 

I had some difficulty in configuring the APRSIS32 to get it to work as I was following the G4ILO setup video as suggested by the wiki.  It suggests setting up both an NMEA port for the GPS and also a 2nd port for the D710.  It took awhile but discovered that this does not work.  You have to pass the GPS data through the D710 port and not set up a 2nd NMEA port as you can't use the same com port for two different purposes.  This took a little while to figure out but I am now configured and everything is running well

 

The most significant problem I am facing now is to power the tablet.  Running on battery gives me only a few hours.  I need it to run continuously over many days.  I see two options - USB OTG/power Y cable or go bluetooth for data and have the tablet plugged in via the micro USB.

 

1. Via cable:  finding a Y connector that supports both USB OTG via the micro USB and powering the tablet has been challenging.  I have tried the Y cable shown here:

 

 

but it does not seem to work for some reason on my tablet.  I am running Windows 10.  

 

I have ordered the following cable from China after corresponding with the person who has successfully done this here:

 

 

It won't arrive for about a month unfortunately.  

 

I have also looked at this option from Toshiba but it is no longer in production:

 

 

 

This option from Lavalink is another option:

 

 

The thing that is a concern with the cable option is that I notice with the USB OTG cable that I am currently using to pass data only, that rad vibration tends to break the connection and I get a TNC error every time this happens and have to restart everything.  Not optimal for off road use.



2. Via Blue tooth.

I am now looking at serial to Bluetooth options.  Any plug and play suggestions that have been used successfully that users would highly recommend?   

 

 


Re: Kenwood TM D710A to Windows 10 tablet in Vehicle

Rob Giuliano
 

I know it will power a Raspberry Pi when connected to an external power supply.
The ON/OFF switch was designed to cycle power for a Pi, so it does provide power on the plug.
 
Robert Giuliano
KB8RCO



From: "a_mascola@... [aprsisce]"
To: aprsisce@...
Sent: Thursday, December 21, 2017 2:10 PM
Subject: [aprsisce] Re: Kenwood TM D710A to Windows 10 tablet in Vehicle

 
I will contact them.  I am wondering if that hub will charge the tablet via the microUSB port if connected to external power or only power the USB A connections...



Re: Kenwood TM D710A to Windows 10 tablet in Vehicle

Anthony Mascola
 

I will contact them.  I am wondering if that hub will charge the tablet via the microUSB port if connected to external power or only power the USB A connections...


Re: Kenwood TM D710A to Windows 10 tablet in Vehicle

Rob Giuliano
 

Not sure if this will help, but have your tried:



This provides multiple USB ports and a port for power.
It doesn't come with a plug, but I have found Adafruit to be most helpful when asked.
They can properly point you to what will work.
 
Robert Giuliano
KB8RCO



From: "a_mascola@... [aprsisce]" To: aprsisce@...
Sent: Thursday, December 21, 2017 12:14 PM
Subject: [aprsisce] Re: Kenwood TM D710A to Windows 10 tablet in Vehicle

 
Hi All, thanks for the suggestions.   have acquired the Toshiba Encore WT8A32 and am successfully running APRSIS32 with my Kenwood TM-D710A.  As previously I am using the K6VHF GPS receiver and have the tablet connected to the Kenwood control head via the RT systems serial to USB cable.  I am using a USB OTG to micro USB adapter I got from Microcenter.  Not all of the OTG cables have worked for some reason unfortunately and I have had to try a few.  

I had some difficulty in configuring the APRSIS32 to get it to work as I was following the G4ILO setup video as suggested by the wiki.  It suggests setting up both an NMEA port for the GPS and also a 2nd port for the D710.  It took awhile but discovered that this does not work.  You have to pass the GPS data through the D710 port and not set up a 2nd NMEA port as you can't use the same com port for two different purposes.  This took a little while to figure out but I am now configured and everything is running well

The most significant problem I am facing now is to power the tablet.  Running on battery gives me only a few hours.  I need it to run continuously over many days.  I see two options - USB OTG/power Y cable or go bluetooth for data and have the tablet plugged in via the micro USB.

1. Via cable:  finding a Y connector that supports both USB OTG via the micro USB and powering the tablet has been challenging.  I have tried the Y cable shown here:


but it does not seem to work for some reason on my tablet.  I am running Windows 10.  

I have ordered the following cable from China after corresponding with the person who has successfully done this here:


It won't arrive for about a month unfortunately.  

I have also looked at this option from Toshiba but it is no longer in production:



This option from Lavalink is another option:


The thing that is a concern with the cable option is that I notice with the USB OTG cable that I am currently using to pass data only, that rad vibration tends to break the connection and I get a TNC error every time this happens and have to restart everything.  Not optimal for off road use.

2. Via Blue tooth.
I am now looking at serial to Bluetooth options.  Any plug and play suggestions that have been used successfully that users would highly recommend?   




Re: Kenwood TM D710A to Windows 10 tablet in Vehicle

Anthony Mascola
 

Hi All, thanks for the suggestions.   have acquired the Toshiba Encore WT8A32 and am successfully running APRSIS32 with my Kenwood TM-D710A.  As previously I am using the K6VHF GPS receiver and have the tablet connected to the Kenwood control head via the RT systems serial to USB cable.  I am using a USB OTG to micro USB adapter I got from Microcenter.  Not all of the OTG cables have worked for some reason unfortunately and I have had to try a few.  

I had some difficulty in configuring the APRSIS32 to get it to work as I was following the G4ILO setup video as suggested by the wiki.  It suggests setting up both an NMEA port for the GPS and also a 2nd port for the D710.  It took awhile but discovered that this does not work.  You have to pass the GPS data through the D710 port and not set up a 2nd NMEA port as you can't use the same com port for two different purposes.  This took a little while to figure out but I am now configured and everything is running well

The most significant problem I am facing now is to power the tablet.  Running on battery gives me only a few hours.  I need it to run continuously over many days.  I see two options - USB OTG/power Y cable or go bluetooth for data and have the tablet plugged in via the micro USB.

1. Via cable:  finding a Y connector that supports both USB OTG via the micro USB and powering the tablet has been challenging.  I have tried the Y cable shown here:


but it does not seem to work for some reason on my tablet.  I am running Windows 10.  

I have ordered the following cable from China after corresponding with the person who has successfully done this here:


It won't arrive for about a month unfortunately.  

I have also looked at this option from Toshiba but it is no longer in production:



This option from Lavalink is another option:


The thing that is a concern with the cable option is that I notice with the USB OTG cable that I am currently using to pass data only, that rad vibration tends to break the connection and I get a TNC error every time this happens and have to restart everything.  Not optimal for off road use.

2. Via Blue tooth.
I am now looking at serial to Bluetooth options.  Any plug and play suggestions that have been used successfully that users would highly recommend?   


Re: APWW10

Michael Wright
 

From: "'Fred Hillhouse

This is the TOCALL for APRSIS32.
http://aprs.org/aprs11/tocalls.txt
I've been looking for a list just like this. thanks for posting.

Mike K6MFW


Re: Yaesu FTM-400XDR Surface 3 Win 10 Config Help?

Greg Depew
 

The 400 is just like the 350 in that the internal tnc is not accessible.  However using an external tnc is possible thru the data port. I personally use UZ7HO soundmodem and signallink for my home and satellite gates. If I had the the 6 to 12 pin adapter for the radio it would be very easy to go mobile with it as well.



Greg KB3KBR Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: "Rob Giuliano kb8rco@... [aprsisce]"
Date: 12/11/17 16:09 (GMT-05:00)
To: aprsisce@...
Subject: Re: [aprsisce] Yaesu FTM-400XDR Surface 3 Win 10 Config Help?

 

Are you sure the TX was working with the FTM-400XDR?

You should be able to configure the FTM-400XDR to send the data to an attached computer, but the Yaesu radios are not "PC friendly" when it comes to APRS.

I find this particular manual even more confusing on the topic than previous Yaesu APRS radios.
My "best guess" would be the following:
Page 170 "Data" section
1 COM PORT SETTING
  SPEED: 9600
  OUPUT: PACKET       (if non-functional, try WAYPOINT)
  WP FORMAT: MEAN9   (default - although that is GPS output, not PACKET)
  WP Filter: ALL
2 DATA BAND SELECT: {Your desired settings for frequency in use)
3 DATA SPEED (Assumed on air data rate) 
   APRS: 1200
   DATA: 1200
Page 171
4 DATA SQUELCH: (your desired settings)
  APRS (1 -4 skipped)
5 APRS MODEM: ON

Scrolling down to 196, 197, and beyond provides some additional information. 
To me, it appears setting output to DATA will cause the internal TNC to turn off and the audio outputs of the Data Jack to be enabled (for an external TNC).

Robert Giuliano
KB8RCO



From: "bjessee@... [aprsisce]"
To: aprsisce@...
Sent: Monday, December 11, 2017 8:43 AM
Subject: [aprsisce] Yaesu FTM-400XDR Surface 3 Win 10 Config Help?

 
I had been using my Surface 3 WIn10 and Yaesu FTM-400XDR successfully with APRSIS32 as a base until the Surface 3 died. I replaced it and just cannot get RF RX/TX between the radio and PC/APRCIS32. I have a similar setup in my mobile car (Dell Venue Win10 tablet running APRSIS32 on hotspot) and have taken pics of each setup screen and confirmed match on my base. My base radio does RX/TX OK but I see no RF in APRSIS32. None listed under View:RF but the radio lists RX in the internal log - I can see a local site UNCAN received that doesn't appear on APRSIS32.Some checks:

1. Upper left on APRSIS32 alternates FTM400XDR OK and APRS IS OK,
2. Device Manger shows connection on COM3 9600 8/n/1 which I have matched under Configure:Ports:FTM400XDR:Device
3. Radio Data COM Port Speed set to 9600 Packet
4. Radio Data Data Speed set APRS 1200 Data 9600; Configure:Ports:FTM400XDR RF Baud set to 1200

I haven't had my mobile or base running for a while so anything logged today is my base.

Bret/N4SRN



Re: Station Display Time

Lynn Deffenbaugh
 

One special note is that a time spec of 0 means that the station never times out.  This is the default for "friends" which includes everyone that is buddy filtered as well as those that you are following in some window (which are added to the buddy filter behind the scenes).

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32



On 12/11/2017 4:49 PM, graham.chaloner@... [aprsisce] wrote:
Rob, many thanks for the information,  I have moved to the development version and edited the XML file which has enabled what I was trying to do.

Graham
M0GWC



Re: Station Display Time

graham.chaloner@...
 

Rob, many thanks for the information,  I have moved to the development version and edited the XML file which has enabled what I was trying to do.

Graham
M0GWC


Re: Yaesu FTM-400XDR Surface 3 Win 10 Config Help?

Rob Giuliano
 

Are you sure the TX was working with the FTM-400XDR?

You should be able to configure the FTM-400XDR to send the data to an attached computer, but the Yaesu radios are not "PC friendly" when it comes to APRS.

I find this particular manual even more confusing on the topic than previous Yaesu APRS radios.
My "best guess" would be the following:
Page 170 "Data" section
1 COM PORT SETTING
  SPEED: 9600
  OUPUT: PACKET       (if non-functional, try WAYPOINT)
  WP FORMAT: MEAN9   (default - although that is GPS output, not PACKET)
  WP Filter: ALL
2 DATA BAND SELECT: {Your desired settings for frequency in use)
3 DATA SPEED (Assumed on air data rate) 
   APRS: 1200
   DATA: 1200
Page 171
4 DATA SQUELCH: (your desired settings)
  APRS (1 -4 skipped)
5 APRS MODEM: ON

Scrolling down to 196, 197, and beyond provides some additional information. 
To me, it appears setting output to DATA will cause the internal TNC to turn off and the audio outputs of the Data Jack to be enabled (for an external TNC).

Robert Giuliano
KB8RCO



From: "bjessee@... [aprsisce]"
To: aprsisce@...
Sent: Monday, December 11, 2017 8:43 AM
Subject: [aprsisce] Yaesu FTM-400XDR Surface 3 Win 10 Config Help?

 
I had been using my Surface 3 WIn10 and Yaesu FTM-400XDR successfully with APRSIS32 as a base until the Surface 3 died. I replaced it and just cannot get RF RX/TX between the radio and PC/APRCIS32. I have a similar setup in my mobile car (Dell Venue Win10 tablet running APRSIS32 on hotspot) and have taken pics of each setup screen and confirmed match on my base. My base radio does RX/TX OK but I see no RF in APRSIS32. None listed under View:RF but the radio lists RX in the internal log - I can see a local site UNCAN received that doesn't appear on APRSIS32.Some checks:

1. Upper left on APRSIS32 alternates FTM400XDR OK and APRS IS OK,
2. Device Manger shows connection on COM3 9600 8/n/1 which I have matched under Configure:Ports:FTM400XDR:Device
3. Radio Data COM Port Speed set to 9600 Packet
4. Radio Data Data Speed set APRS 1200 Data 9600; Configure:Ports:FTM400XDR RF Baud set to 1200

I haven't had my mobile or base running for a while so anything logged today is my base.

Bret/N4SRN



Re: APWW10

Fred Hillhouse
 

This is the TOCALL for APRSIS32.

http://aprs.org/aprs11/tocalls.txt

 

Look towards the bottom:

APWWxx  APRSISCE win32 version

 

Best regards,

Fred N7FMH

 

 

 

From: aprsisce@... [mailto:aprsisce@...]
Sent: Monday, December 11, 2017 2:30 PM
To: aprsisce@...
Subject: [aprsisce] APWW10

 

 

This is probably a dumb question, but I'm still learning. What is APWW10? I haven't seen anyone else in my area using this. Is this a default setting I'm supposed to be changing somewhere? I've spend many hours searching for the meaning behind this. Any hints would be greatly appreciated.

 

KD8THW 


Virus-free. www.avast.com


APWW10

David Simonson
 

This is probably a dumb question, but I'm still learning. What is APWW10? I haven't seen anyone else in my area using this. Is this a default setting I'm supposed to be changing somewhere? I've spend many hours searching for the meaning behind this. Any hints would be greatly appreciated.


KD8THW 


Re: Station Display Time

Rob Giuliano
 

I haven't worked with this area in a long time.
I am unsure if this is in abled in that "very old" version.
   and changing to the development version. 
   I believe the current Development Version has been out for 5 months.
   It is quite stable! 

I believe you have to hand edit the XML to change these settings.
The values you are looking for are:
   80
   120
   0
If I recall, Min is when it starts fading and Max is when it leaves the screen.

Hopefully, Lynn (or someone else) will have more detail - if needed.
 
Robert Giuliano
KB8RCO



From: "graham.chaloner@... [aprsisce]"
To: aprsisce@...
Sent: Monday, December 11, 2017 7:52 AM
Subject: [aprsisce] Station Display Time

 
Have tried to search for this without success, is it possible to change the length of time station icons are displayed for?
Running APRSIS32 2012/08/30 on W10 with Kenwood D700 in Kiss Mode.

Many thanks
Graham M0GWC



Yaesu FTM-400XDR Surface 3 Win 10 Config Help?

bjessee@...
 

I had been using my Surface 3 WIn10 and Yaesu FTM-400XDR successfully with APRSIS32 as a base until the Surface 3 died. I replaced it and just cannot get RF RX/TX between the radio and PC/APRCIS32. I have a similar setup in my mobile car (Dell Venue Win10 tablet running APRSIS32 on hotspot) and have taken pics of each setup screen and confirmed match on my base. My base radio does RX/TX OK but I see no RF in APRSIS32. None listed under View:RF but the radio lists RX in the internal log - I can see a local site UNCAN received that doesn't appear on APRSIS32.Some checks:


1. Upper left on APRSIS32 alternates FTM400XDR OK and APRS IS OK,

2. Device Manger shows connection on COM3 9600 8/n/1 which I have matched under Configure:Ports:FTM400XDR:Device

3. Radio Data COM Port Speed set to 9600 Packet

4. Radio Data Data Speed set APRS 1200 Data 9600; Configure:Ports:FTM400XDR RF Baud set to 1200


I haven't had my mobile or base running for a while so anything logged today is my base.


Bret/N4SRN


Station Display Time

graham.chaloner@...
 

Have tried to search for this without success, is it possible to change the length of time station icons are displayed for?

Running APRSIS32 2012/08/30 on W10 with Kenwood D700 in Kiss Mode.


Many thanks

Graham M0GWC


Re: Multiport mobile tracking feature requests

brian cochran
 

Being able to use dual port tnc even if agwpe is required would be nice

But running 2 installls is a temporary fix

 

Jack Brian Cochran WC4J

703-965-6011

WC4J@...

http://dhampyr.com

http://WC4J.com

 

From: aprsisce@... [mailto:aprsisce@...]
Sent: Saturday, December 9, 2017 4:54 PM
To: aprsisce@...
Subject: [aprsisce] Multiport mobile tracking feature requests

 

 

Greetings,

First and foremost, thanks to all who have contributed to this great program.  I have very much enjoyed all of it's capabilities and look forward to seeing where it all goes in the future.  I have recently been working on my mobile system and was looking closer at using APRSIS32 as a single point to aggregate all data.  I've searched previous posts on some of this and from what I can tell some of this has been planned, but I just want to give my feedback as well as reasoning behind the requests.

1) Please consider bringing back the per port callsign option.  I found references to it being removed at http://aprsisce.wikidot.com/port-configuration, but would like consideration of leaving it, even if it means a manual edit to the XML configuration file.  I currently run both 30m and 2m APRS in my vehicle and am working to incorporate 6m as well.  I have a keen interest in being able to tell which band is being picked up, so I run a different SSID on 30m than 2m and eventually 6m.  This allows me to view my tracking independently without having to inspect the digipeater/iGate path.  I understand the current method involves running a second instance of APRSIS32, but given the fact that my display is a small Windows tablet on my dashboard, the prospect of trying to fit 2 or 3 instances on it's already small display is less than appealing.  I found a thread from K7MT regarding running a second port, but there was some trouble in regards to knowing which port received a given station.  My primary interest mobile is not for digipeating, but being able to send and receive messages.  I am certainly no programmer, but I would think if each port was able to have a unique callsign/SSID, it would be easier for APRSIS32 to know which port the message was received and thus be able to send back an acknowledgement on the port where it arrived as well as "know" which port to send subsequent messages purely based on the callsign/SSID involved in the exchange.

2) Add support for per port digipeater paths.  From what I've been able to find thus far, it appears there is a single path defined for all ports.  Again, I understand the current recommendation is to run multiple instances, but for reasons noted above I would like to avoid this option.  Being a current HF and VHF APRS mobile station, I do not want to put any digipeaters on 30m, but generally want to use WIDE1-1,WIDE2-1 on 2m.  Likewise in researching 6m APRS, the paths there will be considerably different as well.  I am not sure if having a per port callsign/SSID would make this easier to implement, but it would be a useful feature for those of us who are mobile and running on multiple bands/ports.

3) Revisit adding support for multiport TNCs.  I found several references to this in the past and I understand that Lynn does not have access to such a hardware TNC.  I have been doing quite a bit of work with Direwolf on the Raspberry Pi type systems, my most recent tracker system is built around a Raspberry Pi Zero W mounted inside of a Kenwood VHF radio.  It gets NEMA sentences via it's onboard TTL serial port (GPS TXD to RPi RXD, common ground), has a 2 port USB hub to drive a pair of inexpensive USB sound cards, then uses GPIO pins to activate the PTT on the local 2m radio as well as a 30m radio which is wired up via an external connection.  Direwolf itself is capable of 6 ports per instance (or 3 if you're using monaural mic in which is common on USB sound cards).  Right now I have APRSIS32 linking with Direwolf via a TCP connection via it's KISS over TCP listener (defaults to port 8001).  As other have noted, it does not appear that APRSIS32 can support multiple KISS channels, be a serial/USB connection to KAM/KPC-9612, a KISS over TCP type connection or an AGWPE over TCP type connection.  Since Direwolf/UZ7HO Soundmodem/AGWPE are all software, could this possibly used to aid in development of multiport support, even if it's for "software" TNCs?  Natively, Direwolf is capable of driving each radio from a single instance, but as noted, when I connect APRSIS32 to this system, it can receive both ports but only transmit on one port.  This is acceptable for monitoring traffic around me, but limits my ability to exchange messages that come in on the secondary port.  As a workaround, I have split the 30m and 2m into their own instances, running 30m KISS over TCP on port 8001 and 2m KISS over TCP on port 8003.  Likewise I have been doing some testing using the AGWPE interface and other applications (YAAC) seem to be able to query Direwolf to get a list of available port names to select via a single TCP connection (defaults to port 8000).

Many thanks to all past, current and future efforts of this great software.

73,

Matt
KB8UVN

 


Multiport mobile tracking feature requests

Matt Mitchell
 

Greetings,

First and foremost, thanks to all who have contributed to this great program.  I have very much enjoyed all of it's capabilities and look forward to seeing where it all goes in the future.  I have recently been working on my mobile system and was looking closer at using APRSIS32 as a single point to aggregate all data.  I've searched previous posts on some of this and from what I can tell some of this has been planned, but I just want to give my feedback as well as reasoning behind the requests.

1) Please consider bringing back the per port callsign option.  I found references to it being removed at http://aprsisce.wikidot.com/port-configuration, but would like consideration of leaving it, even if it means a manual edit to the XML configuration file.  I currently run both 30m and 2m APRS in my vehicle and am working to incorporate 6m as well.  I have a keen interest in being able to tell which band is being picked up, so I run a different SSID on 30m than 2m and eventually 6m.  This allows me to view my tracking independently without having to inspect the digipeater/iGate path.  I understand the current method involves running a second instance of APRSIS32, but given the fact that my display is a small Windows tablet on my dashboard, the prospect of trying to fit 2 or 3 instances on it's already small display is less than appealing.  I found a thread from K7MT regarding running a second port, but there was some trouble in regards to knowing which port received a given station.  My primary interest mobile is not for digipeating, but being able to send and receive messages.  I am certainly no programmer, but I would think if each port was able to have a unique callsign/SSID, it would be easier for APRSIS32 to know which port the message was received and thus be able to send back an acknowledgement on the port where it arrived as well as "know" which port to send subsequent messages purely based on the callsign/SSID involved in the exchange.

2) Add support for per port digipeater paths.  From what I've been able to find thus far, it appears there is a single path defined for all ports.  Again, I understand the current recommendation is to run multiple instances, but for reasons noted above I would like to avoid this option.  Being a current HF and VHF APRS mobile station, I do not want to put any digipeaters on 30m, but generally want to use WIDE1-1,WIDE2-1 on 2m.  Likewise in researching 6m APRS, the paths there will be considerably different as well.  I am not sure if having a per port callsign/SSID would make this easier to implement, but it would be a useful feature for those of us who are mobile and running on multiple bands/ports.

3) Revisit adding support for multiport TNCs.  I found several references to this in the past and I understand that Lynn does not have access to such a hardware TNC.  I have been doing quite a bit of work with Direwolf on the Raspberry Pi type systems, my most recent tracker system is built around a Raspberry Pi Zero W mounted inside of a Kenwood VHF radio.  It gets NEMA sentences via it's onboard TTL serial port (GPS TXD to RPi RXD, common ground), has a 2 port USB hub to drive a pair of inexpensive USB sound cards, then uses GPIO pins to activate the PTT on the local 2m radio as well as a 30m radio which is wired up via an external connection.  Direwolf itself is capable of 6 ports per instance (or 3 if you're using monaural mic in which is common on USB sound cards).  Right now I have APRSIS32 linking with Direwolf via a TCP connection via it's KISS over TCP listener (defaults to port 8001).  As other have noted, it does not appear that APRSIS32 can support multiple KISS channels, be a serial/USB connection to KAM/KPC-9612, a KISS over TCP type connection or an AGWPE over TCP type connection.  Since Direwolf/UZ7HO Soundmodem/AGWPE are all software, could this possibly used to aid in development of multiport support, even if it's for "software" TNCs?  Natively, Direwolf is capable of driving each radio from a single instance, but as noted, when I connect APRSIS32 to this system, it can receive both ports but only transmit on one port.  This is acceptable for monitoring traffic around me, but limits my ability to exchange messages that come in on the secondary port.  As a workaround, I have split the 30m and 2m into their own instances, running 30m KISS over TCP on port 8001 and 2m KISS over TCP on port 8003.  Likewise I have been doing some testing using the AGWPE interface and other applications (YAAC) seem to be able to query Direwolf to get a list of available port names to select via a single TCP connection (defaults to port 8000).

Many thanks to all past, current and future efforts of this great software.

73,

Matt
KB8UVN



Re: Passcode

mike owen
 

Ki4zlh.  And it said I did


On Fri, Dec 8, 2017 at 2:39 PM, stiv@... [aprsisce]
wrote:
 

Sorry, forgot to add callsign to request to join.  K9STV, 


Re: Passcode

Stiv Ostenberg
 

Sorry, forgot to add callsign to request to join.  K9STV, 

3601 - 4000 of 35618