dtcreation / firmware-molise-artillery Goto Github PK

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

When I want to do a Z-align, I've an error : Unknown command : G34

Bug Timeline

No response

Expected behavior

No response

Actual behavior

No response

Steps to Reproduce

No response

Version of Marlin Firmware

Molise 2.3 (Marlin 2.0.9.1)

Printer model

Artillery Genius

Electronics

No response

Add-ons

No response

Your Slicer

Prusa Slicer

Host Software

SD Card (headless)

Additional information & file uploads

No response

J'ai vu que PrusaSlicer avait une option M73 pour les imprimantes Prusa. Elle n'a pas compatible avec Molise. Lorsqu'on l'active, un message d'erreur dit que la commande M73 ... n'est pas prise en charge ... blablabla 😄

https://marlinfw.org/docs/gcode/M073.html

Bonjour à tous,

Après de nombreux tests, j'arrive à la constatation suivante. En partant d'un "Visual Studio Code" installé récemment, en ayant réussi à installer le plugins nécessaire (très bien expliqué sur la vidéo !) et en essayant de compiler la version 1.3.0, j'y arrive sans problème (je ne suis pas programmeur, hein).

Si je refais cette étape, j'y arrive sans problème avec mon PC rebooté ou pas, depuis diffèrent noms de répertoires où j'ai les fichiers sources.

Maintenant si je prend la version 1.3.1, et dans exactement les mêmes conditions, il m'est totalement impossible de lancer la compilation.

Sur le bandeau du bas j'ai un "truc" qui tourne, continuellement, avec ce message "PlatformIO: Loading tasks..." et si je lance tout de même en appuyant sur le petit "V" (toujours dans le bandeau du bas) il apparaît sur la droite ... "command 'platformio-ide-build' not found"

Alors que j'ai réussi à compiler la version 1.3.0 quelques minutes juste avant.

Encore une fois je ne suis pas un programmeur, mais je pense avoir fait tous les tests systématiques avant de poster ce message.

Je reste à disposition ci-besoin ;-)

PS: je bricole pour l'instant, n'ayant pas encore reçu ma X1

Hey,

I do not know what to do. I installed Molise and a BL Touch, watched the explanatory video carefully. I used the hex "Hex Molise 1_3_0 Genius Stock + BLTouch". So I adjusted my probe offset (-2.86) and leveled the mesh. Then I save in EEPROM.

Except once I print the nozzle in the middle of the platen is not at the correct height at all. I have to play with the baby steps and put at least -3 mm so that it sticks. If I pause a few seconds after starting to print, I can clearly see that the nozzle is too high. Only the purge line seems okay.

Out of curiosity, I also tested the 5 leveling points, and the 5 are too high too. I don't understand what happens between when I do the Probe Offset / Mesh Leveling and when I print. I have done all the manipulations 10 times.

I have to put a particular gcode to apply this probe offset in my prints?

Thank you

Is your feature request related to a problem? Please describe.

No response

Are you looking for hardware support?

No response

Describe the feature you want

Artillery à publié les sources Marlin 2.0.9.1 avec le support de la X2.
Je pense qu'on peut merge la conf pour un support de la X2 par molise :)

https://github.com/artillery3d/sidewinder-x2-firmware

Additional context

No response

Hello David,

You said in the readme, that we can plug the runout sensor on the motherboard

• Removal of the runout filament sensor on the motherboard for compatibility with Octoprint and SD reader on the motherboard (Option)

Do you have the schematics for that ?

Best regards
Antoine

J'ai écris en anglais comme c'est de coutume sur Github ;-)

Is your feature request related to a problem? Please describe.

Est-il prévu une mise à jour à base de MARLIN 2.1.1 pour la Sidewinder X1 ?

Are you looking for hardware support?

SKR 1.4 TURBO

Describe the feature you want

Firmware MOLISE a base de MARLIN 2.1.1 pour une Sidewinder X1

Additional context

Merci

Is your feature request related to a problem? Please describe.

J'utilise la version 3.0.3 avec ma sidewinder X1

Are you looking for hardware support?

Sidewinder X1 avec SKR1.4 Bigtreetech

Describe the feature you want

Est-il prévu une mise à jour pour la Sidewinder X1 avec marlin 2.1 ?

Additional context

No response

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

Bonjour,

J'ai déjà fait part de mes mésaventures sur le forum lesimprimantes3D arrivées il y a quelques semaines environ.

Pour faire court, j'ai une genius, je suis en 2.4, après la MAJ, certaines impressions se bloquaient sans raison apparente. C'est-à-dire que la buse s'arrêtait en plein milieu d'une impression, le fil ne coulait plus, l'écran faisait toujours défiler les secondes. Je n'ai pas plus prêté attention que ça, je me suis dit que ça venait surement d'une erreur de slicage.

J'ai ensuite fait une grosse pause d'impression. Puis il y a quelques semaines, j'ai lancé une impression de nuit, jusqu'au moment où j'ai été réveillé par une odeur de brûlée et une fumée blanche. L'impression avait encore bugguée, sauf que ça a fait d'important dégâts. Pour moi la buse a chauffé à 400°, ça a complétement fait fondre la chaussette en silicone, et ça a attaqué le bloc de chauffe.

Depuis je n'ai pas ré-imprimé. Difficile de savoir d'où vient l'erreur, firmware, slicage ? Mais je me dit qu'il peut-être opportun d'en parler ici. On m'a dit que normalement Marlin est censé couper l'impression s'il y a des anomalies de ce genre (température excessive, etc), mais ça ne s'est pas produit. Je ne sais pas si je peux aider, en donnant des fichiers logs du firmware ou quelque chose d'autre ?

Bug Timeline

No response

Expected behavior

No response

Actual behavior

No response

Steps to Reproduce

No response

Version of Marlin Firmware

2.4

Printer model

No response

Electronics

No response

Add-ons

No response

Bed Leveling

No response

Your Slicer

Prusa Slicer

Host Software

SD Card (headless)

Additional information & file uploads

