Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Development #1

Open
wants to merge 34 commits into
base: Stable
Choose a base branch
from
Open

Conversation

i-make-robots
Copy link

possible fix for issue 1318

wgm4321 and others added 30 commits December 28, 2014 20:43
…t be floats.

The compiler does not support comparing float values: "error: floating constant in preprocessor expression"
The loss in X/Y precision shouldn't matter for Z probes, as most microswitches or inductive sensors are larger than 1mm square anyway.
Add Filament menu and add Filament/Retract settings to config store.
Due to the fix for MarlinFirmware#1248, X and Y probe offsets must not be floats.
…t be floats.

The compiler does not support comparing float values: "error: floating constant in preprocessor expression"
The loss in X/Y precision shouldn't matter for Z probes, as most microswitches or inductive sensors are larger than 1mm square anyway.
Move scripts and documentation to subfolders
Fix for cant compile when REPRAP_DISCOUNT_FULL_GRAPHIC_SMART_CONTROLLER ...
Added further tests to Travis CI config
Define analogInputToDigitalPin only if needed
Philippe L and others added 4 commits January 4, 2015 14:23
temp runaway: proper cast to prevent any overflow.
try, try again.

If 'OK' is garbled on sending PC won't receive it.  Both machines will
wait on each other forever.  This resends OK if nothing is heard from PC
for a while to avoid this bad case.
- added DEFINE In configuration.h with default ok timeout ms (at end of
file)
- changed manage_inactivity() to use the new define
@thinkyhead
Copy link

This should be re-targeted to MarlinFirmware/Marlin -> Development branch.

@releyshic
Copy link

Переводчик
Actively build 3D printer from old inkjet printers )
I have a Chinese Arduino Mega and RAMPS 1.4, DRV8825 drivers (purple, or notebook which), the firmware is Marlin
In test mode all twisted (SM) works
But the main problem is the following -> I have on the z-axis of SM c two gears of different number of steps and straps of different pitch, those physically not able to connect two of these SM's on a single driver the z axis.
RAMPS 1.4 Board has 3 channels for stepper motor 3 axes X, Y, Z and two extruders for E0 and E1. The extruder I have one, so it remains a free driver E2. To it just I want to connect a second stepper motor Z-axis different from the first parameters.
But here is just Zapara - motor control of the extruder differs from the management of SM axis, and plus and myself configuring Marlin to work with 2 extruders are not simple and little information.
The settings of the axes are stored in the header Configuration.h
#define DEFAULT_AXIS_STEPS_PER_UNIT {80,(100_1)/(1.05_40),(100_1)/(1.25_20),(3200 * 39.0)/(11.0 * 6.75 * 3.45)}// X Y Z E0 E1 100 - the number of steps per revolution stepper motor, 1.05 - step belt, 40 is the number of gear teeth
Each Driver receives 4 parameters: MS1, MS2 - microstepping mode(1, 1/2, 1/4,1/8,1/16,1/32); STEP, DIR as I understood - step (pulse) and direction of rotation. However, I do not understand why the code is MS1, MS2 although in the diagram to the controller is not connected
I guess the easiest option would be to find where in the code the firmware sends commands to the outputs of Arduini -> driver-E1 and write down the values for Z, but given its parameters, naturally there will be several edits on the way from DEFAULT_AXIS_STEPS_PER_UNIT to the programming outputs of the mega.
Here's what I can't find where it is set to output mega for STEP, DIR
Well, maybe somebody is already doing? or well versed in the code?

@i-make-robots
Copy link
Author

I don't know why I'm being cc'd on this. It sounds like a mechanical problem, then a confusion problem, never a marlin problem.

On Jan 22, 2016, at 11:49 PM, releyshic notifications@github.com wrote:

Переводчик
Actively build 3D printer from old inkjet printers )
I have a Chinese Arduino Mega and RAMPS 1.4, DRV8825 drivers (purple, or notebook which), the firmware is Marlin
In test mode all twisted (SM) works
But the main problem is the following -> I have on the z-axis of SM c two gears of different number of steps and straps of different pitch, those physically not able to connect two of these SM's on a single driver the z axis.
RAMPS 1.4 Board has 3 channels for stepper motor 3 axes X, Y, Z and two extruders for E0 and E1. The extruder I have one, so it remains a free driver E2. To it just I want to connect a second stepper motor Z-axis different from the first parameters.
But here is just Zapara - motor control of the extruder differs from the management of SM axis, and plus and myself configuring Marlin to work with 2 extruders are not simple and little information.
The settings of the axes are stored in the header Configuration.h
#define DEFAULT_AXIS_STEPS_PER_UNIT {80,(1001)/(1.0540),(1001)/(1.2520),(3200 * 39.0)/(11.0 * 6.75 * 3.45)}// X Y Z E0 E1 100 - the number of steps per revolution stepper motor, 1.05 - step belt, 40 is the number of gear teeth
Each Driver receives 4 parameters: MS1, MS2 - microstepping mode(1, 1/2, 1/4,1/8,1/16,1/32); STEP, DIR as I understood - step (pulse) and direction of rotation. However, I do not understand why the code is MS1, MS2 although in the diagram to the controller is not connected
I guess the easiest option would be to find where in the code the firmware sends commands to the outputs of Arduini -> driver-E1 and write down the values for Z, but given its parameters, naturally there will be several edits on the way from DEFAULT_AXIS_STEPS_PER_UNIT to the programming outputs of the mega.
Here's what I can't find where it is set to output mega for STEP, DIR
Well, maybe somebody is already doing? or well versed in the code?


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants