Lopy with pytrack, how connect/use GPS?

[crumble]

@zceld

If you have something like

while True:
    result = s.recv(256)
    print(result)

and you run it in setblocking(True) mode, the program will wait on the line result = s.resv(256) until it received a message and will then continue. So result will always contains someting you received from the aether. Either from your LoPy or another device. So you shall not forget to check the content before controling some other hardware like servos, etc.

if you run the same loop with setblocking(False) it will not wait. It will directly go to the next line. So you will most of the time get your empty lines, because no one has send someting.

You can use this for easy control your program. If you want to open a door when someone sends a message you will use setblocking(True)

s.setblocking(True)
while True:
    result = s.recv(256)
    if result.equals('Open door'):
         OpenTheDoor()

If you use this with setblocking(False) it will not be that dangerous, because the if guards the door unless someone sends the right message. But it will use a lot of power, because it will run the loop without any pause. This can be really bad, if you run your device by battery. So you may have to charge your device every day instead of once a week,

If you want to stop something when someone sends you a stop message you would to something like this:

s.setblocking(False)
stopMessage = ''
while stopMessage != 'stop'
    toggleLED()
    stopMessage = s.recv(256)

setblocking(True) would be a bad idea, becaus the recv call would wait until someone sends a message. So your LED would change only its state when someone is sending a messages. With setblocking(False) you will see it blinking until someone sends the right message.

[zceld]

@crumble

Thank you very much! , very kind, you got me out of doubt.
There would be a way to program it to stay listening in mode:

x = "no messages"
s.setblocking (true)
data = s.recv (256)
time.sleep (20)

if data! = ''
    print (data)
else
    s.send (x)

In plan, be listening if there is any message for 20 seconds. but at the end of this time, make another function and then listen again.

[crumble]

@zceld
this code will wait infinite for a message and wait additional 20 (milli?)seconds. If you want to use blocking sockets, you have to set the timeout for a socket. I never used them by myself. Browse in the documentation for:

socket.settimeout(value)

Or you use it as nonblocking and use the receive together with the sleep in a loop.

[zceld]

@crumble
On the subject server, I had this code that I would say that I used to run and be able to access Lopy via Filezilla FTP but today it does not work for me.

There may be something I'm missing or what can it be?

import network
import time
from network import WLAN
# setup as a station
wlan = network.WLAN(mode=network.WLAN.STA)
wlan.init(mode=WLAN.AP, ssid='Gateway', auth=(WLAN.WPA2,'witeklab@2018'), channel=7, antenna=WLAN.INT_ANT)

[zceld]

@crumble @livius @seb

Recommendation of the process to be programmed (I am noob):
Ok, I explain the situation. With the chip Lopy and Pytrack I pick up the gps position of a vehicle and send it through LoRa to another board located at home that collects the data by LoRa and saves it to me in a file.txt.

From the board at home I have activated server mode to connect by FTP and download the file.txt that is accumulating positions and that I download on my computer and from a file.php that saves the data in an array to track .

So I know how to do it like that, but it's a tedious job to have to connect, download the file. the ideal idea would be to automate it but I can not think of how.

I do not know if I could program by php / JavaScript or any language that will connect to the FTP of the Lopy every 'x' time and download and read the file atomically or vice versa that Lopy will send an IP of the network that connects this file every some time.

What do you recommend or what options can I take to automate the process?

Thank you very much as always you are fantastic !.

[livius]

@zceld
Recomendation is that lopy connect to your server and send data to it

[zceld]

@livius

Hello again! What's going on? I upload the thread to ask some questions.
Can I assign an ip address in server mode?
I have this configuration / programming to put in server mode:

import network
from network import WLAN
wlan = network.WLAN(mode=network.WLAN.STA)
wlan.init(mode=WLAN.AP, ssid='Gateway3', auth=(WLAN.WPA2,'witeklab@2018'), channel=7, 
antenna=WLAN.INT_ANT)
from network import Server
server = Server(login=('micro', 'python'), timeout=600)
server.timeout(300)
server.timeout()
server.isrunning()

The documentation that I have looked at is this but I have not found the ip theme:
https://docs.pycom.io/chapter/firmwareapi/pycom/network/server.html

I also take the opportunity to ask another question and it is: When I connect the lopy it automatically creates a wifi network to connect to it but with an SSID I guess random. In what loop file is this process? Can this operation be canceled? where are the initial programming that makes the default lopy and if it can be modified?

The reasons for knowing this is because I do not want to start the Wi-Fi automatically in some Lopy apart from that I would like to know what other things it executes or puts in on mode independently.

Thank you for your answers! I wait impatiently!

[livius]

@zceld
IP can you set in the wifi configuration
look for Assigning a Static IP Address at Boot Up in documentation
https://docs.pycom.io/chapter/tutorials/all/wlan.html

you can disable wifi by

wlan.deinit()

or permanently - it does not start automaticaly at board boot - call this once it is stored in nvs

pycom.wifi_on_boot(False)

if you disable it permanently you have full control when and with which ssid it start

[zceld]

Hello again! I have a new problem and I do not know why it may be, I have been reading several that have published similar things but I do not see what happens to me, so I will try to reflotar my thread of questions ..

Vereís wanted to edit the main.py file that had lopy running every time I plugged it. Therefore I take the board I connect it to the pc I open the IDE atom> get serial ports, I copy the path where it has been connected. I go to global settings to indicate which port to connect to and give the connect button.

Up to here are the usual steps that had always worked for me. Well when I connect I see that it is in the loop of the main.py file when it is like this to stop it, it always stops cntrl + c and it stops. This time there was no way to connect to Filezilla and I deleted the main.py file and at least I managed to connect again with LoPy in this case just enough to run os.mkfs ('/ flash') to see if it gave me back control with lopy.

Well now it does not let me connect by the IDE Atom I do not know what happened ... I can only connect by example with putty by telnet ..

Do you know what I can do or what is due?

[seb]

@zceld

I often see an issue like this when I have another atom window/tab open that is also connected to the same serial port. Can you make sure nothing else is trying to access the serial port?