Je n'ai pas touché à grand chose lors de la compilation, hormis mettre les drivers 2209 / BLtouch : Configuration_adv.zip

Dear Dtcreation,
First of all, thanks for the work done on this firmware
I changed the motherboard on my genius and following that, unable to operate the original screen, I have the following message: no printer attached.
I have compiled the firmware several times by changing, for example, the numbers of SERIAL_PORT thinking that it came from there, but nothing to do.
I do not know if the problem comes from the firmware of the motherboard or that of the screen.
Using firmware from kind3r, everything works.
Would there be a solution to the problem?
Thank you in advance

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

Hello
I am new to Marlin software this is my first
Custom code I have tried I am using molisa marlin
V2.1.
Everything works perfect the printer boots up
Perfect and everything else perfect but with
The sd card inserted the printer keeps rebooting
I have looked up information for the last 2 weeks
And tried everything.
Deactivated sd support fail
Change the pin fail
Tried different versions of firmware and when
I do esteps it changes both extruder 1 and 2
Where on the molisa I can change them individually
I manufacture parts and need it to be spot on
Everytime.
Can anyone please assist also this is my first
Post and GITHUB feels confusing to me.
I can upload the whole code later when I have
Access to the pc.
I have formatted the sd card fat32 and used 3
Different ones and still the same problem.
I have no idea how to solve this problem.
Can anyone please assist.
I also found the code on GITHUB.
https://github.com/Dtcreation/Firmware-Molise-Wanhao/blob/master/README.md
Please see the attached code I used just changed
The specs to my printer

Bug Timeline

2 weeks ago

Expected behavior

To read the sd card and be able to print

Actual behavior

Infinite reboot with sd card inserted

Steps to Reproduce

Load new firmware onto SD card
Insert sd card
Booting up
Screen calibration
Then reboot again non stop
Remove sd card printer works perfectly

Version of Marlin Firmware

Molise 3

Printer model

Wanhao D12/230

Electronics

Stock machine

Add-ons

No response

Bed Leveling

No response

Your Slicer

No response

Host Software

SD Card (headless)

Additional information & file uploads

No response

Is your feature request related to a problem? Please describe.

No response

Are you looking for hardware support?

No response

Describe the feature you want

Mise en place d'une option pour passer de 25 points à 49 points pour l'ABL

Additional context

No response

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

When try to do homming or start auto bed leveling the extruder go to center of the plate and start to do homming but when touch the plate don't stop and try to go down.

Since I changed the board to MKS SGEN L 1.0 because the stock drivers, another bltouch and the board fused.

Video attached.

Bug Timeline

Detected when change broken MKSGENL TO MKS_SGENL

Expected behavior

Same functionality as broken MKSGENL

Actual behavior

Z (Extruder) don't stop when bltouch detect the plate when homming or when start ABL.

Steps to Reproduce

I tried enabling SENSHOME and disabled eith same results.
Settings all to false:

#define X_MIN_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop.
#define Y_MIN_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop.
#define Z_MIN_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop.
#define X_MAX_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop.
#define Y_MAX_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop.
#define Z_MAX_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop.
#define Z_MIN_PROBE_ENDSTOP_INVERTING false // Set to true to invert the logic of the probe.

With and without #define HYBRID_THRESHOLD

No works.

Version of Marlin Firmware

DT Creation Molise 3.0.3

Printer model

Artillery Genius V1

Electronics

MKS SGEN L 1.0 MKS TMC2209 UART BLTOUCH-Waggster the rest is stock

https://youtu.be/vSgcH2wjCwY
https://youtu.be/eF8Mqa2Y3oo

Add-ons

No response

Bed Leveling

ABL Bilinear mesh

Your Slicer

Cura

Host Software

No response

Additional information & file uploads

Marlin.zip

VIDEO: https://drive.google.com/file/d/1ikiUIOu7Amw6cRGQB8wAcVq5O6DNpKn5/view?usp=sharing

Un petit souci au niveau de la compilation ces lignes sont en jaune dans vs code
ca n'empêche pas la compilation du firmware

comparison between signed and unsigned integer expressions [-Wsign-compare]

{
"resource": "/d:/Deveveloper/Firmware-Molise/Firmware-Molise-Artillery-1.3.1/Marlin/src/module/probe.cpp",
"owner": "cpp",
"severity": 4,
"message": "comparison between signed and unsigned integer expressions [-Wsign-compare]",
"startLineNumber": 373,
"startColumn": 44,
"endLineNumber": 373,
"endColumn": 44
}

A small improvements suggestion:

• original firmware allows to change the LED while printing
• add 3 more colors by combining R+V, R+B, B+V
• M150 allows to fade blue, green but not red, configuration bug?

Based on Molise 1.3.0

Thanks for the huge work!

Is your feature request related to a problem? Please describe.

No response

Are you looking for hardware support?

No response

Describe the feature you want

Hello

I think you made a mistake on link you gives for this : https://www.thingiverse.com/thing:3972011

You put it 2 times on line 141 and 144 but the probe offset are different
NOZZLE_TO_PROBE_OFFSET { 28, -33, 0 } for 141
NOZZLE_TO_PROBE_OFFSET { 36, -38, 0 } for 144

Same fan duct but 2 different offset... :)

Kind regards

Additional context

No response

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

I can light on the led through the menu or it light on when i do a bed PID with GCode but it don't light and change colour while normal print or while normal operation

Bug Timeline

No response

Expected behavior

I expect the led light on and change colour while nozzle heat or while printing

Actual behavior

it don't light

Steps to Reproduce

just printing

Version of Marlin Firmware

last molise firmware (motherboard and TFT)

Printer model

Xwinder X1

Electronics

No response

Add-ons

No response

Bed Leveling

No response

Your Slicer

Cura

Host Software

No response

Additional information & file uploads

No response

Is your feature request related to a problem? Please describe.

No response

Are you looking for hardware support?

No response

Describe the feature you want

LEVELING_NOZZLE_TEMP 120 --> LEVELING_NOZZLE_TEMP 0

Additional context

No response

Is your feature request related to a problem? Please describe.

No response

Are you looking for hardware support?

No response

Describe the feature you want

Add Restore Leveling After G28 in Marlin

Additional context

No response

Bonjour,

Pendant les impressions via octoprint, le firmware envoie des messages d'erreur de type "Error:Line Number is not Last Line Number+1, Last Line: xxxx" accompagnés de beeps... le seule moyen que j'ai trouvé pour le moment est de déconnecter l'écran via le menu connexion pour arrêter l'affichage des messages :-/
j'avais bien fait un M502 puis M500 juste après l'installation du firmware 1.4.1
Il n'y a pas de problème lors de l'impression via la clé usb.
Please Help ^^

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

Hello, I flashed my printer (artillery SX1 v4) and my bltouch not working well now.

When i turn on my printer, BLTOUCH work as expected by releasing pin two times.

After screen loading, i have a popup regarding bltouch activation issue.
When i try to use BLTOUCH, nothing happen.

I tried Normal wiring (Guero Loco) and Waggster mod with two different BLTOUCHs

Bug Timeline

New

Expected behavior

BLTOUCH work for bed leveling / homing / print

Actual behavior

BLTOUCH not woring for bed leveling / homing / print

Steps to Reproduce

1. Download GIT folder

2. Compile Molise with following parameters:
   
   

3. Retrieve HEX file from .pio\build\mega2560

4. Open printer and disconnect screen

5. Flash printer using Prusa Slicer

6. Reconnect screen

Version of Marlin Firmware

Marlin 2.0.8

Printer model

Artillery Sidewinder X1 v4

Electronics

Stock

Add-ons

None

Bed Leveling

ABL Linear grid

Your Slicer

Cura

Host Software

No response

Additional information & file uploads

No response

Description

J'utilise PrusaSlicer pour mes impressions, leur logiciel permet de faire un M600. Seulement, après le changement de couleur, l'impression reprend, la buse se place à la dernière position connue et extrude du fil (un gros paté) avant de continuer son impression.

Je pensais que le soucis venait de PruaSlicer mais apparement non, le développeur me dit que ça vient du firmware : prusa3d/PrusaSlicer#6523

Steps to Reproduce

1. Ajouter un M600 dans l'impression
2. Changer la couleur
3. Attendre le résultat

Expected behavior: je ne sais pas trop, une sorte de purge à côté de l'impression.

Actual behavior: un gros dépôt de filament sur l'impression

Additional Information

N/A

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

Wrong Homing at the end of the bed and with wrong end stop.

bed
____x
LB RB
LT RT

x- wrong homming, trying to homming outside bed

Extruder beats with bed when homing.

#define MKSSGENLV1 // Choose this if you are using MKS SGEN L V1
#define TITAN // Stock Extruder
#define TMC_2209 // UART Mode
#define BLTOUCH //uncomment if you use a BLTouch
#define Z_STEPPER_AUTO_ALIGN //Uncomment if you want to use Z_STEPPER_AUTO_ALIGN, be carefull, you need to remove the belt from the Z axes for this
#define GraphicalLCD // Will work next to MKS TFT

Bug Timeline

Unknown

Expected behavior

Homming on center to start measure with bltouch

Actual behavior

No response

Steps to Reproduce

MKS SGEN L 1.0
MKS TMC2209

The rest is stock Machine

Version of Marlin Firmware

DT Creation Molise 2.3

Printer model

Artillery Genius

Electronics

MKS SGEN L 1.0 MKS TMC2209 BLTOUCH-Waggster the rest is stock

Add-ons

None

Bed Leveling

ABL Bilinear mesh

Your Slicer

Cura

Host Software

SD Card (headless)

Additional information & file uploads

No response

on dirait qu'il m’attribue 2 hotends et que du coup il n'y a plus de place pour le Z2. sauf que je vois qu'une hotends

#define TEMP_SENSOR_0 1

#define TEMP_SENSOR_1 0
#define TEMP_SENSOR_2 0
#define TEMP_SENSOR_3 0

In file included from c:\skr1-4\marlin\src\inc\marlinconfig.h:32,
                 from c:\skr1-4\marlin\src\core\serial.h:24,
                 from Marlin\src\HAL\LPC1768\DebugMonitor.cpp:25:
c:\skr1-4\marlin\src\pins\pins.h:1370:8: error: #error "No E stepper plug left for Z2!"
 1370 |       #error "No E stepper plug left for Z2!"
      |        ^~~~~
In file included from c:\skr1-4\marlin\src\inc\marlinconfig.h:41,
                 from c:\skr1-4\marlin\src\core\serial.h:24,
                 from Marlin\src\HAL\LPC1768\DebugMonitor.cpp:25:
c:\skr1-4\marlin\src\inc\SanityCheck.h:610:4: error: #error "If NUM_Z_STEPPER_DRIVERS is 2, you must define stepper pins for Z2."
  610 |   #error "If NUM_Z_STEPPER_DRIVERS is 2, you must define stepper pins for Z2."
      |    ^~~~~
c:\skr1-4\marlin\src\inc\SanityCheck.h:1673:6: error: #error "TEMP_SENSOR_1 is required with 2 or more HOTENDS."
 1673 |     #error "TEMP_SENSOR_1 is required with 2 or more HOTENDS."
      |      ^~~~~
In file included from c:\skr1-4\marlin\src\inc\marlinconfig.h:32,
                 from Marlin\src\HAL\LPC1768\HAL.cpp:24:
c:\skr1-4\marlin\src\pins\pins.h:1370:8: error: #error "No E stepper plug left for Z2!"
 1370 |       #error "No E stepper plug left for Z2!"
      |        ^~~~~
In file included from c:\skr1-4\marlin\src\inc\marlinconfig.h:41,
                 from Marlin\src\HAL\LPC1768\HAL.cpp:24:
c:\skr1-4\marlin\src\inc\SanityCheck.h:610:4: error: #error "If NUM_Z_STEPPER_DRIVERS is 2, you must define stepper pins for Z2."
  610 |   #error "If NUM_Z_STEPPER_DRIVERS is 2, you must define stepper pins for Z2."
      |    ^~~~~
