I do not see console=serial0,115200 in cmd.txt. I see console=tty1
If you installed my hackergadgets package then it was already removed.
1 Like
What a difference a beauty sleep makes… or maybe it was the fresh install of bookworm! Thanks Rex (and Vileer). Slowed myself down, and did it right this time. All is working except possibly GPS with the meshtastic app. PyGPSClient is working so GPS should be good. Thanks again!
1 Like
You need to make sure you enable GPS in the meshtastic web settings for it to work.
If you are using MUI,click on the GPS symbol and it will reboot. GPS will be enabled once it restarts.
1 Like
It is enabled … does anything need to be done in position config other than enabling? Pin assignments?
No, my package handles those configs.
Ok… the dust has settled, everything is operational (it seems), but still have an issue. Likely more of a meshtastic one, but thought I would try here first.
I have two other meshtastic devices… the Heltec V3 and the sensecap T1000E. When I fire up mestastic on the uConn, it is not picking up those nodes.
Any idea’s beside operator error?!
Hmm, sounds like you have more experience than me with Meshtastic already. So i guess you already confirmed the uConsole is on the same region/frequency as the other devices?
check region, and channel settings on the uconsole and check that the other nodes are also up to date.
All settings are in place correctly and mimics my other nodes.
Region: US
Channel: LongFast
Role: Client
All nodes running: V2.6.11
It was not ! I can now see 2 of my 3 other nodes that are live from UConn. Thanks!
1 Like
I am tracking mine and it’s still in customs since the 5th. I am not sure why I haven’t gotten it yet.
You can give me the order number, I will look into it.
Yes. Thank you. 3278
Benjamin
Ok, I will contact the carrier next Monday.