PostFrontal Forum
PostFrontal Forum
PF Home | International_Forum | Profile | Register | Active Topics | Members | Search | FAQ | Upload image
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 LK8000 International Support
 General Support
 Major problems again
 New Topic  Reply to Topic
Next Page
Author Previous Topic Topic Next Topic
Page: of 3

davesalmon
Pterodattilo

United Kingdom
904 Posts

Posted - 30/03/2012 :  17:52:28  Show Profile  Reply with Quote
About 10 days ago I reported problems with my iPAQ 314 using 3a for the first time, and what I had done, which seemed to work OK when not flying.
Today was the first time I have flown since and I had exactly the same problems with the iPAQ 314. It stops showing movement on the map, and the screen either does not respond, or responds after a long delay
I then switched from the iPAQ 314 to my M400, with exactly the same setup, and after a time, exactly the same problem happened. I was using the GT Altimeter, so I removed it, but it made no difference, movement freezes and then jumps a bit, freezes again, and the touch screen is almost unusable. It did make sounds when tapped but nothing happened, or occasionally something happened after 10 secs delay. Strsnge that 2 different devices, one using a BT gps, and the other using it's own internal gps, display exactly the same problem.

TiGuy82
Pterodattilo

Canada
1451 Posts

Posted - 30/03/2012 :  18:24:38  Show Profile  Visit TiGuy82's Homepage  Click to see TiGuy82's MSN Messenger address  Reply with Quote
Maybe your problem is related to this: https://github.com/LK8000/LK8000/commit/1a16bd4a2e51f5791a2b06db1bdf0694cc151dba

www.facebook.com/LK8000
Go to Top of Page

davesalmon
Pterodattilo

United Kingdom
904 Posts

Posted - 30/03/2012 :  18:38:40  Show Profile  Reply with Quote
Sorry Sergio, I'm not a computer man, so don't understand.
Go to Top of Page

davesalmon
Pterodattilo

United Kingdom
904 Posts

Posted - 30/03/2012 :  18:47:36  Show Profile  Reply with Quote
BTW, both devices are working normally back home.
Go to Top of Page

zweidee
Pulcino

Germany
27 Posts

Posted - 30/03/2012 :  19:05:30  Show Profile  Reply with Quote
Hi Folks!

I can't confirm these Problems on my iPaQ314. I used it since the release of 3.0a on 3 weekends for local and x-country flights. It worked as expected and lead me to my target-waypoint. Also the actual Airspaces were shown correctly and warnings popped up early. Are you using a Micro-SD-Card? I had a bad Adaptor, which caused LK8000 to crash when trying to save the System Setup. I took another Adaptor and all is working fine since.

Kind Regards HPD (D-MHPD)
Go to Top of Page

TiGuy82
Pterodattilo

Canada
1451 Posts

Posted - 30/03/2012 :  19:08:02  Show Profile  Visit TiGuy82's Homepage  Click to see TiGuy82's MSN Messenger address  Reply with Quote
Dave, I just tried to show you that Bruno made a fix for devices using LK8EX1 protocol, like GT Vario and maybe will fix your issue.

Regards
Sergio

www.facebook.com/LK8000
Go to Top of Page

davesalmon
Pterodattilo

United Kingdom
904 Posts

Posted - 30/03/2012 :  19:36:31  Show Profile  Reply with Quote
No, I'm using SanDisc Ultra SD in the iPaq, I've used it for quite a long time. The Mio doensn't have a card.

Right Sergio, you are suggesting that it could be to do with using the LK8EX1 for the altimeter. That certainly seems to be when it started, when I switched to it. Is there anything I can do, or do I have to wait for it to be included in LK8000. Next time I fly I shall go back to Device B being the internal for the iPAQ, and disabled in the Mio. Thanks
Go to Top of Page

TiGuy82
Pterodattilo

Canada
1451 Posts

Posted - 30/03/2012 :  20:18:04  Show Profile  Visit TiGuy82's Homepage  Click to see TiGuy82's MSN Messenger address  Reply with Quote
I don't know if this fix is on the 3.0b or will be on the 3.1a...

www.facebook.com/LK8000
Go to Top of Page

Coolwind
Moderator

Italy
7511 Posts

Posted - 30/03/2012 :  21:48:39  Show Profile  Visit Coolwind's Homepage  Reply with Quote
3.1a
Go to Top of Page

TiGuy82
Pterodattilo

Canada
1451 Posts

Posted - 04/04/2012 :  17:53:12  Show Profile  Visit TiGuy82's Homepage  Click to see TiGuy82's MSN Messenger address  Reply with Quote
Is 3.1a working fine with GT Vario?

www.facebook.com/LK8000
Go to Top of Page

Coolwind
Moderator

Italy
7511 Posts

Posted - 04/04/2012 :  18:05:45  Show Profile  Visit Coolwind's Homepage  Reply with Quote
yes
Go to Top of Page

davesalmon
Pterodattilo

United Kingdom
904 Posts

Posted - 04/04/2012 :  18:23:38  Show Profile  Reply with Quote
I've not been able to fly with it, would you believe 23 deg C last week, now we've got snow. However, tried in the car yesterday, and it all seemed to be OK.
Go to Top of Page

gigicroce
Pulcino

Italy
28 Posts

Posted - 04/05/2012 :  23:43:46  Show Profile  Reply with Quote
Hi,

I had exactly the same problem with LK8000 3.0b Glidertools vario and MIO 400.
During the flight I managed to disconnect the vario but the problem was still there. The device was extremely slow and responded so slow to taps on the screen that it was unusable.
The log file presents a lot of jumps of several seconds and that has never happened with my m400 over Ferrara..
Once landed after a hard reset everything looks ok. never tried again in flight.
The overall impression is like the CPU was overloaded...
I read about a fix in version 3.1a, where can I get it?
may I use the vario with the old release 2.2e?

Thanks in advance

gigi
Go to Top of Page

Coolwind
Moderator

Italy
7511 Posts

Posted - 05/05/2012 :  01:42:32  Show Profile  Visit Coolwind's Homepage  Reply with Quote
You must wait for 3.0c or use 3.1c , at your choice.
Go to Top of Page

gigicroce
Pulcino

Italy
28 Posts

Posted - 05/05/2012 :  08:23:57  Show Profile  Reply with Quote
thanks a lot Paul!
I'll try 3.1c..

gigi
Go to Top of Page

zweidee
Pulcino

Germany
27 Posts

Posted - 20/05/2012 :  15:01:47  Show Profile  Reply with Quote
Hi Folks!

I faced the Problem, that Dave has described, yesterday during a X-Country-Flight!
This is what happened:

I started in Mainz-Finthen (EDFZ, Homebase) to go to Traben-Trarbach (EDRM, Target).
Bearing is 270°, Distance ~75Km. The direct Track leads through the CTR Frankfurt-Hahn (Airspace D @2500ft).
I radioed Hahn-Tower approx. 5Min before entering CTR and D. They cleared the Pass-through and I moved on.
When entering CTR and D the Map freezes and there was only one sign of life from my iPaQ314: the clock in the right corner still worked!

I remembered Daves Probs with this Phenomenon and waited for action from the iPaQ.
All Data (GS, Distance, Bearing, Track, etc.) was frozen.
Fortunately I also have had an ICAO-Map on my kneetable and was therefore able to navigate "the old fashioned way". :-)
Directly after exit of CTR and D, the Map jumped and started to work as if nothing has happened.

This also happened on my way back at almost the same Point to CTR and D, but this time a bit more severe: the SW crashed completely and the Desktop showed up.
This caused the Production of a lot of Adrenaline that day.
Shortly after Landing I tried to access the Logbook and the Runtime.log.
The Data contained in the Logbook was readable but faulty, stating that I have needed almost 99 Minutes for the Trip from EDFZ to EDRM.
Again, fortunately I have a Cam at my helmet, which records the Flight with a visible Timestamp.
This showed that I have needed 47Min for the Trip, which is only 2Min over my Calculation during Planning.
Thanks to the Crash, the Flight back to EDFZ was not logged at all. :-(

The Runtime.log contained no Data with a date of 19.05.2012!
Version is 3.1d.

If you need any Information for Investigation: please mail me.

Kind Regards HPD (D-MHPD)
Go to Top of Page
Page: of 3 Previous Topic Topic Next Topic  
Next Page
 New Topic  Reply to Topic
Jump To:
PostFrontal Forum © 2005-2010 PostFrontal - La community del Volo a Vela Go To Top Of Page
This page was generated in 0.24 seconds. Snitz Forums 2000