Lopy with pytrack, how connect/use GPS?

[seb]

you typed that in wrong, its py not pycom

[zceld]

@seb yes! Sorry, as I gave an error I was trying and I sent you a test here you have the complete test.

You will also have to apologize for taking a long time to answer the forum, it does not allow me to respond faster.:

[seb]

I upvoted some of your posts, the limit should now be much shorter.

ok sorry, can you try running this instead:

from pytrack import Pytrack
py = Pytrack()
py.read_fw_version()

[zceld]

@seb
Thank you very much for all the support, I have made the indicated and I keep saying the same.

[seb]

Ah, thats annoying, because the error happens when trying to create py and fails we cant then use it later. I am afraid you will have to edit the library some more:

            if self.read_fw_version() < 6:
                raise ValueError('Firmware out of date')

to

            if self.read_fw_version() < 6:
                raise ValueError('Firmware out of date (Version: {})'.format(self.read_fw_version()))

I will make some changes to the library on github once we solve this to make this easier in the future.

[zceld]

@seb
I am also trying to update from this PC again as I mentioned and it is a Mac, but this command that indicates the guide does not accept it:
https://docs.pycom.io/chapter/pytrackpysense/installation/firmware.html

I update this part above to show you that I finally got back to update the board through the Mac:

<-------------- current topic: ------------------->

Well I have made the changes, updated the file in the pycom.
I have tried again the previous and even the main.py but it still fails. I will also try to update the pytrack with Mac.

@seb said in Lopy with pytrack, how connect/use GPS?:

if self.read_fw_version() < 6:
raise ValueError('Firmware out of date (Version: {})'.format(self.read_fw_version()))

[zceld]

@zceld

okay! it seems that the update of the pytrack was not effective for windows despite the screenshot showed that yes, because now at least we can call the class Pytrack ().

The problem when running the main.py that in my case is called main3.py but that it is the same program as this one:

Well now the fault is as follows:

At least we have already advanced! ;-)

[zceld]

@zceld

It seems that at least you have tried a couple of times, get the coordinates!

After I forget this, I would not know how to fix it:

Afterwards he does not let me try it anymore:

[zceld]

@zceld
Well finally it seems that with this code at least try to get the GPS coordinates.

On the other hand now comes another problem and it seems that it runs out of memory. What do you think? the idea of operation is to collect the signal from the gps of a vehicle and send it to LoRa. I understand that if it is due to lack of memory, it will be necessary to program something to clean the cache or something that increases when using the program, not?

CODE:
import time
from L76GNSS import L76GNSS
from pytrack import Pytrack

py = Pytrack()
l76 = L76GNSS(py, timeout=30)
while (True):
coord = l76.coordinates()
print(coord)
time.sleep(1)

I am waiting for new news. Thank you very much for your patience

[zceld]

@zceld

I am happy to inform you that with this code I have at least managed to obtain coordinates without failure:

Code:

import machine
import math
import network
import os
import time
import utime
from machine import RTC
from machine import SD
from machine import Timer
from L76GNSS import L76GNSS
from pytrack import Pytrack
# setup as a station

import gc

time.sleep(2)
gc.enable()

# setup rtc
rtc = machine.RTC()
rtc.ntp_sync("pool.ntp.org")
utime.sleep_ms(750)
print('\nRTC Set from NTP to UTC:', rtc.now())
utime.timezone(7200)
print('Adjusted from UTC to EST timezone', utime.localtime(), '\n')
py = Pytrack()
l76 = L76GNSS(py, timeout=30)
chrono = Timer.Chrono()
chrono.start()
#sd = SD()
#os.mount(sd, '/sd')
#f = open('/sd/gps-record.txt', 'w')
while (True):

coord = l76.coordinates()
#f.write("{} - {}\n".format(coord, rtc.now()))
print("{} - {} - {}".format(coord, rtc.now(), gc.mem_free()))

Result:

Thank you very much to all of you who have had to endure my clumsiness and have helped me especially: @seb and @livius, include @crumble ! :-)

