<firefrommoonligh>
I would imagine there might be some chemical limitations regarding bond strength and electron density which would factor in the project requirements as well.
<firefrommoonligh>
Unrelated: LpUart's Baud setting is a double-overflow trap
<firefrommoonligh>
First you will overflow the u32 if calculating it without minding order-of-operations
<firefrommoonligh>
Second, you will overflow the register's 20-bit limit unless you knock the prescaler down by ~x10 for low BAUDs
<firefrommoonligh>
I accidentally wired two devices to the same uart periph, but one was also a lpuart, so here we are...
_whitelogger has joined #rust-embedded
jannic[m] has quit [Quit: Idle timeout reached: 172800s]
pcs38 has joined #rust-embedded
reto[m] has joined #rust-embedded
<reto[m]>
<cbjamo[m]> "I want to build something that..." <- How fast are you thinking? I am currently working with a quadrature counter that can achieve count frequencies of up to 40 MHz, this chip here: https://www.ichaus.de/product/iC-MD/
<reto[m]>
trying to put together the rust driver for SPI comms. let me know if you are interested :)
sroemer has joined #rust-embedded
<Mihael[m]>
do you guys have any experience how much more expensive a round PCB design is compared to rectangular?
<JamesMunns[m]>
It's not, usually. You might have to pay for the square area it takes up, but the cost per cm² isn't usually the most expensive part
<Mihael[m]>
I physically don't have the space for the esp32 on this side, so i'd have to place it on the other side
<Mihael[m]>
now what i'm wondering is, is it a big complexity to get the connections from one side to another?
Emkanea[m] has joined #rust-embedded
<Emkanea[m]>
depends on the number of total electrical nets you have to route
<Emkanea[m]>
but it doesnt look to bad
<Emkanea[m]>
if that are all components
<Mihael[m]>
yeah that's all. And i'm also wondering about that relay and power supply. I have seen some products do two PCBs and then connect them via a connector (so the pcb with the IC only gets 3.3v and a relay pin connection
<Mihael[m]>
I liked the idea, since it saves me space and allows me to also test it later with a 3.3v connector instead of being on 230
<Yann[m]>
Would anyone know anything and help me figure out why I am unable to receive any data
dne has quit [Remote host closed the connection]
<Emkanea[m]>
<Mihael[m]> "yeah that's all. And i'm also..." <- I think the only argument against a two board solution is cost or EMC considerations. For a trivial power supply and a relay signal this should not be an issue.
dne has joined #rust-embedded
RobinMueller[m] has quit [Quit: Idle timeout reached: 172800s]
<firefrommoonligh>
<Mihael[m]> "I physically don't have the..." <- Two-sided assembly is much more expensive. Since its one part, you could hand-solder the ESP, but hot-plate won't work because there would be parts on the down side. (And hot plate is great for soldering modules like that.
hrmny[m] has joined #rust-embedded
<hrmny[m]>
<Mihael[m]> "I physically don't have the..." <- as mentioned 2 sided assembly is expensive, might be worth considering if you can just put the LEDs on the other side and everything else on this, LEDs would be easy to hand solder
<hrmny[m]>
* on this side, LEDs
diondokter[m] has quit [Quit: Idle timeout reached: 172800s]
Lumpio[m] has joined #rust-embedded
<Lumpio[m]>
Mihael I tried reading the logs but couldn't find an exact answer - what are you building? 🙂
<Mihael[m]>
hrmny[m]: yeah i'll be hand-soldering quite a lot of these elements :/
<Mihael[m]>
I don't think i'll get the assembly on the jlcpcb (except maybe? the chip)
<Mihael[m]>
Lumpio[m]: a smart thermostat
<Lumpio[m]>
Ah, so encoder for a twisty knob, LEDs for temperature display, and a relay to control a heater/cooler/whatever?
<Mihael[m]>
Lumpio[m]: yessir
<Mihael[m]>
I'm trying to make a "clicky clicky" feeling using a spring sleeve, but the ratios of internal gears for that encoder are so ugly
<Lumpio[m]>
Does it have to be that encoder? You can get encoders for knobs with e.g. 20 detends
<Mihael[m]>
not gears of the encoder itself, but to transfer the twisty knob rotation to that encoder
<Lumpio[m]>
s/detends/detents/
<Mihael[m]>
Lumpio[m]: I wasn't able to find any mechanical ones that would be "affordable"
<Mihael[m]>
this one is ~2€
<Mihael[m]>
the rest were like 5+
<Mihael[m]>
actually, i was looking wrong apparently
<Lumpio[m]>
This is a pretty standard form factor for an encoder with a knob, there's also ones with shorter/longer shafts
<Mihael[m]>
yeah this could do, thank you. For some reason i was stuck with this one.
dcz[m] has quit [Quit: Idle timeout reached: 172800s]
<Mihael[m]>
would you say THT is better for this than SMD
<Mihael[m]>
or no difference
<Mihael[m]>
idk why smd mounts are more expensive (at least on mouser, is there some secret sauce?)
<Lumpio[m]>
There's tradeoffs, THT is probably a bit more mechanically stable, but also expensive to assemble if you're doing series production, if you're doing just a few there's no difference
<Lumpio[m]>
Oh and they're available from Mouser too of course, probably for even cheaper, I just had this site open
<Mihael[m]>
thank you!
<Lumpio[m]>
Oh and of course THT takes space from both sides of the PCB, so it's more annoying to lay out potentially
<Lumpio[m]>
Speaking of layout not to be a spoilsport but I see an AC-DC converter in your project so there's probably mains voltage involved, do remember to read up on correct mains isolation if you have high and low voltage on the same PCB and/or connector, in a part that humans might be touching
<Mihael[m]>
Lumpio[m]: yeah that was also one additional reason why i wanted to create a separate pcb behind it
<Mihael[m]>
and connect it through header pins
<Mihael[m]>
okay so apparently i don't understand... I thought "detent" was the element that connects in the encoder itself?
<Mihael[m]>
so i assumed resolution = detents
<Lumpio[m]>
I think in most encoders that have detends the number of detents is the same as resolution
<Lumpio[m]>
Some of them might have slightly different output signals so there might be a separate "number of pulses" spec but the amount of stable and unique positions it can detect is the number of positions/detents
<Mihael[m]>
oh so detents are the "snap"
<Lumpio[m]>
yes they're the clicky bit
<Mihael[m]>
sorry i'm new to this so my terminology needs some work
<Mihael[m]>
that's great since it's not as easy to get "floats"
<Mihael[m]>
i did not know this existed, awesome
lulf[m] has quit [Quit: Idle timeout reached: 172800s]
MichaFita[m] has joined #rust-embedded
<MichaFita[m]>
Question about practices with PAC crates:
<MichaFita[m]>
If I need to publish PACs but my dependencies require now rustc 1.81, should I bother taking them down to lower the MSRV (originally on 1.74), or just bump that minimum on mine and don't bother?
haobogu[m] has quit [Quit: Idle timeout reached: 172800s]
<Mihael[m]>
<Lumpio[m]> "yes they're the clicky bit" <- When would 24 detents and 12 PPR be better than 12 detends and 12 PPR?
dirbaio[m] has quit [Quit: Idle timeout reached: 172800s]
<Lumpio[m]>
I don't really know why both types exist
Noah[m] has quit [Quit: Idle timeout reached: 172800s]
sroemer has quit [Quit: WeeChat 4.5.2]
<Mihael[m]>
i can't just cut off half of the shaft can i
<Mihael[m]>
they're all so long 😂
<Lumpio[m]>
I've done it with a hacksaw and file, but did you look for a shorter shaft one?
<KevinPFleming[m]>
we got a new car last week and there's a rotary wheel on the dashboard for controlling the AC temperature. when the car is configured for Fahrenheit, you have to move through two detents to change the temperature by one degree (it cannot be adjusted by less than one degree). I assume when it is configured for Celsius, it will be one detent per half-degree.
<Lumpio[m]>
Having it click and not do anything sounds like mediocre UI design
<Mihael[m]>
Lumpio[m]: yeah that's what i'm afraid of
<Mihael[m]>
<Lumpio[m]> "I've done it with a hacksaw..." <- either out of stock, x10 price or non existing
<Mihael[m]>
out of stock on multiple stores that deliver
dne has quit [Remote host closed the connection]
dne has joined #rust-embedded
<Mihael[m]>
<KevinPFleming[m]> "we got a new car last week and..." <- how'd they manage that
<Mihael[m]>
i'm correct to read that total height is 23mm
<Mihael[m]>
so tall
BradleyNelson[m] has joined #rust-embedded
<BradleyNelson[m]>
<MichaFita[m]> "Question about practices with..." <- > <@michal.fita:matrix.org> Question about practices with PAC crates:
<BradleyNelson[m]>
> If I need to publish PACs but my dependencies require now rustc 1.81, should I bother taking them down to lower the MSRV (originally on 1.74), or just bump that minimum on mine and don't bother?
<BradleyNelson[m]>
I'm curious what the embedded community thinks about this as well.
<Mathias[m]>
(I hope it's the right thing to do), and I noticed there was a change to support Rust 1.59, but the MSRV notes in READMEs says 1.82.
<thejpster[m]>
Mathias[m]: good catch
<Mathias[m]>
thejpster[m]: Although it's only for the build host and `arm-targets` crate.
<thejpster[m]>
Mathias[m]: arm-targets I want to be widely applicable (until the compiler starts handing out better target information than just 'target_arch=arm'), so I want that to be set as low as possible. The others I am happy if they are just "most recent Ferrocene stable"
<Mathias[m]>
thejpster[m]: Probably some mild form of OCD, but the `authors` fields in the examples/*/Cargo.toml are not indented like the others.
<Mathias[m]>
Mathias[m]: Now that the `rust-version` field is set, do we want to keep this sentence "It might compile with older versions but that may change in any new patch release." in the MSRV section?
<Mathias[m]>
Mathias[m]: It looks good to me, I put a thumbsup emoji in the PR.
<thejpster[m]>
Mathias[m]: oh well now you've pointed it out it will annoy me too
<thejpster[m]>
thejpster[m]: I don't know that the Rust project has good guidance on using the rust-version field. But yeah, if we set it to X, it's hard to claim it will work on < X.
<thejpster[m]>
thejpster[m]: It should say something like "Increasing the MSRV (as recorded by the `rust-version` field in `Cargo.toml`) is not considered a breaking change and may occur in a minor version release"
<Mathias[m]>
<thejpster[m]> "It should say something like "..." <- I agree
<Mihael[m]>
does anyone use Kicad here?
<Mihael[m]>
I'm struggling to cutout a rectangular shape out of a circular PCB. I've tried adding an edge cutout to the already round edge cutout (pcb), but it only cuts a hole if it's entirely inside the original shape
<Emkanea[m]>
<Mihael[m]> "do i even need a cutout?" <- As far as I know you do not need a cutout of the PCB but only remove all copper layers in the antenna area. I designed a BLE antenna on the PCB itself (not as a module). There I just place the antenna at the board and removed all copper areas below the antenna and to the sides
<Emkanea[m]>
* antenna at border of the board
<Mathias[m]>
<MichaFita[m]> "Question about practices with..." <- Sometimes if it's not too painful to do, I will try not to bump the MSRV.
<Mathias[m]>
But otherwise, I would just bump and not bother.
<firefrommoonligh>
You want a keepout
<firefrommoonligh>
not a cutout
<firefrommoonligh>
there is a tool explicitly for that. Mouse over the tools on teh right until you find it
<firefrommoonligh>
*What emkanea said
<firefrommoonligh>
Also, probably obvious and makes sense, but trace antennas are not great, but have obvious convenience and size perks
<firefrommoonligh>
And the module trace is nicer than doing your own
Noah[m] has joined #rust-embedded
<Noah[m]>
<Max[m]> "Noah: anything else i can do..." <- sorry will check again at homr :)
<Mihael[m]>
so keepout on all layers?
<Mihael[m]>
also with the module trace, can i somehow get their antenna area to copy into the keepout?
<dngrs[m]>
<thejpster[m]> "Ooh, they turned QEMU into..." <- "similar items": S8301897 Arm Rest, LH, Black Molded Duratex - Fits Versatile. Makes sense 😅
<dngrs[m]>
* "similar items": S8301897 Arm Rest, LH, Black Molded Duratex - Fits Versatile.
<dngrs[m]>
Makes sense 😅
<Mihael[m]>
just wondering, if it's just like this (photo), is it completely useless or just might not work as optimal as possible
<firefrommoonligh>
<vollbrecht[m]> "esp's offer the PCB layout..." <- This is the answer: Follow the datasheet for these issues. They will tell you if/where you need a KO. If you want to design your own trace antenna, Espressif has its official guide.
<firefrommoonligh>
If you break these rules, things will probably work fine. But may have adverse affects on signal strength, interference resistance, anomalies
therealprof[m] has quit [Quit: Idle timeout reached: 172800s]