Quantcast
Channel: Recent Discussions - Repetier-Forum
Viewing all 9285 articles
Browse latest View live

Change outlet on motherboard

$
0
0
Hey guys,


Can someone help me with my problem, or at least point me in the good direction?

I don't know how it happened, but somehow somethings wrong with my motherboard
This happened when I started up the printer after some idle months (moving house)

Things I know: 
The stepmotor isn't rotating, even when it's hot (200ºC)
I ruled out a wiring issue with help form my multimeter.
I ruled out a busted stepmotor, because it's working fine if I plug it into the X-axis slot on the motherboard.
I've updated to the latest version of Repetier Host.

Some other 3D enthousiasts think it's maybe a busted driver and/or mosfet, so my thinking is:
I've got a vacant slot on my motherboard and I need to plug it in there, but to do that I need to acces the code
I have some programing experience, but I can't seem to locate the way in. Can someome point me in the right direction?

I have a Zonestar P802N Reprap Prusa I3 printer, using Repetier Host V2.0.5 with Repetier_0.92.9 firmware.

Problems with 2 Extruders

$
0
0
Hello,
i have installed 2 Extruders but my Cura do Strange things.
Cura Create a second object.
can you help me ?





i got the same slice if i set my offset´s to 0

After Print finish it stays on 70%

$
0
0
Hi guys,
i run Repetier Server on my Raspi 3 with cl270 Webcam.
My print is already finished at layer 101/101 and ETE 0s.
But it shows me 73,32% ready, so i can´t get my timelaps video.

What´s the Problem.

Thank you.

Firmware install succes, not working

$
0
0
I'm "upgrading" my Da Vinci 2.0a duo.
I used Arduino IDE 1.8.5 and replaced the usb and variant files
I modified the Configuration file

#define DAVINCI 3// "0" if not DAVINCI, "1" For DAVINCI 1.0, "2" For DAVINCI 2.0 with 1 FAN, "3" For DAVINCI 2.0 with 2 FAN, 4 for AiO (WITH NO SCANNER SUPPORT)
#define MODEL  1//"0" for first generation (jumper JP1 to reset ) , "1" for new generation   (jumper J37 to reset)
#define REPURPOSE_FAN_TO_COOL_EXTRUSIONS 0 //Setting this to 1 will repurpose the main Extruder cooling fan to be controlled VIA M106/M107

Uploading the code is succesful 
Verify 211564 bytes of flash

[                              ] 0% (0/827 pages)
[==                            ] 9% (82/827 pages)
[=====                         ] 19% (164/827 pages)
[========                      ] 29% (246/827 pages)
[===========                   ] 39% (328/827 pages)
[==============                ] 49% (410/827 pages)
[=================             ] 59% (492/827 pages)
[====================          ] 69% (574/827 pages)
[=======================       ] 79% (656/827 pages)
[==========================    ] 89% (738/827 pages)
[============================= ] 99% (820/827 pages)
[==============================] 100% (827/827 pages)
Verify successful
done in 8.575 seconds
Set boot flash true
CPU reset.

But after that when i upload a gcode and want to print i get 
22:21:13.322: FIRMWARE_NAME:Repetier_0.92.10 FIRMWARE_URL:https://github.com/luc-github/Repetier-Firmware-0.92/ PROTOCOL_VERSION:1.0 MACHINE_TYPE:DaVinci EXTRUDER_COUNT:2 REPETIER_PROTOCOL:3
22:21:13.322: Printed filament:0.00m Printing time:0 days 0 hours 0 min
22:21:13.322: PrinterMode:FFF
22:21:13.322: Begin file list
22:21:13.385: ad_check_0002 1400
22:21:13.385: Machine_Life.dat 10
22:21:13.385: SAMPLE03.gcode 3669461
22:21:13.432: last_temperature.txt 4
22:21:13.432: eeprom.bin 4096
22:21:13.432: End file list
22:21:25.721: SelectExtruder:0
22:21:25.779: X:NAN Y:NAN Z:NAN E:NAN (2)
22:21:25.779: Unknown command:N318 M107
22:26:26.887: DebugLevel:14
22:26:26.887: Error:One heater seems decoupled from thermistor - disabling all for safety!
22:26:26.887: Error:Temp. raised to slow. Rise = -0.09 after 301028 ms
22:26:26.887: Disabling all heaters due to detected sensor defect.
22:26:26.887: DebugLevel:14
22:26:27.006: fatal:Heater/sensor failure Printer stopped and heaters disabled due to this error. Fix error and restart with M999.
22:26:27.006: TargetExtr 0: 0
22:26:27.006: TargetExtr 1: 0
22:27:27.596: fatal:Heater/sensor failure Printer stopped and heaters disabled due to this error. Fix error and restart with M999. (220)
22:27:27.774: TargetExtr 0: 0
22:27:27.774: TargetExtr 1: 0
22:39:11.915: fatal:Heater/sensor failure Printer stopped and heaters disabled due to this error. Fix error and restart with M999. (702)

