lav8org

Results 13 comments of lav8org

I've got the board operating with EEPROM enabled (idk which intermediate change mattered, but the occasional self solving problem is alright). `19:51:30.745 : N13 M504*16 19:51:30.748 : DIGIPOTS Loading 19:51:30.748...

maybe I just haven't grokked the design patterns yet, but the concurrency and channels of go really don't make it easy to trace the logic of a program a priori!...

doable! M503: ``` [18:36:14:958] echo: G21 ; Units in mm (mm)␊ [18:36:14:979] ␊ [18:36:14:979] echo:; Steps per unit:␊ [18:36:14:979] echo: M92 X94.1020 Y63.2240 Z14.9260 E1.0000␊ [18:36:14:979] echo:; Maximum feedrates (units/s):␊...

nw, at this price point I can be _very_ patient :grin: I just tried it and still get the panic. Running main.go from shell. Double checked things on the top...

``` cat ~/workspace/plot\ optimizer/lnwidth.gcode | ../bin/stepd -device /dev/ttyACM0 -baud 115200 | grep -v "ok" info:generating bed level function... info:config processed info:bed level z-func loaded panic: Failed to load device settings...

Nothing special that I'm aware of. When I do a direct serial connection there's no announce and Repetier-Host always logs "No start signal detected - forcing start" I tried looking...

I don't think so? Not sure how best to check, I just turned on a fan and then disconnected and ran stepd and the fan didn't stop.

Repetier follows that with an M115 fwiw

looked like it didn't work but apparently bash silently updated paths when modified in the UI... wouldn't have had any idea unless the stack trace had "trash" in it. Unfortunately...

DIRECT_STEPPING is enabled. Although I have discovered that since enabling EEPROM some settings in FW are not updated when flashed/overridden by previous settings until manually saved to EEPROM, but don't...