[pskmail] Re: ?bug and idea for Client 1.5

  • From: Per Crusefalk <per@xxxxxxxxxxxx>
  • To: pskmail@xxxxxxxxxxxxx
  • Date: Thu, 12 Jan 2012 19:57:11 +0100

Hi Robert,

I can confirm the attachment issue. Its a known issue but was
unfortunately discovered after I shipped 1.5. I have a working client
here but I am rebuilding it somewhat further. I am altering the email
viewer so that it shows if there is an attachment to the email at the
bottom when you open the email from the inbox. It is then possible to
save the attachment where ever you want it.

Regarding the gps issue I can add that. The issue in the past was that
if the gps fix was lost then it would happily continue to send old data
without warning. Now it will warn if the gps fix is lost but I have not
done anything to it at startup.

73 de Per, sm0rwo

tor 2012-01-12 klockan 07:23 -0800 skrev Robert Krasowski:
> Hi all, 
> just few observations we had while using PSKmail. 
> While downloading GRIB file after "Get GRIB", the grib is put into the
> file and at the end of the name there is ". This is in client ver 1.5.
> I do not have that client running on my side, so I can not verify that
> but that is the problem that SQ2OAZ reported to me. What that do is
> the fact that GRIb file is not recognized by GRIB reading software and
> they have to rename that file. Not a big problem but there. 
> Also while turning PSKmail client on it sends beacon with position
> immediately. If GPS did not have a chance to lock on new position, old
> position will be sent. If that beacon is received by any station, it
> will be put to the system with the time and date when it was received.
> It mess up tracking, because we have old position being sent with new
> time assigned to it. So beacon should wait until GPS get new
> position.  
> Here is raw packet from APRS system showing the result of this: 
> 2012-01-12 09:40:19 UTC: SQ2OAZ>PSKAPR,TCPIP*,qAS,KB2PNM:!
> 2152.50N/02847.95WY000/000/
> 2012-01-12 09:50:46 UTC: SQ2OAZ>PSKAPR,TCPIP*,qAS,KB2PNM:!
> 2152.50N/02847.95WY000/000/
> 2012-01-12 09:53:46 UTC: SQ2OAZ>PSKAPR,TCPIP*,qAS,SM0RWO:!
> 2025.76N/03029.61WY214/005/ [Location changes too fast (>500 km/h)]
> Any idea how to fix it??
> Best regards 
> Robert 

Other related posts: