RAyWB
About
- Username
- RAyWB
- Joined
- Visits
- 2,124
- Last Active
- Roles
- Member
Comments
-
hmm...close repetier host and open arduino ide. select tools->serial monitor is there any response?
-
exactly. (laptop connected to programming port)
-
the red one on Due is same function as black one on radds.is your radds board mounted on arduino during your test?
-
so you seem to have Due Clone, not original one.some of them need a fix on 16U2 serial converter.
-
which micro usb port do you use? the one near power supply connector or the other one? what happens if you press the arduino reset button? (keep repetier host connected)
-
Might be I´m wrong , as Controller 7 is the radds extention board,tot related to display. what´s the exact message on repetier host? wait? or 1 command waiting? if 1command waiting try to set eeprom mode to 2 and upload firmware again
-
as you have no display you have to set #define FEATURE_CONTROLLER 0 (actually it´s set to7) rest looks ok on first sight
-
if firmware is setup correct , usually not.your complete configuration.h would be useful
-
you also have to set the same baudrate in repetier host
-
what drivers do you use?
-
Is your Baudrate set correct?
-
Communication problems seem solved after updating the 16u2. (still running but the last 1000000 lines with not asingle error)
-
The M111 S24 also showed a lot of communication Errors on Programming Port , that´s why i swapped over to native Port.I´ll continue the search on Due... might be the USBSerialFirmware of the 16u2.As i have a China clone may be that´s an issue. I´ll …
-
Communication works fine on native port , last print was 8 errors on 2.2Million lines also found stopping sequence caused by s3d..... wrong feedrate generated on retract/wipe Any Idea whats wrong on Programming port causing that huge amount of e…
-
Well, communication Errors on native Port are much better, not a single unknown command , but print also failed on a couple of timeouts and missing lines detected. Quote:"Since you said it only happens at high speed my guess is that the stepper inte…
-
Server Input buffer is set to 127. M111 S24 showed lots of errors, changed to dues native usb now, looks much better(only 55 errors on more than 2 million lines)started print now and will inform you tomorrow
-
Thats what is in Log : > 23:12:26.922: ok 3459 < 23:12:26.922: N3461 G1 X129.777 Y167.223 Z0.180 E3.7712 F2888 > 23:12:27.046: T:233.13 /234 B:59.94 /60 B@:114 @:180 T0:233.13 /234 @0:180 T1:20.62 /0 @1:0 > 23:12:27.047: ok 3460 > 23:…
-
i had same effect printing via USB from Win7 Computer, so i guess it might be caused by Firmware.i can give a print from SD Card a try.will take a look on exact error message in log file this evening
-
Stell die Zeitzone am Raspi richtig ein, dann gehts
-
that would be great as i´ll switch over to due on my cartesian (where my laser is installed) this weekend.If i can run any test´s let me know.
-
Thanks, will take some time for me to get familiar with the new structure , but i can already see the huge potential.Will continue testing , may be set up a machine for that.Already saw some mismatches on the corexy but may be it´s easier to collect…
-
OK, thanks .So my misunderstanding is propably based on the comments behind the numbers, especially PREPARE_FREQUENCYhow can it be higher than itself ?is there a possibility to couple a fan to f.e. enable of steppers? may be always on at 30% and fl…
-
Great JOB !that solves the issue now i can see the smooth operation :-) just another question, in github you wrote :No more delays for slower drivers wasting CPU time i still have to set STEPPER_HIGH_DELAY to 1 for my drv8825 misunderstanding from…
-
ok, thanks I´ll try that
-
also with slightly off the 45° same result.as i have htd3 belt my steps /mm are only 101.5xxx but my question: why do we not have that jitter on v1.0.3 ? i just switched firmware , same machine,same resolution,same gcode. BTW watchdog seems solved …
-
do you have a corexy running on V2?printing infill on 45° ( 1 motor should stop, 1 moving) has clearly visible and hearable jitter on the motor which should not move. does also happen on a single 45° move clearly visible.measured with oszilloscope …
-
seems watchdog is triggered by eeprom handling .
-
From my experience I2C is quite sensitive on spikes coming from crosstalk or emc for example.So just ignoring the error is mostly enough as usually in the next loop everything is ok again ;-) Of coarse some explicit handling would be better but for …
-
i added a kind of error handling on due´s i2c routines so it continues regular code if i2c is not responding.similar to the handling in u8glib
-
OK, but some kind of error handling would be nice on I2C as Errors issue a Watchdog reset.I have a working one for DUE, will send you a proposal if you are interested