Temp.sensor and heater decoupled

I also cannot move the bed with the arrows. 
First i tried the octopi software then i moved to Repetier host for a direct connetion to the printer.

Am i missing some steps or am i doing something wrong?
Please could someone please help me.

Implementing LASER INTENSITY

$
0
0
Hi all !
I'm trying to implement laser intensity routine, i have a laser driver with a TTL input so, 
i try to modify source from : 

WRITE(LASER_PIN,(LASER_ON_HIGH ? newIntensity > 199 : newIntensity < 200));

to 

analogWrite(LASER_PIN, newIntensity);


But nothing change ! :/
PWM 255 = ON 
PWM <255 = OFF 

i also try 
m42 p44 s254 = ON 
m42 p44 s254 = OFF

Any ideas ? 

Here the simple code : 

void LaserDriver::changeIntensity(uint8_t newIntensity)
{
    if(EVENT_SET_LASER(newIntensity))
    {
        // Default implementation
#if LASER_PIN > -1
        //WRITE(LASER_PIN,(LASER_ON_HIGH ? newIntensity > 199 : newIntensity < 200));
// set PWM wave to TTL laser-driver input 
analogWrite(LASER_PIN, newIntensity);
    }
}

SPI for 5 slaves - custom PCB design

$
0
0
Hey all,

I am currently designing an own board for a 3D-printer having 5 TMC2130 stepper drivers. The board is based on a SAM3X8E (like Arduino Due or Ultratronics). There is already a discussion about the TMC2130 ....
I don't want to control the TMC2130 via SPI but the standard step/dir/en control. But I want to configure the drivers via SPI on startup and maybe add some custom M-commands for reconfiguring them during runtime or reading some errors or whatever. Therefore I will have to add some custom code in Repetier firmware, maybe using this API. But currently I am not at this point so far, so this is a hardware question:
The thing is the SAM3X8E has actually two HW SPIs, SPI0 and SPI1. Repetier firmware supports SPI0. There is also a SW SPI that is known to be pretty slow but that shouldn't be a problem. When using the HW SPI0 I can connect up to 4 slaves on the lines NPCS0 to NPCS3. That is unfortunately one less than needed. Actually there are only 3 SS available for the Arduino Due: 4, 10, 52. Again this depends on some configuration as the line NPCS0 could be used for Mode Fault detection....

So there are a couple of solutions in my mind right now:

- I could use the SW SPI. But I am not sure how many slaves are supported and as the SAM3X8E has two HW SPIs it would be sad not using them.
- I could connect 3 slaves on SPI0 and 2 slaves on SPI1. I alter the SPI code in HAL.h and HAL.cpp and add SPI1. When transmitting anything via the SPI-class I need to distinguish by the driver number which SPI to use. Therefore this would be a fast solution by (simply spoken) copying the SPI0 code and changing it to SPI1. A little more code here and there and it should be working.
- I could stay with SPI0 and use the "Peripheral Chip Select Decoding"-Feature described on page 687 of the SAM3X8E datasheet. In this case some bits in the Mode and Transmit Data Registers have to be changed so the value of the PCS field represents a binary number corresponding to a certain driver. The NPCS0..3 lines are not connected to the slaves but to an multiplexer chip. The value of the NPCS lines would be something like: 0000 -> no driver selected, 0001 -> driver 1 selected, 0010 -> driver 2 selected, 0011 -> driver 3 selected and so on.
I will have to alter some of the SPI code in the HAL files to change the PCS and PS fields and maybe alter some general logic in it. But this should also work.


