Variable ABL

April 8, 2019, 10:19 am

≫ Next: Azteeg X3 Pro - 7th and 8th driver problems

only a short throw-in
A really useful feature would be to assimilate the ABL grid to the size and place of the object i want to print

Something like
small object --> 2x2 grid
big object --> 7x7 grid

background idea:
when printing with thin layers (0.05mm) my 5x5 ABL grid isn't fine enough and i ve problems with adhesion
a bigger grid would take way longer with small objects 5x5 -> 25 Points, 10x10 -> 100 Points

so a pretty cool feature would be to give the printer the dimension (distance) of the grid and the firmare levels only the points, which effects the print object.
like i tried to display in the picture below.
my original grid is 10x10 and the green circle displays my printing area.
Therefore i only want to "level" the red dots, the others retain with the old values

This would improve qualtiy and reduce the amount of restarting a print

Image: https://forum.repetier.com/uploads/editor/1n/bwhf5hxw61kt.png

↧

Azteeg X3 Pro - 7th and 8th driver problems

April 8, 2019, 7:52 pm

≫ Next: PI version works, 3.5 LCD touchscreen, I can't seem to be able to rotate the XY touch

≪ Previous: Variable ABL

I'm having issues using the 7th (or 8th) driver my Azteeg X3 pro board. Everything works great on the first six drivers. I recently added a second extruder that I can't get to function correctly. I think it is a firmware issue that I could use help identifying.

I've tested the motors, drivers, and wiring - all of which work independently by when i flashed a test sketch. I was also able to get the new stepper driver to run when using Marlin - but I don't like marlin and would rather use repetier.

I've been using repetier host to send gcode. Any thoughs?

↧

PI version works, 3.5 LCD touchscreen, I can't seem to be able to rotate the XY touch

April 8, 2019, 10:01 pm

≫ Next: V14 with 0.91.2 in Pi 3 - Babystep not working & - Language Chinese abnormal

≪ Previous: Azteeg X3 Pro - 7th and 8th driver problems

my server is running, I have been racking my brain searching the web, to swap the x for the y, for the UI, the screen is showing the correct orientation but the x and y are swapped, all the info I have found assumes that raspbian or jesse is installed, since i installed the image directly some of modules are not even there. help please

↧

V14 with 0.91.2 in Pi 3 - Babystep not working & - Language Chinese abnormal

April 3, 2019, 8:56 am

≫ Next: #define BAUDRATE

≪ Previous: PI version works, 3.5 LCD touchscreen, I can't seem to be able to rotate the XY touch

<Babystep not working> Firmware Repetier 0.92.9, babystep works on 128x64 controller, but not works on Pi 3 (Z no move when touch).
<Language Chinese abnormal> When change language to Chinese, all words on screen change to block.

Any solutions? Thanks!

↧

#define BAUDRATE

April 9, 2019, 3:16 am

≫ Next: Z Sensors

≪ Previous: V14 with 0.91.2 in Pi 3 - Babystep not working & - Language Chinese abnormal

I have mega 2560 + ramps1.5 on delta printer. I install repetier firmware version 1.0.3. First time i set #define BAUDRATE 115200, then i rebuild config and set #define BAUDRATE 250000, but no changes. I try arduino ide from 1.8.6 to 1.8.9 no change. OS windows 10 pro. Compile no errors. Cange 2 plate the same. If install marlin no problem with BAUDRATE. If i try send M502 i resive Resend:1

ok. in cikle .

What need to be install firmware?

↧

Z Sensors

April 9, 2019, 9:55 am

≫ Next: Home to Z max

≪ Previous: #define BAUDRATE

Hello,

Usually when I use my printer3D, I have a capacitive sensor set on the heated bed, it is declared on the ENDSTOP_PULLUP_Z_MIN.

I would like to use a other sensor (just a switch) when I use CN as CNC Milling, is't possible without deconnect the capacitive sensor ?
and how to declare in firmware on a other pin?

This sensor will always be higher (placed on the part) and used with G30 H (xx) R (xx).

Best regards

↧

Home to Z max

April 3, 2018, 12:54 pm

≫ Next: klipper infinite LOOP once getting in halted status

≪ Previous: Z Sensors

Hi, I have a cartesian printer home made, arduino due with Radds, It's working fine, but I want to try homing Z to max endstop.
The values I'm going to tweak in firmware are:
#define Z_HOME_DIR 1
#define Z_MAX_LENGTH 210
Do I need to edit other values?
What if my Z axis lenght is a non integer value?

↧

klipper infinite LOOP once getting in halted status

April 10, 2019, 9:30 am

≫ Next: Z-Probing, Correction matrix and Z-Home

≪ Previous: Home to Z max

I found RS default setting have issue at halted status handing for klipper. Due to RS will send commectionCommands once it got "!!" (halted signal) and Gcode M220 / M221 / G92 / G90 / M82 / M117 will make klipper resent the halted information. It cause RS looping to get the error info and make the RS stop working.

I workaround to change the startup script from

<connectionCommands>M105

M115

M220 S100

M221 S100

G92 E0

G90

M82

@getip

</connectionCommands>

to

<connectionCommands>M105

M115

</connectionCommands>

and no infinite LOOP after error.

provide part of log:

> 20:52:12.024: Firmware was halted, trying to reconnect. Eventually running print is stopped.

> 20:52:12.035: Response while unconnected:!! Heater extruder not heating at expected rate

> 20:52:12.036: !! Heater extruder not heating at expected rate

