-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for arm64 Raspberry Pi #22
Comments
Subscribed. Thank you Chris! I guess I should have just said arm, not sure if changes things or matters. I'd be perfectly fine running 32bit OS if possible since it would be the Pis only role to run MeshSense and talk to a rooftop node over IP. Either though way thanks for this awesome application! I am loving it! |
I'd love this as well. Especially if it can be headless and running in the background. I'd just simply use the Web portal at that point. See also: #8 |
I'll admit this is surely NOT elegant. I'm not using BT to connect to my node, and only access via WiFi IP. To that extent I've hacked a few of the "api" related .ts files to bypass or ignore some of the BT functions. I simply ran the code and commented out sections until I could get a response on http://localhost:5920/ I've not extensively tested MeshSense doing this, but the attached screenshot shows its at least working to an extent on my RPi 4. Maybe a 'diff' export could be made or possible a #ifdef block for "noBT" to accomplish the same. Aside from having to 'apt-get install' cmake and ninja-build, here are the changes made to some of the MeshSense files prior to starting the api and ui pieces with npm. in api/packages.json
in api/src/meshtastic.ts
lines 54-58 rewrite as:
in api/src/lib/bluetooth.ts
Happy hacking! Mesh node K1RA |
That's awesome! I would anticipate MeshSense to largely work without issue. It was originally built with IP-only and bluetooth was added later. Only thing that stands out to me are the lack of traceroute lines in the screenshot, but the connected node is not reporting a position so that could be part of the reason. This brings up an interesting question of whether or not to provide an official ARM build with bluetooth functionality disabled. Thanks for sharing! 👏 |
A few requests have come in requesting to run MeshSense on a Raspberry Pi. This should be possible, in theory, although the
webbluetooth
library does not have a prebuild currently for arm64. See thegecko/webbluetooth#190Will need to look to see how a build would be accomplished manually.
The text was updated successfully, but these errors were encountered: