Quantcast
Channel: Repetier-Firmware - Repetier-Forum
Viewing all 1057 articles
Browse latest View live

Max number of virtual extruders

$
0
0
Hello,
I am very satisfied of the Repetier FW and I am experimenting new things like a mixing extruder with more than 3 pla filaments.
To test it I would need to exceed the max number of virtual extruders in M163 and M164 gcode commands.
Unfortunately when I exceed the 15 the mixing alghorithm does not work any more. Example:

This sequence works
; Cyan
M163 S0 P0
M163 S1 P0
M163 S2 P0
M163 S3 P1
M163 S4 P0
M163 S5 P0
M164 S0

while this doesn't work
; Cyan2
M163 S0 P0
M163 S1 P0
M163 S2 P0
M163 S3 P1
M163 S4 P0
M163 S5 P0
M164 S16

Thanks for your answer.

Walter

Selective eprom parameters

$
0
0
as i understand, the eprom stores important variables in the firmware without the need of flashing the arduino with new values, but this can lead to a user causing mayhem with the printer.   Is there a way to disable the possibility of changing some of the values?
for example, through eprom changes, one can alter the printer size.  Can this be disabled and how?

Unload script works via Repetier Host but not via SD card

$
0
0
I tried putting simple filament loading scripts for my bondtech extruder on to my sd card:
G92 E0 
G1 E300 F2000
G92 E0 


I tried cold extrusion M302, relative mode M83 nothing works when printed from SD card,
but works fine when send from Repetier Host.

Why is this?

TMC 5160 Support

$
0
0
Hello !

Is there any support for TMC 5160 in repetier firmware ?
As the two steppers seems to be very close in configuration, can we use it or not and if not, when ?

Thanks

Davinci Duo 2.0A not extruding while printing.

$
0
0
I seem to have a problem with my Davinci Duo 2.0 since it is not extruding anything when it starts to print. I can manualy make it extrude through the Repetier Host, but when I try to print something nothing comes out?

Switched to Repetier-firmware from Marlin, now connection problems in Repetier Host

$
0
0
Hi there.  Sorry for having to make this thread but I've searched high and low for a solution and wasted a lot of time trying to figure it out but I'm totally stumped (and a bit frustrated).  I appreciate any help anyone can offer.

A little background:
Printer is a Prusa Mendel v2 I built back in 2013 running Marlin on a Sanguinololu board.  Been spending some time lately getting it dusted off and printing well again and decided to modify/update the firmware.  I cannot for the life of me compile and/or upload Marlin firmware on any version of arduino IDE, so I decided to go with repetier firmware since it appears to have become a lot more user friendly from when I first tried it when I built the printer.  The configuration wizard is genius and the documentation is excellent!  I really want this firmware to work and it needs to because with the compiling problems I'm having with Marlin, I'm past the point of no return.

My problem:
Using Arduino version 1.8.8 with added Sanguino drivers, the upload completes successfully but when I try to connect to Repetier host, I encounter symptoms of incorrect baud rate: serial comm errors with a line of gibberish.  Problem is, I've tried every possible baud rate in both firmware and host software with no change in error message.  Started with 115200 that I was running with Marlin, nothing.  Tried 250000, no change.  Went to 9600, nothing.  I'm changing the value in configuration.h and in the printer settings.  I've tried changing com ports in device manager, no change.  Printer was printing previously in the day on Marlin firmware, so the only variable that has changed is the firmware.  Same USB cord, same USB port, same computer.  I've searched high and low on google with everything pointing to baud rate mismatches, but that doesn't help.  I've uploaded stock repetier firmware (no changes) and customized firmware for my configuration and no difference in result.

Anything I could be overlooking here?

Software leveling delta

$
0
0
Hi, I've recently built a delta printer from scratch, I'm using the newest repetier firmware and I'm having some issues trying to level it. The Z axis/height calibration is successful, but the X/Y calibration isn't. I have tried adjusting Rod_radius to remove the Convex effect and that seem to work, but the whole bed looks like it's tilted along the Z tower (at the same height, it touches the bed close to Z tower, while it isn't touching it at X/Y towers). I have tried to adjust the the endstop offsets, but that doesn't seem to have an effect. I see that there is a "level delta" setting in the display menu, but I have no clue how to use it and I would need some help with that too. I don't have auto-level and the endstops/bed isn't movable.

