#Femtofox - Tiny, low power Linux node!
1 messages · Page 5 of 1
@polar ingot can you guys do ls -l /opt/contact/ and make sure perms arent borked?
also may as well do ls -l /opt
i have a tinysa thats been sitting around a couple years... how would i use it to make that same graphic? i assume thats the pc app you can use with it?
There is no main.py anymore.
#1302945239689990185 message
I used an iOS App called RFforAll but the TinySA does a very similar graphic. I just followed the Comms Channel setup guide and then tweaked a couple settings
I ended up uninstalling it from the SFC manager, and just "pip install contact" and then after reboot it runs with "contact"
femto@femtoFox:~$ ls -l /opt/
total 8
drwxr-xr-x 6 root root 4096 Apr 11 18:03 control
drwxr-xr-x 2 root root 4096 Mar 14 08:23 ttyd
Probably because I installed with pip
which'll install it in /bin or something. the /opt version is broken
Though python3 -m /opt/contact might work?
We've got it on the to-do list to fix
anyone able to review the PRs I put up on the femtofox repo? I have one more to enable the modules for a nftables firewall that I just finished testing yesterday. just waiting on the tun PR for that
got my wires and connected it them. Out of curiosity enviroment sensor data isnt in yet?
I have hooked the bme280 and it shows it but not in meshtastic app
have the settings on the fox set up and waited 1h with a reboot and still nothing
Not supported at the moment 😦
See discussion here and following for the current state of the art:
#meshtasticd message
Tldr: Arduino translation via glue is needed, or something external and inject it in.
Tbh, I was hoping once we got a critical mass of Linux natives, someone would step forward and make something 😁
We built the fox.
Now we need a baseball team to show up and finish off feature parity.
Smol solar node? Very tightly crammed with an 1800mah lifopo4 battery, LiFePO4wered solar1 mppt board
This one have the ra62
Wish there was a way to monitor the batt voltage 😕
You can use a 3:1 voltage divider on one of the saradc pins, and read in that way.
can meshtastic see it like that?
No, but you could probably run that particular bit of telemetry through a chron job quite easily (he says)
heh, I refer you to the "field of dreams" comment above
While I hope the C folks will some day add the glue for sensors, I do have python code that can send telemetry, and I assume collecting that from i2c wouldn't be impossible.
If that is something that is desired?
I'll have a look around.
More and more every day.
Although in this case, it would be collecting it from an ADC pin
Would this interfere with "normal" client usage of the node?
or would it do what we suggested in #meshtasticd and just make the figures available somewhere the firmware could read from?
No client connection needed. It would pretend to be your node and send a telemetry packet over UDP.
something like this
send_environment_metrics(
temperature=23.072298,
relative_humidity=17.5602016,
barometric_pressure=995.36261,
gas_resistance=229.093369,
voltage=5.816,
current=-29.3,
iaq=66,
hop_limit=5,
node_id = "!12345678"
)
how much effort would it be to package this in a configurable form?
I meant setting the "source" for each of these?
I haven't tried to get a value from an adc pin in python yet...
Guess I'm staying up late tonight.
careful tickling the ADC pins
I kept crashing mine with that
but I could read off the values using the methods they suggested
shoot, i gotta feed the kids. I'll dive in later.
No hurry, really!
We've survived this long, a little while longer isn't going to hurt.
# Read the CPU temperature
with open('/sys/class/thermal/thermal_zone0/temp', 'r') as cpu_temp:
telemetry_data.environment_metrics.temperature = int(cpu_temp.read()) / 1000
I also remember crashing went INA3221
whats the command to update meshtastic to the newer version?
Does the fox include X11?
Presume you mean gui? Not afaik.
If you haven't already found it, there should be one in the sfc menu.
didnt see at first but rechecking and yeah it is there
It doesn't pull from the alpha branch, but there's a request in for a switch.
whats the progress on the other mesh software?
but yeah i2c on meshtastic would be way better
Which other software?
the uk one. its by my capital taking some interest and compared has good routing
https://meshtastic.lv/join/ the map
its still building the update. jup its a snail fox
Is that domain allowed? Feels like that'd violate #trademark
dont think it is allowed
its been this for 40min now
huh whats meshbot doing since it comsules so much when compared to before
I have the script functioning mostly. I just can't for the life of me figure out how to get the cryptography package installed on a fox.
pip install cryptography uses Rust for reasons. (compile, not runtime)
searches suggest I may be able to download a pre-compiled wheel but I haven't figure out the right commands.
so with 2.6.4 update done the settings reset and cant set my region well I set it but doesnt save
Hmmm
It feels like it shouldn't be allowed, but I can't say why 🤔
Try deleting the default Femto config in config.d
where is that located
Nowhere near enough ram for that out of the box. With enough swap you could but I think youd have to compile vesa drivers into the kernel? Hmm I might look into resource requirements for X11, and maybe XFCE specifically...
Theres a PR to fix this which hasnt been merged yet
@mild hare
well I got it now, the meshbot was slowing down the cpu
https://wiki.xfce.org/minimum_requirements
Looks like 512MB generally however Slackware is able to do it with 128MB so I wonder
emmm
last time there where a bunch of files
Yes so that the only active yaml is /etc/meshtasticd/config.yaml (not being overwritten/interpolated with femto_config.yaml as well)
did that and set the region and still unset
Have you got a config in there for the radio?
Yeah you need to have something from available.d in config.d (such as lora_femtofox_sx1262TXCO.yaml or whatever)
With Foxbuntu or Linux native?
just in case did apt upgrade and the startup script
Foxbuntu, to fix apt by removing repos that (ostensibly) arent being used
hmmm
Whenever Ive had that in testing it was because meshtasticd was already running (either from commandline or the daemon failed to kill the running process)
Try ps aux | grep meshtastic
Hmm ok try launching meshtasticd manually. @twilit mountain do you know how to find the hwid that the daemon uses for commandline?
Can that be gotten from meshtastic python?
tried but failed
What command did you use
from the menu
No Im talking about manually running the command that the daemon/menu runs in the background, so all the output can be viewed
Like /usr/sbin/meshtasticd -hwid 9999999
Just need to grab the hwid first
Maybe @warm geyser knows
i aint that knowigable about linux I have used it a large amount for stuff but not in very indepth
No worries Im hoping to be able to just give you a command to copy/paste and then you screenshot the output
emm like this?
Hey there ya go
What steps did you take?
woot! I figured it out. it's working.
@nova frost what exactly are we measuring with the adc pin? battery level off a voltage divider?
Yee
I'm planning a 3:1 divider
And it's 1.8v max
So divide by 256 to give bat volts
Well, battery/5vin
i was going to use a formula like:
r1 = 5
r2 = 10
voltage = float(IN0_voltage) * (r1 + r2) /r2
send_device_telemetry(voltage=voltage)```
could be the wrong formula, i'm just getting my day started
Yeah, that sounds about right
It's 5pm here. Nearly time to feed the mob.
with nothing connected to the adc im reading 1.8v
IN0_Voltage: 1.80 V, IN1_Voltage: 1.80 V
IN0_Voltage: 1.79 V, IN1_Voltage: 1.79 V
more or less
If the fox is an x server and I have an x client somewhere else do I need the gpu horsepower on the server or the client? Fox has basically zero gpu
to get the output or...
as a note I removed meshtasticcd via the menu, did the purge command and reinstalled it but same error
Anyone know how low can we go voltage wise? wondering if lifopo4 with its low cut off is useful or naw
My smol has been running for about 14 hours on the single cell without the panel connected (it was night anyway). going to throw the battery on the charger and see how many mah it puts back in
if you use C0 then one could solder an SMD resistor right over to the GND pad, and a through hole resistor on the under side of the smol board right over to the batt. Probably simular on the other boards too
wait a second, the pinout on the luckfox site is different that the labels on the smol board, unless I haven't had enough coffee yet
Seems like 4C0 and 4C1 are swapped (labels)
also did you see this: https://github.com/meshtastic/framework-portduino/pull/55
oopsies
I'm assuming you used the same "part" on all boards, so the Pro version will also have this "bug"
how does one procure this craziness?
@mild hare sent it to me but i believe the files are available to download on GitHub. @nova frost am i correct?
mmm not sure tbh, id guess client side handles most of it
sadly, I seem to have missed the errors about missing packages during the chroot setup when I tested this.. looks like it won't work after all 😦
Working on a version for sale Soon™
Yeah, I've mis-labelled the boards 😦
I'll double-check the pi header pinout later.
Soo, script is working but any voltage over 0.2v crashes
IN0_Voltage: 0.2 V, IN1_Voltage: 1.78 V
CPU_Temp: 45.198 °C
[TX] Portnum = TELEMETRY_APP (67)
To: BROADCAST_NUM
voltage: 0.8
Connection to femtofox.local closed by remote host.
Connection to femtofox.local closed.```
Anyway, nothing a dymo label can't fix, at least.
And the board has to cool off for a bit before it'll boot
Is this with it changing slowly, or with you tickling the pin?
I found sudden changes either way made it hang.
increasing the voltage by 0.01v
i'll try c1
C0 is linked to the reset pins, for some reason
I think through a 10k pullup...
Oh well, if neither work, I'll be adding an ina chip...
c1 works!
Although I'm not sure the budget will stretch to these array resistors...
need to do some math now... the battery indicator apparently uses percent, and my voltage reading is off
Which bit is wrong? The voltage applied, or the battery percentage?
I wasn't sending percentage, and the voltage formula is off
And is it the firmware or your python which is generating the erroneous reading?
very likely the python.
Just use regular like ive done 🙃
I'm going to eat some ham and then dig in
sad times, femto is up and node is deaf 😦
Yes, yes... I was looking for minimum viable number of passives, and this was the best I could find.
Missouri loves company
Fair
i wonder if its because of emf which causes the LNA to get pulled down or whatever and then not come back up (something i read)
It's possibly cos you're both in high noise environments, and need filters of some sort.
If you want to swap it out, I have stock in the UK now.
thats fair 😉 though it wasn't mute the first boot, did a halt to tedt i knew how to powerdown to move it later and nadda on the Rx since
Is it mute or deaf?
can i just compliment the setup process very easy
I can't take credit for that - it's almost all @fiery finch
@fiery finch setting up was painless so thankyou.
❤️
so I did a cleanboot and from the get go installed all updates and 2.6.4 works
FFS fixed it
no the F'ing radio settings hadn't saved, but some how I was able to send on LF
Hmmm
There's often some weirdness around settings in the firmware itself.
CF: all the complaints about restore taking a few goes.
I've had it where the connect page shows region unset, but it's actually set and able to send messages.
¯_(ツ)_/¯
Ok, see how it goes and report back, plz.
yup saw that, i can see 12 nodes now, only 1 with node info but it's better than nothing or the -1 when I started the webinterface
so installed meshbot and see its cpu went to 90% usage and same errors. What is it complaining about?
Are you trying to run two API programs? Or use a mobile client to text at the same time the bot is running?
The bot needs exclusive access, only MQTT or the new UDP stuff can be injected currently
Two clients using the API will cause a cpu runaway in threading for the API
no just on my phone on the t1000 tracker and watching it
Fast charging.
Shouldn’t be disconnecting if nothing else is fighting for API access
thats the only thing I enabled
Cpu temp for spud
Hot potato 🥔
Don't worry, my phone converts to fahrenheit
I'm looking in the firmware where it's defined what 0 percent is, can't be 0 volts right?
2.5v?
probably but I'd like to be sure
lemme find the curve data for you, unless you just found it
i think i found it
{100, 0.0}, // Plugged
{100, CHARGING_VOLTAGE}, // Charging
{80, 4.00}, // Full
{35, 3.50}, // Mid
{10, 3.30}, // Low
{0, 3.12}, // Empty
{0, 3.10} // Warn```
but that's not exactly what i need
huh, interesting. that's not what I was going to show
https://github.com/meshtastic/firmware/blob/72dd5bd88d541eaa8b91dd02ec66a0b8ece41b29/src/power.h#L34
this array is basically every 10% (100, 90, 80, 70, ... 0)
that's for li-ion obviously, some other chemistries above it in the same file
and of course scale 4190 -> 4.19V
https://github.com/meshtastic/firmware/blob/72dd5bd88d541eaa8b91dd02ec66a0b8ece41b29/src/Power.cpp#L230-L241 is where it ends up getting used
ok, lemme see if i can figure out how to map this
since I got nerd-sniped/curious how to translate it too, may as well put it here, heh (sans the clamp to 0-100 and conversion to int, I guess, remainder left to the viewer I guess):
OCV = [4190, 4050, 3990, 3890, 3800, 3720, 3630, 3530, 3420, 3300, 3100]
def show_voltage(voltage):
for i in range(len(OCV)):
if OCV[i] <= voltage:
if i == 0:
return 100.0
else:
return 100.0 / (len(OCV) - 1) * (len(OCV) - 1 - i + (voltage - OCV[i]) / (OCV[i - 1] - OCV[i]))
return 0
I just did a clean new install and didn’t see any abnormal behavior.
Checking and it stopped showing that error. Didnt do anything in the mean time. Cpu is down to 8% usage
Oh good, happy meshing about 🥔
I have a idea what i might be. I have home assistant and it was connected to eth and thinking ha did some discovery since I also have meshtastic client on that
And connected to a different node on the network
You young whippersnappers don't know how good you have it! A 1200 MHz ARM with 64MB isn't enough? We ran X11 on 20 MHz 68020s with 24MB of RAM!
And that was after walking uphill to work both ways during blizzards. With onions tied to our belts, as was the fashion at the time.
Was that delivered with a desk, once they'd checked the 3-phase was up to the task?
It did take a pretty hefty desk to hold it, along with the 19" 1K steel-cased monitor that weighed as much as a small car and put out about as much heat. I still have that machine (a Sun 3/60), but not the monitor or drives anymore.
Perfect, that did it, thanks!
The steel casing on the monitor was to contain the x-rays. Almost not a joke.
Sorry to just pop in . Any time frame on a restock ?
@forest current is that new SDK you're working in a vaguely hackable state? I'm curious to see what's different and mess around a bit if possible
yeah its fully ready to tweak
oh nice! is there a separate repo or branch?
you will need python2 to build uboot though, and i didnt add anything to build a local standalone python2 yet, but you can do that by downloading the tarball
Contribute to joshbowyer/femtofox-lyra-sdk development by creating an account on GitHub.
nice. and this is expected to be backwards compat with the pico?
yeah, i dont think weve actually tested that yet but the dts files are all in there, i may have to add something for the pico's spl
or actually @mild hare has been working on spl stuff so probably mostly him at this point
the goal is to get that sdk working for all the fox variants
very nice! I'll poke around a bit, thanks!
did you do the wizard on femto-config and set the region?
oh, nm, I see it now
To whom it may concern: I wanted to say how I am loving the Femtofox Pro! Well done! I look forward to you restocking and buying another one. I like the 30dBm output. Thank you for a great little Mesh device!
WELL WELL WELL
guess who's fox can hear it's neighbors again
cavity filter was the trick
thanks @mystic mortar for the fast shipping!
the filter???!
epic! Thanks for sharing. Ok to unbox replacement?
i havent tested anything and it's barely attached inside the enclosure... but yeah Fox can see same neighbors as rak was before (and with a better SNR ;))
Man, what a trooper. I'm super rural so not a prob here. But it's going to happen to people.
@forest current Missouri has one less resident.
I think this is ready for a test run if anyone wants to risk it.
https://github.com/pdxlocations/mfoxadc
For those just joining us, this will add battery telemetry to a LuckFox.
It assumes you have at least one node capable of UDP processing on your LAN
Might want to programmatically add the ! Or fix example to..
mfoxadc --node-id \!abcd1234
I also had a fork of mudp to allow meshtastic 1bit keys (outside of AQ) let me know if interesting feel free to pull or I can push up
Hmm. Oh read me should have single quotes I think.
I didn’t think the firmware allowed that?
what does this mean exactly?
2.6 firmware, CLI
meshtastic —host localhost --set network enabled_protocols 1
Might be good to add to the readme @fast adder yea single quotes would work as well
1 bit keys?
Could also pull the node id from local data as well no need to add it on command line
what if the node isnt connected to the interwebs? doesnt matter?
femto@femtofoxHome:~$ meshtastic --host localhost --set network.enabled_protocols 1
Should broadcast on loop back as well
and do I need to enable telemetry on the node aswell?
These packets are sent out the meshtastic firmware
No need to do anything but run it as a service
and will my other nodes see the data? sorry, pretty new to meshtastic. Alright at linux
Press Ctrl+C to quit
IN0_Voltage: 1.79 V, IN1_Voltage: 1.79 V
CPU_Temp: 50.544 °C
[TX] Portnum = TELEMETRY_APP (67)
To: BROADCAST_NUM
voltage: 4.97
battery_level: 100
[SENT] b'\r\x1e\x96@G\x15\xff\xff\xff\xff\x18\x08*\x14J\xff^\xe4\xd0|,j@\xde\xa8\xcdt\x90\x0chV\x11\xa0\xc35\x86\xa9*\xfeH\x03x\x03'
[TX] Portnum = TELEMETRY_APP (67)
To: BROADCAST_NUM
temperature: 50.544
[SENT] b'\r\x1e\x96@G\x15\xff\xff\xff\xff\x18\x08*\x12T\xea\xdf\xbdV8\xce\x88\xf7\xf4z%\x94[k\xc9\xfb\xae5\x87\x85G\x17H\x03x\x03' ```
app seems to work, didn't install the divider yet
Not seeing anything and the “power metrics” is greyed out.
This is from a different node (heltecV3) connected to my phone.
I did change my primary channel, and followed the guide to make the second channel the default longfast
does this mean I need to run the program with the --channel and --key flags?
Is there a new fembunto release coming soon ?
it will default to LongFast and AQ==. Add the flags if you're useing something else. Are you using Meshtastic 2.6.4+? I believe that's the first release with UDP support.
My phone is on 2.6.4. foxbuntu I don't think I ever updated
You would need to sudo update && sudo apt-get install meshtasticD
Update the base 1.0 image
so that 2.6.0
I thought about this but decided against it for two reasons. Getting the nodeid I think uses the client connection which could mess up yer bot for a bit, and it's likely this would be set to run as a service, so leaving the id flag in there is easy, and no need to worry about what order services start up. (meshtasticd specifically)
https://meshtastic.org/docs/configuration/radio/channels/#psk
Must be either 0 bytes (no crypto), 16 bytes (AES128), or 32 bytes (AES256).
Oh, I get it, but does the firmware do that?
If I put AA==, is that valid?
firmware supports any one-byte (not one bit) key except AA== I believe, works much like AQ== for all the others though, except it swaps out the last byte
AA== is the shorthand for "no crypto", at least in some places, so I'd avoid that one
oh haha, of course I'd use that as an example
but yeah. AQ==, Ag==, Aw==, BA==, BQ==, Bg==, Bw==, etc. should all work
(A-Q-g-w is because the second character only has two bits that matter for a one-byte value, in case anyone wonders about that)
sure, I'd merge that but i do the substitution in three places right now, so it may be need there abouts as well.
Fixed that, I haven’t goofed with receiving yet, still lab’n out ideas of how to bot-UDP
make a mudp project thread 🙂
does apt-get crawl for everyone? I feel like its slower then my 1st gen eepc
700mhz celeron in that baby
Yea it will take a hour or so?
Some point 1.0.6 image should be a release party 🎈
SDK in a docker yet I saw Python2 (shivers at the name of tom riddle)
You're trying to make a UDP-only Bot?! 🤯♥️
See how it works out anyway drafted up some rough lab work on it
I've apt-get update && apt-get upgrade and meshtastic is still showing 2.6.0
portduino 0.1.0
femto@femtofoxHome:~$ meshtastic --version
2.6.0```
also:
[sudo] password for femto:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
meshtasticd is already the newest version (2.6.4.16~ppab89355f~jammy)```
We should really make meshtasticd --version return the meshtastic version
(that arg is handled in framework-portduino currently)
meshtastic --version would return the version of the python library
roger that
meshtastic --info will have the version of whatever it connects to in it, or the same without all the other huge pile of stuff in info, meshtastic --device-metadata
workin' for me!
I've got the FemtoFox officially moved into my truck now - but I was curious how much of the maintenance needs to be done through the femto-config versus just raw linux commands like sudo apt update && sudo apt upgrade -y?
I'm used to managing a MeshAdv hat on RaspberryPi OS so I'm not sure how fragile or tolerant the FemtoFox install
the menu is just a graphical frontend for command line stuff, you can definitely do it all via cli (as i do)
okay! Thanks Josh - can I pretty well beat on it like a standard ubuntu system?
Also noticed that meshtastic runs without having the VENV or how did you do that under the hood?
On much of my Ubuntu installs I do workon meshtastic and then any meshtastic related commands
Has anyone tried a pico mini B with the flash as swap? I'm curious if that's a noticeably faster than sdcard swap
Prob system packages
Didnt get the B working yet
@lavish sorrel was trying
oh darn.. I assumed it was basically identical
It only has a smol brain. Venv would break it (probably 🤷)
At least, that was the justification back in the day...
Lies and slander
It is except for some reason we couldnt get the flash chip working in our limited attempts
Let me find the instructions with sizes I shared a little while back
venv's are just... a directory and some PATH / environment mangling 😅
I think we got stuck on kernel modules in the sdk or something (selecting the B in boardconfig?)
By having meshtastic API loaded in native as well as a venv caused some issues
The fox platform memory was around 4mb free last I looked
Last I looked at it was troubleshooting tc2 bbs back around build 0.97 area
seems to install and work, but I don't know how to see any info from other nodes on my network
Ok, I think I've got it working now. wonder if I should run as a cron job at boot or something else?
@hollow dragon Yo, any luck?
@polar ingot so I thought mine was working (I saw telemetry being reported to other nodes) but now not so much had to make sure all the Telemetry modules were disabled and set to 0 . I think they were overriding the madc update
interesting
mine kinda works sometimes.... lol
how are you running it @spring juniper ?
I modified it to submit an ina3221 voltage instead of the adc
seems to work for my fox and setup - if I run meshsense it will overwrite the deviceMetrics with 0.0v after a minut or so - I'm pretty sure that is because meshense is calling devicetelemetry to update it's own UI
but the whole external voltage -> udp -> node reporting voltage works!
oh thats pretty fun! I have one of those coming in the mail
are you starting it with cron? or did you make an init.d service?
i would do a systemctl/init.d thing
Apr 23 01:05:50 ff1 meshtasticd[3944]: INFO | 05:05:02 2281 [DeviceTelemetry] Send: air_util_tx=0.833694, channel_utilization=0.000000, battery_level=101, voltage=0.000000, uptime=2281
Apr 23 01:05:54 ff1 meshtasticd[3944]: INFO | 05:05:48 2327 [Router] (Received from FBBS): air_util_tx=0.000000, channel_utilization=0.000000, battery_level=63, voltage=3.832000
Apr 23 01:06:55 ff1 meshtasticd[3944]: INFO | 05:06:02 2341 [DeviceTelemetry] Send: air_util_tx=0.833694, channel_utilization=2.121667, battery_level=101, voltage=0.000000, uptime=2341
Apr 23 01:07:00 ff1 meshtasticd[3944]: INFO | 05:06:53 2393 [Router] (Received from FBBS): air_util_tx=0.000000, channel_utilization=0.000000, battery_level=63, voltage=3.832000```
something still triggering the DeviceTelemetry update to override it 😕
Yeah the device metrics get sent out and then it dies?
either way I made a simple systemd service:
Description=madc udp reporting service
[Service]
Type=simple
Restart=always
RestartSec=1
User=femto
ExecStart=/home/femto/.local/bin/mfoxadc --node-id '!******' --channel *channelName* --key *channelKeyHere* --interval 300
[Install]
WantedBy=multi-user.target```
seems to work
ish
the issue with sending this with device metrics is the node will still send out device metrics for chutil/airutil. hence it flipping back and forth in the screenshot. the ones with battery/voltage are the ones from the script, and the ones with chutil/airtime are the ones from the node
Hmmm I didn’t think of that.
Could set the interval on the node to maxint or something. Then the script could dm the node with a device metric request and append that info to its broadcast….?
That sounds like the right idea to me
I'd imagine this would work well, as I think the timing is messing with broadcasting some messages. Just a hunch, as I havn't dug deeper, but I don't seem to always get the metrics
hm, yeah, as long as the requests still give up to date info that seems like a decent route
what is the voltage divider expected? I've got 300k to batt and 100k to ground
Better check with an EE. Don’t put more than 1.8 V into the pin. A 5 V supply should deliver 1.8 V.
This page has a calculator https://learn.sparkfun.com/tutorials/voltage-dividers/all
It’s very early code still
May need some fine tuning still
To say it might not be ready to include at startup
I agree. Need to test it out on ma rig...
When are these going to be available again?
Depends where you are. UK/Europe, this weekend (yes, delayed...).
US
10-4. a 3:1 would do a max of like 1.25. 180k:100k would do a max of 1.79 at 5v, but that seems like pushing too close to the edge.
Either way, my smol is doing weird stuff after upgrading packages. RTC doesn't keep time after removing it from the network anymore!
goes back to 1999!
Testing the solar node in the yard before it gets put remote. Would love some sore of voltage monitoring before it gets up a mountain though
I meant more, what does the code expect to see on the pin. If it translates 1.8v to 5v then that fine
I chose 3:1 because max input on 5v might be up to 5.5, and 5.5/1.8 is 3.1, so a ratio of 3:1 is too low. 4:1 is easier, so 100/(300+100) is the answer.
Is it one you got from us, or one you bought/already had?
Some of them don't have a battery backup...
Or don't have a real backup, but just a disposable cell of questionable origin.
voltage = round(IN1_voltage * (5.0 / 1.8), 2)
Hmmm
I thought you had an R1 and R2 in there somewhere?
I did. But I was using a bench supply not a voltage divider so they got commented out, lol!
Can we have them back? I have a shortage of 177777 ohm resistors.
I think I have a 100k and a 75k for a total 175k, but the upper limit would be 4.95, and that's not a risk I'm willing to take.
Oh, cool
Sure just tell me what values to plug in and I can make a note in the readme also.
But I’m traveling atm so might be another day or two.
I think just expose those two values somewhere if you can. All the ADC multiplier stuff just leads to confusion.
Should I add them as mandatory flags? This is the problem with a packaged script vs git clone.
Or we could have default values with an option to override with flags
Default values at 300 and 100, and override flags, I suppose
I stupidly put together a test node without having the right resistors on hand, so I can't actually test this.
Use a bench supply lol
But assuming I get chance to test this tonight, those will be the values I add to the next.... Thing.
A bench whatnow?
I'm crafting this stuff in a cave rn.
Variable power supply
Yeah, I have a long wish list of proper equipment.
Something capable of not blowing up a 1.8v pin with ripple is on that list.
😄
Fair enough. A Riden was in my cart for over a year before I pulled the trigger when I saw it on sale. The safety voltage cutoff saved my fox while testing this.
Yeah, all my money is tied up in foxes at this point, so I can't be risking them 😉
Still can test, the values will just be wrong. Honestly have a gig going for the next couple of weeks that might keep me tied up.
This R1 R2 fix will be quick but I also want to work on that telemetry issue with the node sending 0 values.
alright Tony 😉
One I found in my parts bin. Turns out the backup battery had a cold solder joint and one leg popped off. I've got it figured now.
I can be a useful tester also. I cover the "don't know meshtastic" group, but Im ok at linux and know my way around a soldering iron.
But can you still party like it’s 1999?
every dang day
Does the pin have an internal pullup that could be skewing values? My 300k:100k arrangement Im measuring 1.69 with a voltage of 3.25..... Got me thinking I better check the resistors.
also, according to the Sparkfun calculator, 220k:100k at 5.5v is 1.72v out, and common values. Not sure about the impedence on the pin (not an EE) but I know this is important on Arduinos and the often use lower values. (maybe 22k:10k)
If you translate the chinese convo, both ADC pins have external 10k pullups. If removed on ADC0, on boot it will go into "download mode"
So i think that means we have to use a much "stronger" (lower value) pulldown resistor, which I guess might draw more current? Ooof, this is out of my wheel house officially
Here's a link to the schematic, and shows why SARADC_IN0 possible being weird? "Note: SARADC_IN0 must always be pulled-up." https://files.luckfox.com/wiki/Luckfox-Pico/PDF/Luckfox-Pico-SCH/Luckfox Pico Mini.pdf
Yeah, that was the conclusion I came to when "tickling" it led to crashes.
Are you trying this out, "for science"?
Anyway, brb, just going to shoehorn an ina3221 into something....
@fast adder can you walk me through the new contact install?
pip install contact
lol 😂
if ! git clone https://github.com/pdxlocations/contact.git /opt/contact; then
echo "user_message: Git clone failed. Is internet connected?"
exit 1
fi
pip install -r $location/requirements.txt
chown -R femto $location #give ownership of installation directory to $user
git config --global --add safe.directory $location # prevents git error when updating
echo "Creating \`contact\` shortcut."
echo -e "#!/bin/bash\n\
export NCURSES_NO_UTF8_ACS=1\n\
export TERM=xterm-256color\n\
export LANG=C.UTF-8\n\
$launch" | sudo tee /usr/local/bin/contact > /dev/null
chmod +x /usr/local/bin/contact
echo "user_message: To launch, run \`contact\`."
exit 0 # should be `exit 1` if the installation failed
}```
This is the current install script
Does it self create the shortcut now?
okay so ufw and iptables seem to not be at play on the FemtoFox, but what kind of software firewall is the FemtoFox running?
And —settings or -c will launch control
Both work. contact -c
I'm just trying to then figure out why an HTTPS connection from a separate network isn't permitted then
My FemtoFox runs on 192.168.96.246 and local connections from 192.168.96.x work, but over my VPN and from 192.168.48.X, do not work
Hmmmm I think meshtastic may not allow that?
not sure
I have to do some more digging
I forget the exact path. …/usr… bin/ ?
If you open user config in settings it’ll show the log path
Is your fox gateway set to the proper gateway for the subnet?
Is the VPN properly marking/NAT the traffic to you
@fast adder does contact now need to be run sudo?
unsure. I don’t think so. Not on my mac. I’m traveling sans fox atm.
oh, it's because I'm installing it elevated
how can I pip install unelevated from an elevated script
Would probably need to wrap the command in runuser and pass the --user flag to pip
Iirc it would be sudo runuser -l nagu 'pip install --user package'
ugh now I can't uninstall contact
Sudo pip uninstall contact?
says not installed
I think my issue is elsewhere
gpt is taking 45 seconds to respond to every query
I can't work like this. I'm taking a break
I'm not sure if it's installed or not
working with chatgpt is diabolical
Removing the resistor? If its in an easy to access place I may, But I flush mounted my boards on the smol......
But Now that we know the pin is pulled up to 1.8v with a 10k resistor, maybe its possible to still come up with a voltage table after a divider. If we wanted to lower the current of the divider and use low values like 2.7k:1k we could use a mostfet to turn on the divider, read the ADC, and turn it off with another digital pin.
I just learned there is a mesh poop icon!
like this... ish:
No, there's only 3 pins free, that uses two of them!
I'm looking to just add an INA219 for reading the battery voltage
The smallest package is SOT23-8(!)
Voltage all the things
cute!
it only needs a 100nF cap on vcc, and technically doesn't need filtering on the sensors
Trying to decide whether to bother with a shunt resistor, or just monitor battery volts directly.
the shunt is needed for current, no? I've not gone very deep down the in219 hole
I am working to get a separate Pi in there for testing - I have a different unit with a MeshAdv hat on it; just needed to reassemble some parts. I hate halfway doing something lol
Nice, it sounds like the VPN issue is just a config value. If you can mark a subnet as interesting to tunnel with your VPN you should be able to put any IP thru it
well it's defnitely passing the traffic because I can do meshtastic --host 192.168.96.246 --export-config and that works. So I'm trying to figure out if this is a HTTPS routing issue or an application rejecting traffic issue
I was trying to hunt down if this was like "Access-Control-Allow-Origin" type issue but not sure the responding web server even has something like that
yeah it's listening 0.0.0.0:443
I have a couple work meetings and then I can assemble some 3d printed parts and throw it all in the truck for a test
Nice
This is the setup, bit older photo as its had some revisions
@mild hare @forest current - FINALLY got my Lyra online lol had to use one of the bare wifi boards i just recently got and it connected right up.
This is SO much faster than the pico mini when doing just about anything involving apt...
Noice
Sweet!
The ram really makes the difference.
i mean, i have NO fear running sudo apt update -y with this and actually still sitting here and not thinking i'll have to come back tomorrow to check on it...
word. That clear cache trick I was using helped tons. But once you hit virtual memory...
im eating my own words right now as it's generating locales.... 
oh well locales always takes a minute. potato is potato.
i know. i'm scared to think about what this would look like on a pico mini, or if it'd just be like "nah, f-that... i quit"
I'll give it a try tonight. Haven't had a pico online for a minute because of skunkworks.
using this makes me really hope that the Patron Saint of PCB's* will decide to do one for the Lyra...
*aka @nova frost
its running @forest current 's early build of the SDK. Not sure how "foxbuntu" it is yet.
time to kick the tires... running unminimize lol
"St Nom of Tom"
Make for us 🙏
makes the sign of the impedance symbol
Lyrafox is to Ubuntu as Femtofox is to Linux Mint
All the goodies and polish are not present currently. It just runs lol
@mild hare has been playing with the sdk with the goal of merging it with the femto stuff
Oh also I forget do you have the Lyra with the nand or without?
I keep wandering. It's not ADD. It's just hard to work on a 128mb Honda Civic when there is a Koenigsegg peaking out of the car cover next to me.
Gas mileage is the same too.
New power meter arrives today and that will help me focus on what's important and what's not.
You really need to start using virtualenvs, or leveraging pipx
Just liable to break system packages 😅 asking for trouble
venvs on a luckfox are a bit much
venvs are just... some path mangling...
What makes you think the fox can't handle that?
Yeah it's extremely minimal overhead really 🙂 and I'd be happy to help
i got the lyra plus w/ NAND
were you able to get the nand working as ubifs? i can repost the instructions if you need them, but its confirmed working for me on the lyra with the release you flashed
Any updates on shipping new units to the US?
@mild hare got some nodes in da mail i believe
Are you in Boston btw ? I think I’ve seen you on my node map
Okay, who was asking for tailscale?
I need a basic explainer about tailscale. I have a testrig up with tun installed, as per that PR
oh if you're talking tailscale, I would love to see that
its one of my few device without the package
There was a request for it on the gi
git
I had tried (#1329096340700921898 message) but it took forever to install and then I realized yeah we didn't have the necessary underpinning to make it work
alright
so I think I have the underpinning installed
walk me through installing it
They package it up real nicely
But also have individual OS installs listed on that package too if you're looking for a more interactive install
If this takes forever to install, we'll just have it preinstalled and disabled
so walk me through this
after installation, is there a service?
yes you can do sudo tailscale status and stop/start
actually it's sudo tailscale up and sudo tailscale down
Tailscale is nice
Welp, Lyra works, but Meshtasticd doesn't like it.
lyra@luckfox:~$ sudo meshtasticd
Portduino is starting, VFS root at /root/.portduino/default
Set up Meshtastic on Portduino...
Using /etc/meshtasticd/config.yaml as config file
Also using "/etc/meshtasticd/config.d/femtofox_SX1262_TCXO.yaml" as additional config file
MAC ADDRESS: 00:0C:29:3F:A2:B1
Segmentation fault
Oof
That makes stuff MUCH more complicated
Honestly I'm sure the service is manageable
okay, yeah, I can disable the service
I'll make a package for the manager. Tailscale will be preinstalled but disabled
Are you not happy just to say up and down?
Or is this back to "stuff doesn't behave like it should"?
does the pinout match? i think that yaml is using specific pins, no?
How do I grab that since my install is already working? Reflash?
Ive been so caught up with getting this online, that i forgot to check that. Ill give it a look a little later.
Lora:
## Ebyte E22-900M30S, E22-900M22S with or without external RF switching setup
## HT-RA62 (Has internal switching, but whatever)
## Seeed WIO SX1262 (already has TXEN-DIO2 link, but needs RXEN)
## Will work with any module with or without RF switching, and with TCXO
Module: sx1262
gpiochip: 1 # subtract 32 from the gpio numbers
DIO2_AS_RF_SWITCH: true
DIO3_TCXO_VOLTAGE: true
CS: 16 #pin6 / GPIO48 1C0
IRQ: 23 #pin17 / GPIO55 1C7
Busy: 22 #pin16 / GPIO54 1C6
Reset: 25 #pin13 / GPIO57 1D1
RXen: 24 #pin12 / GPIO56 1D0 # Not strictly needed for auto-switching, but why complicate things?
# TXen: bridge to DIO2 on E22 module
spidev: spidev0.0 #pins are (CS=16, CLK=17, MOSI=18, MISO=19)
spiSpeed: 2000000
General:
MACAddressSource: eth0
this is the contents so yeah it wont work as-is
just need to map the pins and you should be good to go
I think i modified my .conf, but i cant recall what i changed or where i got it from
once youre able, post yours, we can look at it
---
Lora:
## Ebyte E22-900M30S, E22-900M22S with or without external RF switching setup
## HT-RA62 (Has internal switching, but whatever)
## Seeed WIO SX1262 (already has TXEN-DIO2 link, but needs RXEN)
## Will work with any module with or without RF switching, and with TCXO
Module: sx1262
gpiochip: 1 # subtract 32 from the gpio numbers
DIO2_AS_RF_SWITCH: true
DIO3_TCXO_VOLTAGE: true
CS: 11 #pin6 / GPIO48 1C0
IRQ: 34 #pin17 / GPIO55 1C7
Busy: 35 #pin16 / GPIO54 1C6
Reset: 36 #pin13 / GPIO57 1D1
RXen: 37 #pin12 / GPIO56 1D0 # Not strictly needed for auto-switching, but why complicate things?
# TXen: bridge to DIO2 on E22 module
spidev: spidev0.0 #pins are (CS=16, CLK=17, MOSI=18, MISO=19)
spiSpeed: 2000000
General:
MACAddress: 00:0C:29:3F:A2:B1
I have no idea where I got these numbers from, it's been so long.
it'll be a bit before next release
Visiting, but yeah, within the last few weeks. Might not be the last time either 🍕
ok, do two things:
show a pic of where you wired the radio to the lyra
post the output of gpioinfo
@fast adder looks like you don't ship the license as part of your pip package install for contact? Honestly not sure if this is normal or not 😅
Oshpark only sent me two last time cuz one was messed up, and now I have three more!
Anyone had the network port on the FemtoFox carrier board just stop working? I’ve tried two routers and now half a dozen network cables and the FemtoFox will definitely not sense a network cable at all. No activity light, no nothing.
I dont think the lights are enabled regardless. Just checked mine and they're off.
They aren't
Check the soldering on the back 5 pins of the Luckfox. make sure they're solid. Most times ive heard of people having issues, it was due to a cold joint or something came loose with those 5 pins.
I think there was a discussion on how to make them work, but that doesn't matter here..
okay that's actually useful info - may be something else then
Time to flash the SD card
Not sure I have a lot of great news here - reimaged the SD card but the supposed 7 minute wait time basically turned into the FemtoFox blinking for about 10 seconds and then nothing more
Do you have activity/link lights on the ports of the switch/router your plugging into? I had an old orangepi that did weird things sometimes.
is this a Femtofox Pro or a CE?
FemtoFox Pro
I will do some more digging on it, I'll see if I have a different SD card I can try too. For the moment I had to swap around the setup for a trip in the morning. I leave in 8 hours so I need to finish packing and doing what I can to get something working
ok, are you on a Mac/PC/Linux machine?
Got homebrew installed?
No
That's interesting. I do see the license type on pypi. Looking in my pip installed meshtastic directory and don't see a license in there either.
ok, there's a simple way to see if its alive, and it's the primary way I connect to my foxes: tio
it's a command line utiltiy that connects you to the serial port that's available on the Pro, via the side USB-C connector.
For reference: https://github.com/tio/tio
alright I will probably have to pick this adventure up here later. I do appreciate the quick help
if you decide you want to install tio , easiest way to get it is install Homebrew for your mac (it's a package manager). It can be found here:
https://brew.sh
Command to install it is:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
(That's taken right from their landing page)
Then to install tio, you'd run:
brew update && brew install tio
To connect to your node, follow these steps:
- Before connecting the node to your laptop, run this command in Terminal:
ls -1 /dev/cu.*
(Note the output.) - Now, connect the device to your computer via USB-C, run the same command again.
- Look for the new line in the list.
- Once you identify the new line, select it with your cursor, all the way from
/dev/to the end of the path. - Run
tiofollowed by the path you just noted, so it would be like this:
tio /dev/cu.usbmodem3401and hit enter. - Hit the enter key again, and if you don't see anything, unplug the node from its power, but leave the terminal as-is.
- Reconnect the device and you should see a stream of logs in the terminal window.
- If you see "Femtofox Login", when you hit enter the second time, then the Fox is up and waiting for you to login.
Thank you! I’ll take a look at it
The picture would just give you a headache because i used some leftover wires that are all the same color, and everything is on the underside of the proto board.
NSS - 0B1D
SCK - 0A1D
MOSI - 0B3D
MISO - 0B2D
NRST - 1C2D
BUSY - 1B2D
DIO1 - 1B1D
RXEN - 1B3D
TXEN <=> DIO2
VCC is coming out of a TPS61023 board i have attached, with a 100uF cap between VCC and GND.
Also, only GPIOCHIP1 has anything listed for it:
gpiochip1 - 32 lines:
line 0: unnamed "work-led" output active-high [used]
line 1: unnamed unused input active-high
line 2: unnamed unused input active-high
line 3: unnamed unused input active-high
line 4: unnamed unused input active-high
line 5: unnamed unused input active-high
line 6: unnamed unused input active-high
line 7: unnamed unused input active-high
line 8: unnamed unused input active-high
line 9: unnamed unused input active-high
line 10: unnamed unused input active-high
line 11: unnamed unused input active-high
line 12: unnamed unused input active-high
line 13: unnamed unused input active-high
line 14: unnamed "cd" input active-low [used]
line 15: unnamed unused input active-high
line 16: unnamed unused input active-high
line 17: unnamed unused input active-high
line 18: unnamed unused input active-high
line 19: unnamed unused input active-high
line 20: unnamed unused input active-high
line 21: unnamed unused input active-high
line 22: unnamed unused input active-high
line 23: unnamed unused input active-high
line 24: unnamed unused input active-high
line 25: unnamed unused input active-high
line 26: unnamed unused input active-high
line 27: unnamed unused input active-high
line 28: unnamed unused input active-high
line 29: unnamed unused input active-high
line 30: unnamed unused input active-high
line 31: unnamed unused input active-high
JB maybe getting close to native support for i2c? #contributor-lounge message
Also, here's my updated config:
---
Lora:
## Ebyte E22-900M30S, E22-900M22S with or without external RF switching setup
## HT-RA62 (Has internal switching, but whatever)
## Seeed WIO SX1262 (already has TXEN-DIO2 link, but needs RXEN)
## Will work with any module with or without RF switching, and with TCXO
Module: sx1262
gpiochip: 1 # subtract 32 from the gpio numbers
DIO2_AS_RF_SWITCH: true
DIO3_TCXO_VOLTAGE: true
CS: 9 #pin6 / GPIO48 1C0
IRQ: 57 #pin17 / GPIO55 1C7
Busy: 42 #pin16 / GPIO54 1C6
Reset: 50 #pin13 / GPIO57 1D1
RXen: 43 #pin12 / GPIO56 1D0 # Not strictly needed for auto-switching, but why complicate things?
# TXen: bridge to DIO2 on E22 module
spidev: spidev0.0 #pins are (CS=16, CLK=17, MOSI=18, MISO=19)
spiSpeed: 2000000
General:
MACAddress: 00:0C:29:3F:A2:B1
my fox bogged down, could reach the node, could send but it was deaf, and was unable to ssh to the node 😦
Oh dear
Is it physically accessible?
I'll get to it later, just thought it was a bit odd
How's it powered?
They do weird stuff sometimes...
Did you remember to use a decent SD card?
my 4k drone is waiting for a new card 😄
and it's a samsung usb charger as it was in the location
Going to replace SD card and power, node isn’t deaf just doesn’t appear to acknowledge messages after a while…
spidev should definitely show under gpio info on one of the gpiochips... are /dev/spidev0.0 and 1.0 present?
For me to implement tailscale, I'm going to need someone who knows how to use tailscale to participate
Are you running any other services on it, like Meshing-around or anything else?
At the in-laws for the night, I can check when I get home tomorrow. Might be able to ssh in later, just with family for the day.
@nova frost what do you use for PCB design? I've been out of the game for a while, is Kicad still cool?
Kicad is always cool
Which is why I am reliant on EasyEDA std.
I'm hoping they'll eol the std edition to force me to convert
EasyEDA is what Ikeep seeing on cool projects I follow, but yet to try
I found 3 rfm95w modules from early expresslrs days in my parts drawer I was thinking of slapping a quick board together for with the fox. Probably not worth it as I know they are old and not super compatible, but might be fun?
Might be a possibility...
Idk if they work well with Linux native.
@nova frost did you see the note about testing sensors in linux native? Do I need to build a new image for the fox or just a meshtasticd? I've got a few sensors I can easily test
I did. I'm not sure how to go about it - the ones built in are on a patch branch, and the mudp stuff is a separate install.
can we just build it, move it to the femto, and manually upgrade it with apt by choosing the package?
I'm gonna release a Mikrobus version of the Meshtoad (by @buoyant ermine and @twilit mountain), so you could probably play with them on that.
Play radio swapperoo and Try all the things™
yee ha
Indeed.
If I had to vote, tho, I'd say make a pro-micro node with the rfm modules. They're not brilliant modules, and until V3.0 they're going to be trouble with t1000000000e etc.
Possibly. I've never done a rp2040 node 😛
spidev0.0 and spidev1.0 are both present in /dev
FemtoFox has amazing passive SD card protection!!
It's got a nice picket fence
Does this error in Etcher even matter? I'm going with "no" but just double-checking
okay - I'm just back to testing my FemtoFox with the most basic things.
Should the FemtoFox work without the carrier board? I.E. can I plug it into my computer with just the SD card for any tio testing?
Perhaps promising?
so it did that for about 60 seconds and then all the lights turned off, nothing new in /dev/cu.*
it will work without the carrier
tho u cant use serial from usb
it doesent have a converter
actually you know who can help, is @twilit mountain as he said he recently got around to wiring up his lyra hat
ah that got me /dev/cu.usbserial-110
ye the carrier has a converter
@twilit mountain how did that go btw? any luck?
[ 2.327815] thermal thermal_zone0: critical temperature reached (115 C), shutting down
I think I found my issue
It's definitely the FemtoFox itself - even without the carrier board it was getting quite toasty
Here's the whole terminal output if anyone sees a different failure
ambient air temp right now inside my home is 70F / 21C
In my truck which is where it was when it died is a different story - probably 120F / 49C
looking at https://forums.luckfox.com/viewtopic.php?t=618 it seems like the working temps should be between 0C and 85C just for reference
i wonder why it gets that hot
nothing looks wrong to me
Only thing I can't see from the pictures is the soldering on the ETH pins
Did you feed it too much voltage by any chance?
You think it got cooked?
The only time we've seen that behaviour is when @fiery finch connected up the wrong pins.
Same symptoms, anyway
To run the FemtoFox, I'm using the SeenGreat Solar Manager (https://seengreat.com/product/226/solar-energy-manager) and running it off the 5V USB-A female port to the USB-C on the carrier board
Looks like it puts out 5V / 2A
Too much for the FemtoFox?
This looks fine too... 🤔
Hmmmmm... The usb-c port should be protected.
Working up a test rig with a multimeter - I have a small hunch given what you said above. I wonder IF the SeenGreat board will send voltage between the USB ports when it’s switch off and momentarily send over voltage when switched in.
Anyway, self-cooking foxes are not good.
Just enough to poke something with 10V and make it very angry
I am still testing this theory - this not a statement, just hypothesis
I can't remember what voltage I specced for the TVS, but it should be quick enough...
Maybe I need more protection on the next one 🤔
I don’t know enough of electronics to provide enough information likely but I’ll try
Doesn't seem like it passes more than 5V, I just tested it. 5.12V with the SeenGreat turned off (passing through 5.12V to the multimeter. With the SeenGreat enabled, it does go to 5.11V, very so slight change
Maybe just an UnluckyFox
What's the benefit of having a luckyfox around to compile meshtasticd on ?
Who compiles Meshtasticd on a luckfox? I feel like if I even tried to it would take 4 years...
a masochist, clearly..
I hand solder 0603's, so I'm familiar with masochism... but I still can't comprehend why or even how someone would try to compile meshtasticd on an actual luckfox, especially a Pico Mini
Cuz Jonathan said it's a pain to cross compile it.. And I don't have anything setup to crosscompile..
you have a linux computer?
I have WSL, many VMs, etc..
Do you have an old computer?
did you build foxbuntu or did you just download the release from the github
I can just spin up a new VM in my datacenter..
either you can cross compile in a vm, or if you built foxbuntu and still have the build environment, you can cheat and chroot into the rootfs, compile there, and copy the deb
Spin up an Ubuntu 22.04 LTS VM then follow @mild hare's guide to building the firmware
Pretty sure he uses VirtualBox for his build env.
yeah although it works with later too, 22.04 is jammy
if youre building a vm for it just stick with 22.04 as its the release it was made for/against
k
It'll build on 24, but it's not what the SDK is based on
where is the build guide ?
Hmm, I don't see anything about meshtasticd compile..
Is it under the WSL link ?
Basically what you can do is just build it normally first, then back in the main menu you can do the custom chroot option, and put the stuff for building meshtasticd in it
Wait just so I understand, why are you trying to build it again?
Are the ppa debs not working for you?
I want to test out the meshtasticd build that supports sensors..
So I just need to build meshtasticd
so I can copy it over to femtofox, I guess..
Ah gotcha I missed that part
When I select Manual Build Firmware, I get this.
Building firmware...
./foxbuntu-builder.sh: line 89: cd: /home/will/luckfox-pico/: No such file or directory
./foxbuntu-builder.sh: line 90: ./build.sh: No such file or directory
Menu selection completed. Press any key to return to the menu.```
Oh duh, need to install SDK first.. :\
Now I need to figure out how to pull down that release from Jonathan..
keep us posted. I tried building it on arch to no avail and didnt get any further
I also recieved my omni antennas from aliexpress today, and somehow ordered the 868 ones instead of the 915 😦
what a dumb dumb head
Oophf!
I'm not trying to build foxbuntu, just the meshstaticd for it..
ah gotcha
QEMU armhf Ubuntu 22.04 VM is what I used in the very beginning. But then @twilit mountain setup automation on github.
So there is something that makes it so I don't have to compile ? 😉
I'm not familiar with it. I just use the ppt and get the deb currently.
QEMU is easy enough though (on Linux).
I have Proxmox, and just spun up a Ubuntu 22.04 on x86.. I haven't cross-compiled since the Xbox360 days, and that was always in windows.. I just ran the foxbuntu-builder script to get everything setup. I'm at the arm kernel config menu right now..
Nice, I run proxmox at work
I'm migrating from ESXi to Proxmox.. It was a bit of a PITA to get the iSCSI working, so I went NFS route for storage on my NAS..
Death to VMWare!
Especially now that Broadcom owns them, and killed the VMUG program..
I just hope that the builder script pulls in the current master for meshtasticd..
it does not
How can I do that then ?
The builder script is just for the OS and then we lean on the meshtastic ppa for the meshtasticd deb. If you wanna compile meshtasticd you gonna need to use a QEMU ARM VM like I do or a pi 4 like some meshtastic heavies do
or get clever and try and crosscompile it
yea, I'm down to try to cross-compile.. Just not clue how to do it.. HAHAHA
Lemme see if I can do a ARM VM in Proxmox
Will this work on MeshCore?
Only if meshcore can run on Linux which I doubt?
ok, I checked the git. Meshcore is just an alternate firmware "knock off" of meshtastic that has no linux support.
so nope.
sorry
Ok, so that's gonna be a PITA to do.. Guess I need to cross compile..
Or wait for someone to compile it
you windows native?
I use Windows for day to day stuff, but have *nix VMs, proxmox, etc to do whatever I need.. I have a /26 of routable IPs for my colo, which I use as my lab..
There is a crosscompiler in the Foxbuntu sdk but I have never used it for meshtasticd.
it's possible though
@nova frost , any chance of more FemtoFoxes coming available? I suggested them to someone today and they were out of stock on Etsy.
Well the build seems to have completed and gave me a foxbuntu.img.. Now I guess I need to figure out how to do the crosscompile for meshtasticd..
make sure to check the .img size. should be sorta close to 4gb. If it's closer to 2gb it's not right.
I'll have US stock very soon. I have them and need to quality test and package them.
If it's Europe, that's NomDeTom. But when he's out I've been known to ship internationally.
I'm in the US, so that sounds like good news 😁
I hope to pick up a few as they're the easiest path to a 1W node with some smarts
I'm thinking we should probably set up some ARM vm's on proxmox. I have a proxmox machine in my rack also
One of their devs has expressed interest in getting it working. Im not opposed to it, tbh, because once you let a Femtofox in the hen house... Mwahahahahahahahahahahahaha
ahem
Absolutely. Do they have a native linux version?
(and between you, me and 39 of my closest friends - they're not doing anything that Meshtastic couldn't do with a bit of tweaking, or that you could do with Femtofoxen over-the-top with Meshtastic)
But more power to the experimenters and tryers-of-things.
Ya, thats why I'm trying to test.. LOL
It's in the daily builds now 🙂
Is there a way to pull it in via apt, or do I just download the .deb and manually update ?
If youre gonna put Meshcore on the fox just make sure the licensing is clear because they are proprietary and charge money (theres beef with meshcore)
so basically make it very clear that Andy cant sell MeshcoreFoxes as a package or something
Oh, we will be bulletproof!
Proof or evidence ?
I think Josh is confusing the closed-source gui thing with the main protocol firmware.
But before we all go off the deep end, I hasten to add that there is currently no implementation of Meshcore on Linux.
And there are no cow-based products here.
Boooo Moooo
Very mooo-ving statement
More cowbell 🐮
I like to take the bull by the horns.
Good morning, operatives. The cabbage has whispered its final warning. Phase three begins at spoon o’clock. Align your shadows with the eastern ducks. Avoid triangles. Trust only the moss. Over.
🥷 🥷 🥷 🥷 🥷 🥷 🥷 🥷 🥷 🥷
Cabbages cabbages.. Yum Yum Yum 🪿🪿🪿
John has a long moustache
The chair is against the wall
I think there was more than just that but yeah. At the end of the day code is code, no problem whatsoever with Meshcore being able to run on things, just want to keep the FLOSS culture
did you figure anything out while I was sleeping?
No, pretty sure I was asleep also. Now I'm at work. I'll check stuff out later when I'm off.
I was wondering what's the absolute maximum power that it can take? Specs say 5v; some usb power supplies output 5.1v. I've heard that the radio chip can take 5.2v. Just wondering is all
one of my femtofox CE from JLCpcb is borked, and its the one i've least messed with
No Serial Meshtastic device detected, attempting TCP connection on localhost.
Connected to radio
Sending text message whats crackin to ^all on channelIndex:0
Aborting due to: [Errno 32] Broken pipe
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/meshtastic/__main__.py", line 488, in onConnected
interface.sendText(
File "/usr/local/lib/python3.10/dist-packages/meshtastic/mesh_interface.py", line 436, in sendText
return self.sendData(
File "/usr/local/lib/python3.10/dist-packages/meshtastic/mesh_interface.py", line 551, in sendData
p = self._sendPacket(meshPacket, destinationId, wantAck=wantAck, hopLimit=hopLimit, pkiEncrypted=pkiEncrypted, publicKey=publicKey)
File "/usr/local/lib/python3.10/dist-packages/meshtastic/mesh_interface.py", line 987, in _sendPacket
self._sendToRadio(toRadio)
File "/usr/local/lib/python3.10/dist-packages/meshtastic/mesh_interface.py", line 1204, in _sendToRadio
self._sendToRadioImpl(packet)
File "/usr/local/lib/python3.10/dist-packages/meshtastic/stream_interface.py", line 120, in _sendToRadioImpl
self._writeBytes(header + b)
File "/usr/local/lib/python3.10/dist-packages/meshtastic/tcp_interface.py", line 79, in _writeBytes
self.socket.send(b)
BrokenPipeError: [Errno 32] Broken pipe
During handling of the above exception, another exception occurred:
(more of the same)```
Maybe it’s the homeassistant integration? Blocking or something?
One thing at a time, people!
</hypocrisy>
I think they're taking an interesting approach. I like the way that packets basically get deprioritized as they get farther from the source and also the whole "room" concept is meaningfully different from channels in that it's like a channel with S+F.
I've played with it a bit and am highly skeptical it will scale. The model almost requires a router for every client. At least, that's the way it's turning out in my neck of the woods. I hope the projects can learn from each other and keep interactions civil.
I haven't tried it, but the folks in the Seattle area seem happy with it generally.
FYI I didn't have success with my Proxmox CT and switched to a VM. I think it was some kind of container permissions issue, but I didn't dig any deeper into it. It was throwing some errors that were hard to spot and building an image that was too small. YMMV though
Yea, the doc I found said to create a vm, the edit the vm file to make some changes to it. But that's as far as I got..
I'm happy to take a look at my VM and answer any questions if you're also using Proxmox and run into issues. Wasn't too bad, though
I don't see meshtasticd on daily..
Unless I'm completely missing the name of the file..
I don't see any file named meshtasticd*
https://build.opensuse.org/project/show/network:Meshtastic:daily this one was linked, only has raspbian and debian and the raspbian .deb has unmet dependencies on fembuntofox
Yea, Jonathan just posted that link..
I have 3 packages to update, but on 10+ min of waiting for apt list --upgradable to output..
Watching a Steve Morris video while I wait for it..
He's doing a dyno of a tractor pull rig..
he builds epic engines
I think so
dpkg -i thing.deb butmaybe I dont know what im doing?
I thought thats how you install deb via comand line
maybe I try your way
That's 1 way, but apt is another, that builds required debs..
apt is just SLOOOWWWWWWWWW
yeah well my way doesn't work soooooo femto@femtofoxHome:~$ sudo apt install ./meshtasticd_2.6.7.133~ppa635de2d~jammy_armhf.deb it is
you will for sure beat me now....
yeah I will definetly have to watch that later
87%
apparently i have to --fix-broken before I can do any more apt-ing
You just run sudo apt install -f by itself directly after a dpkg -i failure
OH.... LOL
And it goes and fetches the dependencies you're missing 🙂
Told you my head isn't right..
All good. Just a good command to keep in your back pocket for the future
-f <filename> or ./filename?
sudo dpkg -i filename.deb
<fail, missing dependencies>
sudo apt install -f
10-4
lol believe me I know... @nova frost basically pranked me today "Build meshtasticd on a luckfox pico"
It has been running for... 16 hours
VERY surprised it has not crashed
@polar ingot This was the walkthru I was trying to follow for a native arm VM.. https://www.reddit.com/r/Proxmox/comments/ed2ldo/installing_and_launching_an_arm_vm_from_proxmox/
SEE this is why I want a spare luckyfox just to compile on.. LOL
I have a spare luckfox, but I'm not going there
docker run --platform linux/arm/v7 -it --rm ubuntu:22.04 bash
faketofox (this command is my go-to tbh, it's extra fast if the host is arm64 too)
Hell I could do that on the 22.04 x86 VM I spun up to figure out cross-compiling on..
Im so not good at docker, I try and install everything "bare metal" (on vms)
Me either..
I have that open in a tab while searching for solutions
OOoohoohhhh fancy!!!!!!!
femto@femtofox-1:~$ sudo dpkg -i meshtasticd_2.6.7.133~ppa635de2d~jammy_armhf.deb
(Reading database ... 58858 files and directories currently installed.)
Preparing to unpack meshtasticd_2.6.7.133~ppa635de2d~jammy_armhf.deb ...
Unpacking meshtasticd (2.6.7.133~ppa635de2d~jammy) over (2.6.7.133~ppa635de2d~jammy) ...
dpkg: dependency problems prevent configuration of meshtasticd:
meshtasticd depends on libinput10 (>= 0.15.0); however:
Package libinput10 is not installed.
dpkg: error processing package meshtasticd (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
meshtasticd
femto@femtofox-1:~$ sudo apt install -f
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
libinput-bin libinput10 libmtdev1 libwacom-bin libwacom-common libwacom9
The following NEW packages will be installed:
libinput-bin libinput10 libmtdev1 libwacom-bin libwacom-common libwacom9
0 upgraded, 6 newly installed, 0 to remove and 2 not upgraded.
1 not fully installed or removed.
Need to get 237 kB of archives.
After this operation, 1343 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://ports.ubuntu.com/ubuntu-ports jammy/main armhf libmtdev1 armhf 1.1.6-1build4 [13.3 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports jammy/main armhf libwacom-common all 2.2.0-1 [54.3 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports jammy/main armhf libwacom9 armhf 2.2.0-1 [19.4 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main armhf libinput-bin armhf 1.20.0-1ubuntu0.3 [22.1 kB]
Get:5 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main armhf libinput10 armhf 1.20.0-1ubuntu0.3 [115 kB]
Get:6 http://ports.ubuntu.com/ubuntu-ports jammy/main armhf libwacom-bin armhf 2.2.0-1 [12.6 kB]
Fetched 237 kB in 3s (90.0 kB/s)
Then I just need to dpkg -i <filename> again, right ?
@twilit mountain after -f do we dpkg again?
twinsies
It should actually happily install meshtasticd as part of this
@chrome tide can confirm for us in 20 minutes
I can confirm now..
Setting up libwacom-bin (2.2.0-1) ...
Setting up libinput10:armhf (1.20.0-1ubuntu0.3) ...
Setting up meshtasticd (2.6.7.133~ppa635de2d~jammy) ...
Processing triggers for udev (249.11-0ubuntu3.15) ...
I'm 69% building dependency tree on fix broken
@twilit mountain Is webui back on 2.6.0 or still 2.5.4 ?
Or are we still waiting for the webui build.tar to be cut after the flatten FS ?
It's on 2.5.4 still. Be on the lookout for a 2.6.1 release 👀 (I am too believe me)
I'm going to be like Opera giving out i2c devices to my 4 femtos later if this works!
"you get a BMP280, and YOU get a BMP280"
I have a BME680 on mine
Yeah I need to buy some now too 😅 I fully invested in the SH3x family
Which appears to be a loser in this library battle
That's why I had em in the first place ❤️
That's why I have my BME280/680s, along w/ a bunch of other sensors.. Including moisture, and PMS500x..
stuck at 96% right now..
been there for a good 5+ min
Maybe I'll make me another drink, and wait it out.. LOL
Install done
Ok, back to 2.5.4 WebUI.. 😭
Luckily I have a copy of 2.6.0 WebUI, that I can copy over to the web folder.. 😉
Ah, much better.. ;P
2.5.4
Unless you are on meshtasticd 2.6.5, which has WebUI 2.6.0
WebUI was broken on ESP32 starting w/ 2.6.5, reverted back to WebUI 2.5.4 for 2.6.6+
I might be, because I noticed the webui was different after I did all the updates
WebUI 2.6.1 should be out soon tho..
Do you have a (#) next to Nodes ?
If you do, that's 2.6.0, if not you are most likely on 2.5.4
I've been here for quite a while: femto@femtofoxHome:~$ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done
Ya you might not get to install till tomorrow..
lol
Holy heck its still working in this.... but it has progressed
tried @twilit mountain docker command with a exec /usr/bin/bash: exec format error
further down the rabbit hole I go
probably should have saved my nodes config before the ugrade....
Error: Timeout was reached
rude
@chrome tide this up to the "register arm utilities" will get @twilit mountain 's docker command going https://www.docker.com/blog/getting-started-with-docker-for-arm-on-linux/
hmmmmmmmmm
there is a company that does $4/mo for 1gb of data in the US - wonder if this would be a workable solution for super unnatended mgmt. Might buy it and give it a try. These only draw around 300ma @ 5v at absolute peak.
I have done it. it works. but yes, a day's work.
wth, haven't been getting notifications here. yall been busy
4 years ago I caught one of my techs watching windows update. Made him shadow me for a week.
I presume you made him carry your chocolate syrup "water bottle", too?
The secret to such productivity is to drink syrup instead of water....
Also, if you put an Alkaselzter (fizzy tablet) in the syrup bottle with water, the nozzle self opens when enough pressure is built and becomes a rocket that easily shoots 10 meters.
Mobile bottle rockets? I like this...
Quectel EC-25AF is the real goat
At least in the USA
No YOUR the real goat vid 🙂
@chrome tide a faster way might be to pull all the .debs for the dependencies and then install them all on the fox.
How does that speed things up?
Are you still on --fix-broken ?
apt takes hours, SCP files from one pc to the fox takes minutes
Apt does take quite a long time
it was waiting for my password all night
It's a 1 core system with max 512MB RAM, of course it's going to be slow..
Argh, and now i just ctrl-c'd it when i was meaning to ctrl-shift-c
anyway, looks like it needs libinput-bin libinput10 libmtdev1 libwacom-bin libwacom-common libwacom9 to satisfy the needs of the daily meshtasticd
I believe so. I can send you the list it installed for me..
did you get any sensors sensing?
Last night after over 60 min of running, still nothing. I have not checked this morning. Dealing with a bad migraine right now..
better than the Quectel EG25 ?
Same thing iirc. Just LCC vs LGA
Hmmm... I have an issue..
I can't log into my femtofox anymore..
This is from serial console...
Ubuntu 22.04.3 LTS femtofox-1 ttyFIQ0
[username:password] root:root femto:femto (default)
femtofox-1 login: femto
Password:
Login timed out after 60 seconds.
The only thing I did was swap a BME680 for a BME280, and booted it back up..
meshtasticd is still working, I just can't log in at all.. SSH and console both seem to time out..
Moved to foxbuntu 1.0
Too many processes, or network issues maybe
No issues logging into foxbunto 1.0
Now to figure out how to import my config file..
Found out that it's possibly an issue w/ 2.6.6+ from high cpu usage..
@polar ingot Don't install 2.6.7
There is a High CPU bug in it. They are fast tracking a new build..
@nova frost I hate youuu 🤣 for making me do this
Welcome to the club
Don't tell the others, but I love you so much for doing this.
And 28.5 hours times 0.4W is only... 11.4Whr
Yeah, ok, that's not going on the sales flyer.
But woohoo!
BWHAHAHAAHAHAHAHAHA Good GAWD 26.5 hours....
Honestly might be less power than my desktop would have used
Yeah, I have to turn mine off these days, or the room gets too hot.