taking advantage of the post with the doubts and problems that I have had, I will shortly upload a guide in Spanish (since it is already in English) on the subject to facilitate other people.

[olliec]

@zceld I appear to be having a similar issue that you were having, with a LoPy4 and PyTrack.
My error however is "I2C bus error"..

I've updated the PyTrack to 0.0.8 (tried via Windows 10 and Debian) and LoPy4 to 1.14.0.b1, ran "os.mkfs('/flash')" and re-uploaded the files from a ZIP download of the Git (https://github.com/pycom/pycom-libraries).

This is what I get (I added the "print(e)" in pycoproc.py which is returning "I2C bus error"):

@zceld - was there anything else you did other than update PyTrack via your Mac?!

[zceld]

@olliec said in Lopy with pytrack, how connect/use GPS?:

was there anything else you did other than update PyTrack via your Mac?!

hello, well, you'll see that the only thing I did was really update, I attached the screenshots of what I did. I honestly do not know why you can fail, surely you can get a hand those who really know. The teachers who have guided me.

Screenshots:

Greetings, I will be here attentive to your problem to know how it is solved. luck.

[olliec]

@zceld :( yeah I think my error is different.. I'll start a new thread. Thanks anyways!

[zceld]

@olliec good luck!

[seb]

Hi,

I'm glad you got it working! The out of memory issue is a known problem with the GPS library on our older devices that have less RAM. This is due to the large amount of string data that needs to be processed. The advice is to retry a few times and once it gets a lock it will start working. This library will need to be improved in the future to try fix this.

It is very interesting that the update via windows didnt work but via mac it did, I will pass this on to the rest of the team.

Thanks,
Seb

[zceld]

@seb
Good afternoon, I just got back on.
Seeing that happiness is not forever. Since today again I have not managed to obtain GPS coordinates. I'm back in Windows, I'll mention it, but I do not think the problem comes from here. The story is that he always runs out of memory.

Is there anything I can do ?

[zceld]

@seb
Apart from the memory issue, I do not know how to solve it. I have other doubts to see if you can help me:

• Every time I run 'gc.mem_gree ()'. Am I occupying memory? More than anything because as you can see in the image is going down the amount of free memory, until I run 'gc.colletct ()' that seems to empty the cache. It is right ? Image:
  

-On the other hand, executing 'gc.collect ()' and then executing this code to obtain the coordinates, it seems that I avoid the full memory error, but instead it always stays that way and does not continue until I cancel. The doubt is that I do not know if it is because it does not find GPS today or what happens ...
code:

import machine
import math
import network
import os
import time
import utime
from machine import RTC
from machine import SD
from machine import Timer
from L76GNSS import L76GNSS
from pytrack import Pytrack
# setup as a station

import gc

time.sleep(2)
gc.enable()

# setup rtc
rtc = machine.RTC()
rtc.ntp_sync("pool.ntp.org")
utime.sleep_ms(750)
print('\nRTC Set from NTP to UTC:', rtc.now())
utime.timezone(7200)
print('Adjusted from UTC to EST timezone', utime.localtime(), '\n')
py = Pytrack()
l76 = L76GNSS(py, timeout=30)
chrono = Timer.Chrono()
chrono.start()
#sd = SD()
#os.mount(sd, '/sd')
#f = open('/sd/gps-record.txt', 'w')
  while (True):
     coord = l76.coordinates()
     #f.write("{} - {}\n".format(coord, rtc.now()))
     print("{} - {} - {}".format(coord, rtc.now(), gc.mem_free()))

[livius]

@zceld

Apart from the memory issue, I do not know how to solve it

use simple fix for this
https://github.com/pycom/pycom-libraries/pull/43/files

[zceld]

@livius said in Lopy with pytrack, how connect/use GPS?:

use simple fix for this

This solution and you told me about it and the thing is that you have to replace lines 74 and 75 with the lines that are in green, right?

[livius]

@zceld
Yes, but you have indentation problem
remember that python work on proper indentation.
nmea line must be indented