RAyWB
About
- Username
- RAyWB
- Joined
- Visits
- 2,124
- Last Active
- Roles
- Member
Comments
-
you have to increase Z_PROBE_SWITCHING_DISTANCE to untrigger safely try a value around 2
-
if you used the repetier host eeprom editor you don´t have to do anything more,the values are already saved in eeprom(same situation if you did in repetier server)
-
there is a simple way to increase noise immunity.add external Pullup Resistor from endstop signal to + 3.3V 2KOhms should be fine.and yes, radds manual is correct
-
as you´re using due/radds you should have only 3.3 V !!!!!otherwise you can be shure the Due is damaged
-
also confirmed
-
you have to set : #define ALWAYS_CHECK_ENDSTOPS 1 in configuration.hguess you have set it to 0
-
on 250000 baud as its in your configuration.h,for eeprom 0 (no eeprom) please set feature retraction to 0 as this feature needs eeprom. so please try 1st : eeprom 0 without feature retraction for serial connection 2nd : eeprom 1 with feature retr…
-
gave it a short shot...compiles with couple of warnings but it compiles with eeprom -1 as well as eeprom 1 or 2
-
Well I´m "playing" with the V2 now , but i didn´t continue with the 4th/5th axis as I´m busy on other projects.
-
well, i wrote the " trick " a couple of posts above : M452
-
i guess you didn´t send the M452 before test as i suggested in you configuration.h you have #define DEFAULT_PRINTER_MODE 2 this is CNC mode for Laser you have to set #define DEFAULT_PRINTER_MODE 1
-
yes, that´s what i mean
-
well, you can do that, but TTL input takes no power it´s just control signal ;-) the problem using Fan Pin is that it is "double used" and responses to the M106 so it cannot work on the M3/M5 commands. If you use the servo pin as i suggested it wil…
-
I´m shure the negative Y moves caused the error as they are out of printers limit Quote:G0 F3600 X21.755 Y-41.74 Z0.3;TYPE:SKIRTG1 F2700 E0G1 F1800 X26.908 Y-39.695 E0.34574
-
that´s the section : #define SUPPORT_LASER 1 199 : newIntensity < 200)); #endif } intens=newIntensity;//for "Transfer" Status Page } #endif // SUPPORT_LASER
-
ok how did you connect TTL-Input to D9 on your ramps ?
-
no file attached , you have to upload somewhere and attach the link. also add informations about your hardware , which controller etc.
-
Why don´t you use Repetier Laser feature and M3 / M5 commands as usual?with laser feature you can reverse signal qiute easy
-
so it is solved now or still not compiling?
-
reduce number of languages in configuration.h might help.search for this part: #define LANGUAGE_EN_ACTIVE 1 // English #define LANGUAGE_DE_ACTIVE 1 // German #define LANGUAGE_NL_ACTIVE 1 // Dutch #define LANGUAGE_PT_ACTIVE 1 // Brazilian Portuguese …
-
settings for X-Min and Y-Min should be 0 , not 300
-
ok...i use 1.0.3 that might be the compile problem. can you upload your complete repetier folder somewhere ? i have to leave now but in later evening i´ll find some time to test on a spare due/radds
-
for me that settings compile ...ok, back to basics what version of repetier firmware do you have and what arduino version? (see repetier. h line 27/28)
-
if it works, we are still not shure if eeprom is really damaged or if the i2c output of due is defect do you have a second due?
-
so you can try another thing : (we`re back on repetier firmware now) open pins.h goto line 250 and change from : #define EEPROM_AVAILABLE 1 to#define EEPROM_AVAILABLE 0 in configuration.h set #define EEPROM_MODE 0 recompile and upload , now r…
-
just to be shure : you put the radds on the due before running the i2c scanner?
-
if you have arduino due clone it might be solved with updating the 16u2.(that was the reason i had on my due clone). follow these instructions : https://www.arduino.cc/en/Hacking/Upgrading16U2Due
-
first check if due works, try blink sketch from arduino. remove radds for that testif test is ok , reinstall radds and load I2c scanner (https://playground.arduino.cc/Main/I2cScanner)then you should see eeprom address on arduinos serial monitor.if a…
-
try to remove radds board and upload arduinos blink sketch, see if that works. as you wrote before you fried something ... may be eeprom on radds is broken what would result in non booting
-
so I´m very sorry, no more idea from my side