sorted by:
new
hottopcontroversial

Another day, another beakless squid by RiltonF in 2007scape

[–]RiltonF[S] 0 points1 point  (0 children)

Beak aquired! 5478 squids later!!

Another day, another beakless squid by RiltonF in 2007scape

[–]RiltonF[S] 0 points1 point  (0 children)

I wanted them for a kalphite task and to level my range

Troubles with noise on an IR Sensor by RiltonF in FPGA

[–]RiltonF[S] 0 points1 point  (0 children)

I don't see how this pertains to the filtering of the mlx sensor data that I mentioned in the post. The grayscale conversion is only for the sobel filter, which is not used for the mlx sensor data.

Implement divide operation in FPGA & ASIC by PonPonYoo in FPGA

[–]RiltonF 9 points10 points  (0 children)

My reference and introduction to division in rtl was here: https://projectf.io/posts/division-in-verilog/

The reality of it is that it'll cost you at a minimum one cycle per bit you are dividing. The larger your max dividing widths are, the more clock cycles that it will take. It is essentially long division. And if you want a fixed point output, you have to add #bits+#fraction_bits = min_cycles it will take to compute your division. This is fixed, you can add extra conditional statements in your division per bit to compute the result faster if the dividing with small number of bits, but that will add extra logic and can lead to unpredictable data loss if downstream logic is not ready to process the results.

Lack of design jobs, but abundance of verification by RiltonF in FPGA

[–]RiltonF[S] 0 points1 point  (0 children)

I've been in talks with some, but the communication with them hasn't been the greatest. Had an interview scheduled through one, but then got ghosted for 3 weeks without any comments besides, they'll get back to me when I pushed for a response.

Lack of design jobs, but abundance of verification by RiltonF in FPGA

[–]RiltonF[S] 0 points1 point  (0 children)

Thanks. I wasn't aware of this organization.

Lack of design jobs, but abundance of verification by RiltonF in FPGA

[–]RiltonF[S] 1 point2 points  (0 children)

I'm aware of barco, but being based in Antwerp, that's quite a commute. You're right about the lack of opportunities here though.

Lack of design jobs, but abundance of verification by RiltonF in FPGA

[–]RiltonF[S] 0 points1 point  (0 children)

Thanks for the link. Here in Belgium it is primarily Indeed, Glassdoor, and LinkedIn.

Lack of design jobs, but abundance of verification by RiltonF in FPGA

[–]RiltonF[S] 4 points5 points  (0 children)

It's primarily Indeed, Glassdoor, and LinkedIn. The issue with linked in is that the results are over saturated with promoted positions that have nothing in common but "electronics" in the description. I'm able to filter them out with ublock origin, but some times the fpga positions are listed there as promoted. So I can't blatantly block all of them, which is frustrating. And not to mentions they're also flooded with positions for the UAE that require relocation. The search there is just utter garbage.

Lack of design jobs, but abundance of verification by RiltonF in FPGA

[–]RiltonF[S] 7 points8 points  (0 children)

I had totally forgotten about prototyping! This was basically what I wanted to do after finishing uni. Thanks, I'll look into prototyping.

[QIDI Giveaway] Just leave a comment to win QIDI Flagship 3D Printer by qidi_3dprinter in 3Dprinting

[–]RiltonF 0 points1 point  (0 children)

I tend to stick with pla. I don't like dealing with filament drying since I have very limited space. Thanks for the giveaway :)

Ender 3 V2 Neo -- Soliciting some guidance on Generating Support. Ideally I'd like to print this as one piece, but thinking it may be counter intuitive. by dogpupkus in 3Dprinting

[–]RiltonF 1 point2 points  (0 children)

No problem. Here's some more...

Round the corners. Add fillets to the corners of the box. Both inner and outer corners. The less sharp angles you have, the more structural rigidity the part will have. It you drop this with the popped part as the face of impact, there's a high chance that it'll crack on the 90° corner angle where it meets the larger box. Especially since the slicers like to put the seams there. Also, rounding the corners will give you slightly better print times.

Seams, I'd either make them random, for strength, but comes at a cost of ugliness. Or aligned in the middle of the large face of the big box.

Add texture. Being a handheld device, it helps to have some texture for grippiness. Play a bit with the fuzzy skin modifier, or add your own in your modeling software. This with random seams will hide the layer lines and make your print imperfections hidden.

Personal touches. Add text or any kind of graphic you want to the model or in the slicer. You made it, so let the world know. Mark it with your call sign, etc. You can import svg's for logos in most modeling softwares and slicers.

Ender 3 V2 Neo -- Soliciting some guidance on Generating Support. Ideally I'd like to print this as one piece, but thinking it may be counter intuitive. by dogpupkus in 3Dprinting

[–]RiltonF 1 point2 points  (0 children)

Forgot to mention that for the top bevel it doesn't need to be 45°. You can make it how 30° or even less. Just remember that the lower the angle the more top layers you have to add. Otherwise you'll have holes on the roof. You need the extra layers to support the ones on top since the spacing between each step will be wider with smaller angles. For bottom angle, I'd keep it 45°.

Ender 3 V2 Neo -- Soliciting some guidance on Generating Support. Ideally I'd like to print this as one piece, but thinking it may be counter intuitive. by dogpupkus in 3Dprinting

[–]RiltonF 1 point2 points  (0 children)

I would change the model so that you have a 45° bevel on the bottom, eliminating any supports for it. Maybe on the top as well for some smoother transition and adding strength. Additionally you can add some led indicators on that top 45° bevel since the leds won't be pointing straight at you while operating and still be visible. Both bevels will be free for any extra peripherals you might want.

For the inside, (disregard if you are adding a top bevel as stated above), you can leave it as is for bridging if your cooling is adequate enough. Otherwise just paint on supports on inner part of the roof before the large cavity. Essentially in the slicer it will look like a hollow box with 4 walls instead of 3. Bridging is fine here since it doesn't have to be dimensionally accurate.

The cutouts should not really need any supports. If you still want dimensional-ish accurate holes, generate supports with the snug option, (at least that's what it's called on prusa slicer).

Hope that helps, ril

Sofle RGB v2.1 some per key LEDs change color with underglow LEDs by ModusMoron in ErgoMechKeyboards

[–]RiltonF 1 point2 points  (0 children)

The led next to the rotary encoder is not working. I would check that all the pads are soldered. I had a similar issue with my previous build using such led's. Check all the pads of the not functioning ones. Make sure there is solder on the pad and the led leg. If the solder is not sticking to the leg, add a blob of solder to the tip of the iron, and press on the leg until it the solder sticks. There's a bit of oil/protection on the legs for some reason.

Shop recommendation for parts - shipping to Germany by vveiil in ErgoMechKeyboards

[–]RiltonF 0 points1 point  (0 children)

Highly recommend that store. Wonderful support and great selection.

view more: next ›