@jcaron thanks for pointing to this informative thread! I've looked through the library code as well, very informative. In addition, I spent half a day reverse engineering the connections and looking up cryptic SMT markings for the undocumented parts on the board (TPS78233 LDO, BQ24040 Lipo charger, TT8J13 dual P channel FET).
Thankfully I don't need the low power capabilities of this board (I need an active WiFi connection), I only need the sensors, so this simplifies things.
Let's hope Pycom releases the secrecy around this board and published PIC source code and schematics.
Update: Sigfox confirmed it's 1 year now:
Still not a bad deal I think, as 1 year's worth is still about half the price of the LoPy4. But it would be good to clarify this on the website.
For starters, you could use the Pysense board (which has a light sensor and a basic driver) and the AWS example to push the data to AWS IoT. This should work out of the box.
What you do in AWS IoT is another topic.
@ahmedach At the moment we offer the Smaller IP67 Case for Pysense/Pytrack. We are looking at options for a universal IP67 case but don’t yet have any committed timelines for this. The earliest we could deliver this would be late Autumn but there’s a good chance it will be pushed into next year
Thanks @alejandro !
I see that the Contributor link was fixed -- now I understand why I was using the CLA in the wrong repository.
I've redone my pull request after signing the CLA.
@jokr2 Hi, in fact i doesn't understood what do you mean.
LoraMac allows you to send data using lora radio modulation, this radio layer doesn't have ECC.
LoraWan is upper protocol used by lot of gateway and have only a MIC field in frame (Message Integrity Control), i doesn't allow correction, only detection of altered frame (and AES used in lorawan is only used for encryption).
If you use LoraMac mode you have to add to your data payload your ECC code by your own.
Finaly, if you want to have your ECC added to all frame send by your socket without explicitly add ECC in python code (but it will added on lower layer in C code), you can build your own custom lopy firmware (instruction is present in the forum)
Hope this help you
@pas We have KiCad footprints available on GitHub https://github.com/pycom/footprints
All our development modules have the same footprint so if you have one for a WiPy2, LoPy or SiPy etc (NOT WiPy/WiPy1) then that will also work with the FiPy.
We also have Altium design files for the Universal Expansion Board https://docs.pycom.io/chapter/datasheets/oem/universal_reference.html which for the headers uses the same footprint as the FiPy (it fits into the expansion board the same way).
@bmarkus said in How to transmit every 30-60 seconds data from LoPy:
@rcolistete said in How to transmit every 30-60 seconds data from LoPy:
LoRa or LoRaWan ?
Regulations are the same for all devices independtly they are LoRa, LoRaWAN or other ISM devices.
To know the packet size = payload + LoRaWan header/etc (typically 13 bytes).
LoRaWAN is using a non-licensed shared frequency band. As long as you meet local regulations, e.g. in Europe max. 1% transmit duty cycle, do not exceed transmit power and bandwidth limits you are safe. It is not about LoRaWAN it is about local radio regulations. These rules are the same for single and 'normal' multi channel GW's.