> 20:52:12.036: ok 7

< 20:52:12.036: N1 M105

< 20:52:12.036: N2 M115

< 20:52:12.036: N3 M220 S100

< 20:52:12.036: N4 M221 S100

< 20:52:12.036: N5 G92 E0

< 20:52:12.036: N6 G90

< 20:52:12.036: N7 M82

< 20:52:12.036: @getip

> 20:52:12.039: ok B:56.5 /60.0 T0:195.2 /215.0

> 20:52:12.039: ok FIRMWARE_VERSION:v0.7.0-386-g9bd3e80-dirty FIRMWARE_NAME:Klipper

> 20:52:12.039: // Heater extruder not heating at expected rate

> 20:52:12.039: // See the 'verify_heater' section in config/example-extras.cfg

> 20:52:12.039: // for the parameters that control this check.

> 20:52:12.039: //

> 20:52:12.039: // Once the underlying issue is corrected, use the

> 20:52:12.040: // "FIRMWARE_RESTART" command to reset the firmware, reload the

> 20:52:12.040: // config, and restart the host software.

> 20:52:12.040: // Printer is shutdown

> 20:52:12.040: Firmware was halted, trying to reconnect. Eventually running print is stopped.

> 20:52:12.050: Response while unconnected:!! Heater extruder not heating at expected rate

> 20:52:12.051: !! Heater extruder not heating at expected rate

> 20:52:12.051: ok 3

> 20:52:12.051: // Heater extruder not heating at expected rate

> 20:52:12.051: // See the 'verify_heater' section in config/example-extras.cfg

> 20:52:12.051: // for the parameters that control this check.

> 20:52:12.052: //

> 20:52:12.052: // Once the underlying issue is corrected, use the

> 20:52:12.052: // "FIRMWARE_RESTART" command to reset the firmware, reload the

> 20:52:12.052: // config, and restart the host software.

> 20:52:12.052: // Printer is shutdown

> 20:52:12.052: Firmware was halted, trying to reconnect. Eventually running print is stopped.

> 20:52:12.063: Response while unconnected:!! Heater extruder not heating at expected rate

> 20:52:12.063: !! Heater extruder not heating at expected rate

> 20:52:12.063: ok 4

> 20:52:12.064: // Heater extruder not heating at expected rate

> 20:52:12.064: // See the 'verify_heater' section in config/example-extras.cfg

> 20:52:12.064: // for the parameters that control this check.

> 20:52:12.064: //

> 20:52:12.064: // Once the underlying issue is corrected, use the

> 20:52:12.064: // "FIRMWARE_RESTART" command to reset the firmware, reload the

> 20:52:12.064: // config, and restart the host software.

> 20:52:12.064: // Printer is shutdown

> 20:52:12.064: Firmware was halted, trying to reconnect. Eventually running print is stopped.

> 20:52:12.075: Response while unconnected:!! Heater extruder not heating at expected rate

> 20:52:12.076: !! Heater extruder not heating at expected rate

> 20:52:12.076: ok 5

> 20:52:12.076: // Heater extruder not heating at expected rate

> 20:52:12.076: // See the 'verify_heater' section in config/example-extras.cfg

> 20:52:12.076: // for the parameters that control this check.

> 20:52:12.076: //

> 20:52:12.076: // Once the underlying issue is corrected, use the

> 20:52:12.076: // "FIRMWARE_RESTART" command to reset the firmware, reload the

> 20:52:12.077: // config, and restart the host software.

> 20:52:12.077: // Printer is shutdown

> 20:52:12.077: Firmware was halted, trying to reconnect. Eventually running print is stopped.

> 20:52:12.087: Response while unconnected:!! Heater extruder not heating at expected rate

> 20:52:12.088: !! Heater extruder not heating at expected rate

> 20:52:12.088: ok 6

> 20:52:12.088: // Heater extruder not heating at expected rate

> 20:52:12.088: // See the 'verify_heater' section in config/example-extras.cfg

> 20:52:12.088: // for the parameters that control this check.

> 20:52:12.089: //

> 20:52:12.089: // Once the underlying issue is corrected, use the

> 20:52:12.089: // "FIRMWARE_RESTART" command to reset the firmware, reload the

> 20:52:12.089: // config, and restart the host software.

> 20:52:12.089: // Printer is shutdown

> 20:52:12.089: Firmware was halted, trying to reconnect. Eventually running print is stopped.

> 20:52:12.101: Response while unconnected:!! Heater extruder not heating at expected rate

> 20:52:12.101: !! Heater extruder not heating at expected rate

> 20:52:12.101: ok 7

< 20:52:12.102: N1 M105

< 20:52:12.102: N2 M115

< 20:52:12.102: N3 M220 S100

< 20:52:12.102: N4 M221 S100

< 20:52:12.102: N5 G92 E0

< 20:52:12.102: N6 G90

< 20:52:12.102: N7 M82

< 20:52:12.102: @getip

> 20:52:12.105: ok B:56.5 /60.0 T0:195.2 /215.0

> 20:52:12.105: ok FIRMWARE_VERSION:v0.7.0-386-g9bd3e80-dirty FIRMWARE_NAME:Klipper

> 20:52:12.105: // Heater extruder not heating at expected rate

> 20:52:12.105: // See the 'verify_heater' section in config/example-extras.cfg

> 20:52:12.105: // for the parameters that control this check.

> 20:52:12.105: //

> 20:52:12.106: // Once the underlying issue is corrected, use the

