Date   

Re: DSBL lower right corner

Patrick Connor
 

I think it's GPS status.

Patrick (N3TSZ)


On Wednesday, April 21, 2021, 05:16:55 PM EDT, Mike <athome@...> wrote:



Could it be date/time DIsabled?
Mike VA7QC


On Wed, Apr 21, 2021 at 1:14 PM T W via groups.io <kf6kyd=me.com@groups.io> wrote:
Can anyone tell me what the DSBL means in the lower right corner?

TIA kf6kyd






Re: DSBL lower right corner

Mike
 


Could it be date/time DIsabled?
Mike VA7QC


On Wed, Apr 21, 2021 at 1:14 PM T W via groups.io <kf6kyd=me.com@groups.io> wrote:
Can anyone tell me what the DSBL means in the lower right corner?

TIA kf6kyd






DSBL lower right corner

T W
 

Can anyone tell me what the DSBL means in the lower right corner?

TIA kf6kyd


Windows Sound level setting for each application

N0YWB
 

After years of fumbling through the menus to adjust the Windows 10 Sound sliders every time I changed digital modes apps, 
I discover that each application has its own level setting. 
 
Go to Settings | Sound | Advanced sound options | App volume and device preferences. 
You have to open each app to make it visible. 
Change Default to the specific sound device. 
 
Notice that the other apps that share the same device are grayed out.
The first app opened is in control, and can be adjusted, until it is closed.
 
These are a percentage of the Master level setting, so set the Master volume once, and leave it alone.
https://www.technipages.com/change-volume-specific-apps-windows-10 


Re: Computer problems

Rob Giuliano
 


The most common causes for APRSIS32 to get caught at this point in the startup are:
1. Running the EXE file from within the zip file.
    You must extract the APRSIS32.exe file to a folder with full user access.
2. You extracted the file into a folder that is protected.
    Windows10 has become more and more restrictive of folders.
    With newer Windows 10 releasesm creating a folder in the root (C:\) is now protected (read only).
    You will need to select the folder and ensure the proper permissions are set for it.

The reason for that is APRSIS32 was based of the old WIndows 32-bit philosophy. 
It places all support files (ini, maps, etc.) in the same folder as the executable file. 

This is contrary to the Windows10 philosophy:
    All applications (exe) should be placed in Program Files or Program Files (x86).
    Any user data should be placed in the user's home folder with the preferred place
       being a folder with the app's name inside the hidden folder AppData
    This ensures that each users settings are preserved for them.


Robert Giuliano
KB8RCO


On Saturday, April 17, 2021, 1:30:08 PM EDT, Burt N Sammis <kango03@...> wrote:


I am running a desktop on Windows 10 and trying to use APRSISCE.
After downloading when trying to open the file a instead of PRISISCE I get
a horizontal line about 2 inches wide all the way across the screen.
I have tried everything I know to get rid of the line and bring APRISCE up.
To get rid of the line I have to resort to Task Manager.

I have a laptop running APRSISCE with no problem.
There is no sense in running two computers.  
Help?
Burt
AF5AA    


Re: Computer problems

AE7G
 

I had that happen initially.  When you specify COM port and call sign this clears up.  Try restarting it.

 

 

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Burt N Sammis via groups.io
Sent: Saturday, April 17, 2021 10:30 AM
To: APRSISCE@groups.io
Subject: [APRSISCE] Computer problems

 

I am running a desktop on Windows 10 and trying to use APRSISCE.

After downloading when trying to open the file a instead of PRISISCE I get

a horizontal line about 2 inches wide all the way across the screen.

I have tried everything I know to get rid of the line and bring APRISCE up.

To get rid of the line I have to resort to Task Manager.

 

I have a laptop running APRSISCE with no problem.

There is no sense in running two computers.  

Help?

Burt

AF5AA    


Computer problems

Burt N Sammis
 

I am running a desktop on Windows 10 and trying to use APRSISCE.
After downloading when trying to open the file a instead of PRISISCE I get
a horizontal line about 2 inches wide all the way across the screen.
I have tried everything I know to get rid of the line and bring APRISCE up.
To get rid of the line I have to resort to Task Manager.