c:\skr1-4\marlin\src\inc\SanityCheck.h:1673:6: error: #error "TEMP_SENSOR_1 is required with 2 or more HOTENDS."
 1673 |     #error "TEMP_SENSOR_1 is required with 2 or more HOTENDS."
      |      ^~~~~
In file included from c:\skr1-4\marlin\src\inc\marlinconfig.h:32,
                 from Marlin\src\HAL\LPC1768\HAL_SPI.cpp:51:
c:\skr1-4\marlin\src\pins\pins.h:1370:8: error: #error "No E stepper plug left for Z2!"
 1370 |       #error "No E stepper plug left for Z2!"
      |        ^~~~~
In file included from c:\skr1-4\marlin\src\inc\marlinconfig.h:32,
                 from Marlin\src\HAL\LPC1768\eeprom_wired.cpp:24:
c:\skr1-4\marlin\src\pins\pins.h:1370:8: error: #error "No E stepper plug left for Z2!"
 1370 |       #error "No E stepper plug left for Z2!"
      |        ^~~~~
In file included from c:\skr1-4\marlin\src\inc\marlinconfig.h:32,
                 from Marlin\src\HAL\LPC1768\eeprom_sdcard.cpp:25:
c:\skr1-4\marlin\src\pins\pins.h:1370:8: error: #error "No E stepper plug left for Z2!"
 1370 |       #error "No E stepper plug left for Z2!"
      |        ^~~~~
In file included from c:\skr1-4\marlin\src\inc\marlinconfig.h:32,
                 from Marlin\src\HAL\LPC1768\eeprom_flash.cpp:39:
c:\skr1-4\marlin\src\pins\pins.h:1370:8: error: #error "No E stepper plug left for Z2!"
 1370 |       #error "No E stepper plug left for Z2!"
      |        ^~~~~
In file included from c:\skr1-4\marlin\src\inc\marlinconfig.h:41,
                 from Marlin\src\HAL\LPC1768\HAL_SPI.cpp:51:
c:\skr1-4\marlin\src\inc\SanityCheck.h:610:4: error: #error "If NUM_Z_STEPPER_DRIVERS is 2, you must define stepper pins for Z2."
  610 |   #error "If NUM_Z_STEPPER_DRIVERS is 2, you must define stepper pins for Z2."
      |    ^~~~~
In file included from c:\skr1-4\marlin\src\inc\marlinconfig.h:41,
                 from Marlin\src\HAL\LPC1768\eeprom_wired.cpp:24:
c:\skr1-4\marlin\src\inc\SanityCheck.h:610:4: error: #error "If NUM_Z_STEPPER_DRIVERS is 2, you must define stepper pins for Z2."
  610 |   #error "If NUM_Z_STEPPER_DRIVERS is 2, you must define stepper pins for Z2."
      |    ^~~~~
c:\skr1-4\marlin\src\inc\SanityCheck.h:1673:6: error: #error "TEMP_SENSOR_1 is required with 2 or more HOTENDS."
 1673 |     #error "TEMP_SENSOR_1 is required with 2 or more HOTENDS."
      |      ^~~~~
In file included from c:\skr1-4\marlin\src\inc\marlinconfig.h:32,
                 from c:\skr1-4\marlin\src\sd\cardreader.h:24,
                 from Marlin\src\HAL\LPC1768\main.cpp:38:
c:\skr1-4\marlin\src\pins\pins.h:1370:8: error: #error "No E stepper plug left for Z2!"
 1370 |       #error "No E stepper plug left for Z2!"
      |        ^~~~~
c:\skr1-4\marlin\src\inc\SanityCheck.h:1673:6: error: #error "TEMP_SENSOR_1 is required with 2 or more HOTENDS."
 1673 |     #error "TEMP_SENSOR_1 is required with 2 or more HOTENDS."
      |      ^~~~~
In file included from c:\skr1-4\marlin\src\inc\marlinconfig.h:41,
                 from Marlin\src\HAL\LPC1768\eeprom_sdcard.cpp:25:
c:\skr1-4\marlin\src\inc\SanityCheck.h:610:4: error: #error "If NUM_Z_STEPPER_DRIVERS is 2, you must define stepper pins for Z2."
  610 |   #error "If NUM_Z_STEPPER_DRIVERS is 2, you must define stepper pins for Z2."
      |    ^~~~~
c:\skr1-4\marlin\src\inc\SanityCheck.h:1673:6: error: #error "TEMP_SENSOR_1 is required with 2 or more HOTENDS."
 1673 |     #error "TEMP_SENSOR_1 is required with 2 or more HOTENDS."
      |      ^~~~~
In file included from c:\skr1-4\marlin\src\inc\marlinconfig.h:41,
                 from Marlin\src\HAL\LPC1768\eeprom_flash.cpp:39:
c:\skr1-4\marlin\src\inc\SanityCheck.h:610:4: error: #error "If NUM_Z_STEPPER_DRIVERS is 2, you must define stepper pins for Z2."
  610 |   #error "If NUM_Z_STEPPER_DRIVERS is 2, you must define stepper pins for Z2."
      |    ^~~~~
c:\skr1-4\marlin\src\inc\SanityCheck.h:1673:6: error: #error "TEMP_SENSOR_1 is required with 2 or more HOTENDS."
 1673 |     #error "TEMP_SENSOR_1 is required with 2 or more HOTENDS."
      |      ^~~~~
In file included from c:\skr1-4\marlin\src\inc\marlinconfig.h:41,
                 from c:\skr1-4\marlin\src\sd\cardreader.h:24,
                 from Marlin\src\HAL\LPC1768\main.cpp:38:
c:\skr1-4\marlin\src\inc\SanityCheck.h:610:4: error: #error "If NUM_Z_STEPPER_DRIVERS is 2, you must define stepper pins for Z2."
  610 |   #error "If NUM_Z_STEPPER_DRIVERS is 2, you must define stepper pins for Z2."
      |    ^~~~~