Multicolor - Extruder

$
0
0
Hi,

I developed/developing a water-cooled multicolor-extruder and need some help.

I'm using v.1.0.4dev, RADDS 1.5, 5 RAPS128 and 4 other stepper drivers (1/256 sm0ver.drv). two heating elements and one thermistor for the extruder.

The extruder works fine, thats not the problem, but (a support for a second heater in multicolor extruder would be fine, but my heater get the power from outside the radds):

When changing colors I need an option like fillament change in the firmware, but in another way.
- goto x_y(_z)
- change to next used extruder and
- press x mm fillament out (cleaning color)
- ( a cleaning nozzle parameter would be fine - drive with the nozzle over a cleaning pad or such like this)
- go back to position

Is there any way to do that automatically at extruder change?


Here is a suggestion for multicolor extruder support in your firmware:
It's a relatively simple thing (I think so)

I use the colors and mixing tables from RGB and use red, yellow, blue, black and white (set 1 part blue, 1 part yellow for green in best case).
At the Moment I have to write new mixing tables for printing with new colors.

a table or file (colors.h) with up to 256 colors (or more) with mixing tables (like now with virtual extruders) from 2/3-5 extruders (set in the config tool). Then I would give every color a fixed index number, 1- e.g. 32/64/128 fixed color Indexer for better slicer support. Indexer > 256 free color Indexer. I think, then it's easier to integrate a second or third extruder for solutable or electrical filament

Fixed Index for groud colors like red, blue, yellow, cyan, mangenta, black, white. bind the to the 2/3-5 extruders
Fixed Index - fixed color tone with changeable values (M163) for for every fixed Index
Free Index - self made colors

Fixed index ground color - Extruder 1
Color Name (in my case for red in the first extruder)
M163 S0 P1
M163 S1 P0
M163 S2 P0
M163 S3 P0
M163 S4 P0
M16x - I1 (index number)

More information about my multi-color extruder: Thingiverse and look for Sprenger or Multicolor-extruder.

Hope you can help!

Pause after homing X

$
0
0
I have Core-XY printer (H-bot) and my homing sequence is - X then Y and finally Z. Most of the times homing works as it should, but in about 20-30% of cases I am observing that print-head homes at X then stops for several seconds (could be up-to 10) and then continues homing towards Y and Z. While this is not causing any problems, I am just curios what could be the reason and whether anybody else is observing similar behavior.

Thanks

Programming an endstop for an extruder

$
0
0
Hello

I Am bulding a 3D Printer. I use a Radds board with extension and an arduino due.

I have a tool changing system with three hotends.
The hotends are assembled on a plate, so the Stepper Motor has to turn until the right hotend is selected. This motor is configured as a extruder 4.

I already installed 3 endstops for xyz-axis. But I also need a endstop for the tool changing system.
This endstop will be placed on a left space on the board for example y_max.

But currently I have no idea how to programming an endstop for an extruder in the configuration.h file.

Does someone have any suggestions for this problem, or does someone has this problem already solved?

Thanks in advance mates!

Cheers!

BL-Touch fährt nicht aus

$
0
0

Hallo together,

ich habe ein Problem mit meinem BL-Touch. Wenn ich den Drucker einschalte, dann fährt der Sensor zweimal aus und wieder ein und leuchtet danach rot. Wenn ich die z-Achse dann leveln möchte, dann fährt die Z-Achse in Richtung des Betts aber der Sensor fährt nicht aus. Ich muss den Strom dann wieder ausschalten, damit der Druckkopf nicht auf den Tisch fährt. Außerdem funktionieren die ganzen M-Befehle für den BL-Touch auch nicht.

Kann mir hierbei jemand helfen?

Der Bl-Touch ist richtig angeschlossen und die Config.h habe ich auch schon mehrmals überprüft.  Kann mir dabei jemand weiterhelfen?