I have a laptop running APRSISCE with no problem.
There is no sense in running two computers.  
Help?
Burt
AF5AA    


Re: Symbol Persistence Time?

Lynn Deffenbaugh
 

Double-click the narrow vertical bar immediately to the right of the map.  The top section shows the currently effective expiration times.  Stations will begin to fade at 80 minutes and will disappear at 120 minutes (at least, I think I'm running the defaults).  The numbers in () are the applicable times for buddies or friends from your filter or any station that you are actively tracking in any window.

You can set these values in the APRSIS32.XML file if you want something other than the defaults.

<Stations.MinAge>80</Stations.MinAge>
<Stations.MaxAge>120</Stations.MaxAge>
<Stations.MaxAge.Buddy>0</Stations.MaxAge.Buddy>

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


On 4/17/2021 9:17 AM, Charles Jessee wrote:
How is symbol persistence time determined? That is, when a symbol appears on screen, what determines how long it stays on screen before disappearing? Thanks!

Bret/N4SRN


Symbol Persistence Time?

Charles Jessee
 

How is symbol persistence time determined? That is, when a symbol appears on screen, what determines how long it stays on screen before disappearing? Thanks!

Bret/N4SRN


Re: ToCall(s) for SCS PTCx, Dragon etc.

Julian
 

SCS has actually  come back to me in a vy reasonable amount of time. Pretty impressive, compared to other packet radio and the like eqp manufacturers who/which, when contacted, never reply - sharing from own experience - to any reasonable, of course, question.
The reply in SCS case was swift, to the object, but negative. There is also silence on the APRS side, so, I am guessing the matter looks pretty much buried for now.
Tnx fer help Lynn.
73 and best regards de J, MØIPU YOЗFCA (QRTing on this matter)


Re: Telemetry EQNS oddity

Arnold Harding - KQ6DI
 

Yes, I have remote access set up.  The problem becomes one of not having any stations I can relay through that can reach it.  I can use Remote Access when I'm there to avoid walking that last 300 yards, but it doesn't help from here.  I've used remote access to other sites through relays, and it does work great.
Since I see the data fine with aprs.fi and I can get the data directly from the RAW data, it's not critical.  I'll get to it next week on my rounds.
 
I just think it's odd that APRSISCE doesn't seem to pick out the values.
 
Arnold, KQ6DI

On 04/12/2021 2:10 PM James Ewen <ve6srv@...> wrote:
 
 
On Sat, Apr 10, 2021 at 12:27 PM Arnold Harding - KQ6DI < kq6di@...> wrote:
 
That site only sends telemetry parameters once a day at 09:03, IF the RF makes it out of this RF hole.  It's also 3 hours each way for me to change parameters, so I won't make a special trip for this.
 
 
Arnold,
 
Have you read the information on page 74 of the KPC-3 user manual? You might be able to save a bunch of hours driving, and fuel costs as well.
 
Remote Access to Your TNC 
 
You can connect to your TNC from a remote station and change values of your TNC’s parameters. This allows you to add or delete stations from the LLIST, change the size of the PBBS, change the MYCALL and so on, all remotely. Extreme caution must be used when you are accessing your TNC from a remote location. There is no built-in safeguard, and as such it is possible for you to change parameters such that the remote TNC will no longer communicate with you.
 
In order to change parameters in a remote TNC, the RTEXT in the remote TNC must be set to a text string that will be used as the password string. For instance, you might set your RTEXT to:
 
RTEXT Code 
 
The remote TNC must also have its MYREMOTE set to a unique callsign (i.e. WØABC4, or XYZREM). If these two parameters are not set, remote access to the command set of this TNC is not possible. When these parameters are set, you can connect to the MYREMOTE callsign of the remote TNC. 
 
When the connection is made, the remote TNC will send three lines of numbers. The numbers may look like:
 
1 1 1 3 4 3 
3 1 4 3 1 3
2 1 1 2 1 3 
 
You must then pick ONE of these lines and decode the password string. Let’s say you choose to decode line 3 (2 1 1 2 1 3). Rewriting your RTEXT string to make this easier you would have:
 
Character #: 1 2 3 4
Letter:      C o d e 
 
Therefore, to gain remote access, you must send the following string:
 
oCCoCd 
 
(since small letter o is at position 2, capital C is at position 1, and so on) 
 
Note that case is significant and spaces are considered valid characters.  
 
If you fail to properly decode the password, the TNC will send three new lines of numbers. You will be given a maximum of three attempts to properly decode the password string. If you fail in three attempts, the TNC will disconnect you and disable connects to the MYREMOTE for 15 minutes. Also, if you connect to the MYREMOTE and start the password sequence but then disconnect, the penalty timer is in effect for 15 minutes. 
 
Be careful when using the remote access feature. You can change ANY command in the TNC without restriction, but this can lead to problems. For instance, if you change the INTFACE command to KISS and then send a RESET command, the remote TNC will be placed into the KISS mode and will completely quit talking to the radio! Also, if you connect to the MYREMOTE of a TNC and then issue a command like CONNECT W1ABC, the remote TNC will indeed connect to the station, but there will be no data sent to you from that connection. The connected data would be sent to the serial port of that remote TNC. We urge EXTREME caution when using the remote access! Note also that any command that causes a reset (i.e. NUMNODES, PBBS, MAXUSERS) will disconnect all current users (PBBS, NODE, and YOU). 
 
One other minor limitation applies to receiving data from the remote TNC. When you give any command, the response is limited to 300 characters so some commands will not fully display their response. If you give the command DISPLAY, the full list will begin, but you will not receive the entire list because of the limitation on this buffer.  
 
 
You can read more about the remote access by looking at the RTEXT and MYREMOTE command descriptions.
 
A searchable PDF copy of the TNC manual can be found here:
 
 
Remote access is perfect for a situation like this where there is a minor issue to be corrected, and the time and effort to get to the remote site is significant.
 
Now, you do have the issue where your remote site does not have reliable RF network connectivity. I can't do much about that, but it is possible to send remote commands in the blind if you can get logged into the unit. You don't have to see the results of your commands as long as you can get the command to the unit.
 
Building robust reliable networks really helps in situations like this. A network with unreliable connectivity due to intermittent paths between nodes, or overloaded RF network traffic levels can make any type of use of the network poor at best.
 
James
VE6SRV

 

 

 


Re: Telemetry EQNS oddity

James Ewen
 

On Sat, Apr 10, 2021 at 12:27 PM Arnold Harding - KQ6DI <kq6di@...> wrote:
 
That site only sends telemetry parameters once a day at 09:03, IF the RF makes it out of this RF hole.  It's also 3 hours each way for me to change parameters, so I won't make a special trip for this.
 

Arnold,

Have you read the information on page 74 of the KPC-3 user manual? You might be able to save a bunch of hours driving, and fuel costs as well.

Remote Access to Your TNC 

You can connect to your TNC from a remote station and change values of your TNC’s parameters. This allows you to add or delete stations from the LLIST, change the size of the PBBS, change the MYCALL and so on, all remotely. Extreme caution must be used when you are accessing your TNC from a remote location. There is no built-in safeguard, and as such it is possible for you to change parameters such that the remote TNC will no longer communicate with you.

In order to change parameters in a remote TNC, the RTEXT in the remote TNC must be set to a text string that will be used as the password string. For instance, you might set your RTEXT to:

RTEXT Code 

The remote TNC must also have its MYREMOTE set to a unique callsign (i.e. WØABC4, or XYZREM). If these two parameters are not set, remote access to the command set of this TNC is not possible. When these parameters are set, you can connect to the MYREMOTE callsign of the remote TNC. 

When the connection is made, the remote TNC will send three lines of numbers. The numbers may look like:

1 1 1 3 4 3 
3 1 4 3 1 3
2 1 1 2 1 3 

You must then pick ONE of these lines and decode the password string. Let’s say you choose to decode line 3 (2 1 1 2 1 3). Rewriting your RTEXT string to make this easier you would have:

Character #: 1 2 3 4
Letter:      C o d e 

Therefore, to gain remote access, you must send the following string:

oCCoCd 

(since small letter o is at position 2, capital C is at position 1, and so on) 

Note that case is significant and spaces are considered valid characters.  

If you fail to properly decode the password, the TNC will send three new lines of numbers. You will be given a maximum of three attempts to properly decode the password string. If you fail in three attempts, the TNC will disconnect you and disable connects to the MYREMOTE for 15 minutes. Also, if you connect to the MYREMOTE and start the password sequence but then disconnect, the penalty timer is in effect for 15 minutes. 

Be careful when using the remote access feature. You can change ANY command in the TNC without restriction, but this can lead to problems. For instance, if you change the INTFACE command to KISS and then send a RESET command, the remote TNC will be placed into the KISS mode and will completely quit talking to the radio! Also, if you connect to the MYREMOTE of a TNC and then issue a command like CONNECT W1ABC, the remote TNC will indeed connect to the station, but there will be no data sent to you from that connection. The connected data would be sent to the serial port of that remote TNC. We urge EXTREME caution when using the remote access! Note also that any command that causes a reset (i.e. NUMNODES, PBBS, MAXUSERS) will disconnect all current users (PBBS, NODE, and YOU). 

One other minor limitation applies to receiving data from the remote TNC. When you give any command, the response is limited to 300 characters so some commands will not fully display their response. If you give the command DISPLAY, the full list will begin, but you will not receive the entire list because of the limitation on this buffer.  


You can read more about the remote access by looking at the RTEXT and MYREMOTE command descriptions.

A searchable PDF copy of the TNC manual can be found here:


Remote access is perfect for a situation like this where there is a minor issue to be corrected, and the time and effort to get to the remote site is significant.

Now, you do have the issue where your remote site does not have reliable RF network connectivity. I can't do much about that, but it is possible to send remote commands in the blind if you can get logged into the unit. You don't have to see the results of your commands as long as you can get the command to the unit.

Building robust reliable networks really helps in situations like this. A network with unreliable connectivity due to intermittent paths between nodes, or overloaded RF network traffic levels can make any type of use of the network poor at best.

James
VE6SRV



Re: APRS positions not uploading to APRS.FI

macclad44@...
 

2 1/2 months later, I see that what shows up on APRS.fi and how long it remains as reported "packets to" or "packets from" seems a bit random. I have learned to stop worrying about it.  Since I have my own gateway and a moving vehicle with a Robust Packet beacon .. I can always verify my system is working and the long and short of it is, that's "good enough" for me.  
BTW someone on Facebook had problems with APRSISCE (greying out of 1200 baud packets or somesuch - not anything I'm ever going to be involved with) so I sent him to this group to sign up and get involved... 
Thanks Lynn!


Re: Telemetry EQNS oddity

Arnold Harding - KQ6DI
 

As far as I can tell, the only difference between being picked up as intended by APRSISce is the leading zero if the parameter is negative less than zero.  So,  -.644  does not work, and  I believe  -0.644  will work.  So I believe I need to add the leading zero back in.
 
But aprs.fi gets it as I intended.  Either way, the equation is picked up in the correct placement, just the wrong value in 2 parameters with APRSISCE.  So in a week or so, I'll be back and add that leading zero in again.
 
Arnold, KQ6DI
 

On 04/10/2021 6:17 PM Rob Giuliano via groups.io <kb8rco@...> wrote:
 
 
Sorry, looked in the wrong spot.
I was looking at more of a description, not an example; http://www.aprs.net/vm/DOS/TELEMTRY.HTM

FORMAL SPECIFICATION: The specific format for the TITLE, PARM, UNIT, and EQNS message packets are shown below. They are entered as messages to the address of the MIM module:

 

  PARM.P1,P2,P3,P4,P5,B1,B2,B3,etc    Where Pn and Bn are the parameter names

UNIT,U1,U2,U3,U4,U5,L1,L2,L3,etc Where Un are the units for analog ports and Ln are the labels for the bits

EQNS,A1,B1,C1,A2,B2,C2,A3,B3,C3,etc Where the An,Bn,Cn are the coeficients for each of the five analog channels,

I should have looked just above it at the actual packet format:  
N3MIM:EQNS.0,2.6,0,0,.53,-32,3,4.39,49,-32,3,18,1,2,3
Not sure what the colon at the beggining of your packet is from.
 

Robert Giuliano
KB8RCO

 
 
On Saturday, April 10, 2021, 8:00:53 PM EDT, Arnold Harding - KQ6DI <kq6di@...> wrote:
 
 
According to the APRS 101 specification
Page 70, the specification calls for a decimal point after EQNS.  Here's from the specification.
Example:N0QBF-11 :EQNS.0,5.2,0,0,.53,-32,3,4.39,49,-32,3,18,1,2,3
 
You made me look, so that's OK.  The fact that aprs.fi gets it one way ( as I intended) and APRSISCE doesn't makes me wonder if APRSISCE isn't getting it the way intended.  (I'm not suggesting APRSISCE is wrong, it just doesn't come out the same way.)
My guess is I need a leading zero after the negative sign before the decimal point on negative less than 1 calculations.
Arnold, KQ6DI
 
On 04/10/2021 4:24 PM Rob Giuliano via groups.io <kb8rco@...> wrote:
 
 
The format is    EQNS ,A1,B1,C1,A2,B2,C2,A3,B3,C3,etc.
 
You missed the comma (used a decimal)
So your     :KQ6DI-1 :EQNS.0,-.644,150,0,-.5,-190,0,1,0,0,.625,0
 should be :KQ6DI-1 :EQNS,0,-.644,150,0,-.5,-190,0,1,0,0,.625,0
 

Robert Giuliano
KB8RCO

 
 
On Saturday, April 10, 2021, 2:27:32 PM EDT, Arnold Harding - KQ6DI <kq6di@...> wrote:
 
 
I think I may have done something outside the specification, or there is an error somewhere.  I changed telemetry EQNS to remove some leading zeros, and APRSISCE doesn't pick the values out.  What I am sending is:
:KQ6DI-1 :EQNS.0,-.644,150,0,-.5,-190,0,1,0,0,.625,0
 
aprs.fi picks out the values correctly ( at least as I intended ), but APRSISCE doesn't pick up part of the equation.
Channel 1 b=0 should be -.644
Channel 2 b=0 and should be -.5
 
It worked before when I had leading zeros in the equation like -0.644 and -0.5.
But notice that channel 4 did pick up the correct number of .625.
 
So my guess is that negative values less than one must have a leading zero and become -0.644 and -0.5.  Do I need those leading zeros on negative values?
 
That site only sends telemetry parameters once a day at 09:03, IF the RF makes it out of this RF hole.  It's also 3 hours each way for me to change parameters, so I won't make a special trip for this.
 
Arnold, KQ6DI


Re: Telemetry EQNS oddity

Rob Giuliano
 

Sorry, looked in the wrong spot.
I was looking at more of a description, not an example; http://www.aprs.net/vm/DOS/TELEMTRY.HTM

FORMAL SPECIFICATION: The specific format for the TITLE, PARM, UNIT, and EQNS message packets are shown below. They are entered as messages to the address of the MIM module:

  PARM.P1,P2,P3,P4,P5,B1,B2,B3,etc    Where Pn and Bn are the parameter names

UNIT,U1,U2,U3,U4,U5,L1,L2,L3,etc Where Un are the units for analog ports and Ln are the labels for the bits

EQNS,A1,B1,C1,A2,B2,C2,A3,B3,C3,etc Where the An,Bn,Cn are the coeficients for each of the five analog channels,

I should have looked just above it at the actual packet format:  
N3MIM:EQNS.0,2.6,0,0,.53,-32,3,4.39,49,-32,3,18,1,2,3
Not sure what the colon at the beggining of your packet is from.

Robert Giuliano
KB8RCO



On Saturday, April 10, 2021, 8:00:53 PM EDT, Arnold Harding - KQ6DI <kq6di@...> wrote:


According to the APRS 101 specification
Page 70, the specification calls for a decimal point after EQNS.  Here's from the specification.
Example:N0QBF-11 :EQNS.0,5.2,0,0,.53,-32,3,4.39,49,-32,3,18,1,2,3
 
You made me look, so that's OK.  The fact that aprs.fi gets it one way ( as I intended) and APRSISCE doesn't makes me wonder if APRSISCE isn't getting it the way intended.  (I'm not suggesting APRSISCE is wrong, it just doesn't come out the same way.)
My guess is I need a leading zero after the negative sign before the decimal point on negative less than 1 calculations.
Arnold, KQ6DI
 
On 04/10/2021 4:24 PM Rob Giuliano via groups.io <kb8rco@...> wrote:
 
 
The format is    EQNS ,A1,B1,C1,A2,B2,C2,A3,B3,C3,etc.
 
You missed the comma (used a decimal)
So your     :KQ6DI-1 :EQNS.0,-.644,150,0,-.5,-190,0,1,0,0,.625,0
 should be :KQ6DI-1 :EQNS,0,-.644,150,0,-.5,-190,0,1,0,0,.625,0
 

Robert Giuliano
KB8RCO

 
 
On Saturday, April 10, 2021, 2:27:32 PM EDT, Arnold Harding - KQ6DI <kq6di@...> wrote:
 
 
I think I may have done something outside the specification, or there is an error somewhere.  I changed telemetry EQNS to remove some leading zeros, and APRSISCE doesn't pick the values out.  What I am sending is:
:KQ6DI-1 :EQNS.0,-.644,150,0,-.5,-190,0,1,0,0,.625,0
 
aprs.fi picks out the values correctly ( at least as I intended ), but APRSISCE doesn't pick up part of the equation.
Channel 1 b=0 should be -.644
Channel 2 b=0 and should be -.5
 
It worked before when I had leading zeros in the equation like -0.644 and -0.5.
But notice that channel 4 did pick up the correct number of .625.
 
So my guess is that negative values less than one must have a leading zero and become -0.644 and -0.5.  Do I need those leading zeros on negative values?
 
That site only sends telemetry parameters once a day at 09:03, IF the RF makes it out of this RF hole.  It's also 3 hours each way for me to change parameters, so I won't make a special trip for this.
 
Arnold, KQ6DI


Re: Telemetry EQNS oddity

Arnold Harding - KQ6DI
 

According to the APRS 101 specification
Page 70, the specification calls for a decimal point after EQNS.  Here's from the specification.
Example:N0QBF-11 :EQNS.0,5.2,0,0,.53,-32,3,4.39,49,-32,3,18,1,2,3
 
You made me look, so that's OK.  The fact that aprs.fi gets it one way ( as I intended) and APRSISCE doesn't makes me wonder if APRSISCE isn't getting it the way intended.  (I'm not suggesting APRSISCE is wrong, it just doesn't come out the same way.)
My guess is I need a leading zero after the negative sign before the decimal point on negative less than 1 calculations.
Arnold, KQ6DI
 

On 04/10/2021 4:24 PM Rob Giuliano via groups.io <kb8rco@...> wrote:
 
 
The format is    EQNS ,A1,B1,C1,A2,B2,C2,A3,B3,C3,etc.
 
You missed the comma (used a decimal)
So your     :KQ6DI-1 :EQNS.0,-.644,150,0,-.5,-190,0,1,0,0,.625,0
 should be :KQ6DI-1 :EQNS,0,-.644,150,0,-.5,-190,0,1,0,0,.625,0
 

Robert Giuliano
KB8RCO

 
 
On Saturday, April 10, 2021, 2:27:32 PM EDT, Arnold Harding - KQ6DI <kq6di@...> wrote:
 
 
I think I may have done something outside the specification, or there is an error somewhere.  I changed telemetry EQNS to remove some leading zeros, and APRSISCE doesn't pick the values out.  What I am sending is:
:KQ6DI-1 :EQNS.0,-.644,150,0,-.5,-190,0,1,0,0,.625,0
 
aprs.fi picks out the values correctly ( at least as I intended ), but APRSISCE doesn't pick up part of the equation.
Channel 1 b=0 should be -.644
Channel 2 b=0 and should be -.5
 
It worked before when I had leading zeros in the equation like -0.644 and -0.5.
But notice that channel 4 did pick up the correct number of .625.
 
So my guess is that negative values less than one must have a leading zero and become -0.644 and -0.5.  Do I need those leading zeros on negative values?
 
That site only sends telemetry parameters once a day at 09:03, IF the RF makes it out of this RF hole.  It's also 3 hours each way for me to change parameters, so I won't make a special trip for this.
 
Arnold, KQ6DI


Re: Telemetry EQNS oddity

Rob Giuliano
 

The format is    EQNS,A1,B1,C1,A2,B2,C2,A3,B3,C3,etc.

You missed the comma (used a decimal)
So your    :KQ6DI-1 :EQNS.0,-.644,150,0,-.5,-190,0,1,0,0,.625,0
 should be :KQ6DI-1 :EQNS,0,-.644,150,0,-.5,-190,0,1,0,0,.625,0

Robert Giuliano
KB8RCO



On Saturday, April 10, 2021, 2:27:32 PM EDT, Arnold Harding - KQ6DI <kq6di@...> wrote:


I think I may have done something outside the specification, or there is an error somewhere.  I changed telemetry EQNS to remove some leading zeros, and APRSISCE doesn't pick the values out.  What I am sending is:
:KQ6DI-1 :EQNS.0,-.644,150,0,-.5,-190,0,1,0,0,.625,0
 
aprs.fi picks out the values correctly ( at least as I intended ), but APRSISCE doesn't pick up part of the equation.
Channel 1 b=0 should be -.644
Channel 2 b=0 and should be -.5
 
It worked before when I had leading zeros in the equation like -0.644 and -0.5.
But notice that channel 4 did pick up the correct number of .625.
 
So my guess is that negative values less than one must have a leading zero and become -0.644 and -0.5.  Do I need those leading zeros on negative values?
 
That site only sends telemetry parameters once a day at 09:03, IF the RF makes it out of this RF hole.  It's also 3 hours each way for me to change parameters, so I won't make a special trip for this.
 
Arnold, KQ6DI


Telemetry EQNS oddity

Arnold Harding - KQ6DI
 

I think I may have done something outside the specification, or there is an error somewhere.  I changed telemetry EQNS to remove some leading zeros, and APRSISCE doesn't pick the values out.  What I am sending is:
:KQ6DI-1 :EQNS.0,-.644,150,0,-.5,-190,0,1,0,0,.625,0
 
aprs.fi picks out the values correctly ( at least as I intended ), but APRSISCE doesn't pick up part of the equation.
Channel 1 b=0 should be -.644
Channel 2 b=0 and should be -.5
 
It worked before when I had leading zeros in the equation like -0.644 and -0.5.
But notice that channel 4 did pick up the correct number of .625.
 
So my guess is that negative values less than one must have a leading zero and become -0.644 and -0.5.  Do I need those leading zeros on negative values?
 
That site only sends telemetry parameters once a day at 09:03, IF the RF makes it out of this RF hole.  It's also 3 hours each way for me to change parameters, so I won't make a special trip for this.
 
Arnold, KQ6DI


Re: How to Igate WX Stations to RF?

Yankee Zulu Delta
 

Hi Lynn

I see your point 

How about this

CWOP-3:@041630z1429.22N/12100.99E_

153/008g014t082r000p000P000h74b10129L000

.DsIP

That part seems to be a good wxnow.txt format.
If I put i can put that in a wxnow.txt file and get that picked up by APRSIS32 as a weather report in, would that be sent over RF?

Thanks!


On Tue, Apr 6, 2021, 00:03 Lynn Deffenbaugh <kj4erj@...> wrote:

Read those raw packets closely.  Those weather stations are not on the APRS-IS, but are getting to aprs.fi via CWOP.  And your node, if it is a properly functioning IGate, needs to be connected to the APRS-IS because CWOP doesn't support IGate connections.

Therefore, there is no way to gate those particular stations from CWOP to RF with APRSISCE/32.

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

PS.  And further, the CWOP servers are designed for incoming packet consolidation only and don't even support filtered feeds.

On 4/5/2021 11:13 AM, Yankee Zulu Delta wrote:

HI All,

 

I know that this has probably been asked before and I was trying my best to search for this but I think I really did not find the answers I need.

 

So right now my APRSIS32 is in development mode. Built 2020/12/30

 

I see 2 WX stations near me in APRS.FI

FW0027 and EW0758
I know that the headers have TCPXX in them…

When I look them up in findu.com these is what’s displayed.

 

FW0027>APRS,TCPXX*,qAX,CWOP-4:@041515z1429.22N/12100.99E_115/009g014t082r000p000P000h75b10131L000.DsIP
FW0027>APRS,TCPXX*,qAX,CWOP-4:@041545z1429.22N/12100.99E_119/009g015t082r000p000P000h75b10131L000.DsIP
FW0027>APRS,TCPXX*,qAX,CWOP-3:@041600z1429.22N/12100.99E_148/008g020t082r000p000P000h74b10129L000.DsIP
FW0027>APRS,TCPXX*,qAX,CWOP-4:@041615z1429.22N/12100.99E_121/012g016t082r000p000P000h74b10128L000.DsIP
FW0027>APRS,TCPXX*,qAX,CWOP-3:@041630z1429.22N/12100.99E_153/008g014t082r000p000P000h74b10129L000.DsIP

 

I am still wondering if there’s a way to parse this and send it over as a bulletin or a message announcement to a group (ANSRVR) as a proper weather report like this in aprs.fi

Or WX report in radios.

 

 

I did a test filter (CTRL-G) g/FW0027/EW0758 but I don’t think I’m getting it.

 

My goal is to be able to transmit via RF a WX Report from these two weather stations that I see in aprs.fi

 

Thanks and 73!

 

Sent from Mail for Windows 10

 


Re: How to Igate WX Stations to RF?

Lynn Deffenbaugh
 

Read those raw packets closely.  Those weather stations are not on the APRS-IS, but are getting to aprs.fi via CWOP.  And your node, if it is a properly functioning IGate, needs to be connected to the APRS-IS because CWOP doesn't support IGate connections.

Therefore, there is no way to gate those particular stations from CWOP to RF with APRSISCE/32.

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

PS.  And further, the CWOP servers are designed for incoming packet consolidation only and don't even support filtered feeds.

On 4/5/2021 11:13 AM, Yankee Zulu Delta wrote:

HI All,

 

I know that this has probably been asked before and I was trying my best to search for this but I think I really did not find the answers I need.

 

So right now my APRSIS32 is in development mode. Built 2020/12/30

 

I see 2 WX stations near me in APRS.FI

FW0027 and EW0758
I know that the headers have TCPXX in them…

When I look them up in findu.com these is what’s displayed.

 

FW0027>APRS,TCPXX*,qAX,CWOP-4:@041515z1429.22N/12100.99E_115/009g014t082r000p000P000h75b10131L000.DsIP
FW0027>APRS,TCPXX*,qAX,CWOP-4:@041545z1429.22N/12100.99E_119/009g015t082r000p000P000h75b10131L000.DsIP
FW0027>APRS,TCPXX*,qAX,CWOP-3:@041600z1429.22N/12100.99E_148/008g020t082r000p000P000h74b10129L000.DsIP
FW0027>APRS,TCPXX*,qAX,CWOP-4:@041615z1429.22N/12100.99E_121/012g016t082r000p000P000h74b10128L000.DsIP
FW0027>APRS,TCPXX*,qAX,CWOP-3:@041630z1429.22N/12100.99E_153/008g014t082r000p000P000h74b10129L000.DsIP

 

I am still wondering if there’s a way to parse this and send it over as a bulletin or a message announcement to a group (ANSRVR) as a proper weather report like this in aprs.fi

Or WX report in radios.

 

 

I did a test filter (CTRL-G) g/FW0027/EW0758 but I don’t think I’m getting it.

 

My goal is to be able to transmit via RF a WX Report from these two weather stations that I see in aprs.fi

 

Thanks and 73!

 

Sent from Mail for Windows 10

 

201 - 220 of 35490