-
Notifications
You must be signed in to change notification settings - Fork 69
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
base: Stable
Are you sure you want to change the base?
Development #1
Conversation
…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
Added .gitignore back into repo
Readd .travis.yml
…le errors until translated
Fix for cant compile when REPRAP_DISCOUNT_FULL_GRAPHIC_SMART_CONTROLLER ...
Added further tests to Travis CI config
Define analogInputToDigitalPin only if needed
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
This should be re-targeted to MarlinFirmware/Marlin -> Development branch. |
Переводчик |
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.
|
possible fix for issue 1318