You need to downgrade the PlatformIO core to version 6.1.6 or lower. Probably using pip uninstall platformio and then pip install platformio==6.1.6.
@Crichton He’s using an older branch where these changes weren’t applied yet, so it only works with an older version of the PlatformIO core.
still tryng without errors
I am sorry, still not having success! I really dont know what i am doing wrong!
Can you someday help me to access my manchine ? 
I pushed a new commit to the branch LoRa-e5 to make it compile with newer versions of the PlatformIO core. Can you try again after you did git pull in that branch?
git clone GitHub - GUVWAF/Meshtastic-device: Device code for the Meshtastic ski/hike/fly/customizable open GPS radio
cd Mes…
git checkout LoRa-e5
git pull
This sequence…or something optional ?
That’s correct. But if you already cloned it, only doing git checkout LoRa-e5 and git pull is enough. You can check with git log if the last commit is from today.
gotcha! :):):):):)
Some questions:
a) This ?
b) Must the Console wait for a AT or similar command to get some result ? looks that is freeze…or, uses other UART…
c) where do you define your Region ?
LOOKS THAT SOLVED!
Mine will be AU915
void initRegion()
{
const RegionInfo *r = regions;
for (; r->code != Config_LoRaConfig_RegionCode_UNSET && r->code != Config_LoRaConfig_RegionCode_ANZ;
r++) // TODO remove hardcoded region
;
myRegion = r;
LOG_INFO("Wanted region %d, using %s\n", config.lora.region, r->name);
}
d) i have more STM32WL55 to make the MESH :), i will need some help late
meshtastic cli installed
I powered other module…looks that there is communication between them!
How can i send a example of message between them ? (still testing)
Thanks for you help!
a) Yes, that output looks correct.
b) Meshtastic doesn’t work with AT commands. Since the STM32WL doesn’t have Bluetooth you have to use the WebUI or Python CLI over serial (or the Android app with USB OTG cable).
c) Yes, that is the right place. If your region is Australia & New Zealand you set it correctly.
d) Yes, they indeed did already find each other. There is a lot of information on the web, just take into account that your devices don’t have a working file system, so all settings will need to be hardcoded.
making communication, slow, but making
do you know if possible to send messages without use the WEBUI or Python CLI ? I mean, the user embedded their application into STM32WL55…and the message comes from into STM32WL55, not from outside…
I’m not sure what kind of application you have in mind but there are some modules, e.g. the Telemetry module that sends device telemetry and can be used to send sensor data by the device itself. If needed, you can create a module yourself.
But be aware that you are running an older firmware without filesystem on an unsupported board, so it’s likely a lot of the functionality won’t work.
yes, telemetry!!!
Thanks to the Module link!!!
Yes, i agree, it´s a older firmware…just to test for now on our STM32WL55 module that we represent in south america…and write a blog (with your glads)
Where do i setup the PAN ID of my Mesh Network ?
Or the difference is the channel used ?
Some news about FS on stm32wl55 ?
Unfortunately there’s no progress yet.
Hi there,
Could you try, in HEAD/2.3.6 to uncomment and set accordingly this line in src/configuration.h?
// #define LORA_REGIONCODE meshtastic_Config_LoRaConfig_RegionCode_SG_923
You should be able to boot fine thereafter. You can also set this in the build environment for your variant/board.
I’m quite curious if this works for you, because I may purchase some STM32WL-based boards and hardcode device mode as ROUTER to use as a router.
Works on stm32wl55, but you need to solve the flash store config…
Little FS
See topic about, duscussion
Hi how should i port stm32wl55jc, which configs need to change to work with Wio-e5 code?
try the same of my blog
MÓDULOS E KITS LoRa/LoRaWAN, LoRa MESH - PRIMEIROS PASSOS: LSM110A MESH - Meshtastic (lom204-cli-wisol.blogspot.com)
