Hi again, answers are as follows:
1: The flashing process for firmware & display software has already been described by Sovol here.
2: It is a feature of GitHub to provide the sources in two different archive types. The packed source files are identical. You’ll just need the .bin file to flash your firmware. The source files will become handy in case you want to build up your own firmware version.
3: It won’t make any difference, but your SV04 will need both changes to work properly.
5: Sure - you can change back anytime you want.
4: There are several downsides:
Custom firmware is updated more often than the stock firmware, therefore you might be updating in a higher frequency.
Once you tried custom firmware you propably won’t be willing to go back to the stock firmware because you’ll get used to additional features.
I really appreciate that. Please keep your money - receiving feedback is totally sufficient for me.
EDIT - looks like the screen didn’t like the 32gb SD card it worked with my 8GB SD card so all is good now to have fun and play around. thanks so much
i have successfully flashed the main board however i think the screen flash is failing. according to solvols instructions if it displays all 0 then it has failed. i have tried multiple times now and its always all 0 here is a picture
so the firmware swap did not fix the issue. that said im still glad i switched. i just did a PID calibration on both print heads and that didnt fix it either… i have found a way to get the 2nd extruder to start though ill post a video of me doing it maybe that can help solve the issue.
I notice there is a new bed leveling feature called tramming. i am not to sure how to use it.
my current method is to:
auto z allign,
aux leveling
auto leveling
can you please let me know when/ at what step i should use the feature. it spits out some info after its done and im not to sure what to do with it
finally i think i found a bug or 2 in the firmware is there a specific place i can share the bug info?
Hi again,
thanks a lot for the feedback - now I’m very curious what the problem is. We will keep looking for it if you provide information on it,
The tramming procedure helps to adjust the bed corners so that the bed is as true to the machine frame as possible. It tells you how to rotate the leveling wheels in the corners (like an analog clock: CW=turn clockwise, CCW=turn counterclockwise, 1 hour= 1 full turn, 1 minute = 6 degrees).
My bed leveling process starts with tramming, then I run auto leveling & save. The auto leveling output screen shows the height difference between the measurement in the centre and each probing points in mm. All probing points are illustrated by squares according to XY position and height difference: Negative distances are colored green, positive distances in red. Large differences are shown in bright color, small differences in dark color. The result is a height map of your print bed.
Auto z alignment runs a mechanical gantry calibration procedure.
You can send bug reports directly via personal message in this forum (click on my “B” avatar & click message button) or post them in this thread or a separate one. In case that you have a github account you can raise issues using my github repository.
THANKS, the auto tramming seems to work great now that I know how to use it.
after my attempts to fix the problem had failed. I decided to study the temps more closely and noticed the problem extruder temps where rapidly swinging + - 15 degrees and never really staying at a constant temp. my other extruder was very constant. I knew the problem had to be something with temp.
It appears that when I was calibrating the PID levels for extruder #2 (t1) I did not assign the extruder number when imputing the results… I just simply put M301 Pxx.xx Ix.xx Dxx.xx that ended up saving the results to extruder 0 instead of extruder 1 (the problem one.)
seeing those numbers sway like that, and at the time not realizing i did the PID calibration wrong i replaced the hot end it was when I went to calibrate the replacement hot end that I realized the mistake I originally made…
so I’m not to sure what ended up fixing the problem the proper PID calibration or the replacement of the hot end and sensor. but it is going great ATM. I will post a confirmation after several runs. I picked up this SV04 heavily used so I think I have a few more problems to hammer out.
Hi again,
you can check the success of your PID tuning process by sending the M503 g-code command via Printrun to your SV04 iot get a report of all settings including PID parameters.
It is very unlikely that PID tuning has been successful in case that the PID parameters for both extruders are equal. The same applies in case that the firmware default PID parameters are displayed [E0 P29.93 I3.50 D64.04 E1 P30.13 I3.39 D66.88].
If PID tuning has not been successful you may want to try the following procedure via Printrun:
M106 P0 S255; left fan max power
M303 C8 E0 S210 U; run left extruder 210°C PID tuning for 8 cycles & set results
When finished take notes of computed PID parameters for left extruder & continue:
M106 P0 S0; stop left fan
M106 P1 S255; fan 1 max power
M303 C8 E1 S210 U; run right extruder 210°C PID tuning for 8 cycles & set results
When finished take notes of computed PID parameters for right extruder & continue:
M106 P1 S0; stop right fan
M500; save data to EEPROM
M503; report settings
Just in case that the previously computed PID settings still have not been saved:
M301 E0 Pxx.xx Ix.xx Dxxx.xx; set results for left extruder
M301 E1 Pxx.xx Ix.xx Dxxx.xx; set results for right extruder
M500; save data to EEPROM
M503; report settings
