Show all posts by user
Page 1 of 1 Pages: 1
Results 1 — 27 of 27
QuoteVDX
... as for the "temperature spikes" -- the are mostly caused by EMI, transients and instability of the reference voltage, used as base ...
Of course. But it's hard to investigate without oscilloscope. And no need, honestly.
by
PB
-
Firmware - experimental, borrowed, and future
BTW for those who asked about temperature spikes, they are still present. But as I mentioned before, these single reading spikes of more than 10 degrees don't affect heater temperature in excess of 0.5 degree so I stopped to investigate it.
by
PB
-
Firmware - experimental, borrowed, and future
As far as I remember the spikes are indeed present but not causing problems as my (autocalibrated) PID parameters are not sensitive to it so temperature of heater is stable despite one wrong reading sometimes. I forgot about this because really there is no problem to me.
Also I remember that once I got vastly increased number of wrong readings and the cause was self-unsoldering of heater (!) con
by
PB
-
Firmware - experimental, borrowed, and future
Quotesinned
I get some random flakiness from DWC - the browser window will say "Lost Connection" but wont re-establish until I reset the board. The browser will not reconnect, but the webcam feed still
Me too. Sometimes. Got no system in this and prints finish sucessfully anyway.
Here is my M122 in working condition. Of course I can not say in advance when it will stop working and make M122 jus
by
PB
-
Firmware - experimental, borrowed, and future
Quotesdavi
I think the SBase boards have a LPC1768. Have you checked what's printed on top of the chip on your board?
Thank you! Re-checked and found that the chip in Sbase 1.3 is actually LPC1768 although in BOM specified LPC1769.
by
PB
-
Firmware - experimental, borrowed, and future
Quotedc42
QuotePB
BTW it seems that nonlinear extrusion uses segment average speed, not current speed of effector for correction. Start and end of a long segment where acceleration is not zero and actual speed is therefore decreased by frimware seem overextruded. Is it right?
That's correct, nonlinear extrusion adjusts the extrusion rate of the move as a whole. But I would expect the effect on t
by
PB
-
Firmware - experimental, borrowed, and future
BTW it seems that nonlinear extrusion uses segment average speed, not current speed of effector for correction. Start and end of a long segment where acceleration is not zero and actual speed is therefore decreased by frimware seem overextruded. Is it right?
by
PB
-
Firmware - experimental, borrowed, and future
I calibrated and tested nonlinear extrusion. Everything seems to work. In free-flowing nozzle I get A=0.027 (measured extraction shortage of 100mm of filament at 1 and 5 mm/s) in real printing A=0.156 (this value makes equal width of printed 70 mm long single perimeter walls at 30 mm/s (extrusion rate 1.15 mm/s) and 75 mm/s (extrusion 2.88 mm/s). B=0 in both cases.
Seems that back pressure and t
by
PB
-
Firmware - experimental, borrowed, and future
Quotesdavi
QuotePB
Thanks! I tried to make from current source (of course I enabled it in Pins_LPC.h beforehand) and got some syntax errors I consider they are because of older version compiler.
1. ../RepRapFirmware/src//Libraries/Fatfs/port/lpc/diskio.cpp:64:51: error: no matching function for call to 'SDCard::disk_read(BYTE*&, DWORD&, BYTE&)'
while(_ffs->disk_read(buff, se
by
PB
-
Firmware - experimental, borrowed, and future
Quotesdavi
QuotePB
I try to use nonlinear extrusion feature but firmware says "M592 not supported".
RepRapFirmware for LPC176x based Boards 2.03+2
Duet Web Control 2.0.0-RC5
According to changelog I think it is already implemented. What can be done to enable it?
Yeah I just checked the code and it's still disabled in Pins_LPC.h, so it's not currently compiled in. I'll enable it for next versio
by
PB
-
Firmware - experimental, borrowed, and future
Quotesinned
QuotePB
I try to use nonlinear extrusion feature but firmware says "M592 not supported".
What are you other parameters?
E.g. M592 D0 A0.1 B0.0 C0.2
The output is same at any parameters "Warning: M592 command is not supported"
by
PB
-
Firmware - experimental, borrowed, and future
I try to use nonlinear extrusion feature but firmware says "M592 not supported".
RepRapFirmware for LPC176x based Boards 2.03+2
Duet Web Control 2.0.0-RC5
According to changelog I think it is already implemented. What can be done to enable it?
by
PB
-
Firmware - experimental, borrowed, and future
Quotesdavi
QuotePB
3. On temperature plot I notice short but high spikes at all thermistors. Probably only one reading wrong. Not causing problems.
3. So far it seems only some users of mkssbase 1.3 boards have reported those temperature fluctuations. As mentioned a few times in the thread, also make sure to use the thermistor analog gnd all the way to the thermistor. Are the temps are stable af
by
PB
-
Firmware - experimental, borrowed, and future
After 2 days of silly problems I use this cool firmware!
1. Noticed that DRV8825 steppers which are quite noisy in smoothie, are much less noisy in RRF. Probably is is because in RRF I set recommended pulse delays M569 P0 S0 T1.9:1.9:0.65:0.65 according to DRV8825 datasheet which option is absent in smoothie. Furthermore in low power idle mode (M906 X1000.00 Y1000.00 Z1000.00 E1000.00 I30) it is
by
PB
-
Firmware - experimental, borrowed, and future
Quotesdavi
Can you try a 12 point calibration instead? If that works, then I can increase the main task stack size if it needs a bit more space.
Yes, decreasing number of calibration points to 16 works. In fact it was 17 when it was not working.
Thank you!
by
PB
-
Firmware - experimental, borrowed, and future
Quotedc42
Have you tried sending M665 and M666 without parameters after running G32, to see if they have changed? Then you can run M500 to save the new values to config-override.g.
Yes I run M665 and M666 without parameters before and after G32 and all values reported are completely same. I even tried to put 1mm thick sheet on half of bed to make it feel differently inclined for probe and no er
by
PB
-
Firmware - experimental, borrowed, and future
When I try auto calibration G32 everything seems to proceed fine, homing and probing all points without any error messages but resulting M665 M666 parameters are completely same like before calibration.
config.g
M208 Z0 S1
M574 X2 Y2 Z2 S0
M558 P5 R0 H5 F300 T18000
M558 H15
G31 P500 X0 Y0 Z
by
PB
-
Firmware - experimental, borrowed, and future
Quotesdavi
If you don't want to use 2.6 as a heater, then just remove it from the heatOnPins array in board.txt.
As for setting up the PSU thermostatic fan, just guessing here (never tried that before), but maybe its not yet monitoring heater 2 temps? So have you tried creating another "tool" with Heater2 (but without any drives etc attached)? Perhaps something like M563 P2 H2 might work. I al
by
PB
-
Firmware - experimental, borrowed, and future
QuotePB
QuotePB
Seems Sbase do have level shifters i.e. SN74LVC1T45DCK at 0.15, 0.16, 0.18
I can not guess why it has problem with RRD displays.
May it be incompatibility like inverted SCK levels (wrong CPOL) or time shifted MOSI to SCK (wrong CPHA)?
BTW Sbase 1.2 schematics available
The only thing I can confirm about Sbase 1.3 that level shifters IC at same places are present in 1.3 board.
by
PB
-
Firmware - experimental, borrowed, and future
QuotePB
Seems Sbase do have level shifters i.e. SN74LVC1T45DCK at 0.15, 0.16, 0.18
I can not guess why it has problem with RRD displays.
May it be incompatibility like inverted SCK levels (wrong CPOL) or time shifted MOSI to SCK (wrong CPHA)?
by
PB
-
Firmware - experimental, borrowed, and future
Quotedc42
QuotePB
Sinned,
thank you for helping to verify that everything were connected right.
Found that at F100000-50000 some part of image appeared and was becoming increasingly in sync
M918 P1 F30000 helped completely (but screen redraw is slow)
Is there some way to get same at faster redraw or it is not worth efforts?
I believe the problem is that the SBase drives the 12864 display with 3.
by
PB
-
Firmware - experimental, borrowed, and future
Sinned,
thank you for helping to verify that everything were connected right.
Found that at F100000-50000 some part of image appeared and was becoming increasingly in sync
M918 P1 F30000 helped completely (but screen redraw is slow)
Is there some way to get same at faster redraw or it is not worth efforts?
by
PB
-
Firmware - experimental, borrowed, and future
Good day for everyone!
I decided to quit smoothieware and now try to use RRFv2.03 with Sbase 1.3 and RRD 12864 display. As of now board.txt:
lcd.lcdCSPin = 0.16;
lcd.lcdBeepPin = 1.31;
lcd.encoderPinA = 3.25;
lcd.encoderPinB = 3.26;
lcd.encoderPinSw = 1.30;
lcd.lcdDCPin = NoPin;
lcd.panelButtonPin = 2.11;
and with M918 P1 F1000000 I get picture like this . It doesn't ch
by
PB
-
Firmware - experimental, borrowed, and future