> 20:52:12.106: // "FIRMWARE_RESTART" command to reset the firmware, reload the

> 20:52:12.106: // config, and restart the host software.

> 20:52:12.106: // Printer is shutdown

> 20:52:12.106: Firmware was halted, trying to reconnect. Eventually running print is stopped.

> 20:52:12.117: Response while unconnected:!! Heater extruder not heating at expected rate

> 20:52:12.117: !! Heater extruder not heating at expected rate

> 20:52:12.117: ok 3

> 20:52:12.117: // Heater extruder not heating at expected rate

> 20:52:12.117: // See the 'verify_heater' section in config/example-extras.cfg

> 20:52:12.118: // for the parameters that control this check.

> 20:52:12.118: //

> 20:52:12.118: // Once the underlying issue is corrected, use the

> 20:52:12.118: // "FIRMWARE_RESTART" command to reset the firmware, reload the

> 20:52:12.118: // config, and restart the host software.

> 20:52:12.118: // Printer is shutdown

> 20:52:12.118: Firmware was halted, trying to reconnect. Eventually running print is stopped.

> 20:52:12.129: Response while unconnected:!! Heater extruder not heating at expected rate

> 20:52:12.129: !! Heater extruder not heating at expected rate

> 20:52:12.130: ok 4

> 20:52:12.130: // Heater extruder not heating at expected rate

> 20:52:12.130: // See the 'verify_heater' section in config/example-extras.cfg

> 20:52:12.130: // for the parameters that control this check.

> 20:52:12.130: //

> 20:52:12.130: // Once the underlying issue is corrected, use the

> 20:52:12.130: // "FIRMWARE_RESTART" command to reset the firmware, reload the

> 20:52:12.130: // config, and restart the host software.

> 20:52:12.130: // Printer is shutdown

> 20:52:12.131: Firmware was halted, trying to reconnect. Eventually running print is stopped.

> 20:52:12.240: Response while unconnected:!! Heater extruder not heating at expected rate

> 20:52:12.241: !! Heater extruder not heating at expected rate

> 20:52:12.241: ok 5

> 20:52:12.241: // Heater extruder not heating at expected rate

> 20:52:12.241: // See the 'verify_heater' section in config/example-extras.cfg

> 20:52:12.241: // for the parameters that control this check.

> 20:52:12.241: //

> 20:52:12.241: // Once the underlying issue is corrected, use the

> 20:52:12.241: // "FIRMWARE_RESTART" command to reset the firmware, reload the

> 20:52:12.242: // config, and restart the host software.

> 20:52:12.242: // Printer is shutdown

> 20:52:12.242: Firmware was halted, trying to reconnect. Eventually running print is stopped.

> 20:52:12.252: Response while unconnected:!! Heater extruder not heating at expected rate

> 20:52:12.253: !! Heater extruder not heating at expected rate

> 20:52:12.253: ok 6

> 20:52:12.253: // Heater extruder not heating at expected rate

> 20:52:12.253: // See the 'verify_heater' section in config/example-extras.cfg

> 20:52:12.253: // for the parameters that control this check.

> 20:52:12.254: //

> 20:52:12.254: // Once the underlying issue is corrected, use the

> 20:52:12.254: // "FIRMWARE_RESTART" command to reset the firmware, reload the

> 20:52:12.254: // config, and restart the host software.

> 20:52:12.254: // Printer is shutdown

> 20:52:12.254: Firmware was halted, trying to reconnect. Eventually running print is stopped.

> 20:52:12.265: Response while unconnected:!! Heater extruder not heating at expected rate

> 20:52:12.265: !! Heater extruder not heating at expected rate

> 20:52:12.265: ok 7

< 20:52:12.266: N1 M105

< 20:52:12.266: N2 M115

< 20:52:12.266: N3 M220 S100

< 20:52:12.266: N4 M221 S100

< 20:52:12.266: N5 G92 E0

< 20:52:12.266: N6 G90

< 20:52:12.266: N7 M82

< 20:52:12.266: @getip

> 20:52:12.268: ok B:56.4 /60.0 T0:195.0 /215.0

> 20:52:12.269: ok FIRMWARE_VERSION:v0.7.0-386-g9bd3e80-dirty FIRMWARE_NAME:Klipper

> 20:52:12.269: // Heater extruder not heating at expected rate

> 20:52:12.270: // See the 'verify_heater' section in config/example-extras.cfg

> 20:52:12.270: // for the parameters that control this check.

> 20:52:12.270: //

> 20:52:12.270: // Once the underlying issue is corrected, use the

> 20:52:12.270: // "FIRMWARE_RESTART" command to reset the firmware, reload the

> 20:52:12.270: // config, and restart the host software.

> 20:52:12.270: // Printer is shutdown

> 20:52:12.270: Firmware was halted, trying to reconnect. Eventually running print is stopped.

> 20:52:12.281: Response while unconnected:!! Heater extruder not heating at expected rate

> 20:52:12.282: !! Heater extruder not heating at expected rate

> 20:52:12.282: ok 3

> 20:52:12.282: // Heater extruder not heating at expected rate

> 20:52:12.283: // See the 'verify_heater' section in config/example-extras.cfg

> 20:52:12.283: // for the parameters that control this check.

> 20:52:12.283: //

> 20:52:12.283: // Once the underlying issue is corrected, use the

> 20:52:12.283: // "FIRMWARE_RESTART" command to reset the firmware, reload the

> 20:52:12.283: // config, and restart the host software.

