No need to post this everywhere... on marlin github was enough...
↧
Re: Waves when printing
↧
Re: Waves when printing
Then just delete this topic, I will not be offended.:)
↧
↧
Re: Error compiling Marlin-bugfix-2.0
Again, thank you. I solved my issue. You got me thinking about files and paths and I found that my anti-spyware had quarantined a piece of my platform IO files.
↧
Re: Problem z axis
Okay so now I have managed to manipulate the Z offset, but strange things are happening. When I use the M206 command to set the Z offset to -1.49 the echo in Pronterface shows that it is set to that. So I save it to EPROM with the M500 command. What I am seeing on the LCD Info Screen is that the Z is set to -2.98.
Also much of the X and Y axies are screwed up. Help...
Also much of the X and Y axies are screwed up. Help...
↧
Re: TMC2130 Not Moving. Marlin 2.0. M122 "Unknown command"
Thanks for your help guys. Really appreciate it. They started to move when I used Cura monitor tab instead of pronterface (weird behavior) but once they started moving they do the job. They work well now except for sensorless homing, but I will try these days again. Watterott drivers seems to work fine.
↧
↧
Re: Problem z axis
M206 is persistent, from the description in the marlin site:
"The home offset is persistent — added to the current position until changed."
I think it means that the effect is cumulative.
I am not sure but isn't it better to use M851 Z-1.49
Or is that only for when homing with a probe?
"The home offset is persistent — added to the current position until changed."
I think it means that the effect is cumulative.
I am not sure but isn't it better to use M851 Z-1.49
Or is that only for when homing with a probe?
↧
Re: Problem z axis
So this is what I get when I try to use M851:
echo:Unknown command: "M851 Z-1.49"
echo:Unknown command: "M851 Z-1.49"
↧
anycubic 4max (TriGorilla ) marlin 2.0 filament problem
Hello,
I upgraded marlin in my printer to 2.0 stable, almost finished configuration, but I have a problem with filament runout sensor.
I added BLtouch (working fine), then enabled filament sensor:
First I check sensor by M119, not working (always open), so I added to pins.trigorilla.h
now filament sensor start working, its opened when filament is out and trigger when is in, then I check M600 command, and everything work fine.
Now the problem, when filament is over, printer ignore this, nothing happens, like filament sensor stop working (but is working).
I can't find solution.
Need help :D
I upgraded marlin in my printer to 2.0 stable, almost finished configuration, but I have a problem with filament runout sensor.
I added BLtouch (working fine), then enabled filament sensor:
/** Filament Runout Sensors Mechanical or opto endstops are used to check for the presence of filament. RAMPS-based boards use SERVO3_PIN for the first runout sensor. For other boards you may need to define FIL_RUNOUT_PIN, FIL_RUNOUT2_PIN, etc. By default the firmware assumes HIGH=FILAMENT PRESENT. */ #define FILAMENT_RUNOUT_SENSOR #if ENABLED(FILAMENT_RUNOUT_SENSOR) #define NUM_RUNOUT_SENSORS 1 // Number of sensors, up to one per extruder. Define a FIL_RUNOUT#_PIN for each. #define FIL_RUNOUT_INVERTING true // Set to true to invert the logic of the sensor. #define FIL_RUNOUT_PULLUP // Use internal pullup for filament runout pins. //#define FIL_RUNOUT_PULLDOWN // Use internal pulldown for filament runout pins. // Set one or more commands to execute on filament runout. // (After 'M412 H' Marlin will ask the host to handle the process.) #define FILAMENT_RUNOUT_SCRIPT "M600" // After a runout is detected, continue printing this length of filament // before executing the runout script. Useful for a sensor at the end of // a feed tube. Requires 4 bytes SRAM per sensor, plus 4 bytes overhead. //#define FILAMENT_RUNOUT_DISTANCE_MM 25 #ifdef FILAMENT_RUNOUT_DISTANCE_MM // Enable this option to use an encoder disc that toggles the runout pin // as the filament moves. (Be sure to set FILAMENT_RUNOUT_DISTANCE_MM // large enough to avoid false positives.) //#define FILAMENT_MOTION_SENSOR #endif #endif
First I check sensor by M119, not working (always open), so I added to pins.trigorilla.h
#define FIL_RUNOUT_PIN 19,
now filament sensor start working, its opened when filament is out and trigger when is in, then I check M600 command, and everything work fine.
Now the problem, when filament is over, printer ignore this, nothing happens, like filament sensor stop working (but is working).
I can't find solution.
Need help :D
↧
Marlin build problem for Anet A6
Hello to the group,
I have an ANET A6 and am trying to build the Marlin 1.1.9 firmware.
I can build the firmware OK with Arduino 1.8.5 but with Arduino 1.8.10 I get the following:
-----------------------------------------------------------------------------------------------------------------------------------------
Arduino: 1.8.10 (Windows 10), Board: "Anet V1.0"
In file included from sketch\endstops.cpp:35:0:
sketch\endstop_interrupts.h: In function 'void setup_endstop_interrupts()':
endstop_interrupts.h:121:7: error: non-constant condition for static assertion
static_assert(digitalPinToPCICR(X_MIN_PIN) != NULL, "X_MIN_PIN is not interrupt-capable");
^~~~~~~~~~~~~
In file included from C:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino/Arduino.h:257:0,
from sketch\HAL.h:36,
from sketch\MarlinConfig.h:39,
from sketch\Marlin.h:35,
from sketch\endstops.cpp:27:
pins_arduino.h:117:66: error: reinterpret_cast from integer to pointer
#define digitalPinToPCICR(p) ( (((p) >= 0) && ((p) <= 31)) ? (&PCICR) : ((uint8_t *)0) )
~^~~~~~~
sketch\endstop_interrupts.h:121:21: note: in expansion of macro 'digitalPinToPCICR'
static_assert(digitalPinToPCICR(X_MIN_PIN) != NULL, "X_MIN_PIN is not interrupt-capable");
^~~~~~~~~~~~~~~~~
In file included from sketch\endstops.cpp:35:0:
endstop_interrupts.h:141:7: error: non-constant condition for static assertion
static_assert(digitalPinToPCICR(Y_MIN_PIN) != NULL, "Y_MIN_PIN is not interrupt-capable");
^~~~~~~~~~~~~
In file included from C:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino/Arduino.h:257:0,
from sketch\HAL.h:36,
from sketch\MarlinConfig.h:39,
from sketch\Marlin.h:35,
from sketch\endstops.cpp:27:
pins_arduino.h:117:66: error: reinterpret_cast from integer to pointer
#define digitalPinToPCICR(p) ( (((p) >= 0) && ((p) <= 31)) ? (&PCICR) : ((uint8_t *)0) )
~^~~~~~~
sketch\endstop_interrupts.h:141:21: note: in expansion of macro 'digitalPinToPCICR'
static_assert(digitalPinToPCICR(Y_MIN_PIN) != NULL, "Y_MIN_PIN is not interrupt-capable");
^~~~~~~~~~~~~~~~~
In file included from sketch\endstops.cpp:35:0:
endstop_interrupts.h:162:7: error: non-constant condition for static assertion
static_assert(digitalPinToPCICR(Z_MIN_PIN) != NULL, "Z_MIN_PIN is not interrupt-capable");
^~~~~~~~~~~~~
In file included from C:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino/Arduino.h:257:0,
from sketch\HAL.h:36,
from sketch\MarlinConfig.h:39,
from sketch\Marlin.h:35,
from sketch\endstops.cpp:27:
pins_arduino.h:117:66: error: reinterpret_cast from integer to pointer
#define digitalPinToPCICR(p) ( (((p) >= 0) && ((p) <= 31)) ? (&PCICR) : ((uint8_t *)0) )
~^~~~~~~
sketch\endstop_interrupts.h:162:21: note: in expansion of macro 'digitalPinToPCICR'
static_assert(digitalPinToPCICR(Z_MIN_PIN) != NULL, "Z_MIN_PIN is not interrupt-capable");
^~~~~~~~~~~~~~~~~
Any suggestions?
Thanks.
Wayne
I have an ANET A6 and am trying to build the Marlin 1.1.9 firmware.
I can build the firmware OK with Arduino 1.8.5 but with Arduino 1.8.10 I get the following:
-----------------------------------------------------------------------------------------------------------------------------------------
Arduino: 1.8.10 (Windows 10), Board: "Anet V1.0"
In file included from sketch\endstops.cpp:35:0:
sketch\endstop_interrupts.h: In function 'void setup_endstop_interrupts()':
endstop_interrupts.h:121:7: error: non-constant condition for static assertion
static_assert(digitalPinToPCICR(X_MIN_PIN) != NULL, "X_MIN_PIN is not interrupt-capable");
^~~~~~~~~~~~~
In file included from C:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino/Arduino.h:257:0,
from sketch\HAL.h:36,
from sketch\MarlinConfig.h:39,
from sketch\Marlin.h:35,
from sketch\endstops.cpp:27:
pins_arduino.h:117:66: error: reinterpret_cast from integer to pointer
#define digitalPinToPCICR(p) ( (((p) >= 0) && ((p) <= 31)) ? (&PCICR) : ((uint8_t *)0) )
~^~~~~~~
sketch\endstop_interrupts.h:121:21: note: in expansion of macro 'digitalPinToPCICR'
static_assert(digitalPinToPCICR(X_MIN_PIN) != NULL, "X_MIN_PIN is not interrupt-capable");
^~~~~~~~~~~~~~~~~
In file included from sketch\endstops.cpp:35:0:
endstop_interrupts.h:141:7: error: non-constant condition for static assertion
static_assert(digitalPinToPCICR(Y_MIN_PIN) != NULL, "Y_MIN_PIN is not interrupt-capable");
^~~~~~~~~~~~~
In file included from C:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino/Arduino.h:257:0,
from sketch\HAL.h:36,
from sketch\MarlinConfig.h:39,
from sketch\Marlin.h:35,
from sketch\endstops.cpp:27:
pins_arduino.h:117:66: error: reinterpret_cast from integer to pointer
#define digitalPinToPCICR(p) ( (((p) >= 0) && ((p) <= 31)) ? (&PCICR) : ((uint8_t *)0) )
~^~~~~~~
sketch\endstop_interrupts.h:141:21: note: in expansion of macro 'digitalPinToPCICR'
static_assert(digitalPinToPCICR(Y_MIN_PIN) != NULL, "Y_MIN_PIN is not interrupt-capable");
^~~~~~~~~~~~~~~~~
In file included from sketch\endstops.cpp:35:0:
endstop_interrupts.h:162:7: error: non-constant condition for static assertion
static_assert(digitalPinToPCICR(Z_MIN_PIN) != NULL, "Z_MIN_PIN is not interrupt-capable");
^~~~~~~~~~~~~
In file included from C:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino/Arduino.h:257:0,
from sketch\HAL.h:36,
from sketch\MarlinConfig.h:39,
from sketch\Marlin.h:35,
from sketch\endstops.cpp:27:
pins_arduino.h:117:66: error: reinterpret_cast from integer to pointer
#define digitalPinToPCICR(p) ( (((p) >= 0) && ((p) <= 31)) ? (&PCICR) : ((uint8_t *)0) )
~^~~~~~~
sketch\endstop_interrupts.h:162:21: note: in expansion of macro 'digitalPinToPCICR'
static_assert(digitalPinToPCICR(Z_MIN_PIN) != NULL, "Z_MIN_PIN is not interrupt-capable");
^~~~~~~~~~~~~~~~~
Any suggestions?
Thanks.
Wayne
↧
↧
Re: Marlin build problem for Anet A6
The error message is "static_assert(digitalPinToPCICR(X_MIN_PIN) != NULL, "X_MIN_PIN is not interrupt-capable");"
So you have enabled endstops interrupts but the pin you are using for X Min endstop cannot do this.
disable #define ENDSTOP_INTERRUPTS_FEATURE in the Configuration.h
So you have enabled endstops interrupts but the pin you are using for X Min endstop cannot do this.
disable #define ENDSTOP_INTERRUPTS_FEATURE in the Configuration.h
↧
Re: Marlin build problem for Anet A6
Thanks,
That worked. However, now the lcd display is pixelated with the 1.8.10 build but is OK with the 1.8.5 build.
Any Ideas? If not I will generate a new post .
Thanks again,
Wayne
That worked. However, now the lcd display is pixelated with the 1.8.10 build but is OK with the 1.8.5 build.
Any Ideas? If not I will generate a new post .
Thanks again,
Wayne
↧
Zonestar End Stop Issues
Hi All,
I have "upgraded" my Zonestar P802M with a Rumba board and Marlin. It seems that all is ok, but every now and then the printer ignores the x-min endstop and it I have to hit the emergency stop ("nasty grrrrrrrrr") . It happens mostly after Home, but is inconsistent. Many times it is fine. I do not think it is mechanical, but I cannot determine a pattern. Please see my files attached
Best Regards
Jean
I have "upgraded" my Zonestar P802M with a Rumba board and Marlin. It seems that all is ok, but every now and then the printer ignores the x-min endstop and it I have to hit the emergency stop ("nasty grrrrrrrrr") . It happens mostly after Home, but is inconsistent. Many times it is fine. I do not think it is mechanical, but I cannot determine a pattern. Please see my files attached
Best Regards
Jean
↧
Re: Marlin 2.0 Hardware
Looks interesting. Thanks for the info.
↧
↧
Re: Delta TMC2130 sensorless homing Marlin 2.0
Some Homing Help for Delta.
Im using SKR v1.3 with TMC2130 (same as Einsy Rambo) and have also been struggling over getting Marlin 2.0 to Sensorless Home my Delta.
I had the same issue where the X and Y homed perfectly, but Z would just crash unless I used a physical endstop.
What fixed it for me was commenting out the #define USE_ZMIN_PLUG. This made the Z tower home the same as the others.
I also found that #define MINIMUM_STEPPER_PULSE 2 was Wrong!.
2 is NOT the correct pulse value for TMC2130s, 0 is..I commented this line out all together and used default value.
This was only thing that actually made sensorless homing trigger at all.
Until I commented this out, nothing was making a difference and StallGuard was never triggering.
Also, the homing code for Delta is not correct for Sensorless homing. See Thinkyhead's comment from Mar 17 2018. [github.com]
This is still incorrect in the latest Marlin 2.0. However it is now in the delta.ccp file.
This causes the printer to move all carriages only a tiny bit (juts a few microsteps) before homing individual towers.
This is fine if the carriages are close to the top, but if they're not, X starts to move up alone and jams up the printer.
I also noticed that if you have StallGuard Threshold set just 1 point to low, you will have odd homing behavior.
If X gets home first, Y just stops, then Z homes normally.
If Y gets home first X stops, then Z homes normally.
So either way, I end up with one axis not homed, and the other 2 homed
Anyway, I Hope some/any of this helps someone.
Im using SKR v1.3 with TMC2130 (same as Einsy Rambo) and have also been struggling over getting Marlin 2.0 to Sensorless Home my Delta.
I had the same issue where the X and Y homed perfectly, but Z would just crash unless I used a physical endstop.
What fixed it for me was commenting out the #define USE_ZMIN_PLUG. This made the Z tower home the same as the others.
I also found that #define MINIMUM_STEPPER_PULSE 2 was Wrong!.
2 is NOT the correct pulse value for TMC2130s, 0 is..I commented this line out all together and used default value.
This was only thing that actually made sensorless homing trigger at all.
Until I commented this out, nothing was making a difference and StallGuard was never triggering.
Also, the homing code for Delta is not correct for Sensorless homing. See Thinkyhead's comment from Mar 17 2018. [github.com]
This is still incorrect in the latest Marlin 2.0. However it is now in the delta.ccp file.
This causes the printer to move all carriages only a tiny bit (juts a few microsteps) before homing individual towers.
This is fine if the carriages are close to the top, but if they're not, X starts to move up alone and jams up the printer.
I also noticed that if you have StallGuard Threshold set just 1 point to low, you will have odd homing behavior.
If X gets home first, Y just stops, then Z homes normally.
If Y gets home first X stops, then Z homes normally.
So either way, I end up with one axis not homed, and the other 2 homed
Anyway, I Hope some/any of this helps someone.
↧
BLTouch and Marlin 2.0
How's it going,
The other day I upgraded to the new marlin firmware (using an MKS Gen 1.4). Interfacing with pronterface I was carrying out an automatic bed leveling cycle and checking out the values it was producing. Now I know the BLtouch is not the most accurate piece of equipment but after doing multiple rounds the values seem almost random. When I get home from work I can post some examples but not changing anything and preforming G29 I would get 1mm or more differences. This is rendering the BLtocuh system useless and I cant even lay down a first layer. I like to do multiple rounds of bed leveling and slowly teak the bed so all nine values are within 0.1mm and I could do this before but now it just feels like a lost cause. I spent over 6 hours yesterday trying to develop some correlation between the values it was producing with no luck. Anyone have any ideas what I could change. I was thinking about dropping the z axis feed rate and probing each point over 3 times. I just dont remember it taking this long to solve. Also sometimes the values would run away, as in although changing nothing and running G29 the values would double every time. I would have to turn the printer off and back on to get it to act somewhat predictable again. Sorry for the rant but I am just puzzled, could it be a wiring issue, anyone having issues with this? After work I will downgrade back to 1.9 and report back. I am tempted to rewire the entire BLtouch system and downgrade back to 1.9. I also have three different BLtouch's two V2.1 and one V3.0 if that helps. Used all three last night during the 6 hour leveling session.
Thanks for reading!
The other day I upgraded to the new marlin firmware (using an MKS Gen 1.4). Interfacing with pronterface I was carrying out an automatic bed leveling cycle and checking out the values it was producing. Now I know the BLtouch is not the most accurate piece of equipment but after doing multiple rounds the values seem almost random. When I get home from work I can post some examples but not changing anything and preforming G29 I would get 1mm or more differences. This is rendering the BLtocuh system useless and I cant even lay down a first layer. I like to do multiple rounds of bed leveling and slowly teak the bed so all nine values are within 0.1mm and I could do this before but now it just feels like a lost cause. I spent over 6 hours yesterday trying to develop some correlation between the values it was producing with no luck. Anyone have any ideas what I could change. I was thinking about dropping the z axis feed rate and probing each point over 3 times. I just dont remember it taking this long to solve. Also sometimes the values would run away, as in although changing nothing and running G29 the values would double every time. I would have to turn the printer off and back on to get it to act somewhat predictable again. Sorry for the rant but I am just puzzled, could it be a wiring issue, anyone having issues with this? After work I will downgrade back to 1.9 and report back. I am tempted to rewire the entire BLtouch system and downgrade back to 1.9. I also have three different BLtouch's two V2.1 and one V3.0 if that helps. Used all three last night during the 6 hour leveling session.
Thanks for reading!
↧
More than 3 linear axis (UVW) with marlin
Hey,
I did a lot of research but I couldn't find out if more than 3 linear axis (XYZ) are finally implemented in Marlin?
g2core has 6 linear axis for example (XYZUVW).
There has been some works and discussions regarding Marlin:
[github.com] (see posts by tobbelobb and DerAndere1)
Though, I couldn't find any information if it's Marlin is capable of working with more than 3 linear axis out of the box (secondary Z-axis for example).
Can anyone help? :)
I did a lot of research but I couldn't find out if more than 3 linear axis (XYZ) are finally implemented in Marlin?
g2core has 6 linear axis for example (XYZUVW).
There has been some works and discussions regarding Marlin:
[github.com] (see posts by tobbelobb and DerAndere1)
Though, I couldn't find any information if it's Marlin is capable of working with more than 3 linear axis out of the box (secondary Z-axis for example).
Can anyone help? :)
↧
Damaged my motherboard and LCD on my T-Rex 3
Hi all,
I want to share my experience and at the same time ask for your thoughts.
I have a Vivedino/Formbot T-Rex 3. I have never updated any of my 3D printers before but it seemed simple enough, Or at least so I thought.
I looked at some videos on youtube and did some reading on the Marlin firmware page. I then downloaded arduino IDE, downloaded Marlin 2.0.0 and used the example files for my printer. I downloaded U8glib V1.17 and uploaded to the printer. Then the LCD was not showing the pixels correctly and it kind of flickered but I was still able to make out what it said. I tried reset to default but no change. When I tried to operate the printer it moved in the wrong directions and I guess most of the settings regarding that was wrong, the homing pushed the hotend down in the bed etc.
I contacted the Vivedino support asking for the default firmware files and uploaded them. During all this the LCD got even worse and I could not make out much of the display at all. I was also given another U8glib library, V1.19.1 that I used instead but the LCD still was all messed up but it worked properly.
I was then told that my LCD had broken due to my uploading and I bought a new one, that at first showed the graphic correct for the first 30 seconds or so and then gradually started to get worse. After about 2 hours printing (or just with the power on) it very hard to read what it says.
I was then told by the support that my motherboard needed to be replaced. So here I am today, I have ordered a new LCD and a motherboard and waiting for it to arrive.
I have tried to remove cables between LCD and motherboard, reset to default in menu and cut the power many many times in all the combinations I can think of.
I have learned my lesson and hopefully I can save someone else some money and time by discouraging if you don’t know exactly what you are doing.
I want to share my experience and at the same time ask for your thoughts.
I have a Vivedino/Formbot T-Rex 3. I have never updated any of my 3D printers before but it seemed simple enough, Or at least so I thought.
I looked at some videos on youtube and did some reading on the Marlin firmware page. I then downloaded arduino IDE, downloaded Marlin 2.0.0 and used the example files for my printer. I downloaded U8glib V1.17 and uploaded to the printer. Then the LCD was not showing the pixels correctly and it kind of flickered but I was still able to make out what it said. I tried reset to default but no change. When I tried to operate the printer it moved in the wrong directions and I guess most of the settings regarding that was wrong, the homing pushed the hotend down in the bed etc.
I contacted the Vivedino support asking for the default firmware files and uploaded them. During all this the LCD got even worse and I could not make out much of the display at all. I was also given another U8glib library, V1.19.1 that I used instead but the LCD still was all messed up but it worked properly.
I was then told that my LCD had broken due to my uploading and I bought a new one, that at first showed the graphic correct for the first 30 seconds or so and then gradually started to get worse. After about 2 hours printing (or just with the power on) it very hard to read what it says.
I was then told by the support that my motherboard needed to be replaced. So here I am today, I have ordered a new LCD and a motherboard and waiting for it to arrive.
I have tried to remove cables between LCD and motherboard, reset to default in menu and cut the power many many times in all the combinations I can think of.
I have learned my lesson and hopefully I can save someone else some money and time by discouraging if you don’t know exactly what you are doing.
↧
↧
Toolchange swap Tool-numbers
I have 4 Spoolholder fix in my printer and have 2 switching extruders (with a servo)
Spoolholder 1 goes to left Lever of first Extruder,
Spoolholder 2 goes to right Lever of second Extruder,
Spoolholder 3 goes to right Lever of first Extruder,
and Spoolholder 4 goes to right Lever of second Extruder.
Physically i can not change this because i have 2 Spoolholders in the back and 2 in the bottom of the Printer.
I'd like to change this in Firmware but how can i do that?
desired configuration is:
T0 = E0
T1 = E2
T2 = E3
T3 = E1
Any ideas?
My Printer uses an MKS SBASE 1.3 and the MKS-TFT32, no other displays.
I use a single Hotend and the Firmware is Marlin 2.0.
On TFT i can make custom buttons for change the extruder, thats not a big deal, but for Temp messages that goes to the screen i must have the value T without a number.
For Printing i only use the TFT.
Spoolholder 1 goes to left Lever of first Extruder,
Spoolholder 2 goes to right Lever of second Extruder,
Spoolholder 3 goes to right Lever of first Extruder,
and Spoolholder 4 goes to right Lever of second Extruder.
Physically i can not change this because i have 2 Spoolholders in the back and 2 in the bottom of the Printer.
I'd like to change this in Firmware but how can i do that?
desired configuration is:
T0 = E0
T1 = E2
T2 = E3
T3 = E1
Any ideas?
My Printer uses an MKS SBASE 1.3 and the MKS-TFT32, no other displays.
I use a single Hotend and the Firmware is Marlin 2.0.
On TFT i can make custom buttons for change the extruder, thats not a big deal, but for Temp messages that goes to the screen i must have the value T without a number.
For Printing i only use the TFT.
↧
Problem with LCD in Marlin 2/Marlin2.bugfix
Hi, When i enable #REPRAP_DISCOUNT_FULL_GRAPHIC_SMART_CONTROLLER in marlin 2, it cannot compile/upload and gives following error:
Uninstalling and reinstalling arduino IDE and all libraries didn't solve the problem.
Marlin 2 bugfix didn't solve the problem.
If i disable the LCD it uploads without any error.
configurations attached.
Arduino: 1.8.10 (Windows 10), Board: "Arduino Mega or Mega 2560, ATmega2560 (Mega 2560)" Multiple libraries were found for "SPI.h" Used: F:\Users\avazeh1\Documents\Arduino\libraries\SPI Multiple libraries were found for "SoftwareSerial.h" Used: F:\Users\avazeh1\Documents\Arduino\libraries\SoftwareSerial Multiple libraries were found for "U8glib.h" Used: F:\Users\avazeh1\Documents\Arduino\libraries\U8glib_Arduino-master Multiple libraries were found for "TMCStepper.h" Used: F:\Users\avazeh1\Documents\Arduino\libraries\TMCStepper fork/exec C:\Users\Safa\AppData\Local\Arduino15\packages\arduino\tools\avr-gcc\7.3.0-atmel3.6.1-arduino5/bin/avr-gcc.exe: The filename or extension is too long. Error compiling for board Arduino Mega or Mega 2560. This report would have more information with "Show verbose output during compilation" option enabled in File -> Preferences.
Uninstalling and reinstalling arduino IDE and all libraries didn't solve the problem.
Marlin 2 bugfix didn't solve the problem.
If i disable the LCD it uploads without any error.
configurations attached.
↧
Re: Problem with LCD in Marlin 2/Marlin2.bugfix
Yip...
This is a windows error
Marlin no longer compiles on windows if you enable to many features...
The paths just get to long and windows loses it shit...
EDIT (this doesn't help) Are you running a 32 bit version of windows10 if so try "11. Make changes to Group Policy" on this list [windowsreport.com]
also enable verbose compiling like it suggests
This is a windows error
Marlin no longer compiles on windows if you enable to many features...
The paths just get to long and windows loses it shit...
EDIT (this doesn't help) Are you running a 32 bit version of windows10 if so try "11. Make changes to Group Policy" on this list [windowsreport.com]
also enable verbose compiling like it suggests
↧