It's finally here! It's the first video on the Meshtastic on Native Linux! This guide takes you from zero to meshtasticd hero. meshtastic.org... www.waveshare.... www.buymeacoff...
It looks like MeshtasticD is exactly what im looking for for a base station. Simple to run POE up a mast/tree/tower, control it on the network, and easy to update it from the ground. Everyone seems so preocupied with the low power devices, but having a network controlled base station is key.
Hey Jonathan, thank you for all your hard work and dedication. I'm presently setting up a Meshtastic network in my area for the purpose of alarm based pagers for our small industry.
Thanks. One off topic: You don´t need to be shy with microphone gain (in editing soft its supposed to be "almost but never" touching clipping range). Best to adjust before recording. Its no huge issue but you can be a bit "louder". Great videos :)
I disagree, respectfully though. I have to adjust each video when playing back anyway, so I like to be able to crank it up to get that dynamic range. Even though it’s “only” speech he comes off clearer to my ears anyway. Can’t please everyone lol!
@@witchdoctor88 there's no discussion about proper gain settings, everyone does it same way, it has nothing to do with sound quality. Some other creators can over gain sound- there is your clipping experience.
I have already edited the boot, and config.yaml file. Do I need to enable "Enable the internal GPS module" within the meshtatic web server to enable GNSS ? This setting will not remain enabled.
I'm not the only one. I'm not sure if the UI actually needs that flag enabled. On an RPI 3b+ w/ brand new install of raspberry os 64-bit lite (bookwork), and recommended /etc/firmware/config.txt settings (dtparam=spi=on, dtoverlay=spi0-0cs, & enable_uart=1) the logs indicated that meshtastic couldn't communicate with the L76K GNSS module (failed iteratively on increasing baud rates). I noticed the GNSS module docs recommended disabling login shell over serial, while leaving serial port hardware enabled via raspi-config (see link). After setting that and rebooting, the Meshtastic logs at least show the GPS module is initializing, but there's no GPS lock. Whenever another nodes exchanges position data, it's showing lat=0 and long=0. And no matter what the UI won't keep GPS Enabled = true in the web ui. www.waveshare.com/wiki/L76K_GPS_Module#Enable_UART_Port_.28Skip_if_enabled.29
The zero two is much easier to set up, and performs great. The original zero requires some compiling, but once all that stuff is done, it's been reported to work as expected, too.
Hi There, followed your instructions and the device is working great, except for one thing. i cannot get the device to show (BLE) via the iOS app... tried many different versions of debian and i have the waveshare hat... all is good, but cannot connect from phone iOS app.... just does not show up. Any hints?
No BLE support for Native yet. I've spent a little bit of time working on it, and it's a bit tricky to get the BLE chip in the right mode to even show up as a compatible device. Still hope to eventually get it working.
