Jaki obecnie Firmware wybrać dla Ramps i PI?
- dragonn
- Zasłużony
- Postów w temacie: 16
- Posty: 6384
- Rejestracja: 12 gru 2016, 21:50
- Lokalizacja: Opole
- Drukarka: LUME
- x 1455
Re: Jaki obecnie Firmware wybrać dla Ramps i PI?
https://github.com/KevinOConnor/klipper ... cramps.cfg zobacz tutaj na samym końcu output_pin machine_enable, ostatnio zmienili nazewnictwo tego.
Marcin.KnD
- Marcin.KnD
- Konto z ograniczeniami
- Postów w temacie: 35
- Posty: 648
- Rejestracja: 03 maja 2017, 03:16
- Drukarka: CoreXY 300x300x300
- x 51
Re: Jaki obecnie Firmware wybrać dla Ramps i PI?
Recv: // Unable to translate pin name: config_digital_out oid=7 pin=P9_23 value=1 default_value=0 max_duration=0
Recv: // Once the underlying issue is corrected, use the "RESTART"
Recv: // command to reload the config and restart the host software.
Recv: // Printer is halted
Recv: !! Unable to translate pin name: config_digital_out oid=7 pin=P9_23 value=1 default_value=0 max_duration=0
pin się nie zgadza
Recv: // Once the underlying issue is corrected, use the "RESTART"
Recv: // command to reload the config and restart the host software.
Recv: // Printer is halted
Recv: !! Unable to translate pin name: config_digital_out oid=7 pin=P9_23 value=1 default_value=0 max_duration=0
pin się nie zgadza
- dragonn
- Zasłużony
- Postów w temacie: 16
- Posty: 6384
- Rejestracja: 12 gru 2016, 21:50
- Lokalizacja: Opole
- Drukarka: LUME
- x 1455
Re: Jaki obecnie Firmware wybrać dla Ramps i PI?
To przykład, wpisz tam swój pin po prostu. Zauważasz że to jest plik do CRAMPS (cokolwiek to jest).
Marcin.KnD
- Marcin.KnD
- Konto z ograniczeniami
- Postów w temacie: 35
- Posty: 648
- Rejestracja: 03 maja 2017, 03:16
- Drukarka: CoreXY 300x300x300
- x 51
Re: Jaki obecnie Firmware wybrać dla Ramps i PI?
OK
dodałem na końcu ;
teraz po wpisaniu do terminala
SET_PIN PIN=machine_enable VALUE=1
lub
SET_PIN PIN=machine_enable VALUE=0
właczam i wyłaczam lae jak to teraz połączyć z PSU control lub jak to zrobic żeby nie trzeba było klepać komend do terminala
dodałem na końcu ;
Kod: Zaznacz cały
[output_pin machine_enable]
pin: ar12
value: 0
shutdown_value: 0
SET_PIN PIN=machine_enable VALUE=1
lub
SET_PIN PIN=machine_enable VALUE=0
właczam i wyłaczam lae jak to teraz połączyć z PSU control lub jak to zrobic żeby nie trzeba było klepać komend do terminala
- Marcin.KnD
- Konto z ograniczeniami
- Postów w temacie: 35
- Posty: 648
- Rejestracja: 03 maja 2017, 03:16
- Drukarka: CoreXY 300x300x300
- x 51
Re: Jaki obecnie Firmware wybrać dla Ramps i PI?
Idzie kostka w między czasie
Tak wygląda wyswietlacz
Tak wygląda wyswietlacz
- Marcin.KnD
- Konto z ograniczeniami
- Postów w temacie: 35
- Posty: 648
- Rejestracja: 03 maja 2017, 03:16
- Drukarka: CoreXY 300x300x300
- x 51
Re: Jaki obecnie Firmware wybrać dla Ramps i PI?
Już mam, wystarczy jako G code wpisać w PSU Control
Masz jakiś pomysł na kalibrację Z??
Mi do głowy tylko zmiana position_max przychodzi do głowy ale to mało wygodne, a nie mam teraz sondy Z min, w repetier jest to fajne Z calibration
Masz jakiś pomysł na kalibrację Z??
Mi do głowy tylko zmiana position_max przychodzi do głowy ale to mało wygodne, a nie mam teraz sondy Z min, w repetier jest to fajne Z calibration
- Marcin.KnD
- Konto z ograniczeniami
- Postów w temacie: 35
- Posty: 648
- Rejestracja: 03 maja 2017, 03:16
- Drukarka: CoreXY 300x300x300
- x 51
Re: Jaki obecnie Firmware wybrać dla Ramps i PI?
Zakończyłem ustawiania Kliper'a.
Kostka drukowana 100mm/s
Teraz idzie 3dbenchy z tą samą prędkością.
Jak dla mnie soft na plus tylko brakuje kilku rzeczy, jak odsunięcie po homingu i obsługa filament run out sensor
mój config;
Kostka drukowana 100mm/s
Teraz idzie 3dbenchy z tą samą prędkością.
Jak dla mnie soft na plus tylko brakuje kilku rzeczy, jak odsunięcie po homingu i obsługa filament run out sensor
mój config;
Kod: Zaznacz cały
# This file contains common pin mappings for RAMPS (v1.3 and later)
# boards. RAMPS boards typically use a firmware compiled for the AVR
# atmega2560 (though other AVR chips are also possible).
# See the example.cfg file for a description of available parameters.
# The stepper_x section is used to describe the X axis as well as the
# stepper controlling the X+Y movement.
[stepper_x]
step_pin: ar54
dir_pin: ar55
enable_pin: !ar38
step_distance: .0125
endstop_pin: ^!ar3
position_endstop: 0
position_max: 295
homing_speed: 20
homing_retract_dist: 5.0
# The stepper_y section is used to describe the Y axis as well as the
# stepper controlling the X-Y movement.
[stepper_y]
step_pin: ar60
dir_pin: ar61
enable_pin: !ar56
step_distance: .0125
endstop_pin: ^!ar14
position_endstop: 0
position_max: 295
homing_speed: 20
homing_retract_dist: 5.0
[stepper_z]
step_pin: ar46
dir_pin: !ar48
enable_pin: !ar62
step_distance: .0025
#endstop_pin: ^!ar18
endstop_pin: ^!ar19
position_endstop: 296.4
position_max: 296.4
homing_retract_dist: 5.0
homing_speed: 20
[extruder]
step_pin: ar26
dir_pin: ar28
enable_pin: !ar24
step_distance: .0022779043280182
nozzle_diameter: 0.400
filament_diameter: 1.750
heater_pin: ar10
sensor_type: NTC 100K beta 3950
sensor_pin: analog13
control: pid
pid_Kp: 17.818
pid_Ki: 0.742
pid_Kd: 106.907
min_temp: 10
max_temp: 275
# Heater and temperature sensor verification. Heater verification is
# automatically enabled for each heater that is configured on the
# printer. Use verify_heater sections to change the default settings.
[verify_heater extruder]
heating_gain: 2
# The minimum temperature (in Celsius) that the heater must increase
# by when approaching a new target temperature. The default is 2.
check_gain_time: 20
# The amount of time (in seconds) that the heating_gain must be met
# in before an error is raised. The default is 20 seconds for
# extruders and 60 seconds for heater_bed.
hysteresis: 2
# The difference between the target temperature and the current
# temperature for the heater to be considered within range of the
# target temperature. The default is 5.
max_error: 120
# The maximum temperature difference a heater that falls outside the
# target temperature range may accumulate before an error is
# raised. For example, if the target temperature is 200, the
# hysteresis is 5, the max_error is 120, and the temperature is
# reported at 185 degrees for 12 seconds then an error would be
# raised (or 24 seconds at 190, or 120 seconds at 194, etc.). The
# default is 120.
[heater_bed]
heater_pin: ar8
sensor_type: NTC 100K beta 3950
sensor_pin: analog14
#control: watermark
#max_delta: 2.0
control: pid
pid_Kp: 39.491
pid_Ki: 1.522
pid_Kd: 256.195
min_temp: 10
max_temp: 150
[fan]
pin: ar9
max_power: 1.0
kick_start_time: 0.100
cycle_time: 0.010
hardware_pwm: False
[heater_fan my_nozzle_fan]
# See the "fan" section for fan configuration parameters.
pin: ar4
# The remaining variables are specific to heater_fan.
heater: extruder
# Name of the config section defining the heater that this fan is
# associated with. The default is "extruder".
heater_temp: 50.0
# A temperature (in Celsius) that the heater must drop below before
# the fan is disabled. The default is 50 Celsius.
#fan_speed:
# The fan speed (expressed as a value from 0.0 to 1.0) that the fan
# will be set to when its associated heater is enabled. The default
# is max_power.
[mcu]
serial: /dev/ttyUSB0
baud: 250000
pin_map: arduino
restart_method: arduino
[printer]
kinematics: corexy
# This option must be "corexy" for corexy printers.
max_velocity: 300
max_accel: 4000
max_z_velocity: 25
max_z_accel: 30
motor_off_time: 600
junction_deviation: 0.02
# "RepRapDiscount 128x64 Full Graphic Smart Controller" type displays
[display]
lcd_type: st7920
cs_pin: ar16
sclk_pin: ar23
sid_pin: ar17
#[servo bltouch]
#pin: ar11
#maximum_servo_angle: 180
#minimum_pulse_width: 0.0006
#maximum_pulse_width: 0.0024
# Define a probe using the BLTouch
#[probe]
#pin: ar30
#activate_gcode:
# SET_SERVO SERVO=bltouch ANGLE=10
# SET_SERVO SERVO=bltouch ANGLE=60
# G4 P200
#deactivate_gcode:
# SET_SERVO SERVO=bltouch ANGLE=90
# Example bed_tilt config section
#[bed_tilt]
#x_adjust:
#y_adjust:
#points:
# 100,100
# 10,10
# 10,100
# 10,190
# 100,10
# 100,190
# 190,10
# 190,100
# 190,190
#probe_z_offset: 0,8
# If the BLTouch is used to home the Z axis, then define a
# homing_override section, use probe:z_virtual_endstop as the
# endstop_pin in the stepper_z section, and set the endstop_position
# in the stepper_z section to match the probe's probe_z_offset.
#[homing_override]
#set_position_z: 5
#gcode:
# ; G90 ; Uncomment these 2 lines to blindly lift the Z 2mm at start
# ; G1 Z7 F600
# G28 X0 Y0
# G1 X100 Y100 F3600
# G28 Z0
[output_pin machine_enable]
pin: ar12
value: 0
shutdown_value: 0
[output_pin light]
pin: ar5
value: 0
shutdown_value: 0
- Marcin.KnD
- Konto z ograniczeniami
- Postów w temacie: 35
- Posty: 648
- Rejestracja: 03 maja 2017, 03:16
- Drukarka: CoreXY 300x300x300
- x 51
- Marcin.KnD
- Konto z ograniczeniami
- Postów w temacie: 35
- Posty: 648
- Rejestracja: 03 maja 2017, 03:16
- Drukarka: CoreXY 300x300x300
- x 51
Re: Jaki obecnie Firmware wybrać dla Ramps i PI?
Dragon mam pomysł jak zaimplementować Filament Run Out sensor ale potrzebuje czytać z wybranego Pinu Ramps.
coś na zasadzie Z-probe, ale jako druga funkcja --> stan wysoki OK drukuj dalej, stan niski - PASUE czyli M0:
{code]# Z height probe. One may define this section to enable Z height
# probing hardware. When this section is enabled, PROBE and
# QUERY_PROBE extended g-code commands become available. The probe
# section also creates a virtual probe:z_virtual_endstop pin. One may
# set the stepper_z endstop_pin to this virtual pin on cartesian style
# printers that use the probe in place of a z endstop.
#[probe]
#pin: ar15
# Probe detection pin. This parameter must be provided.
#z_offset:
# The distance (in mm) between the bed and the nozzle when the probe
# triggers. This parameter must be provided.
#speed: 5.0
# Speed (in mm/s) of the Z axis when probing. The default is 5mm/s.
#activate_gcode:
# A list of G-Code commands (one per line) to execute prior to each
# probe attempt. This may be useful if the probe needs to be
# activated in some way. The default is to not run any special
# G-Code commands on activation.
#deactivate_gcode:
# A list of G-Code commands (one per line) to execute after each
# probe attempt completes. The default is to not run any special
# G-Code commands on deactivation.{/code]
coś na zasadzie Z-probe, ale jako druga funkcja --> stan wysoki OK drukuj dalej, stan niski - PASUE czyli M0:
{code]# Z height probe. One may define this section to enable Z height
# probing hardware. When this section is enabled, PROBE and
# QUERY_PROBE extended g-code commands become available. The probe
# section also creates a virtual probe:z_virtual_endstop pin. One may
# set the stepper_z endstop_pin to this virtual pin on cartesian style
# printers that use the probe in place of a z endstop.
#[probe]
#pin: ar15
# Probe detection pin. This parameter must be provided.
#z_offset:
# The distance (in mm) between the bed and the nozzle when the probe
# triggers. This parameter must be provided.
#speed: 5.0
# Speed (in mm/s) of the Z axis when probing. The default is 5mm/s.
#activate_gcode:
# A list of G-Code commands (one per line) to execute prior to each
# probe attempt. This may be useful if the probe needs to be
# activated in some way. The default is to not run any special
# G-Code commands on activation.
#deactivate_gcode:
# A list of G-Code commands (one per line) to execute after each
# probe attempt completes. The default is to not run any special
# G-Code commands on deactivation.{/code]