RAyWB
About
- Username
- RAyWB
- Joined
- Visits
- 2,124
- Last Active
- Roles
- Member
Comments
-
rein interessehalber, wieso brauchst du den analogeingang ? ich rate mal dass du damit eine Gabellichtschranke auswertest..
-
don´t worry about that , i remember my own "problems" when i started :-)
-
got it : change uiconfig to : #define UI_HAS_BACK_KEY 0
-
Z_PROBE_BED_DISTANCE ist die z-höhe bei der er anfängt zu proben, Z_PROBE_HEIGHT ist der Abstand vom bett zur düse, bei dem die probe triggert mit den beiden parametern müsstest du das aufs gleis kriegen (ist doch nur ein werkzeugtaster der an de…
-
schau mal in die Configuration.h wo steht der #define Z_PROBE_BED_DISTANCE ?? setz den mal auf 10 oder 20, einfach mal spielen
-
just hooked up a mega with the display (i just have a 0.96") without problem did you change something else in uiconfig?
-
ok, so we are talking about the ssd1306 . also tried one , but to be honest i´m not shure if there were problems or not.
-
du kannst deine signale z.b. im timer 500ms abfragen und dann deine routinen aufrufen. wenn du dir bei mir den timer anschaust : void Custom_500MS() { loopcount++; if(loopcount=3) { CustomMessage(); loopcount=0; } } dann …
-
if i followed up correct , this display was added to dev by yourself, where did you add it?
-
what happens if you turn the encoder? i also use dev. branch on a graphic display and i have the "back" line
-
nutze doch die custom events , dann klappt es auch mit Printer::continuePrint(); etc. da kannst du alles was in deiner plotter.h und cpp ist reinpacken und hast keine probleme mit den #includes beispiele findest du hier : https://github.com/repeti…
-
if you are talking about what Host shows after homing , be shure that Printer settings in Host match Firmware settings.
-
why rewrite m104? may be there is a misunderstanding, the original parts of commands still work. for example if there is a m104 in custom events the modified one gets executed if there is not a modified one the original one gets executed.
-
no, this is not possible to do with variables. what is the intended use?
-
there is no need to remove from original, customized stuff is executed before the original, so the original will not be executed. thats the advantage of the custom events, you can just copy the original and modify it for your needs without changing …
-
i mean a mix of sensing power decrease and ups system. not shure about the buffers , but that wouldn´t matter. I´m just thinking of buffering the arduino by a combination of Diode/huge capacitor and sensing the 12V line. via analog input. But from …
-
regarding a "trigger" to M480... what power supply do you use? you could check a pin status in function timer100ms. just triggering the pin on a defined voltage level to run the M480
-
arduino Mega has 4096 bytes EEPROM so last number is 4095. quote: for me it's the first real addition to the printer firmware so I am working a little bit slowly because I need some time to understand each function and use it …
-
just one question : from my point of view the functions are very useful for cnc , but how do you want to handle your intended use quote: My idea was just to continue the job even if the printer/router accidentally powered off how do you manage to w…
-
i suggest one important change : replace my name by yours as you coded it and it´s public in github ;-) there is no need to comment out //#undef EVENT_UNHANDLED_G_CODE(c) //#define EVENT_UNHANDLED_G_CODE(c) Custom_GCode(c…
-
ok, youre modifying the old 0.92 version. you should use developmentbranch to have event system. it´s different.
-
sorry, as i wrote yesterday : " regarding eeprom modification it might get a little tricky to do it from custom events as there are multiple points to be considered. I´m not really shure at the moment how to handle that . " couldnt find somethi…
-
so it´s simple to add Encoder.in configuration.h set #define FEATURE_UI_KEYS 1in uiconfig.huncomment // UI_KEYS_INIT_CLICKENCODER_LOW(33,31); and replace the pin numbers by yoursdo the same for //UI_KEYS_CLICKENCODER_LOW_REV(33,31)similar for…
-
how did you set up yor display? did you use the uiconfig.h?
-
so if you use the empty template i uploaded just take a look at https://github.com/repetier/Repetier-Firmware/tree/development/src/SampleEventSystems/Laser PWM and DAC so you can figure out how it works, the empty template might be a good startin…
-
they are listed at beginning of configuration.h
-
just uploaded an empty template for G/M codes to my Github. Hope that helps you to start. https://github.com/RAyWB/Additions-for-Repetier-Firmware/tree/master/CustomEventsEmpty @Repetier : Roland you can also take it to the samples if you want to
-
Dawido said: Ok, Z_MIN_POS set to 0, without G32 S2 it is wrong, so to sum up, after doing Z home for Z max 125 it is doing it 5mm above bed, here are the 5mm : #define ZHOME_HEAT_HEIGHT 5 it moves to zmax, then to ZHOME_HEAT_HEIGHT 5 ..…
-
you can select in cofiguration tool or here : https://github.com/repetier/Repetier-Firmware/tree/development
-
- M500 Store settings to EEPROM - M501 Load settings from EEPROM - M502 Reset settings to the one in configuration.h. Does not store values in EEPROM! refer repetier.ino for commands