// ################ Endstop configuration #####################
#define ENDSTOP_PULLUP_X_MIN true
#define ENDSTOP_X_MIN_INVERTING false
#define MIN_HARDWARE_ENDSTOP_X true
#define ENDSTOP_PULLUP_Y_MIN true
#define ENDSTOP_Y_MIN_INVERTING false
#define MIN_HARDWARE_ENDSTOP_Y false
#define ENDSTOP_PULLUP_Z_MIN false
#define ENDSTOP_Z_MIN_INVERTING false
#define MIN_HARDWARE_ENDSTOP_Z true
#define ENDSTOP_PULLUP_X_MAX true
#define ENDSTOP_X_MAX_INVERTING false
#define MAX_HARDWARE_ENDSTOP_X false
#define ENDSTOP_PULLUP_Y_MAX true
#define ENDSTOP_Y_MAX_INVERTING false
#define MAX_HARDWARE_ENDSTOP_Y true
#define ENDSTOP_PULLUP_Z_MAX true
#define ENDSTOP_Z_MAX_INVERTING false
#define MAX_HARDWARE_ENDSTOP_Z false
#define max_software_endstop_r true

#define min_software_endstop_x false
#define min_software_endstop_y true
#define min_software_endstop_z true   //geändert
#define max_software_endstop_x true
#define max_software_endstop_y false
#define max_software_endstop_z true
#define ENDSTOP_X_BACK_MOVE 5
#define ENDSTOP_Y_BACK_MOVE 5
#define ENDSTOP_Z_BACK_MOVE 2
#define ENDSTOP_X_RETEST_REDUCTION_FACTOR 3
#define ENDSTOP_Y_RETEST_REDUCTION_FACTOR 3
#define ENDSTOP_Z_RETEST_REDUCTION_FACTOR 3
#define ENDSTOP_X_BACK_ON_HOME 10
#define ENDSTOP_Y_BACK_ON_HOME 10
#define ENDSTOP_Z_BACK_ON_HOME 20
#define ALWAYS_CHECK_ENDSTOPS 0

======== Servos =======
Control the servos with
M340 P<servoId> S<pulseInUS>   / ServoID = 0..3  pulseInUs = 500..2500
Servos are controlled by a pulse width normally between 500 and 2500 with 1500ms in center position. 0 turns servo off.
WARNING: Servos can draw a considerable amount of current. Make sure your system can handle this or you may risk your hardware!
*/
#define FEATURE_SERVO 1
#define SERVO0_PIN 5
#define SERVO1_PIN -1
#define SERVO2_PIN -1
#define SERVO3_PIN -1
#define SERVO0_NEUTRAL_POS  1500
#define SERVO1_NEUTRAL_POS  -1
#define SERVO2_NEUTRAL_POS  -1
#define SERVO3_NEUTRAL_POS  -1
#define UI_SERVO_CONTROL 1    //geändert
#define FAN_KICKSTART_TIME  200

        #define FEATURE_WATCHDOG 1    //geändert

### Z-Probing #####################

#define Z_PROBE_Z_OFFSET 0
#define Z_PROBE_Z_OFFSET_MODE 0
#define UI_BED_COATING 1
#define FEATURE_Z_PROBE 1
#define Z_PROBE_BED_DISTANCE 5
#define Z_PROBE_PIN ORIG_Z_MIN_PIN
#define Z_PROBE_PULLUP 1
#define Z_PROBE_ON_HIGH 1
#define Z_PROBE_X_OFFSET 0
#define Z_PROBE_Y_OFFSET 0
#define Z_PROBE_WAIT_BEFORE_TEST 0
#define Z_PROBE_SPEED 2
#define Z_PROBE_XY_SPEED 150
#define Z_PROBE_SWITCHING_DISTANCE 5
#define Z_PROBE_REPETITIONS 2
#define Z_PROBE_HEIGHT 5
#define Z_PROBE_START_SCRIPT "M340 P0 S700"
#define Z_PROBE_FINISHED_SCRIPT "M340 P0 S1500"
#define Z_PROBE_REQUIRES_HEATING 0
#define Z_PROBE_MIN_TEMPERATURE 150
#define FEATURE_AUTOLEVEL 1
#define Z_PROBE_X1 20
#define Z_PROBE_Y1 20
#define Z_PROBE_X2 160
#define Z_PROBE_Y2 20
#define Z_PROBE_X3 100
#define Z_PROBE_Y3 260
#define BED_LEVELING_METHOD 0     // geändert
#define BED_CORRECTION_METHOD 0
#define BED_LEVELING_GRID_SIZE 2
#define BED_LEVELING_REPETITIONS 5
#define BED_MOTOR_1_X 0
#define BED_MOTOR_1_Y 0
#define BED_MOTOR_2_X 200
#define BED_MOTOR_2_Y 0
#define BED_MOTOR_3_X 100
#define BED_MOTOR_3_Y 200
#define BENDING_CORRECTION_A 0
#define BENDING_CORRECTION_B 0
#define BENDING_CORRECTION_C 0
#define FEATURE_AXISCOMP 0
#define AXISCOMP_TANXY 0
#define AXISCOMP_TANYZ 0
#define AXISCOMP_TANXZ