> 20:52:12.283: // Printer is shutdown

> 20:52:12.283: Firmware was halted, trying to reconnect. Eventually running print is stopped.

> 20:52:12.294: Response while unconnected:!! Heater extruder not heating at expected rate

> 20:52:12.294: !! Heater extruder not heating at expected rate

> 20:52:12.295: ok 4

> 20:52:12.295: // Heater extruder not heating at expected rate

> 20:52:12.295: // See the 'verify_heater' section in config/example-extras.cfg

> 20:52:12.295: // for the parameters that control this check.

> 20:52:12.295: //

> 20:52:12.295: // Once the underlying issue is corrected, use the

> 20:52:12.295: // "FIRMWARE_RESTART" command to reset the firmware, reload the

> 20:52:12.295: // config, and restart the host software.

> 20:52:12.296: // Printer is shutdown

> 20:52:12.296: Firmware was halted, trying to reconnect. Eventually running print is stopped.

> 20:52:12.306: Response while unconnected:!! Heater extruder not heating at expected rate

> 20:52:12.307: !! Heater extruder not heating at expected rate

> 20:52:12.307: ok 5

> 20:52:12.307: // Heater extruder not heating at expected rate

> 20:52:12.307: // See the 'verify_heater' section in config/example-extras.cfg

> 20:52:12.307: // for the parameters that control this check.

> 20:52:12.307: //

> 20:52:12.307: // Once the underlying issue is corrected, use the

> 20:52:12.308: // "FIRMWARE_RESTART" command to reset the firmware, reload the

> 20:52:12.308: // config, and restart the host software.

> 20:52:12.308: // Printer is shutdown

> 20:52:12.308: Firmware was halted, trying to reconnect. Eventually running print is stopped.

> 20:52:12.318: Response while unconnected:!! Heater extruder not heating at expected rate

> 20:52:12.319: !! Heater extruder not heating at expected rate

> 20:52:12.319: ok 6

> 20:52:12.319: // Heater extruder not heating at expected rate

> 20:52:12.319: // See the 'verify_heater' section in config/example-extras.cfg

> 20:52:12.319: // for the parameters that control this check.

> 20:52:12.319: //

> 20:52:12.320: // Once the underlying issue is corrected, use the

> 20:52:12.320: // "FIRMWARE_RESTART" command to reset the firmware, reload the

> 20:52:12.320: // config, and restart the host software.

> 20:52:12.320: // Printer is shutdown

↧

Z-Probing, Correction matrix and Z-Home

April 10, 2019, 10:44 am

≫ Next: Upload to repetier from slic3r prusa edition

≪ Previous: klipper infinite LOOP once getting in halted status

I am facing an issue with 1.04 or so.
"ALWAYS_CHECK_ENDSTOPS" seems to not working anymore for movements.

In fact it is still check at movements.
Just home the Printer and try to go below 0.0mm in Z in the "Move" Panel. Does not work anymore.
With "Slow" you get -0.01mm but thats it.

The effect in Print: If you need to go below 0.0mm (i.e. -0.05mm) because of Leveling/Correction matrix, this move is not executed. No Error, no nothing, Z still at 0.0mm, just not moved. But going up is working. So you constantly going away from bed, going out of sync. In the test I'm printing you end up with arround 0.6mm Z away from bed in the first layer.

You don't even home the printer. Just go away from bed, switch off/on, try to move below 0.0mm. Does not work.
snipped from my configuration.h:

...
#define ENDSTOP_Z_BACK_ON_HOME 0

#define ALWAYS_CHECK_ENDSTOPS 0

#define MOVE_X_WHEN_HOMED 0

...

Oh, I'm using Visual Code to compile firmware. Good move, I really like it.

↧

Upload to repetier from slic3r prusa edition

February 26, 2019, 6:35 am

≫ Next: Show what COM ports are being used during adding a new printer

≪ Previous: Z-Probing, Correction matrix and Z-Home

Hi,

I made a simple script to upload to repetier server waiting for slic3r native implementation as for octoprint or duet.

Script for Windows is the following :

@echo off

c:\Windows\System32\curl.exe -i -X POST -H "Content-Type: multipart/form-data" -H "x-api-key: xxxxxxxxxxxxxxxxxxxx" -F "a=upload" --url "http://192.168.0.xx:3344/printer/model/xxxxxxx" -F "filename=@%1" > curl_log.txt

You need to replace xxx by api key, ip adress and printer name.

in slic3r, in post processing scripts, just call the file you created, file name shall be .bat or .cmd to work.

In my case curl case already installed, you may need to install curl on a fresh windows...

Easy to adapt to mac or linux... just change the path and create a shell script instead.

Regards,
Pierre

↧

Show what COM ports are being used during adding a new printer

April 10, 2019, 4:19 pm

≫ Next: Delta calibration is incorrect

≪ Previous: Upload to repetier from slic3r prusa edition

This is a minor inconvenience when installing a new printer into RS, but could you make it show what ports are being used in it, as in showing what printers are already connected to prevent mixing the ports up and causing issues? Thanks!

↧

Delta calibration is incorrect

January 27, 2019, 6:26 pm

≫ Next: Touch GUI: Is it possible to show both extruder temperatures?

≪ Previous: Show what COM ports are being used during adding a new printer

His guys, I've read multiple posts on this forum and even followed the guide on this page https://www.repetier.com/documentation/repetier-firmware/z-probing/ but still have issues.

Attached are:

