bdiefinder VS serialport

check this and this and aim for a b-die only kit

You can check on this side : https://benzhaomin.github.io/bdiefinder/

Your kit is not listed here and 18-22-22-42 is untypical for b-die. Altest for the good bins.

I can get my hands on F4-4000C19D-32GTZR. According to b-die finder it is b-die. Will I be able to max out the performance on a 5900x? Is there a difference on kits that run on 1.35V vs 1.5V ? Can I just increase the voltage to 1.5V and reduce timings and frequency? AFAIK 4000Mhz is not possible or not recommended on ryzen because of the 2:1 fclk. Should I buy it or try to find something else?

That kit is indeed b-die. here

Use Samsung b die finder to check SKU, but good rule of thumb is if the frequency is 3200+ and timings are flat (e.g. 16-16-16-34 or 19-19-19-39) most likely it’s bdie. I don’t think patriot sells any 2x16GB kits. I know OLOY and Gskill have some around the $250-275 dollar range. If you aren’t running itx mobo you might just go 4x8GB to save some money.

Absolutely. Just enter the exact model under the link I have earlier: https://benzhaomin.github.io/bdiefinder/

Trident Z memory, only get it if it's listed in the B-Die Finder because then those sticks will be great for overclocking. If not, just stick with Crucial Ballistix.

And for a big list: https://benzhaomin.github.io/bdiefinder/

Strangely enough it does package fine with electron-builder but does not work in dev mode. The same happens when I try to use https://serialport.io/ which is also another module where you could achieve device detection.

We use node-serialport instead of the WebSerial API, since it was only recently that Electron supported WebSerial permission overrides to make things like a 'devices screen' viable. The WebBluetooth APIs are still in a situation where you have to do polling shenanigans to get a full device list. I've found the mutated permissions system leaves a lot to be desired when debugging, whereas the NAPI modules are a lot more straightforward.

It really depends. The stuff I'm doing in this video for example is writing a driver stack for a device called the Bus Pirate. Communication is done over serial (which is easy in node with the serialport library). The bus pirate is a device that allows you to talk to other devices over different protocols, including SPI, I2C, and OneWire (as well as bit banging, where you control some electrical signals directly any way you want using software). So while it's not something you'd do directly in production, you can actually test communication with devices in JS in a fast, iterative, interactive way without having to use a microcontroller. You can actually figure out all of your design decisions there and port your code to the microcontroller later if you're building some kind of embedded system device, potentially saving a lot of time and debugging.

Turns out, there is: https://github.com/serialport/node-serialport/issues/2259

We use node-serialport for USB serial communications. It's included in the transport manager renderer process. The installation guide and docs should be good enough to get you started. Hopefully serialport has prebuilds for the combination of system and electron version you're trying. We had to setup an internal prebuilds system and CDN for our app since we'd often find ourselves ahead of the prebuilt versions for node-serialport. Alternatively you can build from source.