Show all posts by user
There are default values assigned from Configuration.h The defined values apply to all extruders. For simplicity, there is just one set that applies to all. But you can change individual extruders. If you change the values, you can save them in EEPROM.
by
Roxy
-
Firmware - Marlin
First, you need to get Arduino up and running with a PrintrBoard. They want you to use a very very old version of Arduino. The reason is the PrintrBoard additions do not work with every version of Arduino.
This version is very old, but it does work. Hopefully, it still works with the newer versions of Marlin.
If it doesn't we can (with work) get you going on a newer version of Arduino.
by
Roxy
-
Firmware - Marlin
You want to start with the Marlin code they shipped the unit. It should be available on their site. It is part of the license agreement. Marlin is free to use and ship in commercial products, but as a condition to this, they have to provide the full source to anybody that asks for it.
With the code base that shipped with your unit, you can easily start making changes or migrate to a new ve
by
Roxy
-
Firmware - Marlin
Pretty much, all of the GPIO (General Purpose I/O) pins can be configured as either input or output. And when configured as input, you can specify if you want a pull up resistor turned on for them.
Download the specification for your processor. All of this is detailed in great detail in the specification.
by
Roxy
-
Firmware - Marlin
Quotestephenrc
Edit not available on first post, so I can't change it.
OK! Thanks for trying!
by
Roxy
-
Firmware - Marlin
Quotestephenrc
I didn't notice that they added more RAMPS definitions. I was using BOARD_RAMPS_13_EFB and changed it to BOARD_RAMPS_14_EFB. The servo now work on servo 0. The wiki says the only difference between 1.3 and 1.4 is that 1.4 uses surface mount compnents. Why does that affect the servo?
More changed than the fact they are using surface mount components. I know there were a lot o
by
Roxy
-
Firmware - Marlin
There are multiple RAMPS board definitions over at www.github.com/MarlinFirmware right now. Apparently something got changed on the board. It may be you declared the 'wrong' version of RAMPS for the electronics you have. You might want to check and see if that is the case. (Just because there may be other stuff that isn't defined right for your electronics without getting that setup right.
by
Roxy
-
Firmware - Marlin
I'm not sure... But I would make a couple of changes. I would bump the NUM_SERVO count up to 3 just because we are using the 3rd field. The code should be tolerant of having it at 1 but for right now, I would move it to 3. And I would try it with the //#define Z_ENDSTOP_SERVO_NR 0 commented out. I think this has to do with using the Z-Probe as a Z_MIN_ENDSTOP. Also, are you sure t
by
Roxy
-
Firmware - Marlin
Yikes!!! Thank You for the correction Dust!
(I see what happened now. I clicked on the M207 link instead of M206 because I wasn't being careful enough. )
by
Roxy
-
Firmware - Marlin
I think the original poster's problem did not involve the Z-Axis. M206 is focused on the Z-Axis and not X or Y.
by
Roxy
-
Firmware - Marlin
Do you know the actual Thermistor you are using? Because if you do you can look at the parameters that define its behavior and most likely there will be a very close match already defined. If there is not a close match, using those parameters you can run the Python script and have it generate a new table entry for your particular Thermistor and just use that.
by
Roxy
-
Firmware - mainstream and related support
I have a biased opinion. But my response is you should fix this issue by physically getting the printer to be 'correct'. When you home the printer, you do want to accurately know where the limits are and for simplicity you don't want some weird values for Min and Max travel on the various axis. But what ever you end up with, my vote would be to change values in the Configuration.h file of Mar
by
Roxy
-
Firmware - Marlin
OK. Well, I don't know Python so I can't help with what ever is blowing up the script. But if you post this issue over at: I think you will get an answer. That is where the code is evolving and things like this get dealt with on a routine basis. If you do get a good answer and a fix, please bring it back to this thread.
by
Roxy
-
Firmware - Marlin
So if you know the correct values, can't you take an existing table that is close and just manually shift the values to get it right for your setup?
by
Roxy
-
Firmware - Marlin
I don't know Python, so I can't really debug that code. But I do have a couple of comments. First, isn't 60 C a very high starting point for the first temperature in the table? And the second comment is you don't actually have to use the generation script. You can edit the Thermistortables.h file to have the values the way you want them.
Can you explain why you need to generate a new table
by
Roxy
-
Firmware - Marlin
Probably the place to start is take the command line that is working and change one parameter at a time until you understand which one is causing the failure. But do you really need to create a custom table? Aren't you using standard thermistors?
by
Roxy
-
Firmware - Marlin
QuoteRepRot
Roxy, With CoreXY printers you usually lower the print bed after a print is finished so it is handy to have this feature available.
Ok! I don't have a CoreXY and have a lot to learn about them. Can you post the code?
by
Roxy
-
Firmware - Marlin
About 9 months ago, the Triggered and Open messages were changed to be more clear. The terminology used is clumsy for another reason. The switches can be configured to be active wither with a closed or open state. They had to be changed back. The problem is it broke all the client programs that were looking for specific text. Getting these messages changed to something more clear is going t
by
Roxy
-
Firmware - Marlin
RepRot, are you suggesting these as changes to the main line code? At a minimum the wording would need to be changed. For example a lot (most???) of printers do not lower the heat bed. They raise the extruder. The wording of anything in the menu's should be neutral.
by
Roxy
-
Firmware - Marlin
Marlin Firmware Questions, Support and Feature Requests ????
(But that is kind of like your "All things Marlin" idea.)
I don't think it really matters. The whole goal is to get the Marlin stuff into its own area so it is easier to support.
AND... THANKS!!!!
by
Roxy
-
Administration, Announcements, Policy
If it is Marlin... You can do a M503 and print out most of the important settings. Anything that isn't printed out, is going to be obvious the first time you load the firmware and it doesn't work exactly the same.
For example, if one of the axis is inverted, you will see it move the wrong way and be able to flip it.
But with that said... We should add an instruction to hex dump the current
by
Roxy
-
Firmware - mainstream and related support
QuoteDeuxVis
Are there still some opposition ? If yes please explain why.
I'll give everyone 2 weeks, given the time of the year, to get a chance to express your point if you don't want to create firmwares sub-folders by "brand".
After that I'll go ahead and create that Marlin one
It's been two weeks and hardly any concerns expressed!
by
Roxy
-
Administration, Announcements, Policy
I would start small. I would reset everything, and connect PronterFace to the printer. I would see if it can home. I would give it a M114 and a M119 command and see what it says.
by
Roxy
-
Firmware - mainstream and related support
That looks like a normal start up sequence to do Auto Bed Leveling. The G28 is going to use the probe to do the home operation. You might want to change the G29 to something like G29 V4 P4 so you can see when it gets to that particular GCode line of the file.
by
Roxy
-
Firmware - mainstream and related support
On #1, do you mean ABL? Like Auto Bed Leveling? What is ABS ? The first probe might be G28. And then G29 does do some more probes???
On #2, You can adjust the feed rate... But probably you want smaller Z_PROBE_RAISE before, between, after numbers....
by
Roxy
-
Firmware - mainstream and related support
That is the Bed Topology Report. It looks like you are missing a lot of probe points. My guess is you have the Z-Probe on the right side of the effector. You have a some what dish shaped bed right now. Probably you should be adjusting your Delta_Radius. But all that is just a guess based on one set of numbers.
by
Roxy
-
Firmware - mainstream and related support
Micro Stepping just gives you better resolution. Very typically, if you are going to be running in micro-step mode there are jumpers you have to set on your controller board. You should make sure that how ever you have the board configured matches the software mode you are using.
by
Roxy
-
Firmware - mainstream and related support