In file included from c:\skr1-4\marlin\src\inc\marlinconfig.h:32,
                 from Marlin\src\HAL\LPC1768\tft\tft_spi.cpp:23:
c:\skr1-4\marlin\src\pins\pins.h:1370:8: error: #error "No E stepper plug left for Z2!"
 1370 |       #error "No E stepper plug left for Z2!"
      |        ^~~~~
c:\skr1-4\marlin\src\inc\SanityCheck.h:1673:6: error: #error "TEMP_SENSOR_1 is required with 2 or more HOTENDS."
 1673 |     #error "TEMP_SENSOR_1 is required with 2 or more HOTENDS."
      |      ^~~~~
In file included from c:\skr1-4\marlin\src\inc\marlinconfig.h:41,
                 from Marlin\src\HAL\LPC1768\tft\tft_spi.cpp:23:
c:\skr1-4\marlin\src\inc\SanityCheck.h:610:4: error: #error "If NUM_Z_STEPPER_DRIVERS is 2, you must define stepper pins for Z2."
  610 |   #error "If NUM_Z_STEPPER_DRIVERS is 2, you must define stepper pins for Z2."
      |    ^~~~~
c:\skr1-4\marlin\src\inc\SanityCheck.h:1673:6: error: #error "TEMP_SENSOR_1 is required with 2 or more HOTENDS."
 1673 |     #error "TEMP_SENSOR_1 is required with 2 or more HOTENDS."
      |      ^~~~~
*** [.pio\build\LPC1769\src\src\HAL\LPC1768\DebugMonitor.cpp.o] Error 1
*** [.pio\build\LPC1769\src\src\HAL\LPC1768\HAL.cpp.o] Error 1
*** [.pio\build\LPC1769\src\src\HAL\LPC1768\eeprom_sdcard.cpp.o] Error 1
*** [.pio\build\LPC1769\src\src\HAL\LPC1768\HAL_SPI.cpp.o] Error 1
*** [.pio\build\LPC1769\src\src\HAL\LPC1768\eeprom_wired.cpp.o] Error 1
*** [.pio\build\LPC1769\src\src\HAL\LPC1768\tft\tft_spi.cpp.o] Error 1
*** [.pio\build\LPC1769\src\src\HAL\LPC1768\main.cpp.o] Error 1
*** [.pio\build\LPC1769\src\src\HAL\LPC1768\eeprom_flash.cpp.o] Error 1
=========================================================================== [FAILED] Took 5.30 seconds ===========================================================================

Environment    Status    Duration
-------------  --------  ------------
LPC1769        FAILED    00:00:05.300

Can you take a look of the config from the MKS SGEN L v2 for the next build? Some changes are necessary : E0_AUTO_FAN_PIN -> FAN2_PIN, Filamentsensor on X+ -> FIL_RUNOUT_PIN P1_28 (2 is for AUX1), if no waggster-mod for RGB-LED with the extra pins P1_19 - P1_21 of this board enable only RGB_LED (pins are defined in PINS) so you can put the white connector with the brown cables direct. (wrong order of the cables, have to change the config in PINS or change two cables). Also with molise i dont
see the onboard-SD form PC over USB (for send firmware to the bord) with stock marlin-bugfix i see it.

The printing speed seems to be higher than expected.

Prevision from Prusaslicer: 30h

Filament was not melted enough, so I increased the temperature and slow down the printing speed to 90% most of the time and 80% on some parts, some slower tests. Total print time: 28h45'. According to the reduced print speed and initial prevision, I expected at least 35h of print time.

28h45' is the printed value, it is correct according to the wall clock.

Is Prusaslicer so pessimistic?

Hello,

What firmware do I need to auto Bed Leveling with Stock Sensor?

Thank you!

Bonjour/Bonsoir David,

Juste pour signaler que dans la version 1.4.0 (fichier avec les sources) l'option "#define MKSGENL_TFT" est présente avec les deux "//", donc "//#define MKSGENL_TFT", étant donné que je ne sais pas si dans les fichier précompilés "xxxx.hex" cette option est bien activée et comme j'ai modifié le câblage de mon écran, je me suis compilé ma version pour mon prochain flashage.

Ma question y-a-t 'il une raison pour avoir laissé les "//" dans les sources pour cette option ?

Merci,
Stéphane

Do you know that the #ifdef MKSSGENLV2 value isnt set right, in configuration.h?

Is your feature request related to a problem? Please describe.

No response

Are you looking for hardware support?

BTT SKR 2.0

Describe the feature you want

Add the board to configuration.h

Additional context

Hello!
I recently fried my TMC2100 drivers by "accidentally" disconnecting the case fan. So I decided to upgrade the whole board with a SKR 2.0 plus a full TMC2209 set, just to discover that there is little support for this board on the Sidewinder X1.
I have already made some modifications to your firmware configuration but before starting a new fork I would like to know if you are interested in integrating the board.

I also run the printer with an inductive probe PLUS the z_min endstop as a failsafe. The probe is the same z_min sensor type, I just got a replacement part and wired to the LED.

Is your feature request related to a problem? Please describe.

No response

Are you looking for hardware support?

No response

Describe the feature you want

Bonjour,
J’ai besoin d’une aide car je désire utiliser la configuration avec BL Touch sur Artillery X1, https://www.thingiverse.com/thing:4033595
De ce fait pour le MOLISE j’aurais besoin du « NOZZLE_TO_PROBE_OFFSET » de ce dernier.
Merci de ton aide.

Additional context

No response

Hello,