Vielen Dank und viele Grüße

Hans-Gustav

What is a temperature sensor?

$
0
0
Have you ever left your smartphone in your car on a hot day? If so, your screen might have displayed an image of a thermometer and a warning that your phone has overheated. That is because there is a tiny embedded temperature sensor that measures the interior temperature of your phone. Once the inside of the phone reaches a certain temperature (iPhones shut down at approximately 113 degrees Fahrenheit, for example), the temperature probe sends an electronic signal to an embedded computer. This, in turn, restricts users from accessing any applications or features until the phone has cooled back down, as running programs would only further damage the phone’s interior components.  

A temperature sensor is an electronic device that measures the temperature of its environment and converts the input data into electronic data to record, monitor, or signal temperature changes. There are many different types of temperature sensors. Some temperature sensors require direct contact with the physical object that is being monitored (contact temperature sensors), while others indirectly measure the temperature of an object (non-contact monitor temperature probe).  

Non-contact temperature sensors are usually infrared (IR) sensors. They remotely detect the IR energy emitted by an object and send a signal to a calibrated electronic circuit that determines the object's temperature.

Among the contact medical temperature probe are thermocouples and thermistors. A thermocouple is comprised of two conductors, each made of a different type of metal, that are joined at an end to form a junction. When the junction is exposed to heat, a voltage is generated that directly corresponds to the temperature input. This happens on account of the phenomena called the thermoelectric effect. Thermocouples are generally inexpensive, as their design and materials are simple. The other type of contact temperature sensor is called a thermistor. In thermistors, resistance decreases as temperature increases. There are two main types of thermistors: Negative Temperature Coefficient (NTC) and Positive Temperature Coefficient (PTC). Thermistors are more precise than thermocouples (capable of measuring within 0.05-1.5 degrees Celsius), and they are made of ceramics or polymers. Resistance Temperature Detectors (RTD) are essentially the metal counterpart of thermistors, and they are the most precise and expensive type of temperature sensors.

Temperature sensors are used in automobiles, medical devices, computers, cooking appliances, and other types of machinery.

CNC tool length measurement on Z-Axis

$
0
0
Hi @all,

i am using repetier firemware for my cnc machine.
I was planing on using a tool length measurement end stop.

Basicly it is an endstop that activates somewhere above my worktable.
Something like this https://bit.ly/2Opo3an

The question is how to configure this?

The behaviour I would need is:

* Home Z in negative direction against Z-Min-Endstop
* Stop When hitting endpoint
* set absolut coordinates of repetier controler to tool length sensor height(e.g. 18mm), instead of setting it to zero

Is there any way? 


G32 works but drives outside bed bounds and crashes

$
0
0
So I finally got sick of manually levelling my bed with a screwdriver and bought an IR sensor. It works super well and was extremely easy to install because I already have an E3Dv6 hotend. After a couple of hours of struggling through extremely poor documentation I thought I had understood everything. I set up my slicer start code to this:

