Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. Bobbyofna
    • Profile
    • Following 0
    • Followers 0
    • Topics 7
    • Posts 11
    • Best 1
    • Controversial 0
    • Groups 0

    Bobbyofna

    @Bobbyofna

    1
    Reputation
    1
    Profile views
    11
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    Bobbyofna Unfollow Follow

    Best posts made by Bobbyofna

    • ReprapFirmware Build Instructions for Linux (Arch)

      Hello, despite attending one of the top computer science schools in the country, my entire schools ethernet has been down all day so I only had access to wifi on my laptop running arch linux. I had to make a few minor changes to the firmware for my printer so i decided to try and build reprapfirmware on linux. After a few hours of messing around I finally got it to compile. Here is what I did, but please keep in mind that I did this for RADDS on 1.19, and that I did this on Arch Linux which is a little bit different than most distros…

      Install Eclipse through pacman

      [[language]]
      sudo pacman -S eclipse-cpp
      
      

      As described in BuildInstructions.md, download CoreNG and RRF, create a workspace (doesn't matter where), in my case i created one in /home/Documents/Firmware, and move folders there with proper names as described. Some of these packages are probably unnecessary but it doesn't hurt to install them all

      [[language]]
      sudo pacman -S arduino arduino-avr-core arduino-builder  arduino-ctags arduino-docs arm-none-eabi-gdb
      
      

      You would think that the pacman arm-none-eabi-gcc and arm-none-eabi-newlib packages would work for this but they don't. You need to use a community made package in order for RRF to compile. Doesn't matter what folder you install it into.

      [[language]]
      cd /home/Applications
      git clone https://aur.archlinux.org/gcc-arm-none-eabi-bin.git
      cd gcc-arm-none-eabi-bin
      make -sri
      
      

      Then open eclipse, import both projects as described, and open the project properties for CoreNG. Under 'Settings', change 'Cross Settings' path to '/usr/bin/arm-none-eabi-gcc'. Then go to 'Tool Chain Editor' and change the 'Current Builder' to 'CDT Internal Builder'. Repeat for RRF. All thats left is to build CoreNG followed by RRF, and then that's it! Hope this helps others!

      posted in Firmware installation
      Bobbyofnaundefined
      Bobbyofna

    Latest posts made by Bobbyofna

    • ReprapFirmware Build Instructions for Linux (Arch)

      Hello, despite attending one of the top computer science schools in the country, my entire schools ethernet has been down all day so I only had access to wifi on my laptop running arch linux. I had to make a few minor changes to the firmware for my printer so i decided to try and build reprapfirmware on linux. After a few hours of messing around I finally got it to compile. Here is what I did, but please keep in mind that I did this for RADDS on 1.19, and that I did this on Arch Linux which is a little bit different than most distros…

      Install Eclipse through pacman

      [[language]]
      sudo pacman -S eclipse-cpp
      
      

      As described in BuildInstructions.md, download CoreNG and RRF, create a workspace (doesn't matter where), in my case i created one in /home/Documents/Firmware, and move folders there with proper names as described. Some of these packages are probably unnecessary but it doesn't hurt to install them all

      [[language]]
      sudo pacman -S arduino arduino-avr-core arduino-builder  arduino-ctags arduino-docs arm-none-eabi-gdb
      
      

      You would think that the pacman arm-none-eabi-gcc and arm-none-eabi-newlib packages would work for this but they don't. You need to use a community made package in order for RRF to compile. Doesn't matter what folder you install it into.

      [[language]]
      cd /home/Applications
      git clone https://aur.archlinux.org/gcc-arm-none-eabi-bin.git
      cd gcc-arm-none-eabi-bin
      make -sri
      
      

      Then open eclipse, import both projects as described, and open the project properties for CoreNG. Under 'Settings', change 'Cross Settings' path to '/usr/bin/arm-none-eabi-gcc'. Then go to 'Tool Chain Editor' and change the 'Current Builder' to 'CDT Internal Builder'. Repeat for RRF. All thats left is to build CoreNG followed by RRF, and then that's it! Hope this helps others!

      posted in Firmware installation
      Bobbyofnaundefined
      Bobbyofna
    • Heated Bed Power Blinking (RADDS)

      Hello so I am having an issue where when I set the heated bed to say 60C, the heated bed is getting power in very short blips. Both the led next to the mosfet on radds, and the led on the heated bed, blink at a consistent rate when I turn it on. It looks like it is only on for a very short blip, every half of a second or so. In my room the bed lies around 22-23C, but after having the bed blinking for 30 minutes it reaches 26C, so it is working. I believe the issue is the PID parameters. This is my config file, if someone could tell me what I am doing wrong that'd be great. The bed I am using is a standard pcb heater from an old anet a8. Here part of my config.g…

      [[language]]
      ; Heater and thermistor section
      M305 P0 T100000 R4700 H0 L0				; Put your own H and/or L values here to set the bed thermistor ADC correction
      M305 P1 T100000 R4700 H0 L0				; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
      M305 P2 T100000 R4700 H0 L0				; Put your own H and/or L values here to set the second nozzle thermistor ADC correction
      M301 H0 P85 I5 D500 T2.7 W200 B5		        ; PID settings for heated bed
      M301 H1 P10 I0.10 D100 T0.50 S1.0		        ; PID settings for extruder 0
      M301 H2 P10 I0.10 D100 T0.50 S1.0		        ; PID settings for extruder 1
      M570 S120								; Increase to allow extra heating time if needed
      
      
      posted in Tuning and tweaking
      Bobbyofnaundefined
      Bobbyofna
    • RE: '/RepRapFirmware-RADDS.elf': No such file

      Also, even tho it seems to compile, I get these errors…

      [[language]]
      Description	Resource	Path	Location	Type
      Function 'ARRAY_SIZE' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 158	Semantic Error
      Symbol 'NoPin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 70	Semantic Error
      Symbol 'NoPin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 70	Semantic Error
      Symbol 'NoPin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 70	Semantic Error
      Symbol 'NoPin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 70	Semantic Error
      Symbol 'NoPin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 129	Semantic Error
      Symbol 'NoPin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 129	Semantic Error
      Type 'Pin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 52	Semantic Error
      Type 'Pin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 54	Semantic Error
      Type 'Pin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 55	Semantic Error
      Type 'Pin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 70	Semantic Error
      Type 'Pin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 79	Semantic Error
      Type 'Pin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 86	Semantic Error
      Type 'Pin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 102	Semantic Error
      Type 'Pin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 105	Semantic Error
      Type 'Pin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 110	Semantic Error
      Type 'Pin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 114	Semantic Error
      Type 'Pin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 118	Semantic Error
      Type 'Pin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 124	Semantic Error
      Type 'Pin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 128	Semantic Error
      Type 'Pin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 129	Semantic Error
      Type 'Pin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 130	Semantic Error
      Type 'Pin' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 151	Semantic Error
      Type 'size_t' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 6	Semantic Error
      Type 'size_t' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 21	Semantic Error
      Type 'size_t' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 29	Semantic Error
      Type 'size_t' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 35	Semantic Error
      Type 'size_t' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 36	Semantic Error
      Type 'size_t' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 40	Semantic Error
      Type 'size_t' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 41	Semantic Error
      Type 'size_t' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 42	Semantic Error
      Type 'size_t' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 44	Semantic Error
      Type 'size_t' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 99	Semantic Error
      Type 'size_t' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 117	Semantic Error
      Type 'size_t' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 127	Semantic Error
      Type 'uint32_t' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 161	Semantic Error
      Type 'uint32_t' could not be resolved	Pins_RADDS.h	/RepRapFirmware/src/RADDS	line 162	Semantic Error
      
      
      posted in Firmware installation
      Bobbyofnaundefined
      Bobbyofna
    • '/RepRapFirmware-RADDS.elf': No such file

      Hello I am trying to compile RRF because I need to swap the 3rd heater pin and the heated bed pin as my heated bed mosfet on radds died. I made the change in the pins.h file but I am having trouble getting the final firmware file. Everything compiles but the last command is…

      [[language]]
      arm-none-eabi-gcc "-LC:\\Eclipse\\Firmware\\CoreNG\\RADDS" -Os -Wl,--gc-sections -Wl,--fatal-warnings -mcpu=cortex-m3 "-TC:\\Eclipse\\Firmware\\CoreNG\\variants\\RADDS\\linker_scripts\\gcc\\flash.ld" -Wl,-Map,/RepRapFirmware-RADDS.map -o RepRapFirmware-RADDS.elf -mthumb -Wl,--cref -Wl,--check-sections -Wl,--gc-sections -Wl,--entry=Reset_Handler -Wl,--unresolved-symbols=report-all -Wl,--warn-common -Wl,--warn-section-align -Wl,--warn-unresolved-symbols -Wl,--start-group "C:\\Eclipse\\Firmware\\CoreNG\\RADDS\\cores\\arduino\\syscalls.o" "src\\Fan.o" "src\\FilamentSensors\\Duet3DFilamentSensor.o" "src\\FilamentSensors\\FilamentSensor.o" "src\\FilamentSensors\\SimpleFilamentSensor.o" "src\\GCodes\\GCodeBuffer.o" "src\\GCodes\\GCodeInput.o" "src\\GCodes\\GCodeMachineState.o" "src\\GCodes\\GCodeQueue.o" "src\\GCodes\\GCodes.o" "src\\GCodes\\GCodes2.o" "src\\GCodes\\RestorePoint.o" "src\\Heating\\FOPDT.o" "src\\Heating\\Heat.o" "src\\Heating\\Pid.o" "src\\Heating\\Sensors\\CpuTemperatureSensor.o" "src\\Heating\\Sensors\\CurrentLoopTemperatureSensor.o" "src\\Heating\\Sensors\\RtdSensor31865.o" "src\\Heating\\Sensors\\SpiTemperatureSensor.o" "src\\Heating\\Sensors\\TemperatureSensor.o" "src\\Heating\\Sensors\\Thermistor.o" "src\\Heating\\Sensors\\ThermocoupleSensor31855.o" "src\\Heating\\Sensors\\ThermocoupleSensor31856.o" "src\\Heating\\Sensors\\TmcDriverTemperatureSensor.o" "src\\Heating\\TemperatureError.o" "src\\Libraries\\Fatfs\\ccsbcs.o" "src\\Libraries\\Fatfs\\diskio.o" "src\\Libraries\\Fatfs\\fattime_rtc.o" "src\\Libraries\\Fatfs\\ff.o" "src\\Libraries\\General\\StringRef.o" "src\\Libraries\\Math\\Isqrt.o" "src\\Libraries\\sha1\\sha1.o" "src\\Movement\\BedProbing\\Grid.o" "src\\Movement\\BedProbing\\RandomProbePointSet.o" "src\\Movement\\DDA.o" "src\\Movement\\DriveMovement.o" "src\\Movement\\Kinematics\\CartesianKinematics.o" "src\\Movement\\Kinematics\\CoreBaseKinematics.o" "src\\Movement\\Kinematics\\CoreXYKinematics.o" "src\\Movement\\Kinematics\\CoreXYUKinematics.o" "src\\Movement\\Kinematics\\CoreXZKinematics.o" "src\\Movement\\Kinematics\\Kinematics.o" "src\\Movement\\Kinematics\\LinearDeltaKinematics.o" "src\\Movement\\Kinematics\\ScaraKinematics.o" "src\\Movement\\Kinematics\\ZLeadscrewKinematics.o" "src\\Movement\\Move.o" "src\\OutputMemory.o" "src\\Platform.o" "src\\PortControl.o" "src\\PrintMonitor.o" "src\\RADDS\\Network.o" "src\\RepRap.o" "src\\RepRapFirmware.o" "src\\Roland.o" "src\\Scanner.o" "src\\SoftTimer.o" "src\\Storage\\CRC32.o" "src\\Storage\\FileStore.o" "src\\Storage\\MassStorage.o" "src\\Tools\\Filament.o" "src\\Tools\\Tool.o" "src\\ZProbeProgrammer.o" -lCoreNG -Wl,--end-group -lm -gcc 
      arm-none-eabi-objcopy -O binary /RepRapFirmware-RADDS.elf /RepRapFirmware-RADDS.bin 
      arm-none-eabi-objcopy: '/RepRapFirmware-RADDS.elf': No such file
      
      

      I do get a .elf file but im not sure how to get the actual firmware .bin file. I've tried changing the extension to .bin instead of .elf but the file is double the size of the latest 1.19 RRF binary. What do I do? Thanks!

      posted in Firmware installation
      Bobbyofnaundefined
      Bobbyofna
    • DRV8825 Motor Whining (RADDS)

      Hello, I am new to RFF and am trying to install RRF on my custom designed IDEX 3D Printer. All of the motors are using the RAPS128 driver except for the extruders, which are using drv8825 stepper drivers. The two motors using the drv8825 drivers make a high pitched noise and dont move when i send the command for them to move. I have the things on the bottom of RADDS properly set for 1/32nd stepping, and I have checked all of the connections. The motors work with raps but not with the drv8825 driver. All motor currents are properly set for the current rating of the motor. I believe the issue lies in the configuration but im not totally sure. Are the drv8825 drivers compatible with radds and RRF in the first place. I have attached my config.g for reference. Thanks!

      [[language]]
      ; Movement section
      M569 P0 S0 R1                          	; Drive 0 goes forwards (change to S0 to reverse it)
      M569 P1 S0 R1                         	; Drive 1 goes forwards
      M569 P2 S1 R1                         	; Drive 2 goes forwards
      M569 P3 S1 R1                         	; Drive 3 goes forwards
      M569 P4 S1 T2							; Drive 4 goes forwards
      M569 P5 S1 T2                         	; Drive 5 goes forwards
      M584 X0 Y1 Z2 U3 E4:5               	; Create U axis for second X carriage before we try to configure it
      M574 X1 Y1 U2 Z0 S0                 	; Set endstop configuration (X and Y endstops at low end, U endstop at high end, active high, no Z endstop)
      M201 X1500 Y1500 U1500 Z15 E10000      	; Accelerations (mm/s^2)
      M203 X15000 Y15000 U15000 Z100 E3600	; Maximum speeds (mm/min)
      M566 X6000 Y6000 U6000 Z300 E3000     	; Minimum speeds mm/minute
      M208 X170 Y235 U240 Z200				; set axis maxima (adjust to suit your machine)
      M208 X-45 Y-15 U25 Z-0.2 S1				; set axis minimum (adjust to make X=0 and Y=0 the edge of the bed)
      M92 X640 Y1280 U1280 Z800				; Set axis steps/mm
      M92 E775:775                       		; Set extruder steps per mm
      G21                                 	; Work in millimetres
      G90                                 	; Send absolute coordinates...
      M83                                 	; ...but relative extruder moves
      
      ; Z probe section
      M558 P1 X0 Y0 Z1 H3 F20 T3600			; Smart IR Z probe, used for homing Z axis, dive height 3mm, probe speed 200mm/min, travel speed 5000mm/min
      G31 X15 Y35 Z1 P500           			; Set the probe height and threshold (put your own values here)
      
      ; Heater and thermistor section
      M305 P0 T100000 R4700 H0 L0				; Put your own H and/or L values here to set the bed thermistor ADC correction
      M305 P1 T100000 R4700 H0 L0				; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
      M305 P2 T4700 R4700 H0 L0				; Put your own H and/or L values here to set the second nozzle thermistor ADC correction
      M301 H1 P10 I0.10 D100 T0.50 S1.0		; PID settings for extruder 0
      M301 H2 P10 I0.10 D100 T0.50 S1.0		; PID settings for extruder 1
      M570 S120								; Increase to allow extra heating time if needed
      
      ; Tool definition section
      M563 P0 D0 H1 F1                       	; Define tool 0 to use extruder drive 0 and heater 1
      M563 P1 D1 H2 X3 F2                    	; Define tool 1 to use extruder drive 1 and heater 2
      G10 P0 X0 Y0 Z0 S0 R0      				; set tool 0 offsets and temperatures
      G10 P1 Y0 U0 Z0 S0 R0      				; set tool 1 offsets and temperatures
      
      
      posted in Duet Hardware and wiring
      Bobbyofnaundefined
      Bobbyofna
    • U Axis Max Endstop (RADDS)

      Hello, I am a new RRF user trying to install and configure RRF for my custom independent dual x axis 3d printer. I am stuck on trying to figure out where to wire the U axis endstop and how to get RRF to recognize it. I have tried plugging the end stop into every single min and max endstop pin on radds minus the ones being used(x min and y min). Where do I wire the U max endstop to on RADDS and what do I have to do in the config to map the U axis endstop to wherever it is plugged in? I have attached my config.g for reference Thanks!

      [[language]]
      ; Movement section
      M569 P0 S0 R1                          	; Drive 0 goes forwards (change to S0 to reverse it)
      M569 P1 S0 R1                         	; Drive 1 goes forwards
      M569 P2 S1 R1                         	; Drive 2 goes forwards
      M569 P3 S1 R1                         	; Drive 3 goes forwards
      M569 P4 S1								; Drive 4 goes forwards
      M569 P5 S1                          	; Drive 5 goes forwards
      M584 X0 Y1 Z2 U3 E4:5               	; Create U axis for second X carriage before we try to configure it
      M574 X1 Y1 U2 Z0 S0                 	; Set endstop configuration (X and Y endstops at low end, U endstop at high end, active high, no Z endstop)
      M201 X1500 Y1500 U1500 Z15 E10000      	; Accelerations (mm/s^2)
      M203 X15000 Y15000 U15000 Z100 E3600	; Maximum speeds (mm/min)
      M566 X6000 Y6000 U6000 Z300 E3000     	; Minimum speeds mm/minute
      M208 X220 Y220 U220 Z200				; set axis maxima (adjust to suit your machine)
      M208 X0 Y0 U0 Z-0.2 S1					; set axis minimum (adjust to make X=0 and Y=0 the edge of the bed)
      M92 X640 Y1280 U1280 Z800				; Set axis steps/mm
      M92 E775:775                       		; Set extruder steps per mm
      G21                                 	; Work in millimetres
      G90                                 	; Send absolute coordinates...
      M83                                 	; ...but relative extruder moves
      
      ; Z probe section
      M558 P1 X0 Y0 Z1 H3 F20 T3600			; Smart IR Z probe, used for homing Z axis, dive height 3mm, probe speed 200mm/min, travel speed 5000mm/min
      G31 X20 Y20 Z1 P500           			; Set the probe height and threshold (put your own values here)
      
      ; Heater and thermistor section
      M305 P0 T100000 R4700 H0 L0				; Put your own H and/or L values here to set the bed thermistor ADC correction
      M305 P1 T100000 R4700 H0 L0				; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
      M305 P2 T4700 R4700 H0 L0				; Put your own H and/or L values here to set the second nozzle thermistor ADC correction
      M301 H1 P10 I0.10 D100 T0.50 S1.0		; PID settings for extruder 0
      M301 H2 P10 I0.10 D100 T0.50 S1.0		; PID settings for extruder 1
      M570 S120								; Increase to allow extra heating time if needed
      
      ; Tool definition section
      M563 P0 D0 H1 F1                       	; Define tool 0 to use extruder drive 0 and heater 1
      M563 P1 D1 H2 X3 F2                    	; Define tool 1 to use extruder drive 1 and heater 2
      G10 P0 X0 Y0 Z0 S0 R0      				; set tool 0 offsets and temperatures
      G10 P1 Y0 U0 Z0 S0 R0      				; set tool 1 offsets and temperatures
      
      
      posted in Firmware installation
      Bobbyofnaundefined
      Bobbyofna
    • RE: Radds Bltouch configuration

      P3 is the only one that doesnt give me an invalid servo index for M280 and that doesnt work. The issue is radds actually uses heater 3. H3's pin is 21. I think to fix my issue I need to direct M558 to pin 39 instead of heater 3 in order for it to work.

      posted in Firmware installation
      Bobbyofnaundefined
      Bobbyofna
    • Radds Bltouch configuration

      So I have been trying to get my BLTouch sensor working with reprap firmware on radds but have been unsuccessful. I currently have the black and white pins connected to z min, and the other 3 pins connected to pin 39 or PWM3 on Radds. From my understanding reading other bltouch related threads, M558 P4 uses pin 39 while M558 P5 uses pin 5. In the z probe documentation for reprap firmware it says to use P5 for the BLTouch however most people use P4. I have tried both P5 and P4 however I cannot figure out which pin on Radds is pin 5. Whether I use P4 or P5 the Bltouch does not respond to any of my commands even the retract and deploy probe commands. Whenever I try to home Z, I get an error saying something like the probe is already at min. One thing I noticed is if i turn on the printer normally, M119 returns z min: at min stop, z probe: at min stop. However if i turn on the printer and hold the bltouch pin to put it in the error state, then M119 returns z min: not stopped z probe: at min stop. I also am not using the bltouch's 3.3v logic because its stealing 5v from an lcd pin and that seemed to have worked before with marlin. I know for the Duet the 3.3v logic needs to be turned on but should I turn it on in this case? I believe the problem with the bltouch lies in the config.g trying to communicate through a different pin but I'm not sure. Please let me know what you think.

      config.g

      [[language]]
      M307 H3 A-1 C-1 D-1
      M558 P5 X0 Y0 Z1 H3 F200 T5000
      G31 X-20.0 Y20.0 Z0 P25
      
      

      homez.g```
      [[language]]
      G28 X Y
      G90
      G1 X120 Y130
      M98 Pdeployprobe.g
      G30 S-1
      M98 Pretractprobe.g

      
      deployprobe.g
      

      [[language]]
      M280 P3 S10 I1

      retractprobe.g```
      [[language]]
      M280 P3 S90 I1
      
      
      posted in Firmware installation
      Bobbyofnaundefined
      Bobbyofna
    • RE: Radds - Endstops ignored and bltouch issues

      Okay so I fixed the endstop logic but am still having troubles with the bltouch. I can get it to home the x and y but when it goes to home the z it says the z probe is already triggered. Here are the lines from my config.g for the bltouch. I've tried setting p as both 5 and 4 just but neither work.

      [[language]]
      M307 H3 A-1 C-1 D-1
      M558 P5 X0 Y0 Z1 H3 F200 T5000
      G31 X-20.0 Y20.0 Z0 P25
      
      

      I am also having an issue with thermal runaways. When heating my hotend, I configured it so it heats slowly but even when it hits its target temperature it continues to heat. The entire time it is heating up, it does so in bursts. I dont know how to configure the pid properly please help.

      [[language]]
      M305 P0 T100000 B3950 R4700 H0 L0
      M305 P1 T100000 B3950 R4700 H0 L0
      M305 P2 T100000 B3950 R4700 H0 L0
      M301 H1 P0.1 I0.10 D100 T0.10 S1
      M301 H2 P0.1 I0.10 D100 T0.10 S1
      
      
      posted in Firmware installation
      Bobbyofnaundefined
      Bobbyofna
    • RE: Radds - Endstops ignored and bltouch issues

      Okay so I changed the M574 command to use S1 and now it is responding to the endstops however the logical is inverted. How do i invert the logic?

      As for the bltouch I do have the deployprobe.g and retractprobe.g files, but when sending those commands myself through simplify3d, I cannot get the pin to move on the bltouch. I would try to home Z but when i do the x and y axis start grinding because the logic of the endstops are inverted.

      posted in Firmware installation
      Bobbyofnaundefined
      Bobbyofna