Yes!! The problem is solved! THANK YOU SO MUCH for sorting it out!
↧
Re: Endstop issue
↧
Re: Endstop issue
yes when I posted this I also remembered that in the first post you mentioned port 25...
reading threw annother board.h i see the same issue mentioned
/**
* In some versions of the Sanguino libraries the pin
* definitions are wrong, with SDSS = 24 and LED_PIN = 28 (Melzi).
* If you encounter issues with these pins, upgrade your
* Sanguino libraries! See #368.
*/
#368 is [github.com]
so somewhere along the line those 8 ports have been switched around
so what Sanguino libraries are you running and how did you install them? and what arduino ide?
reading threw annother board.h i see the same issue mentioned
/**
* In some versions of the Sanguino libraries the pin
* definitions are wrong, with SDSS = 24 and LED_PIN = 28 (Melzi).
* If you encounter issues with these pins, upgrade your
* Sanguino libraries! See #368.
*/
#368 is [github.com]
so somewhere along the line those 8 ports have been switched around
so what Sanguino libraries are you running and how did you install them? and what arduino ide?
↧
↧
Re: Endstop issue
So my library is this. I checked on the tools section of the Arduino IDE and you can select which pinout to use. I got the standard pinout instead of the Sanguino that I think is used in Marlin Firmware. Arduino IDE version is 1.8.7.
↧
Help With BLTouch clone Not Responding to gcode Commands?
I tried installing a 3DTouch (BLTouch clone) on my Tevo Tarantula with an MKS-Base v1.4 controller running Marlin 1.1.8. When powered up, the sensor cycles the pin in self-test successfully and the blue LED remains on steady. When I execute the gcode commands [M80 P0 Sxxx], however, nothing happens. The two pin connector is plugged into the Z-Min Endstop connector (just like the capacitive sensor I am attempting to replace) and the three wire connected is plugged into (what my diagram shows are) the servo pins D11-GND-5v with the power and ground wires swapped on the sensor connector so that they align properly with the supply voltage pins on the board. I am attaching the Configuration.h file so you can see the changes I made to that, but I followed the instructions given for the BLTouch.
Unsure whether the issue was the sensor, the firmware or the mainboard, I had someone write up a small arduino code that sent random servo commands to the 3DTouch. With the sensor hooked to an arduino, running that code, the pin cycled in and out, so I have to assume that the sensor is OK and that the issue is either my board or the firmware.
Any help here would be greatly appreciated!
Unsure whether the issue was the sensor, the firmware or the mainboard, I had someone write up a small arduino code that sent random servo commands to the 3DTouch. With the sensor hooked to an arduino, running that code, the pin cycled in and out, so I have to assume that the sensor is OK and that the issue is either my board or the firmware.
Any help here would be greatly appreciated!
↧
Re: Help With BLTouch clone Not Responding to gcode Commands?
I too was looking into the 3D-Touch and researched and found this link.
The complete BLTouch | 3DTouch guide for Creality printers CR-10s Ender 2 - Ender 3 for Auto Bed Leveling UPDATED
Hope it helps you.
The complete BLTouch | 3DTouch guide for Creality printers CR-10s Ender 2 - Ender 3 for Auto Bed Leveling UPDATED
Hope it helps you.
↧
↧
Filament runout echo:unknown command: M412
I have set in configuration.h
#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 FILAMENT_RUNOUT_SCRIPT "M600"
#endif
and in pins_rumba.h
// Runout sensors
#define FIL_RUNOUT_PIN 14
#define FIL_RUNOUT2_PIN 15
I am getting echo:unknown command: M412
Any ideas?
#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 FILAMENT_RUNOUT_SCRIPT "M600"
#endif
and in pins_rumba.h
// Runout sensors
#define FIL_RUNOUT_PIN 14
#define FIL_RUNOUT2_PIN 15
I am getting echo:unknown command: M412
Any ideas?
↧
Re: Filament runout echo:unknown command: M412
I believe that this Command is only valid in Marlin 2 as shown in the attached photo. ("</>2.0.0") in green
It allows you to enable or disable the Filament run-out sensor and continue printing without a filament run-out sensor.
M412 works perfect in My Marlin 2.0.x BugFix which has been installed in both my 3D Printers.
[attachment 110114 2.0.x.jpg]
It allows you to enable or disable the Filament run-out sensor and continue printing without a filament run-out sensor.
M412 works perfect in My Marlin 2.0.x BugFix which has been installed in both my 3D Printers.
[attachment 110114 2.0.x.jpg]
↧
Is there a Temp Offset parameter buried someplace in Bugfix 2.0?
My Thermistors report one Temp but regular and IR Thermometers report another. It's pretty common with most Temp Controllers to be able to calibrate/fine tune your Temp sensor with a +/- offset degree value. DOes this exist with Marlin?
Thanks in advance for any advice!
Thanks in advance for any advice!
↧
Re: Help With BLTouch clone Not Responding to gcode Commands?
Try with
M280 P0 Sxxx
M280 P0 Sxxx
↧
↧
Re: Filament runout echo:unknown command: M412
Thanks for the quick reply.
I am new to Marlin and 3d printers in general and and have nearly finished completing my cubex duo/rumba build. I am utilising the built in filament detector on the duo.
Runout Sensors is defined in the 1.1.9 Configuration.h file. I am surprised it would be defined but not supported.
/**
* 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 FILAMENT_RUNOUT_SCRIPT "M600"
#endif
I avoided going with 2 because I was worried about bugs (if there are any) confusing my learning curve.
Is 2 ready to use? Or should I wait and just not use the runout sensors for now?
Will my 1.1.9 configuration file be usable in 2 or will it need a lot of work?
I couldn't see any attached photo btw.
I am new to Marlin and 3d printers in general and and have nearly finished completing my cubex duo/rumba build. I am utilising the built in filament detector on the duo.
Runout Sensors is defined in the 1.1.9 Configuration.h file. I am surprised it would be defined but not supported.
/**
* 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 FILAMENT_RUNOUT_SCRIPT "M600"
#endif
I avoided going with 2 because I was worried about bugs (if there are any) confusing my learning curve.
Is 2 ready to use? Or should I wait and just not use the runout sensors for now?
Will my 1.1.9 configuration file be usable in 2 or will it need a lot of work?
I couldn't see any attached photo btw.
↧
Re: Filament runout echo:unknown command: M412
Mostly the bugs are in the 32bit controller firmware, as I am still using a 16bit controller I do not have to worry about any 32bit errors.
They are maintaining a list of the controllers that are still having problems Here and my RAMPS, compatible is good to go so I went...
They are maintaining a list of the controllers that are still having problems Here and my RAMPS, compatible is good to go so I went...
↧
Re: Filament runout echo:unknown command: M412
Good to know. My Rumba is basically a ramps board so I should be good to go.
↧
Re: Is there a Temp Offset parameter buried someplace in Bugfix 2.0?
I would ask you what thermister you are using and the setting you used in Marlin for your Nozzle and bed.
↧
↧
Re: Filament runout echo:unknown command: M412
I like it, it has many features that make it better, an still learning the features.
#define S_CURVE_ACCELERATION
#define JUNCTION_DEVIATION // in lieu of XYZ Jerk
#define RESTORE_LEVELING_AFTER_G28
#define PARK_HEAD_ON_PAUSE // Normally when I paused it stopped at the current location and melted the model, now stops and moves to a park location
#define S_CURVE_ACCELERATION
#define JUNCTION_DEVIATION // in lieu of XYZ Jerk
#define RESTORE_LEVELING_AFTER_G28
#define PARK_HEAD_ON_PAUSE // Normally when I paused it stopped at the current location and melted the model, now stops and moves to a park location
↧
Re: Help With BLTouch clone Not Responding to gcode Commands?
Quote
obewan
Try with
M280 P0 Sxxx
I'm sorry. Sometimes my brain goes faster than my fingers. 280 is what I mean. That is the command(s) that I tried.
↧
Re: Filament runout echo:unknown command: M412
I installed Marlin 2bf and am back up and running with 'runout sensors On displayed on the LCD. Thanks for the assistance.
↧
Re: Help With BLTouch clone Not Responding to gcode Commands?
It is ok, have the same problem.
↧
↧
Re: Is there a Temp Offset parameter buried someplace in Bugfix 2.0?
Thanks for the reply!!! I am using FYSETC, HT-NTC100K Thermistors on both Bed & Hot End. Setting in FW is 1 for both
↧
Re: Is there a Temp Offset parameter buried someplace in Bugfix 2.0?
Thermistor responses are not linear, An offset would correct the temperature at one particular temperature and make it incorrect everywhere else
You need to select the correct temperature table for you're device. Google tells me this is 13 not 1
You need to select the correct temperature table for you're device. Google tells me this is 13 not 1
↧
Re: Is there a Temp Offset parameter buried someplace in Bugfix 2.0?
Thanks Dust!
↧