Full Firmware files form repetier online configurator
Config.JSON file (currently named config.zip so you must rename to config.json since forum doesn't allow uploading .JSON extension)

Machine details: HE3D K280 with genuine BL-Touch probe

Problem: After running calibration procedures, the nozzle is floating inconsistently above the print bed (as if none of the distortion values are being applied from EEPROM).

Procedure used is from this video: https://youtu.be/L9URtv2LqKc

EEPROM is first reset, then enabled (1)
Heatbed and extruder at working temperature
Calibrating endstop offsets went well.
G32 S2 Bed leveling seems to have gone well (used 7x7 matrix and results are below)

20:31:44.449 : SelectExtruder:0

20:31:44.455 : X:0.00 Y:0.00 Z:548.987 E:0.0000

20:32:07.759 : Z-probe:20.669 X:-90.00 Y:-90.00

20:32:16.198 : Z-probe:19.644 X:-90.00 Y:-60.00

20:32:24.519 : Z-probe:19.087 X:-90.00 Y:-30.00

20:32:32.809 : Z-probe:18.988 X:-90.00 Y:0.00

20:32:41.176 : Z-probe:19.331 X:-90.00 Y:30.00

20:32:49.654 : Z-probe:19.831 X:-90.00 Y:60.00

20:32:58.366 : Z-probe:20.869 X:-90.00 Y:90.00

20:33:08.406 : Z-probe:19.806 X:-60.00 Y:-90.00

20:33:16.652 : Z-probe:18.775 X:-60.00 Y:-60.00

20:33:24.780 : Z-probe:18.219 X:-60.00 Y:-30.00

20:33:32.869 : Z-probe:18.100 X:-60.00 Y:0.00

20:33:41.000 : Z-probe:18.288 X:-60.00 Y:30.00

20:33:49.296 : Z-probe:19.013 X:-60.00 Y:60.00

20:33:57.833 : Z-probe:20.087 X:-60.00 Y:90.00

20:34:07.750 : Z-probe:19.319 X:-30.00 Y:-90.00

20:34:15.890 : Z-probe:18.250 X:-30.00 Y:-60.00

20:34:23.884 : Z-probe:17.587 X:-30.00 Y:-30.00

20:34:31.849 : Z-probe:17.544 X:-30.00 Y:0.00

20:34:39.880 : Z-probe:17.831 X:-30.00 Y:30.00

20:34:48.060 : Z-probe:18.500 X:-30.00 Y:60.00

20:34:56.479 : Z-probe:19.562 X:-30.00 Y:90.00

20:35:06.371 : Z-probe:19.219 X:0.00 Y:-90.00

20:35:14.479 : Z-probe:18.150 X:0.00 Y:-60.00

20:35:22.448 : Z-probe:17.531 X:0.00 Y:-30.00

20:35:30.376 : Z-probe:17.375 X:0.00 Y:0.00

20:35:38.376 : Z-probe:17.700 X:0.00 Y:30.00

20:35:46.505 : Z-probe:18.275 X:0.00 Y:60.00

20:35:54.877 : Z-probe:19.356 X:0.00 Y:90.00

20:36:04.819 : Z-probe:19.450 X:30.00 Y:-90.00

20:36:12.974 : Z-probe:18.375 X:30.00 Y:-60.00

20:36:20.985 : Z-probe:17.712 X:30.00 Y:-30.00

20:36:28.957 : Z-probe:17.544 X:30.00 Y:0.00

20:36:36.992 : Z-probe:17.869 X:30.00 Y:30.00

20:36:45.164 : Z-probe:18.456 X:30.00 Y:60.00

20:36:53.584 : Z-probe:19.556 X:30.00 Y:90.00

20:37:03.615 : Z-probe:19.837 X:60.00 Y:-90.00

20:37:11.872 : Z-probe:18.831 X:60.00 Y:-60.00

20:37:19.986 : Z-probe:18.144 X:60.00 Y:-30.00

20:37:28.074 : Z-probe:18.094 X:60.00 Y:0.00

20:37:36.258 : Z-probe:18.525 X:60.00 Y:30.00

20:37:44.579 : Z-probe:19.125 X:60.00 Y:60.00

20:37:53.129 : Z-probe:20.131 X:60.00 Y:90.00

20:38:03.348 : Z-probe:20.613 X:90.00 Y:-90.00

20:38:11.808 : Z-probe:19.725 X:90.00 Y:-60.00

20:38:20.149 : Z-probe:19.175 X:90.00 Y:-30.00

20:38:28.425 : Z-probe:18.919 X:90.00 Y:0.00

20:38:36.795 : Z-probe:19.350 X:90.00 Y:30.00

20:38:45.332 : Z-probe:20.113 X:90.00 Y:60.00

20:38:54.095 : Z-probe:21.075 X:90.00 Y:90.00

20:38:54.100 : plane: a = 0.0005 b = 0.0017 c = 18.9291

20:38:54.108 : Transformation matrix: 1.000000 0.000000 -0.000479 -0.000001 0.999999 -0.001656 0.000479 0.001656 0.999999

20:38:54.111 : Printer height:552.92

20:38:54.113 : CurrentZ:18.93 atZ:15.00

20:38:54.121 : Info:Autoleveling enabled

20:38:55.142 : X:89.99 Y:89.97 Z:19.117 E:0.0000

20:38:55.142 : Z correction enabled

20:38:55.145 : Info:Autoleveling disabled

20:39:16.947 : SelectExtruder:0

20:39:16.954 : X:0.00 Y:0.00 Z:552.925 E:0.0000

20:39:16.954 : Info:Autoleveling enabled

Next G33 R0 to ensure reset of distortion data from EEPROM
Used Bed map tool to measure initial uncorrected bed map (7x7 matrix Values below and image attached)

X: -90.00 -60.00 -30.00 0.00 30.00 60.00 90.00

y:90.00 6.84 6.01 5.44 5.26 5.44 6.01 6.91

y:60.00 5.85 5.01 4.49 4.23 4.40 5.06 5.93

y:30.00 5.38 4.35 3.86 3.72 3.83 4.41 5.20

y:0.00 5.11 4.20 3.64 3.51 3.64 4.13 4.97

y:-30.00 5.26 4.39 3.73 3.65 3.85 4.29 5.24

y:-60.00 5.91 4.98 4.50 4.34 4.54 4.96 5.86

y:-90.00 6.97 6.07 5.58 5.53 5.68 6.06 6.81

Then G33 to re-measure distortion (Note, it seems like the matrix boundary used by G33 command is a 60x60 mm square instead of 180x180 as set in firmware...all other commands above used 180x180mm bounding area as expected). Results of G33 are below:

21:04:08.681 : N124 G33*30

21:04:08.700 : Z correction disabled

21:04:08.703 : Reference Z for measurement:20.000

21:04:18.747 : Z-probe:18.750 X:-10.00 Y:30.00

21:04:26.889 : Z-probe:18.744 X:10.00 Y:30.00

21:04:35.275 : Z-probe:18.662 X:-30.00 Y:10.00

21:04:43.364 : Z-probe:18.494 X:-10.00 Y:10.00

21:04:51.466 : Z-probe:18.569 X:10.00 Y:10.00

21:04:59.588 : Z-probe:18.650 X:30.00 Y:10.00

21:05:08.156 : Z-probe:18.637 X:-30.00 Y:-10.00

21:05:16.242 : Z-probe:18.494 X:-10.00 Y:-10.00

21:05:24.340 : Z-probe:18.556 X:10.00 Y:-10.00

21:05:32.462 : Z-probe:18.644 X:30.00 Y:-10.00

21:05:40.833 : Z-probe:18.625 X:-10.00 Y:-30.00

21:05:48.974 : Z-probe:18.731 X:10.00 Y:-30.00

21:05:50.064 : Info:Distortion correction matrix:
////SOMETHING IS WRONG HERE//// Values seem too high

21:05:50.064 : 102, 100, 101, 104

21:05:50.067 : 107, 121, 115, 108

21:05:50.067 : 109, 121, 116, 109

21:05:50.070 : 114, 110, 102, 102

21:05:50.072 : G33 X-30.00 Y-30.00 Z1.425

21:05:50.075 : G33 X-30.00 Y-10.00 Z1.363

21:05:50.078 : G33 X-30.00 Y10.00 Z1.337

21:05:50.081 : G33 X-30.00 Y30.00 Z1.275

21:05:50.081 : G33 X-10.00 Y-30.00 Z1.375

21:05:50.084 : G33 X-10.00 Y-10.00 Z1.513

21:05:50.086 : G33 X-10.00 Y10.00 Z1.513

21:05:50.089 : G33 X-10.00 Y30.00 Z1.250

21:05:50.092 : G33 X10.00 Y-30.00 Z1.275

21:05:50.094 : G33 X10.00 Y-10.00 Z1.450

21:05:50.094 : G33 X10.00 Y10.00 Z1.437

21:05:50.097 : G33 X10.00 Y30.00 Z1.263

21:05:50.100 : G33 X30.00 Y-30.00 Z1.275

21:05:50.103 : G33 X30.00 Y-10.00 Z1.363

21:05:50.105 : G33 X30.00 Y10.00 Z1.350

21:05:50.108 : G33 X30.00 Y30.00 Z1.300

21:05:50.108 : Z correction enabled

Using Bed height map tool again yields the following results:

X: -90.00 -60.00 -30.00 0.00 30.00 60.00 90.00

y:90.00 8.16 7.31 6.81 6.55 6.86 7.36 8.22

y:60.00 7.13 6.29 5.78 5.50 5.72 6.38 7.31

y:30.00 6.64 5.60 5.16 4.98 5.18 5.71 6.48

y:0.00 6.46 5.52 4.97 4.93 4.99 5.46 6.33

y:-30.00 6.69 5.83 5.21 4.99 5.16 5.58 6.53

y:-60.00 7.33 6.40 5.88 5.67 5.81 6.23 7.11

y:-90.00 8.34 7.54 6.99 6.85 6.94 7.32 8.06

Now during, 2 things happen:
A) The nozzle is not close enough to the bed (I can fix this using nozzle offset)