G28 ;home all axes
G92 E0 ;I don't remember what this is for
G1 Z30 F750 ;lower gently closer to bed to avoid horrible-sounding resonance from z-axis higher up
G32 ;auto-level
G1 X0 Y75 Z50 F1000 ;lift nozzle in preparation for extruding
G1 E20 F120 ;extrude 20mm of filament (which I trim off manually with pliers before the print starts)
G92 E0
G4 P3000

...and hit print. All going well, but the print started too close to the bed and the filament was getting squished completely flat. I actually have no idea why that happened (it seems to be printing at z=0 for some reason?) but that's not the main issue today. Since I had to cancel the print anyway I decided to try again but with the probe points further out, closer to the edges of the bed for better accuracy. I originally had the 3rd probe point at x=74, y=143 (maximum Y length is 173mm, so it was measuring 30mm in from the end of the bed) but I thought I should probably get it a bit closer, so I changed it to x=74, y=163 (which should probe 10mm from the end of the print area). That worked fine.... until the G32 completed and it randomly tried to drive way off the end of the bed and crashed it.

So... wtf? Why did it ignore the software endstops? Why did it even try to move after completing G32? I don't understand why it tries to move 30mm forwards at the end of a G32 at all, let alone why it overrides the software endstops and crashes the bed. I also can't figure out if the probe points (i.e. Z_PROBE_X1, Z_PROBE_Y1, etc.) are supposed to indicate the position of the probe when probing, or the position of the extruder when probing. It doesn't say. I would assume it means the probe position, but then when I start a G32 it first moves the extruder to what looks like y=60..... so..... again, wtf? The probe is already at y=30 and you KNOW the probe is 30mm ahead of the extruder so WHY are you moving another 30mm?? I just don't understand :'(

My X and Y limits are 147mm and 173mm respectively. My probe sits ~30mm in front of the extruder (so 30mm ahead of the extruder, in the Y+ direction; in other words, with the extruder at y=0, the probe would be roughly y=30). I'm on version 0.92.9. This my z-probe config:

// #################### Z-Probing #####################

#define Z_PROBE_Z_OFFSET 0
#define Z_PROBE_Z_OFFSET_MODE 0
#define UI_BED_COATING 1
#define FEATURE_Z_PROBE 1
#define Z_PROBE_BED_DISTANCE 5
#define Z_PROBE_PIN ORIG_Z_MIN_PIN
#define Z_PROBE_PULLUP 0
#define Z_PROBE_ON_HIGH 1
#define Z_PROBE_X_OFFSET 0
#define Z_PROBE_Y_OFFSET 30
#define Z_PROBE_WAIT_BEFORE_TEST 0
#define Z_PROBE_SPEED 2
#define Z_PROBE_XY_SPEED 150
#define Z_PROBE_SWITCHING_DISTANCE 0.5
#define Z_PROBE_REPETITIONS 2
#define Z_PROBE_HEIGHT 1.20
#define Z_PROBE_START_SCRIPT ""
#define Z_PROBE_FINISHED_SCRIPT ""
#define Z_PROBE_REQUIRES_HEATING 0
#define Z_PROBE_MIN_TEMPERATURE 150
#define FEATURE_AUTOLEVEL 1
#define Z_PROBE_X1 10   //10 from left, facing electronics
#define Z_PROBE_Y1 30   //30 from back, facing electronics
#define Z_PROBE_X2 137  //10 from 147 max right, facing electronics
#define Z_PROBE_Y2 30   //30 from back, facing electronics
#define Z_PROBE_X3 74   //half of 147 max right, facing electronics
#define Z_PROBE_Y3 163  //10 from 173 max forward, facing electronics - CRASHES BED INTO PHYSICAL MAXIMUM Y+ WTF
#define BED_LEVELING_METHOD 0
#define BED_CORRECTION_METHOD 0
#define BED_LEVELING_GRID_SIZE 5
#define BED_LEVELING_REPETITIONS 5
#define BED_MOTOR_1_X 0
#define BED_MOTOR_1_Y 0
#define BED_MOTOR_2_X 200
#define BED_MOTOR_2_Y 0
#define BED_MOTOR_3_X 100
#define BED_MOTOR_3_Y 200
#define BENDING_CORRECTION_A 0
#define BENDING_CORRECTION_B 0
#define BENDING_CORRECTION_C 0
#define FEATURE_AXISCOMP 0
#define AXISCOMP_TANXY 0
#define AXISCOMP_TANYZ 0
#define AXISCOMP_TANXZ 0