Can anyone recommend the best solution? I am not very much in the Repetier Firmware Code right now as I first want to finish my hardware design before getting to the software part. I prefer solution 2 or 3.

I am thankful for any help and recommendations. If there is any interest I will share my custom code to get the driver running as soon as it's working (in a couple of months, I am still designing the schematics of the board....)

Best regards
Stefan

Ultimaker 2+

$
0
0
Configuring the Repetier Server for Ultimaker 2+ I get terrible noises by manual moving of the z-axis .
Does anyone have the correct configuring settings ?



Server Cannot Connect to Printer but Host Can

$
0
0
Before I explain my problem, here is my setup:
Windows 8.1 computer 
Repetier Host 1.0.6
Repetier Server 0.50.3
PrintrBot Jr v1 
PrintrBoard rev D with Marlin Firmware
The printer registers as COM3 on the computer and when I'm using Repetier-Host, I'm able to connect to the printer just fine; I'm able to control it manually, do prints, etc. But when I try to use Repetier-Server using the same COM port, baud rate, etc., the Server website only shows a orange colored connected image. I realize I have to disconnect / close Host when I try to use Server and have the printer deactivated on Server when using Host; that doesn't seem to be the issue.

I've tried finding a log file somewhere for Repetier-Server but I can't seem to find one.

