-
@Roberto @daniel I have the same issue as brotherdust.
Reading up about the 'struct' I found a commen that in ypython the name if the module has changed - refer point 11:
https://github.com/micropython/micropython/wiki/Differences
I changed the code to reflect 'ustruct' and the LoPys no longer crash and I can still see them with my Pymakr - however they are not connecting..
-
Hi @brotherdust,
A CRC its not required as it is included in the protocol. You can still implement it if you want. I tried this in a project we have running just to make sure and all the checksums are positive
-
Hi @gertjanvanhethof
I'll provide a new code example this week on the blog section that might answer your question.Best,
Roberto -
Hi @brotherdust
This issue is not related to the nano-gateway code, it is a known issue regarding the WatchDog and we will be addressing it soon, i'll keep you informed with a fix for this. -
Hi @brotherdust,
The watchdog problem was fixed in the new firamware version, please download it since this is important not only for the nano-gateway but for all the other apps you want to run as well.
The update is here:
https://www.pycom.io/support/supportdownloads/Please test the nano-gateway code afterwards to make sure that everything is working
Best,
Roberto -
@Roberto
Is it possible to implement some kind of ranging algorithm in LoRa. So that one can calculate the distance between the nodes to the gateway or something along those lines? Thanks. -
time measurement should be then in nanoseconds i believe
you can send signal and wait for receive and calc distance divide time by two ;-) -
@kgadeshi with the RSSI of the received packet and knowing the amount of power that was used to transmit it, the free space loss formula can be used to estimate the distance between the 2 nodes.
-
You might also have a look at these resources:
- An extensive discussion on the TTN forum
- An article by Linklabs stating the issues especially for LoRa (they do have competing products, but the reasoning seems sound)
-
After quite a bit of trial and error I have managed to get the LoPy to "talk" in P2P mode to a Dragino LoRa/GPS hat (which uses the same SX1272 chip that's in the LoPy.
For anyone interested I have posted some more details here and have made the source code for the LoPy and Raspberry Pi available on github.
-
This is extremely exiting, since I have exactly the same hardware! I hope I'll have some time this month to test your code, @Xykon, and make the bits fly.
-
Hello.
It would be great to get a proper tutorial on how to do a http request from a lora through a nano gateway.
I backed you in KS because you made a big point of making this possible. It is great to have the device. But really not very user friendly at all. And you are already launching a new one with more radios. Yet you still have not make LoPy work as promised.
Please help!
Thank you!
Angel
-
Ditto. What's LoRa without a gateway!? Time for proper documentation on this product feature.
-
@angel-imaz please see my post here:
https://forum.pycom.io/topic/98/lopy-as-lorawan-basestation/20
Our team is working on examples and there will be in the docs soon. If you need a HTTP client library, please try this one out: https://github.com/micropython/micropython-lib/tree/master/http.client
-
A good way to test it:
2 Lopy's with PymakrBoard connected on 2 usb ports
2 instances of Pymakr -
Hi,
I test this sample but after about one hour of working i get "ValueError: buffer too small" on nano gateway. Any clues why?
Firmware: (sysname='LoPy', nodename='LoPy', release='0.9.7.b1', version='v1.8.6-234-g765f2bc on 2016-12-02', machine='LoPy with ESP32')
Best Regards
-
@microman7k Hi, first of all you should update the firmware of your Lopy.
-
@Oneillsite On the latest firmware (1.0.1.b1), results are even worse. After one event i get:
execfile('nanogw.py')
D: 1 P: b'22.5'
E (200196) wifi: error malloc bcn_paramTraceback (most recent call last):
File "<stdin>", line 1, in <module>
File "nanogw.py", line 20, in <module>
ValueError: buffer too small -
@microman7k i can't figure out why the message mention "wifi"...
-
I have been playing with it, actually receiving the packets on a Raspberry Pi with a Dragino Lora+GPS Hat and it works. (The "hat" is based on the SX1276).
There is a possibility of making an ugly hack in order to support multiple channels for a gateway. It wouldn´t be a multi channel gateway, but a channel hop capable gateway :)
The trick (I'll try next week) is to use the CAD functionality. Given the length of the prefix it may be possible to do something like this:
-
Set frequency
-
repeat
CAD
if CAD_DONE // this means timeout
next frequency in list
until CAD_DETECTED
. receive packet
It may be a bit tight, but it should be possible to monitor three frequencies. I'll get back with the results.
-
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login