Help!

Adjusting bed leveling procedure with BL-Touch

$
0
0
Hello,

I have an Arduino Due with Radds V1.6 and Bl-Touch. If i start the bed leveling procedure the printer drives to every point and starts leveling in z direction. The printer checks every positions twice. In the first step the print head drives up (away from the bed) and during this he is pushing down the pin (no contact to bed is happening) and then drives back down to bed until the pin hits the bed. After this the print head drives up again for the second leveling step. But during the way up the pin gets pushed down immediately and now he has contact to the bed too early. Then the print head drives back down, but now the bl touch can't deliver a signal because it still has contact to bed. 
If this is happening I need to push the emergency button, otherwise the printer crashes. 

I also tried to reduce the repetitions in the config.h to 1, but it failed he still did 2. I don't know why.

To my question: 
Is there a possibility to set a delay time in a sub program or somewhere else when the pin gets pushed down in the second step? 

Thank you in advance :) 



Radds 1.6 on board micro SD usage?

$
0
0
Hi guys,

Does anyone know how to get the Micro SD slot to work on the RADDS 1.6 board?
Everytime I plug in a SD it tries to load it but says it failed. I tried Fat32, fat and exfat formats.
All of them don't work.

I don't have a LCD screen, it's running with octoprint but I want to use an SD.

Thanks in common.

Dennis

Tmc2208

$
0
0
How do I setup tmc2208 stepper drivers in stand alone mode in the firmware?

Manual (v. 0.91)

Dual X endstops and homing

$
0
0
I need some help understanding configuration settings for dual X setup.

In my initial configuration I tried to replicate my Velleman Vertex K8400 printer that has Tool 0 at the right and Tool 1 at the left.  
My settings were
X_HOME_DIR=1
MIN_HARDWARE_ENDSTOP_X false
MAX_HARDWARE_ENDSTOP_X true
MIN_HARDWARE_ENDSTOP_X2 true
MAX_HARDWARE_ENDSTOP_X2 false

Right motor was connected to the default X driver and left (X2) motor was connected to 3rd (unused) extruder's driver.

All endstops were tested with M119 and worked correctly.
Both print heads moved correctly, however, during homing, X2 motor would not stop when MIN_HARDWARE_ENDSTOP_X2 was triggered.

Then I decided to swap the motors, made left motor X and right motor X2.
I changes settings to 
X_HOME_DIR=-1
MIN_HARDWARE_ENDSTOP_X true
MAX_HARDWARE_ENDSTOP_X false
MIN_HARDWARE_ENDSTOP_X2 false
MAX_HARDWARE_ENDSTOP_X2 true
The behavior was the same - MAX_HARDWARE_ENDSTOP_X2 would trigger but not stop X2 motor during homing.

Since nether MIN, nor MAX X2 endstops worked, I decided to switch to the default endstops
X_HOME_DIR=-1
MIN_HARDWARE_ENDSTOP_X true
MAX_HARDWARE_ENDSTOP_X true
MIN_HARDWARE_ENDSTOP_X2 false
MAX_HARDWARE_ENDSTOP_X2 false

Surprisingly, this configuration worked just fine, but I left wondering, are these settings correct and if they are, under which conditions MIN and MAX ENSTOP_X2 should be used.

I am attaching my configuration.h file in case somebody wants to have a look at it. 

If you are running Repetier firmware on dual X printer, I'd really appreciate if you share your configuration.h file with me.

Thanks.
P.S. My mainboard is Ultratronics PRO v1.0

When printing a curved surface, it indicates a convex rib

$
0
0
hi,I use repetier firmware 0.92 version .but when I print some model ,convex rib occur on the surface。


when I use marlin ,these convex rib disappear,thanks in advance for any suggestion
Viewing all 1057 articles
Browse latest View live