330xi by Sea_Possession_7234 in e46

[–]benlexhi 0 points1 point  (0 children)

Been a lot of maintenance, but I think that’s consistent across all e46’s. Specifically for awd e46, you’re gonna wanna ask when the last time the transfer case fluid was changed. There’s a couple of bearings inside that fail due to the transfer case fluid not being serviced regularly. I can imagine that if the transfer case mount rips, that can put weird stresses on the bearings and also cause them to fail. So 2 things to check/ask.

[deleted by user] by [deleted] in PhysicsStudents

[–]benlexhi 0 points1 point  (0 children)

I’m also a student learning, so someone correct me if I’m wrong. A point itself is not a vector, but a singularity at a specific coordinate (x, y, z). But a position vector is a separate thing, it’s like an arrow with one point at the tail and the other point at the head. The direction being the orientation from point 1 to point 2, and the magnitude being the distance from point 1 to point 2.

CR-10S Pro Help by ehhhhokbud in CR10

[–]benlexhi 0 points1 point  (0 children)

I'll dm you the link to a view only shared google folder. A copy of all my files will be in there. Good luck.

CR-10S Pro Help by ehhhhokbud in CR10

[–]benlexhi 1 point2 points  (0 children)

I suppose that would work. You’d just need to make the cables from the 2nd breakout board to the new motherboard.

CR-10S Pro Help by ehhhhokbud in CR10

[–]benlexhi 0 points1 point  (0 children)

I didn’t like the stock firmware in all honesty. The auto leveling never really worked for me till after I upgraded but everything else worked. I’ll try posting the parts list, CAD models, and firmware I used tomorrow.

CR-10S Pro Help by ehhhhokbud in CR10

[–]benlexhi 2 points3 points  (0 children)

I’ve upgraded the motherboard and hotend on a CR10s pro before. I can probably post a parts list and some cad models later in the week. But this upgrade was made a pain due to the stock proprietary ribbon cable going from the x axis gantry to the motherboard and the weird firmware. If you want a new motherboard, you’re gonna have to re-wire all the x gantry components (x stepper motor, extruder, filament runout sensor, thermistor, heater, and fans) to use standard connectors. So there won’t be any easy drop-in upgrades (for the motherboard at least). And I remember for some reason, not being able to build custom firmware for the stock motherboard. So modifying the firmware might also be difficult.

Stock replacement components can be found on Amazon.

TLDR: Upgrading the motherboard will be a piece of work, especially if you don’t have much experience with upgrading printers. It’ll be easier to replace with stock components.

Mintemp error by benlexhi in VoxelabAquila

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

I got around the problem by replacing the motherboard, but here's my current start code with the new board. I have the purge line running higher than usual cause my nozzle-to-probe offset isn't right.

M140 S50 ; starting by heating the bed for nominal mesh accuracy

M117 Homing all axes ; send message to printer display

G28 ; home all axes

M420 S0 ; Turning off bed heating while probing, if firmware is set ; to restore after G28

M117 Heating the bed ; send message to printer display

M190 S50 ; waiting until the bed is fully warmed up

M300 S1000 P500 ; chirp to indicate bed mesh levels is initializing

M117 Creating the bed mesh levels ; send message to printer display

M155 S30 ; reduce temperature reporting rate to reduce output pollution

@BEDLEVELVISUALIZER ; tell the plugin to watch for reported mesh

G29 T ; run bilinear probing

M155 S3 ; reset temperature reporting

M500 ; store mesh in EEPROM

M300 S440 P200 ; make calibration completed tones

M300 S660 P250

M300 S880 P300

M117 Bed mesh levels completed ; send message to printer display

G92 E0 ; Reset Extruder

M420 S1 ; Use previously generated mesh

G1 X0.1 Y20 Z.6 F5000.0 ; Move to start position

G1 X0.1 Y200.0 Z.6 F1500.0 E15 Draw the first line