Here is an image of the Repetier-Host printer config (you'll notice the green connected image in the top left as well)

Here is an image of the Repetier-Server printer config

And here is an image of the status once I activate the printer on Repetier-Server

For what it's worth, I have a Raspberry Pi with OctoPrint on it that has been working with this printer for over a year without problems. It had the same baud rate, 250000, on it as well.

Any suggestions or ideas on how to fix this?

Problem with TMC2130 and SPI

$
0
0
Hey guys,
I am struggling getting my TMC2130 drivers working on my self developed "PilotBoard". It's based on an SAM3X8E so to make it short: It's an Due with 5x TMC2130 drivers onboard.

To make some things clear in the beginning:
  • I tested all components on my board first separately to make sure they are all working: EEPROM via I2C works, TMC2130s via SPI are working
  • So I started configure Repetier Firmware and connect via Repetier Host to make sure the Firmware is at least sending something
  • I didn't enable TMC2130 feature and firmware was not responding. After changing line 130 and 131 in HAL.cpp from TWI1 to TWI0 for EEPROM Repetier Host connected and responded and was able to read data from EEPROM. BTW a configuration feature for TWI0 or TWI1 would be nice so one doesn't have to change firmware!
  • In the next step I enabled TMC2130 feature and tried to connect. Repetier Host was not receiving anything. So I expect Repetier Firmware to stop initialization when communication with TMC2130 doesn't work. That's my current problem now.
As other Arduino sketches work to configure the drivers I am pretty sure there is no hardware problem. Furthermore I routed PCK1 of SAM3X8E to the TMC2130 clock inputs. TMC2130 won't respond to SPI if there is no clock signal or clk is not connected to GND instead (it will put MISO line low the whole CS LOW time). So for the moment I put the following code in Repetier.ino before "Printer::setup();":
    REG_PIOA_PDR |= 0x01000000;        // enable peripheral control
    REG_PIOA_PER &= ~0x01000000;        // Prevents disabling peripheral control of the pin
    REG_PIOA_ABSR |= 0x01000000;       // B preipherial select
  
    REG_PMC_SCER |= 0x200;
    PMC->PMC_PCK[1] = 0x01;       // master clock = 12Mhz (crystal freq)

To make sure the drivers have this signal. Measuring the signal with an oscilloscope confirms the signal is working at 12MHz. That shouldn't be the problem either. To make absolutely sure it's not a clk problem I connected a SilentStepStick TMC2130 (Watterott) to my board headers (it has the clk input connected to GND what is mostly the standard). I reconfigured the pins of SilentStepStick in my files to be my "X" driver (it's the first one getting initialized). The result was the same as before.

So next thing I did is connecting a logic-analyzer to my SPI bus and the CS pin of motor X (as it's the first one getting initialized):


Obviously here's the problem. Taking a look at channel0 shows the SPI's clock line is doing something strange. Sure it's an software SPI but taking channel3 into consideration shows that the amount of falling edges of the clock line differs from CS LOW cycle to CS LOW cycle. As MISO generates different signals I assume the driver is responding somehow.

As a very unlikely reason I could imagine that the counter used for generating PCK1 is used by SPI. Nevertheless I am pretty sure that's not the problem. But I am going to deactivate this feature and connect the SilentStepStick again.

Regarding "#define SDSS 77" I am not sure what to do. I also tried several combinations trying other configurations like "#define NONSTANDARD_SDSS". (Pin configurations at the end of this post)

Does anyone has an idea what the problem might be? I would be super thankful for any help!

Best regards
Stefan

PS: A nice configuration feature for the DEV version of Repetier would be to set the proper Sense Resistor value for TMC2130. Standard is 0.11Ohm for the SilentStepStick TMC2130. Clones or other boards may have other sense resistors. Function:
tmc_driver->rms_current(level);
in Commands.cpp line 533 assumes the sense resistor to be 0.11Ohm. Mine is currently 0.1Ohm so current calculation of function rms_current() is not exact in my case. 
Changing it to "tmc_driver->rms_current(level, 0.5, 0.1);" does pretty much the same but taking the sense resistor into account. The value "0.5" stands for the hold current multiplier. Being able to set this value in the firmware configuration would be great as well.

Here is my userpins.h file:
//Definition der individuellen Pins für das PilotBoard 4.0 REV 1

#define MOSI_PIN 75
#define MISO_PIN 74
#define SCK_PIN 76
//#define SDSSORIG 52
#define SDSS   77
//#define NONSTANDARD_SDSS 1

#define ORIG_X_STEP_PIN 46
#define ORIG_X_DIR_PIN 44
#define ORIG_X_ENABLE_PIN 45
#define ORIG_X_MIN_PIN   -1
#define ORIG_X_MAX_PIN     12

/*#define ORIG_Y_STEP_PIN 50
#define ORIG_Y_DIR_PIN 48
#define ORIG_Y_ENABLE_PIN 49
#define ORIG_Y_MIN_PIN       11
#define ORIG_Y_MAX_PIN       -1*/
#define ORIG_Y_STEP_PIN 40
#define ORIG_Y_DIR_PIN 39
#define ORIG_Y_ENABLE_PIN 38
#define ORIG_Y_MIN_PIN       11
#define ORIG_Y_MAX_PIN       -1

#define ORIG_Z_STEP_PIN 64
#define ORIG_Z_DIR_PIN 63
#define ORIG_Z_ENABLE_PIN 62
#define ORIG_Z_MIN_PIN       28
#define ORIG_Z_MAX_PIN       -1

#define ORIG_E0_STEP_PIN 25
#define ORIG_E0_DIR_PIN 26
#define ORIG_E0_ENABLE_PIN 24

/*#define ORIG_E1_STEP_PIN 40
#define ORIG_E1_DIR_PIN 39
#define ORIG_E1_ENABLE_PIN 38*/

#define ORIG_PS_ON_PIN       -1

#define PCK1    55 //PCK1 pin

#define HEATER_0_PIN   9 //Extruder 1
#define HEATER_1_PIN   2   //Heizbett
#define HEATER_2_PIN   3   //Extruder 2

#define TEMP_0_PIN     2 //Extruder 1
#define TEMP_1_PIN     1   //Heizbett (Pin muss nach Port lt. Datenblatt des SAM3X gewählt werden: Heibzett Thermistor = Due Pin 60 = Due Analog In 6 = PA3 = SAM3X AD1)
#define TEMP_2_PIN     3 //Extruder 2
#define TEMP_3_PIN     0 //Steuerplatine

#define ORIG_FAN_PIN   8 //Bauteilkuehler 
#define ORIG_FAN2_PIN       6 //Steuerplatinenluefter

#define E0_PINS ORIG_E0_STEP_PIN,ORIG_E0_DIR_PIN,ORIG_E0_ENABLE_PIN,
#define E1_PINS ORIG_E1_STEP_PIN,ORIG_E1_DIR_PIN,ORIG_E1_ENABLE_PIN,

#define LED_PIN   13

// 20 or 70
#define SDA_PIN 70
// 21 or 71
#define SCL_PIN 71

#define TWI_CLOCK_FREQ           400000
// see eeprom device data sheet for the following values, these are for 24xx256
#define EEPROM_SERIAL_ADDR     0x50   // 7 bit i2c address (without R/W bit)
#define EEPROM_PAGE_SIZE       64     // page write buffer size
#define EEPROM_PAGE_WRITE_TIME   7      // page write time in milliseconds (docs say 5ms but that is too short)
// TWI_MMR_IADRSZ_1_BYTE for 1 byte, or TWI_MMR_IADRSZ_2_BYTE for 2 byte
#define EEPROM_ADDRSZ_BYTES     TWI_MMR_IADRSZ_2_BYTE
#define EEPROM_AVAILABLE 1

And part of my Configuration.h:
#define TMC2130_X_CS_PIN 47
#define TMC2130_Y_CS_PIN 41
#define TMC2130_Z_CS_PIN 65
#define TMC2130_EXT0_CS_PIN 23
#define TMC2130_EXT1_CS_PIN -1
#define TMC2130_EXT2_CS_PIN -1

Object not appearing

$
0
0
Most objects that I create with Freecad  load and slice as expected (slc3r).  Even if they are not manifold, they  still show in the preview (and may slice OK).  But just sometimes the object doesn't show and I don't know why.  - If it doesn't show on the printer bed preview, it never slices.

For example I created a
cube with a single hole through it- no problem
cube with two holes - no problem
cube with two holes but closer together - doesn't show.
cuboid with 5 holes well spaced - doesn't show.

It's actually this last one that I really want to print, I just did the others to try to work out what was going on - any ideas?

Thanks
 

To move my 3D printer without an extrusor

$
0
0
Hello,
does anyone know how I can to start moving my 3D printer without an extrusor? I only need to verify the movement but it sends a "Heating ERROR", even when I have already dissabled the extrusor options. I would appreciate any help or suggestion.
Thanks a lot.

Wanhao i3 duplicator PLUS does not show any messages on LCD, because it runs marlin?

$
0
0
My maker select V2 shows message on screen (ETA, ETE, etc.) pushed from repetier server or host (Not sure on the flow) I cannot seem to find a way to make this work. Even when I try to send an M117 w/ text I get nothing.   Anyone find a way around this? is this a Marlin limitation or this stupid touchscreen FW in this plus model?

Thanks
Dave

Láser pin pwm. Help-__-

$
0
0
I do not understand how to implement or manage the pwm pulses of 0-255.

I have arduino mega + ramps v 1. 4.
I understand that pin 44 is pwm.
I also have this

To be.

https://m.banggood.com/450nm-3500mW-3_5W-Blue-Laser-Module-With-TTL-Modulation-for-DIY-Laser-Cutter-Engraver-p-1103261.html?rmmds=orderdetail


I work with the laser with this code.

/////

int led = 9; // the PWM pin the LED is attached to
int brightness = 0; // how bright the LED is
int fadeAmount = 5; // how many points to fade the LED by

// the setup routine runs once when you press reset:
void setup() {
// declare pin 9 to be an output:
pinMode(led, OUTPUT);
}

// the loop routine runs over and over again forever:
void loop() {
// set the brightness of pin 9:
analogWrite(led, brightness);

// change the brightness for next time through the loop:
brightness = brightness + fadeAmount;

// reverse the direction of the fading at the ends of the fade:
if (brightness = 255) {
fadeAmount = -fadeAmount;
}
// wait for 30 milliseconds to see the dimming effect
delay(30);
}

/////


I send this from the console.

M452 // mode laser
M3 s33 //

but nothing happens.


#define SUPPORT_LASER 1
#define LASER_PIN 44
#define LASER_ON_HIGH 1
#define LASER_WARMUP_TIME 0
#define LASER_PWM_MAX 255
#define LASER_WATT 2


//////****

how to modify this file so that it works?
Drivers.h


#if defined(SUPPORT_LASER) && SUPPORT_LASER

secondspeed_t LaserDriver::intensity = LASER_PWM_MAX; // Intensity to use for next move queued if we want lasers. This is NOT the current value!
secondspeed_t LaserDriver::intens = 0;

bool LaserDriver::laserOn = false;
bool LaserDriver::firstMove = true;

void LaserDriver::initialize()
{
if(EVENT_INITIALIZE_LASER)
{
#if LASER_PIN > -1
SET_OUTPUT(LASER_PIN);
#endif
}
changeIntensity(0);
}

void LaserDriver::changeIntensity(secondspeed_t newIntensity)
{
#if defined(DOOR_PIN) && DOOR_PIN > -1
if(Printer::isDoorOpen()) {
newIntensity = 0; // force laser off if door is open
}
#endif
if(EVENT_SET_LASER(newIntensity))
{
// Default implementation
#if LASER_PIN > -1
WRITE(LASER_PIN,(LASER_ON_HIGH ? newIntensity > 199 : newIntensity < 200));
#endif
}
intens=newIntensity;//for "Transfer" Status Page
}
#endif // SUPPORT_LASER


*********
I modific

#if LASER_PIN > -1
WRITE(LASER_PIN,(LASER_ON_HIGH ? newIntensity > 199 : newIntensity < 200));
#endif


To


#if LASER_PIN > -1
analogWrite( LASER_PIN, newIntensity);
#endif


... no found

Auto-levelling and Z-endstop problem

$
0
0
I am stumped and hope that someone can help please.

I have changed the X-carriage and extruders on my Prusa i3 steel derivative printer and have added Z-probe capabilities using one of David Crockers optical boards connected to the X-max endstop channel. It works when I test it with a G30 P0 command, doing the three checks and then providing a response.

I also have Z-endstops on maximum and minimum channels. I have set the Z-probe offset (2.5mm) and the heatbed has three manual height adjustment screws.

I am using Repetier firmware (0.92.9), host (2.0.1) and server (0.80.3).

I have run through this page https://www.repetier.com/documentation/repetier-firmware/z-probing/ and think I have done everything correctly.

Symptoms:


1. When I home the Z axis with no Z-probing, the endstop triggers and the nozzles is about where it should be to print but the nozzles then raise a few millimetres. If I start a print it prints those same few millimetres above the bed

2. When I do a G30 P0 it works fine and returns results that make sense for the Z axis

3. Executing a G29 when the head is at the centre of the heatbed causes the Z-height to decrease to about 10mm then the X-axis goes to home and the Y axis goes to maximum (my Y-home is minimum) followed by a critical error reported by Repetier Host (G29 fialed, clear problem then run M999). Why does it try to home on Y Max, not Min and why does it error on G29?

4. G32 causes the Y axis to go to minimum again, the X to home and the Z to go to maximum where it hits the endstop and I get the error message from Repetier again.

What am I doing wrong, please?

Thanks.

Richard

G32 end up with a hard Reset

$
0
0
Hi !

I need to Level my bed so I just make G28 followed by G32. The Bed comes up, the head moves to the left front corner and then nothing happens. After one second of waiting the printer (SparkCube XL) makes a hard Reset. :/

Did I miss something for G32? I tried it with the latest 1.0.1 Firmware.

The Log says "17:50:38.064: Info:Watchdog Reset"

regards
  Dominik


Autolevel Producing errors

$
0
0
i already try G33 , G32 , with all parameters, but my delta still producing these errors, i follow all the tips on wizard but i aways got these matriz transformation errors, i suspect that i need to use a field called "error collum" but i really don´t know how to do that , plz, someone can help me ?

Communication Errors Again...

$
0
0
Hi Repetier, I have ruined a couple of print with communication error. They happen in different place on same print.I already have checksum error but when I have uploaded the new firmware they were gone. Now its not only a comms errors, it does the same things if I unplug the usb in the middle of a print. Can you help ?


 Here is the log:

14:23:14.747 : Printing layer 37 of 222
14:24:38.873 : Printing layer 38 of 222
14:26:00.672 : Printing layer 39 of 222
14:27:23.695 : Printing layer 40 of 222
14:28:20.572 : M20
14:28:22.691 : M20
14:28:22.691 : start
14:28:22.691 : Info:PowerUp
14:28:22.691 : Detected EEPROM version:18
14:28:22.691 : Info:Autoleveling enabled
14:28:22.691 : Transformation matrix: 0.999962 0.000000 0.008662 0.000035 0.999992 -0.004084 -0.008662 0.004084 0.999954
14:28:23.841 : zDistortionCorrection:1
14:28:23.842 : Free RAM:78368
14:28:23.842 : Autoretract:0
14:28:23.842 : X:0.00 Y:0.00 Z:0.000 E:0.0000
14:28:23.842 : SelectExtruder:0
14:28:23.843 : FIRMWARE_NAME:Repetier_1.0.0dev FIRMWARE_URL:https://github.com/repetier/Repetier-Firmware/ PROTOCOL_VERSION:1.0 MACHINE_TYPE:Delta EXTRUDER_COUNT:4 REPETIER_PROTOCOL:3
14:28:23.843 : Cap:PROGRESS:1
14:28:23.843 : M155 S1
14:28:23.843 : Cap:AUTOREPORT_TEMP:1
14:28:23.843 : Cap:EEPROM:1
14:28:23.844 : Cap:AUTOLEVEL:1
14:28:23.844 : Cap:Z_PROBE:1
14:28:23.844 : Cap:SOFTWARE_POWER:1
14:28:23.844 : Cap:TOGGLE_LIGHTS:0
14:28:23.844 : Cap:PAUSESTOP:1
14:28:23.844 : Cap:PREHEAT:1
14:28:23.844 : Printed filament:366.71m Printing time:10 days 14 hours 4 min
14:28:23.844 : PrinterMode:FFF
14:28:23.844 : Error:Checksum required when switching back to ASCII protocol.
14:28:23.844 : Resend:3
14:28:23.844 : Resend after 4350885ms
14:28:23.845 : Info:No case lights
14:28:23.845 : X:10.00 Y:10.00 Z:0.000 E:0.0000
14:28:23.845 : DebugLevel:6
14:28:23.845 : Config:Baudrate:250000
14:28:23.845 : Config:InputBuffer:127
14:28:23.845 : Config:NumExtruder:4
14:28:23.845 : Config:MixingExtruder:0
14:28:23.845 : Config:HeatedBed:1
14:28:23.845 : Config:SDCard:1
14:28:23.845 : Config:Fan:1
14:28:23.845 : Config:Fan2:0
14:28:23.845 : Config:LCD:1
14:28:23.845 : Config:SoftwarePowerSwitch:1
14:28:23.845 : Config:XHomeDir:-1
14:28:23.845 : Config:YHomeDir:-1
14:28:23.845 : Config:ZHomeDir:1
14:28:23.845 : Config:XHomePos:0.00
14:28:23.846 : Config:YHomePos:0.00
14:28:23.846 : Config:ZHomePos:185.106
14:28:23.846 : Config:SupportG10G11:1
14:28:23.846 : Config:SupportLocalFilamentchange:1
14:28:23.846 : Config:CaseLights:0
14:28:23.846 : Config:ZProbe:1
14:28:23.846 : Config:Autolevel:1
14:28:23.846 : Config:EEPROM:1
14:28:23.846 : Config:PrintlineCache:16
14:28:23.846 : Config:JerkXY:20.00
14:28:23.846 : Config:KeepAliveInterval:2000
14:28:23.846 : Config:RetractionLength:1.00
14:28:23.846 : Config:RetractionLongLength:1.00
14:28:23.846 : Config:RetractionSpeed:40.00
14:28:23.846 : Config:RetractionZLift:0.00
14:28:23.846 : Config:RetractionUndoExtraLength:0.00
14:28:23.846 : Config:RetractionUndoExtraLongLength:0.00
14:28:23.846 : Config:RetractionUndoSpeed:20.00
14:28:23.846 : Config:XMin:0.00
14:28:23.846 : Config:YMin:0.00
14:28:23.846 : Config:ZMin:0.00
14:28:23.846 : Config:XMax:200.00
14:28:23.846 : Config:YMax:200.00
14:28:23.846 : Config:ZMax:185.11
14:28:23.846 : Config:XSize:200.00
14:28:23.846 : Config:YSize:200.00
14:28:23.846 : Config:ZSize:185.11
14:28:23.846 : Config:XPrintAccel:100.00
14:28:23.846 : Config:YPrintAccel:100.00
14:28:23.846 : Config:ZPrintAccel:100.00
14:28:23.846 : Config:XTravelAccel:100.00
14:28:23.846 : Config:YTravelAccel:100.00
14:28:23.846 : Config:ZTravelAccel:100.00
14:28:23.846 : Config:PrinterType:Delta
14:28:23.847 : Config:MaxBedTemp:120
14:28:23.847 : Config:Extr.1:Jerk:20.00
14:28:23.847 : Config:Extr.1:MaxSpeed:50.00
14:28:23.847 : Config:Extr.1:Acceleration:5000.00
14:28:23.847 : Config:Extr.1:Diameter:0.00
14:28:23.847 : Config:Extr.1:MaxTemp:275
14:28:23.847 : Config:Extr.2:Jerk:20.00
14:28:23.847 : Config:Extr.2:MaxSpeed:50.00
14:28:23.847 : Config:Extr.2:Acceleration:5000.00
14:28:23.847 : Config:Extr.2:Diameter:0.00
14:28:23.847 : Config:Extr.2:MaxTemp:275
14:28:23.847 : Config:Extr.3:Jerk:20.00
14:28:23.847 : Config:Extr.3:MaxSpeed:50.00
14:28:23.847 : Config:Extr.3:Acceleration:5000.00
14:28:23.847 : Config:Extr.3:Diameter:0.00
14:28:23.847 : Config:Extr.3:MaxTemp:275
14:28:23.847 : Config:Extr.4:Jerk:20.00
14:28:23.847 : Config:Extr.4:MaxSpeed:50.00
14:28:23.847 : Config:Extr.4:Acceleration:5000.00
14:28:23.847 : Config:Extr.4:Diameter:0.00
14:28:23.847 : Config:Extr.4:MaxTemp:275
14:28:23.847 : Begin file list
14:28:23.847 : End file list
14:28:33.874 : G28
14:28:34.711 : Info:Autoleveling disabled
14:28:40.097 : SelectExtruder:0
14:28:40.097 : X:0.00 Y:0.00 Z:185.110 E:0.0000
14:28:40.097 : Info:Autoleveling enabled

v. 1.1.0 Update Error

$
0
0
When I try to update Repetier-Host to version 1.1.0, it will download the update, but when I click "install and relaunch" it comes up with the error "Failed to change owner & group for wx-config with owner ID 501 and group ID 80". Has anyone else had this problem, and does anyone know what I can do to fix it?

Support for new TMC2130 SSS (SilentStepStick) via SPI

$
0
0
Do you know this driver?
http://www.trinamic.com/products/integrated-circuits/stepper-power-driver/tmc2130
https://github.com/watterott/SilentStepStick
The driver is Pololu compatible. BUT(!) you can also drive with SPI. Then you get a lot of new features. 
https://ultimaker.com/en/community/17498-new-sss-driver-tmc2130
image
example:
1) Auto Bed Leveling / Ebdstopf (Load detection)
2) Emergency ShutDown
3) Lost Step/Load Indicator (Extruder)
4) no filament detection (zero load)
Is it possible to integgrate this Driver (SPI-register) to Repetier firmware?


Problem with laser option

$
0
0
Hi everyone,
I'm having some problems with activation laser. Using 101 firmware, laser is On/Off style, 1W, connected to hotend fan pin (ORIG_FAN_PIN as in Configuration file). 
Here's a piece of gcode:
;start g_code
G28 ; home all axes
M452 ; select laser mode
G21 ; set units to millimeters
G90 ; use absolute coordinates
;general g_code
M106 S0
G0 X0 Y0 Z40 F1000
G0 X-2 Y0 F1000
G0 X0.02 Y0 F1000
M106 S255
G1 X40.01 Y0 F500
M107 S0

I can manually activate laser, but it doesn't activate in print process. What am I doing wrong?
Viewing all 9285 articles
Browse latest View live