Hy,
what Kind of Z-Probe do you use ?
Posts made by wummelfrosch
-
RE: Mesh Bed compensation "not working enough"
-
RE: possible error in firmware 3.2x
@wilriker
at first... sorry for the delay of my reply, because there are a lot of work in business and at homeI have testing the Firmware 3.2.11 and it seems to work fine for me
Thank you
-
RE: possible error in firmware 3.2x
Great ! I will test it and give you a feeedback again
-
RE: possible error in firmware 3.2x
@wilriker said in possible error in firmware 3.2x:
For version 3.3 a revised fan handling is planned so you can control all fans of all tools in all situations. But no work in this direction has yet been implemented.
ok thank you. I wait for v 3.3 and would be happy if this change is implemented then
-
RE: possible error in firmware 3.2x
@wilriker
oh super... Thank you very much. Just how can I solve you best? as written above I always need both fans, no matter which tool I'm using -
RE: possible error in firmware 3.2x
@wilriker
Hello, nothing changes even after the update to rrf3.2.2. However, I have now noticed the following : if I print with tool 1 it goes ! only with tool2 it is not possible ! I think that could help a lot in the solution. maybe I can fix it with the slicer startcode ? -
RE: Grid Compensation only for a few layers ?
Super, thanks for the hint. I somehow overlooked or misinterpreted this
-
Grid Compensation only for a few layers ?
Hello, is there a possibility to use the grid compensation only for a certain height and then, for example, to let slowly weaken from 3mm or possibly switch off directly ? under my old repetier firmware this was possible. in the docu I found nothing about it. Thank you for the feedback
-
RE: possible error in firmware 3.2x
@wilriker
Hello, thank you for the answer. I've tested it and it's not working. I used the latest RRF and until the update of the Panel Due Firmware it still went. I have to say that I use a Chimera Dual WakΓΌ Hotend and always use both component fans, i.e. right and left at the same time. The firmware was created with the Config tool. In the Config.g, the fans are assigned to both tools ( (F 0:1) ! I need no Hotend fan because i use WakΓΌ. That has always been the case and I haven't changed anything about it.I will try the new Firmware bundle 3.2.2
-
RE: possible error in firmware 3.2x
Hello, is there already a solution for the component fan problem ? Can I do something wrong? at felt one of 10 print it goes and at all other .. Not.
I slice with s3Deven if I manually set the fan on the Panel Due it often does not work !
-
RE: bad bed adhesion on one side after rff3 upgrade
which sensor (Z-probe) is used ? maybe this is the fault ? I had such a similar problem with the optical sensor of DC on the green gfk print surface. The values were sometimes good and then again bad and partly implausible ! Only after switching to BlTouch did I have reproducible values.
-
RE: possible error in firmware 3.2x
@garyd9
ok thank you ! such variant already came to my mind , I would have tried it over the pause.g :-), but I would have thought that such a thing should also go automatically in the RRF 3.2I will adapt it
-
possible error in firmware 3.2x
Hello, since I updated to the 3.2.7 shows my Paneldue 7i 0% on the component fan, even though the fan is running ! On the web interface it is displayed correctly ! The error can only be solved once I set the fan to a desired level on the panel due. from this point on, it then also takes over the correct fan setting at the next fan change in the pressure ! I have now fused on the panel due 3.2.9 and the error is still present ! What could that be? First of all, thank you for your ideas. best regards from Germany
another funny thing is that since the RRF 3 the component fans continue to run when I pause the print and then break ! I always have to turn it off manually !
Duet Web Control 3.2.0
RRF 3.2
config (1).g -
RE: Since updating to RRF 3.2 Release Heater Fault
I dont think so !
I have no T0 in Start Code or in my Config.g , because i use the e3d chimera+ and have set offset T0=-9mm / T1= +9mm.
and the bed distances goes from the mioddle of the chimera !
I havent change the startcode ! -
RE: Since updating to RRF 3.2 Release Heater Fault
for the sake of completeness and as a possible clue for other users here is the result of the E3D Chimera+ WakΓΌ Hotends with brass heating block, brass E3D 0,4 Nozzle , E3D High Precision Heater Cartridge 24V / 30W heater and E3D 104 GT Semitec Sensor:
Auto tuning heater 2 completed after 3 idle and 10 tuning cycles in 775 seconds. This heater needs the following M307 command:
M307 H2 R1.480 C349.2:241.3 D7.99 S1.00 V24.4Bye and have a good time
-
RE: Since updating to RRF 3.2 Release Heater Fault
Wonderfull
The printing started without any problem and change to the start code and is running properly! I assume that the error message "No Tool Selected" came due to the heater error. Now after another measure, it's time to do it again. In addition, it should be mentioned: Until the new measuring method of the heaters ( rrf3.2 stable) I had used the Epkos T100000 B4092 for the heating bed and there were no errors except for the overpowerd message and I could print. Now with the new method there was no more pressure and the error of the wrong sensor was noticedsuper work . Respect and I regret no second only to use original parts and to leave the fingers of all the copies :-)I think the thread can be closed. Thank you very much
-
RE: Since updating to RRF 3.2 Release Heater Fault
Great
the heatbed tuning is finishing perfect !
These are the results:Auto tuning heater 0 completed after 3 idle and 5 tuning cycles in 1701 seconds. This heater needs the following M307 command:
M307 H0 R0.170 C1012.5 D4.86 S1.00 V24.5
Send M500 to save this command in config-override.g -
RE: Since updating to RRF 3.2 Release Heater Fault
Ok, very big thanks for the moment
can anybody upgrade the documentation ?
- that it doesn't matter with the bl touch whether 25, 500 or 1000 ! because the configtool chooses 500 and is mentioned in the description 25
- and that you can take t instead of h for the autotune
- in addition, the possible error of the endstops with the missing "!" in the creation of the config by the Config Tool ! see above in the first post
I have consistently followed the description and yet questions have come up again and again
-
RE: Since updating to RRF 3.2 Release Heater Fault
wow Great Thanks for the fast reply !
The Vendor of the Heatbed Says:
Thermistor ist 3950K in Marlin-Firmware (Epcoslike)
Neue Marlin Firmware 60 als Thermistor wΓ€hlen.Actually ive used the : QWG-104F-3950 Sensor in RRF Konfigurator for testing. I hope this is the right one
also blTouch ist 25 ok ? or better go with 500 or 1000 ? I think this are the sensitivy:-)
can you look at my S3D Startcode in the first post ? Is that ok so ?
ive tune the heater tomorrow again with M303 T1 S250 then it should go