The distance from nozzle to bed varies inconsistently especially towards the outside of the circular print area (This is my only roadblock to get this machine finally printing using repetier firmware.

i've tripple checked all dimensions and re-measured all rods and verified BL touch repeatability and machine structural alignment as best as I could. I'm ready to trash this delta and go back to Cartesian machine...any help is appreciated...please help save a 3D Printer and my sanity :'(

UPDATE: I realised my distortion radius was set to 30 but even after increasing this value the issue persists

↧

Touch GUI: Is it possible to show both extruder temperatures?

April 11, 2019, 2:48 am

≫ Next: Z Probe with Piezo element errors

≪ Previous: Delta calibration is incorrect

Hi, using V14 0.91.2 on Pi3 with Touchscreen.

The GUI shows the extruder temp and bed temp in the head line and in status lines during printing.

Since I have a dual extruder setup and heat always both extruders for wiping prior to printing, it would be hepful if both extruder temperatures could be shown parallel.

In case this is just an easy step I would appreciate some hints.

Thanks in advance!

↧

Z Probe with Piezo element errors

April 11, 2019, 1:27 pm

≫ Next: Custom Z-probe question

≪ Previous: Touch GUI: Is it possible to show both extruder temperatures?

Hi there. I have been having trouble getting Repetier FW to play nicely with my precisionpiezo board, but I can't get it to trigger/untrigger properly. The board is tuned in that it detects taps but not so much as to induce false positives. I have made posts on the RepRap Forum piezo thread to no avail, which I render below. https://reprap.org/forum/read.php?1,767998,850895#msg-850895

I have a 27mm piezo sensor on a Rostock Max, but I can't seem to get it interfaced with my RAMBo and Repetier Firmware properly.
I've reflashed the firmware many times, each time changing a setting. I have tested an entire matrix of probe/endstop settings.

I'm certain it is wired correctly from Piezo20 to RAMBo, as I color coded the connectors, and I verified the piezo is in the proper polarity (no trigger on pressure release)

In Repetier Firmware I've tested all combinations of true/false for Z_PROBE_ON_HIGH, ENDSTOP_PULLUP_Z_MIN, and inverted Z Min logic. No matter what it either gives me Z probe triggered before probing, or the Z probe didn't untrigger on repetitive probe; only in two instances of the second situation did the carriage actually do a probe plunge and not raise instantly.
The only thing I kept constant was that Z probe pin is the Z Min pin, and ENDSTOP_Z_MIN = true. I realize that the Piezo20 works by pulling SIG low, thus requiring pullup, but I wanted to test it anyways.
Result denotes a scenario: 1 is triggered before probe starts error. 2 is probe didn't untrigger on probe. The letter in that column denotes the physical movement made after G30 P0 was sent. P is where the effector actually descended and touched an object, whereas i occurs in a configuration that caused instant raising of the probe.

ENDSTOP_Z_MIN_INVERTING	Z_PROBE_ON_HIGH	ENDSTOP_Z_MIN_PULLUP	M119 TRIGGERED (BLUE) ZMIN/PROBE	RESULT	M119 UNTRIGGERED RED ZMIN/PROBE
X	X	Y	L/L	1i	L/H
Y	Y	Y	L/H	2i	L/L
Y	X	Y	L/H	2p	L/L
X	Y	Y	L/L	1i	L/H
X	X	X	L/L	1i	L/H
Y	X	X	L/H	2i	L/L
X	Y	X	L/L	1i	L/H
Y	Y	X	L/H	2p	L/L

↧

Custom Z-probe question

April 11, 2019, 8:13 pm

≫ Next: Get version repieter-firmware

≪ Previous: Z Probe with Piezo element errors

Hi,
This is my 1st post here and I'd like to say BIG THANKS to the developers of Repetier-Firmware. I switched to Repetier 0.92 about 5 weeks ago after using different versions of Marlin and then Klipper and so far am extremely happy with Repetier's stability, reliability and performance.

I am in the process of designing my own 3d printed touch-based z-probe and have a question about the output signals it should generate.
During normal operation/printing, my z-probe's sensor-pin will be lifted and the output of z-probe will be HIGH. During bed leveling, when the pin is lowered, output will be LOW and will switch to HIGH when pin touches the bed. Could you please advice if such output from z-probe is supported and whether Z_PROBE_ON_HIGH should be set to 1 or 0. I have Z_max_endstop and will not be using z-probe as Z_min_endstop.
Another related question - does it matter whether z-probe's output is HIGH or LOW during the time when we are not running bed leveling?

Thanks

↧

Get version repieter-firmware

April 12, 2019, 1:34 am

≫ Next: New printer (Ender-3) won't connect through USB

≪ Previous: Custom Z-probe question

Hi! How i can get version installed repieter-firmware?

↧

New printer (Ender-3) won't connect through USB

April 12, 2019, 9:10 am

≫ Next: Communication timeout - Command waiting

≪ Previous: Get version repieter-firmware

I have used the Repetier server with my previous printer (Anet A8), but now traded it out for a Creality Ender 3 printer. While I could easily connect the Repetier Server to the A8 over the USB cable, the Ender-3 will not. With the A8 it showed it was connecting through COM3. I now only see COM4, and no COM3 showing (Windows 10). COM4 is showing as RAMPS. I can change it to COM3, but it still doesn't connect. I have also tried the "Add New Printer" wizard, but it just sits at the "Waiting for connection" stage.

I would really like to be able to connect via the USB / serial so that I can send gcodes for fine tuning. Any assistance would be appreciated.

↧

Communication timeout - Command waiting

April 13, 2019, 12:09 am

≫ Next: Dual extruder X Y offset

≪ Previous: New printer (Ender-3) won't connect through USB

Hello.
I tried all recommendations in this forum and none of tghem worked for me.
The problem is that Repetier "connects" to my 3d printer. I know that because it detects the temperature of hotend and hotbed. But I can not send any command to my printer or print anything.

The printer is a DIY Prusa I3. Using Marlin 1.0
All drivers are set. The port is COM3 and baudrate 115200.
What else can I do?

This is the log

04:06:32.354 : OpenGL version:4.6.0 NVIDIA 425.31
04:06:32.354 : OpenGL extensions:GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_polygon_offset_clamp GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_spirv_extensions GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_filter_anisotropic GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_R8 GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_window_rectangles GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_EXT_memory_object GL_EXT_memory_object_win32 GL_EXT_win32_keyed_mutex GL_KHR_parallel_shader_compile GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_EXT_semaphore GL_EXT_semaphore_win32 GL_KTX_buffer_region GL_NV_alpha_to_coverage_dither_control GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_square GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_draw_vulkan_image GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_feature_query GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_query_resource GL_NV_query_resource_tag GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_rectangle_compressed GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NVX_multigpu_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle GL_KHR_blend_equation_advanced GL_OVR_multiview GL_OVR_multiview2 GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control
04:06:32.354 : OpenGL renderer:GeForce GTX 650/PCIe/SSE2
04:06:32.354 : Using fast VBOs for rendering is possible
04:07:00.276 : Error puerto serie:System.IO.Ports.SerialErrorReceivedEventArgs
04:07:00.338 : Printer reset detected - initalizing
04:07:00.354 : start
04:07:00.354 : echo: External Reset
04:07:00.370 : Marlin 1.0.1 RRP
04:07:00.370 : echo: Last Updated: 2014-07-05-Lankeda-i3 | Author: Sim Wang
04:07:00.370 : echo: Free Memory: 11513 PlannerBufferBytes: 1232
04:07:00.370 : echo:Using Default settings:
04:07:00.370 : echo:Steps per unit:
04:07:00.370 : echo: M92 X100.000 Y100.000 Z2560.000 E105.000
04:07:00.370 : echo:Maximum feedrates (mm/s):
04:07:00.479 : echo: M203 X300.000 Y300.0?start
04:07:00.479 : echo: External Reset
04:07:00.479 : Marlin 1.0.1 RRP
04:07:00.479 : echo: Last Updated: 2014-07-05-Lankeda-i3 | Author: Sim Wang
04:07:00.479 : echo: Free Memory: 11513 PlannerBufferBytes: 1232
04:07:00.479 : echo:Using Default settings:
04:07:00.479 : echo:Steps per unit:
04:07:00.479 : echo: M92 X100.000 Y100.000 Z2560.000 E105.000
04:07:00.479 : echo:Maximum feedrates (mm/s):
04:07:00.479 : echo: M203 X300.000 Y300.000 Z3.000 E45.000
04:07:00.479 : echo:Maximum Acceleration (mm/s2):
04:07:00.479 : echo: M201 X800 Y800 Z30 E250
04:07:00.479 : echo:Acceleration: S=acceleration, T=retract acceleration
04:07:00.495 : echo: M204 S1000.000 T1000.000
04:07:00.495 : echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum xY jerk (mm/s), Z=maximum Z jerk (mm/s), K=advance_k
04:07:00.495 : echo: M205 S0.000 T0.000 B20000 X15.000 Z0.400 E15.000
04:07:00.495 : echo: M206 X0.000 Y0.000 Z0.000
04:07:00.495 : echo: M208 X210.000 Y210.000 Z160.000
04:07:00.495 : echo:PID settings:
04:07:00.495 : echo: M301 P12.000 I2.200 D80.000 W125
04:07:00.495 : echo:Thermistor settings: M304 Hh Bb Rr Tt, H0=Bed, H1..n=nozzle, b=thermistor beta value, r=series resistor, t=thermistor resistance as 25C
04:07:00.495 : echo: M304 H0
04:07:00.495 : B3960 R10000 T100000 M304 H1
04:07:00.495 : B3960 R10000 T100000
04:07:00.495 : FPU Enabled no
04:07:02.776 : transform correction not enabledecho:SD init fail
04:07:02.791 : FIRMWARE_NAME:Marlin V1; Sprinter/grbl mashup for gen6 FIRMWARE_URL:http://www.mendel-parts.com PROTOCOL_VERSION:1.0 MACHINE_TYPE:Mendel EXTRUDER_COUNT:1
04:07:02.823 : X:0.000Y:0.000Z:0.000E:0.000 Count X:0.000Y:0.000Z:0.000
04:07:02.823 : echo:Active Extruder: 0
04:07:42.833 : Communication timeout - reset send buffer block
04:08:23.587 : Communication timeout - reset send buffer block

↧

Dual extruder X Y offset

April 13, 2019, 2:32 am

≫ Next: Case light over I2c PCA9685

≪ Previous: Communication timeout - Command waiting

hallo liebe leute

ich habe ein problem und zwar habe ich ein drucker selber gebaut und eigentlich funktioniert alles ganz gut, doch bei einer sache komme ich nicht weiter!

Es geht darum das ich mit 2 extrudern zb mehrfarbige objekte drucken will oder auch mit extruder 2 stützstrukuren machen will.

beide estruder funktionieren und drucken auch aber nicht an der richtigen position kann mir jemand helfen? Wie kann ich das extruder offset in X Und Y enstellen.?

freundliche grüsse

klaus

↧

Case light over I2c PCA9685

April 13, 2019, 9:55 am

≫ Next: 4 Printers, one of them doesnt save config

≪ Previous: Dual extruder X Y offset

Hello,
I have an PCA9685 PWM Board connected over I2c on my Marlin Board. I use it to control a laser via PWM.
Now I would like to use it also for the case light but I don't know how I can do this. In the configuration I can't set the case light to an I2c Pin I think. Any ideas??

Best regards

Iksi

↧