Pymesh wishlist

[catalin]

Hello community 🙌,

We would like to collect here the wishes for the Pymesh - LoRa based Mesh networking.
Last release v1.20.1.r2 (3rd Nov 2019).

Features:

1. Sending data on socket to multicast IP address(groups) as briefly explaine by @CAPKE here
2. next one ?!?

[Danne]

@catalin

Is Pymesh still under development?

I wish to have the issue with running out of buffers resolved :)

Problem:
After a while nodes are unable to send data to each other.

To reproduce, start up two nodes, send message until you run out of "free buffer", to check available buffer, run buffer info...

[catalin]

This post is deleted!

[thinginnovations]

@catalin That works. Now I can reflash firmware on a mac.

Thanks

Andrew

[catalin]

@thinginnovations

Using latest pycom updater (1.16.1) and I cant seem to select tar.gz files from the file list when using the Flash from local file option. All the files are greyed out and unselectable.

If you still have this problem, it can be easily sorted by renaming firmware package .tar, instead of tar.gz. We're looking into it.

[thinginnovations]

Finally got around to reflashing the firmware on a few LoPy4 devices. Seems 1 repeatedly guru mediates. I used a windows laptop to reflash, gave up on the Mac.

Next question for @catalin , when will the L01 firmware be available or can the Lopy4 firmware be used on the L01 ?

thanks

Andrew

[andreas]

@thinginnovations said in Pymesh wishlist:

Using latest pycom updater I can't seem to select .tar.gz files from the file list when using the Flash from local file option. All the files are greyed out and unselectable.

I believe someone from our community also reported this recently. I couldn't believe it.

@catalin said in Pymesh wishlist:

This is due to newest application rights in macOS Catalina.

Thanks for letting us know about this detail, @catalin! Bummer.

---

@thinginnovations: Maybe invoking the programm from the command line still works for you like

Prepare

alias pycom-fwtool-cli='/Applications/Pycom\ Firmware\ Update.app/Contents/Resources/pycom-fwtool-cli'
export MCU_PORT=/dev/cu.usbmodemPye090a1

Invoke

pycom-fwtool-cli --verbose --port $MCU_PORT flash --tar FiPy-1.20.1.r1-0.7.0-vanilla-dragonfly-onewire.tar.gz

[catalin]

@thinginnovations This is due to newest application rights, in Catalina. (Try System Preferences/Security&Privacy/Full Disk access).

Could you make a new topic in https://forum.pycom.io/category/17/software-tools and maybe the community has the solutions.

[thinginnovations]

Using latest pycom updater (1.16.1) and I cant seem to select tar.gz files from the file list when using the Flash from local file option. All the files are greyed out and unselectable.

This is on Mac OS Catalina.

Any ideas?

The file received did not contain the L01 firmwar images, only for FPy and Lopy4.

Andrew

[thinginnovations]

Got it all now, thanks @catalin

[thinginnovations]

no reply yet.

[thinginnovations]

@catalin
ok, form sent back.

Thanks

Andrew

[catalin]

@thinginnovations hi Andrew,

I'm not sure what you mean. After signing the licence, you'll receive the firmware binary (for Lopy4 and Fipy) immediately.

On the long run, more features and bugfixes will be added to the Pymesh release, probably you'll receive updates automatically (the process is under implementation now).

At some point, Pymesh firmware flashing (and licence signing) will be done within the Firmware Update Tool.

[thinginnovations]

@catalin Thanks, I'll give it a try.

What is the timescale for getting the updated firmware after jumping through the licensing hoops?

Andrew

[catalin]

@thinginnovations fyi, as explained here the sleepy end devices was implemented using a simple pymesh.end_device(True).
For the ref, this is in v1.20.1.r2.

[thinginnovations]

@catalin This is my understanding, the edge nodes don't route traffic, they are like the leaves on a tree - at the very edge.

I was originally looking at the definitions at https://openthread.io/guides/thread-primer/node-roles-and-types

Cheers

Andrew

[catalin]

@thinginnovations Thanks Andrew, for suggestion.

Could you be a bit more exact of what do you expect?

I am thinking, that a certain node (connected within a Pymesh network), can be forced to a Child role, so it can go to (deep)sleep as much as it wants. When it wakes up, he will take its old role back (look for the same parent, if not found connect as Child to a different Parent), important thing is that he won't affect the Pymesh. Being a Child he won't relay/route packages.

Then probably for some nodes, an opposite feature (always Router role) needs to be created, right? So these nodes, would always (most of the time) be active, and they will be designated Leader/Router role with a higher priority.

Let me know what you think!

[thinginnovations]

Sleepy edge nodes.

Andrew