I would use neopixel with the skr 1.4T motherboard.
Could you add an option to enable neopixel instead of stock led ? (I'm using bltouch directly connect directly on the motherboard. So the stock led connector is still available.

Heating the bed before every homing is sometimes not practical at all.
Anoyances:

• delay
• hot surface

Could be better if the bed temperature could be selected (some preset values and adjustments buttons) at each homing order instead of automatic heating to 50°C.

Probe leveling for example has no interest into bed heating, extruder heating is more appropriate.

Thanks!

Dear All,
There is a problem with the 317 line and the MKS SGEN L V2.0 cards.
End of line creates errors when compile : 1151 // MKS GEN L V2
Not knowing what it's for, I deleted it.

Is your feature request related to a problem? Please describe.

No response

Are you looking for hardware support?

No response

Describe the feature you want

Actuellement, lorsqu'on fait un M600, la buse va se loger en haut à gauche du plateau, et purge du filament. Je ne trouve pas que c'est super pratique pour en faire beaucoup. Effectivement, ca coule dans l'angle du plateau, pour nettoyer on a le plateau qui nous gène, et surtout lorsqu'on fait un M600 en mode tableau (style 1/2 mm de haut) , le filament se purge, mais la buse est tellement basse que parfois le filament s'agglomère dans la buse, on doit nettoyer la buse avant de lancer le print.
Du coup je pense, après plusieurs essais que le mieux serait de mettre la plateau en arrière, d'envoyer la buse en 0 0, et de relever l'axe Z de au moins 10/20mm minimum. purger et reprendre. Ainsi on n'aurait je pense moins de soucis pour la reprise du M600, moins de ménage a faire et on mettrait moins nos gros doigts gras sur le plateau :P
Qu'en penses tu @Dtcreation ?

Additional context

No response

Bug Description

Bonjour,

Il semble qu'une régression a été introduite dans la dernière release (3.0.3) du firmware pour TouchMi sur la Sidewinder X1. Lorsque je flash ce firmware, plus aucun des axes de l'imprimante ne fonctionne, que ce soit piloté via octoprint ou via le TFT. Si je downgrade sur la 3.0.1 (la 3.0.2 n'étant que pour le BLTouch), tout fonctionne correctement et je peux de nouveau piloter mes axes.

Bug Timeline

3.0.3

Expected behavior

Les axes devraient bouger.

Actual behavior

Les axes ne bougent pas.

Steps to Reproduce

1. Flasher le firmware 3.0.3 Stock+TouchMi pour la X1
2. Essayer de bouger n'importe quel axe depuis le TFT => Rien ne se passe
3. Essayer de bouger n'importe quel axe avec Octoprint => Rien ne se passe

Version of Marlin Firmware

2.0.9.3

Printer model

Sidewinder X1

Electronics

No response

Add-ons

TouchMi

Bed Leveling

No response

Your Slicer

No response

Host Software

No response

Additional information & file uploads

Pour l'anecdote, je viens d'installer le TouchMi et j'ai bien cru que j'avais raté mes câblages, mais non il semble bien que c'est le firmware 😅 …

Par contre, plus étonnant, j'ai aussi recablé le TFT sur EXP1 tel qu'indiqué dans la section Installation et configuration et pourtant je suis toujours obligé de débrancher le TFT pour pouvoir flasher 🤷‍♂️ . À noter que l'option de "Déconnecter" le TFT depuis l'interface ne fonctionne pas non plus et n'a jamais fonctionné sur ma X1 pour flasher un nouveau firmware. Le TFT affiche bien "Déconnecté", mais je ne peux pas flasher quoi que ce soit pour autant.

Un grand merci pour ce superbe backport pour la Sidewinder X1.

Hi,

It would be really cool if you could add the support for the MeatPack compression for Octoprint (https://github.com/scottmudge/OctoPrint-MeatPack#firmware-with-meatpack-support)

Seems like the nightly builds of Marlin has it already so if luck is on our side it would be easy to do

Estimated filament length from Prusaslicer: 303.59m
Displayed at printing end: 98.43m

The displayed value is clearly wrong.
As the extruder is calibrated in mm, this should not happen.

If it is computed from mm3 back to filament length and configuration uses 3mm instead of 1.75mm as filament diameter, then it can be close to explain the value. This is just a guess...

Note: observed on X1.

Is your feature request related to a problem? Please describe.

J’ai cherché un peu partout dans les réglages de l’écran mais je n’ai pas trouvé quelle version de Molise j’ai. Oui c’est un peu bête mais je ne sais plus si j’ai la dernière version et si je dois l’être a jour le firmware :D

Are you looking for hardware support?

No

Describe the feature you want

A moins que j’ai mal vu, je n’ai que cet écran :

En le basant sur la version de Marlin, je pense avoir la version 2.1, mais il serait judicieux d’ajouter la version de Molise sur cet écran ?

Additional context

No response

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

Wrong Homing at the end of the bed and with wrong end stop.

bed
____x
LB RB
LT RT

x- wrong homming, trying to homming outside bed

Extruder beats with bed when homing.

#define MKSSGENLV1 // Choose this if you are using MKS SGEN L V1
#define TITAN // Stock Extruder
#define TMC_2209 // UART Mode
#define BLTOUCH //uncomment if you use a BLTouch
#define Z_STEPPER_AUTO_ALIGN //Uncomment if you want to use Z_STEPPER_AUTO_ALIGN, be carefull, you need to remove the belt from the Z axes for this
#define GraphicalLCD // Will work next to MKS TFT

Bug Timeline

Detected on Release 2.3

Expected behavior

Homming on center to start measure with bltouch

Actual behavior

When press Home, Artillery Genius goes to x0, y0, then on the middle of the bed, extract the bltouch and start down, when arrive to the bedm, bl touch detect the bed, go up again and start to download and doesn't stop.

Steps to Reproduce

MKS SGEN L 1.0
MKS TMC2209
DT 2.4

Press Home button.

Version of Marlin Firmware

DT Creation Molise 2.4

Printer model

Artillery Genius

Electronics

MKS SGEN L 1.0 MKS TMC2209 BLTOUCH-Waggster the rest is stock

Add-ons

None

Bed Leveling

ABL Bilinear mesh

Your Slicer

Cura

Host Software

SD Card (headless)

Additional information & file uploads

No response

Hello,

Is it possible to add an option for the BTT Smart Sensor (on the mainboad to use with octoprint) ?
Doc of the bidule : https://github.com/bigtreetech/smart-filament-detection-module/tree/master/manual

Thanks for the great work.

Is your feature request related to a problem? Please describe.

No response

Are you looking for hardware support?

No response

Describe the feature you want

Ajouter option

• Remplacement des fonctions "Junction Deviation" & "S-Curve" par le "Classic Jerk" (les Jonction Déviation et S-Curve sont encore capricieuse sous Marlin pour le moment).

Additional context

No response

Is your feature request related to a problem? Please describe.

No response

Are you looking for hardware support?

RELAY MODULE V1.0

Describe the feature you want

Hi, I have the Bigtreetech RELAY MODULE V1.0 and this is the PSU control in configuration.h

#if ENABLED(PSU_CONTROL)
//#define MKS_PWC // Using the MKS PWC add-on
//#define PS_OFF_CONFIRM // Confirm dialog when power off
//#define PS_OFF_SOUND // Beep 1s when power off
#define PSU_ACTIVE_STATE HIGH // Set 'LOW' for ATX, 'HIGH' for X-Box

I have to define the MKS_PWC? Something else is mising? The PSU_Active_Satate is ok in High?

Additional context

No response

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

Hey,

I tried to update my Molise firmware today with 3.0.3 version. My setup:

• Genius with stock board
• TMC 2209
• BLTouch

When I compile I habe 2 errors:

Marlin\src\inc\Warnings.cpp:179:4: warning: #warning "Auto-assigned Z2 STEP/DIR/ENABLE_PINs to unused En_STEP/DIR/ENABLE_PINs." [-Wcpp]
   #warning "Auto-assigned Z2 STEP/DIR/ENABLE_PINs to unused En_STEP/DIR/ENABLE_PINs."
    ^~~~~~~
Marlin\src\inc\Warnings.cpp:554:4: warning: #warning "Disabled CONFIGURATION_EMBEDDING because the target usually has less flash storage. Define FORCE_CONFIG_EMBED to override." [-Wcpp]
   #warning "Disabled CONFIGURATION_EMBEDDING because the target usually has less flash storage. Define FORCE_CONFIG_EMBED to override."
    ^~~~~~~

When I'm trying to do an bed leveling, probe goes in / out 2 times, flash red and I have an error:
STOP called because of BLTouch error - restart with M999

My marlin configuration:

/*** Section 1 Artillery Printer ***/

#define GENIUS
//#define X1
//#define GENIUSPRO
//#define SWD_X2
//#define HORNET

/*** Section 2 Board Type ***/

#define MKSGENL         // Stock Board for Genuis and X1
//#define RUBY            // Stock Board for Genuis Pro, X2 and Hornet
//#define MKSGENLV21      // Choose this if you are using MKS GEN L V2.1
//#define SKR13           // Choose this if you are using BigTreeTech SKR 1.3
//#define SKR14           // Choose this if you are using BigTreeTech SKR 1.4
//#define SKR14T          // Choose this if you are using BigTreeTech SKR 1.4 Turbo
//#define MKSSGENLV1      // Choose this if you are using MKS SGEN L V1
//#define MKSSGENLV2      // Choose this if you are using MKS SGEN L V2
//#define MKSROBINNANOV3  // Choose this if you are using MKS ROBIN NANO V3


/*default_envs in Platformio.ini :
-Board name: MKS GEN L, change_value = mega2560 //use this value in platform.ini. Search for 'change_value' and replace it with this value mega2560
-Board name: RUBY, change_value = Artillery_Ruby //use this value in platform.ini. Search for 'change_value' and replace it with this value Artillery_Ruby
-Board name: MKS GEN L V2.1, change_value = mega2560 //use this value in platform.ini. Search for 'change_value' and replace it with this value mega2560
-Board name: SKR13, change_value = LPC1768 //use this value in platform.ini. Search for 'change_value' and replace it with this value LPC1768
-Board name: SKR14, change_value = LPC1768 //use this value in platform.ini. Search for 'change_value' and replace it with this value LPC1768
-Board name: SKRV14TURBO, change_value = LPC1769 //use this value in platform.ini. Search for 'change_value' and replace it with this value LPC1769
-Board name: MKSSGENLV1, change_value = LPC1768 //use this value in platform.ini. Search for 'change_value' and replace it with this value LPC1768
-Board name: MKSSGENLV2, change_value = LPC1769 //use this value in platform.ini. Search for 'change_value' and replace it with this value LPC1769
-Board name: MKSROBINNANOV3, change_value = mks_robin_nano_v3_usb_flash_drive_msc //use this value in platform.ini. Search for 'change_value' and replace it with this value mks_robin_nano_v3_usb_flash_drive_msc
*/

/*** Section 3 Extruder Type ***/

#define TITAN       // Stock Extruder
//#define BMG         // Choose this if you are using BMG/BMG Wind
//#define HEMERA      // Choose this if you are using HEMERA
//#define MATRIX      // Choose this if you are using MATRIX

/*** Section 4 Drivers Type ***/

//#define TMC_2100        // Stock Drivers
//#define TMC_2208_STA    // Standalone Mode
#define TMC_2209_STA    // Standalone Mode
//#define LV_8729
//#define TMC_2208        // UART Mode
//#define TMC_2209        // UART Mode

/*** Section 5 Bed Leveling ***/

#define BLTOUCH      //uncomment if you use a BLTouch
  #ifdef BLTOUCH
    #ifdef RUBY
    //#define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN
      #else
      #define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN
    #endif
    #define Z_MIN_PROBE_REPEATABILITY_TEST
  #define NOZZLE_TO_PROBE_OFFSET { 28, -33, 0 }         //Offset preset for this fanduct : Sidewinder X1 Waggster Mod BLTouch with improved Fan Duct  by 3dprintbeginnercom on Thingiverse: https://www.thingiverse.com/thing:3972011
  //#define NOZZLE_TO_PROBE_OFFSET { 27.25, -12.8, -2 }   //Offset preset for stock X2 and Genius Pro
  //#define NOZZLE_TO_PROBE_OFFSET { -17, -42, 0 }        //Offset preset for this fanduct with 5015 Fan on Thingiverse : https://www.thingiverse.com/thing:4741530
  //#define NOZZLE_TO_PROBE_OFFSET { 56, -34, 0 }         //Offset preset for this fanduct with 5015 Fan on Thingiverse : https://www.thingiverse.com/thing:4548854
  //#define NOZZLE_TO_PROBE_OFFSET { 36, -38, 0 }         //Offset preset for BMG Wind for this fanduct : Sidewinder X1 Waggster Mod BLTouch with improved Fan Duct  by 3dprintbeginnercom on Thingiverse: https://www.thingiverse.com/thing:3972011
  //#define WAGGSTER_MOD_WIRING                       //Comment if you don't use Waggster mode on Sidewinder (Guero Loco method by exemple) Mod needed for Genius standard wiring
  #define Z_STEPPER_AUTO_ALIGN                    //Uncomment if you want to use Z_STEPPER_AUTO_ALIGN, be carefull, you need to remove the belt from the Z axes for this - NOT FOR ARTILLERY RUBY
  //#define DISABLE_LED                             // Uncomment to disable LED, some users report compatibilty issues with BL Touch and LED enabled
  #endif

//#define ZMIN_SENSOR_AS_PROBE                      //uncomment to use Z min as Probe for bed leveling (incompatible with BLTouch)
  #ifdef ZMIN_SENSOR_AS_PROBE
    #define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN
    #define Z_MIN_PROBE_REPEATABILITY_TEST
    #define NOZZLE_TO_PROBE_OFFSET { 28, -33, 0 }   
  #endif

//#define TOUCH_MI_PROBE                            //uncomment if you use a Touch Mi
  #ifdef TOUCH_MI_PROBE
    #define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN
    #define Z_MIN_PROBE_REPEATABILITY_TEST
    #define NOZZLE_TO_PROBE_OFFSET { -43, -32, 0 }  //Offset preset for this fanduct : https://www.thingiverse.com/thing:4713319
    #define TOUCH_MI_RETRACT_Z 0.5                  // Height at which the probe retracts
    //#define TOUCH_MI_DEPLOY_XPOS (X_MAX_BED + 2)  // For a magnet on the right side of the bed
    //#define TOUCH_MI_MANUAL_DEPLOY                // For manual deploy (LCD menu)
    //#define Z_STEPPER_AUTO_ALIGN                    //Uncomment if you want to use Z_STEPPER_AUTO_ALIGN, be carefull, you need to remove the belt from the Z axes for this - NOT FOR ARTILLERY RUBY
    //#define TOUCH_MI_LED                          // Uncomment if you have the additional LED from Hotends.fr for the X1
    #define TOUCH_MI_NEOPIXEL                      // Uncomment if you have the additional Neopixel LED from Hotends.fr
#endif

//#define MESH_BED_LEVELING                         //uncomment if you want to use Mesh Bed Leveling

/*** Section 6 Options ***/

//#define GraphicalLCD                              // Will work next to MKS TFT
//#define MKSGENL_TFT                               // To be activated if you have deported the TFT connection to EXP1 on the MKS Gen L ==> communication speed : 250000
//#define FILAMENT_RUNOUT_SENSOR                    // If you connect your filament runout sensor to the motherboard instead of the TFT
//#define NEOPIXEL_PERSO                            // If you want to use a personal Neopixel LED on the Neopixel Port
//#define LED_PORT_NEOPIXEL                         // If you want to use a personal Neopixel LED on the original LED Port
//#define LINEAR_ADV                                // If you want to use Linear Advance

/*** Section 7 Sensorless Homing XY ***/

//#define SENSHOME                                  // Active sensorless homing ONLY for TMC 2208 UART and 2009 UART with SKR 1.3 (extra wiring needed) and SKR 1.4 (no extra wiring needed)

Any idea why it fails ? I never had this problem before.

UPDATE : probe goes in / out without problem, but if flashes red.

Hello,

It is just a suggestion about section 3 of the configuration file.
In my case I plan to use a Matrix extruder but with the stock volcano block heat cartridge and thermistor.
Not a big deal to modify what I need but I suppose I am not the only one in this configuration. So, it would be nice to have section 3 and maybe 3 bis to differentiate extruder and hotend setups.

I spent a full day to make the bl touch working with pre-compiled firmware handling the bl touch. I was ready to give up, convinced that my bl touch was defective, when I found the problem: in the pre-compiled firmware, the bl-touch is configured to be plugged on Z+ and I plug it in Z- as Guero Loco.

This point is not detailed in all the documents I read.

If the configuration file is available within the zip file containing the pre-compiled firmware, at least everyone can check the settings made.

Thanks

Is your feature request related to a problem? Please describe.

NO it is a friendly request

Are you looking for hardware support?

Sidewinder x1
SKR board

Describe the feature you want

I know that it is an hard job the coding, I'm mechanical old guys with very very few knowledge in electronic.
It could be a good feature to add the functionality of BIGTREETECH Relay V1.2 and BTT UPS 24V V1.0 on our Molise, means the part of the code to activate it.

It is only a request not a bug

Additional context

No response

Hello

I checked a lot of firmware based on marlin for sidewinder X1 (and the most popular ones, including Waggster etc.), and all of them have this feature activate :
#define ENDSTOP_NOISE_THRESHOLD 2

It's not activated in Molise, and it's clearly impacting X/Y homing with random issues (not common but it happens)

I would suggest to activate it by default in molise.

Matt

Is your feature request related to a problem? Please describe.

No response

Are you looking for hardware support?

No response

Describe the feature you want

• Implement M486 to allow Marlin to skip objects

Additional context

No response

Hello,
I'm in love with such firmware, i use it starting from first version on my X1 stock, what i noticed is that i flash the last version 1.4 MBL stock and when i need to create my first mesh he started from 15 mm each point, this is not suitable because you have to decresa manually each point till arrive to 0 and start to use the babystep, in my opinion 0,35 mm as starting point is more than enough. Thanks in advance to take in care it