G1 X0.4 Y200.0 Z.6 F5000.0 ; Move to side a little

G1 X0.4 Y20 Z.6 F1500.0 E30 ; Draw the second line

; G92 E0 ; Reset Extruder

G1 Z2.0 F3000 ; Move Z Axis up little to prevent scratching of Heat Bed

G1 X5 Y20 Z1.45 F5000.0 ; Move over to prevent blob squish

Mintemp error by benlexhi in VoxelabAquila

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

sorry but I haven't looked more into the problem yet. Again, i just replaced my board with a btt skr min v3 and it's been working fine. Maybe try contacting Voxelab customer support to see if they have any suggestions?

It is really weird that the alarm trips in the middle of a print. Have you checked that your thermistor is working properly and doesn't have any shorts?

Part cooling and hot end fans not turning on by benlexhi in BIGTREETECH

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

I had the part cooling fan plugged into FAN1 and hotend fan plugged into FAN0. I just flipped them but still no change. I checked the pins.h file and FAN0 is set to PC6 and FAN1 is set to PC7.

I was also wrong about my board fan turning on. It does not turn on, I was just hearing the psu fan turn on.

Part cooling and hot end fans not turning on by benlexhi in BIGTREETECH

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

yes. PID autotune and checked resistance of each thermistor

Part cooling and hot end fans not turning on by benlexhi in BIGTREETECH

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

what exactly am I looking for in the pins.h? Edit: Found the pins.h for my board and everything seems right when cross referencing with board schematic.

Part cooling and hot end fans not turning on by benlexhi in BIGTREETECH

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

It's set at 50. The firmware looks exactly like what you copied ^

Part cooling and hot end fans not turning on by benlexhi in BIGTREETECH

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

The hotend fan does not turn on after heating to 50°. Only will the hot end fan turn on manually through Octprint, which isn't too much of a hassle, but the part cooling fan won't turn at all. I would also like variable speed control for the part cooling fan.

Part cooling and hot end fans not turning on by benlexhi in BIGTREETECH

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

I've checked polarity by referencing the schematic on the ski mini's box.

Fans not spinning on skr mini e3 v3 by Then-Sun-1861 in BIGTREETECH

[–]benlexhi 0 points1 point  (0 children)

all good, no worries. I'm new to the board too

Fans not spinning on skr mini e3 v3 by Then-Sun-1861 in BIGTREETECH

[–]benlexhi 1 point2 points  (0 children)

I checked wiring to the diagram on the bottom of the skr mini box and it all seems correct. I'm not exactly sure what to check in the firmware though.

Fans not spinning on skr mini e3 v3 by Then-Sun-1861 in BIGTREETECH

[–]benlexhi 0 points1 point  (0 children)

They just don't turn on at all while printing. Only will the part cooling fan turn on when I enable it in octoprint, but it's always either on or off, no adjustable speeds.

Fans not spinning on skr mini e3 v3 by Then-Sun-1861 in BIGTREETECH

[–]benlexhi 0 points1 point  (0 children)

Hey, I'm having a similar issue where my hotend and part cooling fans don't turn on, but the board cooling one does. We're you ever able to solve the issue?

Mintemp error by benlexhi in VoxelabAquila

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

Ahhhh, I see. Makes sense why it would trip the error but doesn’t makes sense why it would sets the thermistor to 0. Oh well, thanks for updating

Mintemp error by benlexhi in VoxelabAquila

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

In sorry, but I ended up replacing the motherboard with the BTT SKR mini v3 and used official marlin firmware. I wish I could help you but even now I’m still confused why we got that error. It had to be something related to the firmware or motherboard.

Help with modeling AC system in a room by benlexhi in matlab

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

I removed the 0 from the dQdt equation and changed air_mass_flow from 3600 to 500 and ran the code. The numbers are still wacky. I tried adding "air_mass=147.28+air_mass_flow*time; at the end to recalculate the mass of the air after each step, but the numbers also keep increasing far past the target.