luc-github / repetier-firmware-4-davinci Goto Github PK

Move issue from 0.91
https://github.com/luc-github/Repetier-Firmware/issues/46

If any decoupled issue printer should stop printing if it is printing - currently extruder go to dry run and stop heating but printer continue to move like printing is still ongoing

When attempting a hot bed levelling configuration and selecting manual levelling within the menu, the user is prompted to clean the bed and nozzle. If I click on No, it still attempts to heat the nozzle and remains in that state indefinitely, without actually heating the nozzle.

issue pulled from 0.91 https://github.com/luc-github/Repetier-Firmware/issues/52

Hi,

I cannot control the printer via Repetier-host, but I am able to do basic movements on the extruder using Pronterface.

In Repetier-host, I am able to configure everything and select the correct com port, but that's about it.

If I click on Manual Control and thereafter click on the connect button, the status changes from disconnected to idle and it says "8 commands waiting".

Any ideas what this could be related to?

It looks like the current nightly builds of Arduino have incompatible changes with variants.cpp. I was able to build by copying the "hardware" directory from 1.5.8.

Add Configuration.h and uconfig.h files in additional files directory to support DUE/RADDS/FullGraphicLCD and an optional Keypad, others files should be able to be shared with Davinci

If some printer moding has not correct design, the result is air flow is not managed properly, this can generate the target temperature is not reached but lower off few degres, which generate decoupled test error.
Add a flag to disable decoupled test with warning as it means to decrease the safety control

This will allow people who update/modify extruder/bed to keep their personnal tables when they update FW
If table file is found on SD Card it will overide the default one, may be also add a command to generate the file with default values, or do storage on EEPROM may be more easy

Issue pulled from 0.91 https://github.com/luc-github/Repetier-Firmware/issues/38

Issue come with commit 1b4c93a
seems linked to partial SHARED_COOLER current implementation

MIssing command to pause the host if out of filament

This would be linked to Preheat bed/extruder and used in bed leveling
About load filament question is open: if change filament from ABS to PLA need another entry than unload/load but change filament to use the correct temperature to unload then load and change profile

like:
if ABS->PLA
profile = ABS
1 - unload : temperature = ABS
2 - load : temperature = ABS, to purge ABS while loading PLA
3 - change profile to PLA

if PLA ->ABS
1 - unload : temperature = PLA
2 - load : temperature = ABS
3 - change profile to ABS

Preheat :
1 extruder : follow profile ->Bed/Extruder
2 extruder : follow profile for extruder, follow hotest bed temperature profile for bed

Bed leveling / cleaning nozzle : they follow preheat

LCD is scramble after emergency stop since 195076d
No issue when starting printer

Import some minor fixes from 92.2:
SD Card Reading improvement: 7e2b604
Typo issues
Decoupled messages : 1b4c93a
Protocol V3:c7d79c7
Auto leveling
Auto PID
Kickfan start
filament usage update
CONTROLLER_GATE_3NOVATICA
shared cooler : fba5e49

When pausing a SD print, the carriage moves to the front right which is very difficult to get at. For pause print could the carriage be moved to either x/y home or the clean nozzle position? This would allow for both nozzle cleaning and filament change mid print. Thanks.

Extruder table is not correct for 19 degres for 1.0a it generate a sensor error

At initialization the AiO boards have very high failure rate and get white screen or 2 lines visibles
When printing screen become white randomly and need reboot on 1.0 old generation.

these commands are now available in repetier, need to importe them

When this happen on serial monitor I see bunch of "wait" commands and on LCD the buffer decreasing, Can navigate in printer menu when this happen - so printer is not frozen and this does not trigger the watchdog
After few seconds print resume, I did not observed any crash neiter print failure but, seems weird.
This never happened with repetier host so far
I have set same setting for communication in S3D than for repetier
202 cache / Hw flow control / baud rate 230400

not sure how to address this

Import ADC reading changes from repetier 92.2 for DUE

Must you use this file?
What is it?

Thank :)

When EEPROM_MODE is set to 1, compile works fine (Mac OS X 10.7.5 Arduino 1.5.8) but change the value to zero and the following errors appear

Arduino: 1.5.8 (Mac OS X), Board: "Arduino Due (Native USB Port)"

In file included from /var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/Repetier.h:332:0,
from /var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/Communication.cpp:22:
/var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/HAL.h:71:48: error: 'const char Com::tManualProbeX1 []' is not a static member of 'class Com'
#define FSTRINGVALUE(var,value) const char var[] PROGMEM = value;
^
/var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/Communication.cpp:33:1: note: in expansion of macro 'FSTRINGVALUE'
FSTRINGVALUE(Com::tManualProbeX1,"Manual-probe X1")
^
/var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/HAL.h:71:48: error: 'const char Com::tManualProbeY1 []' is not a static member of 'class Com'
#define FSTRINGVALUE(var,value) const char var[] PROGMEM = value;
^
/var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/Communication.cpp:34:1: note: in expansion of macro 'FSTRINGVALUE'
FSTRINGVALUE(Com::tManualProbeY1,"Manual-probe Y1")
^
/var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/HAL.h:71:48: error: 'const char Com::tManualProbeX2 []' is not a static member of 'class Com'
#define FSTRINGVALUE(var,value) const char var[] PROGMEM = value;
^
/var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/Communication.cpp:35:1: note: in expansion of macro 'FSTRINGVALUE'
FSTRINGVALUE(Com::tManualProbeX2,"Manual-probe X2")
^
/var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/HAL.h:71:48: error: 'const char Com::tManualProbeY2 []' is not a static member of 'class Com'
#define FSTRINGVALUE(var,value) const char var[] PROGMEM = value;
^
/var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/Communication.cpp:36:1: note: in expansion of macro 'FSTRINGVALUE'
FSTRINGVALUE(Com::tManualProbeY2,"Manual-probe Y2")
^
/var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/HAL.h:71:48: error: 'const char Com::tManualProbeX3 []' is not a static member of 'class Com'
#define FSTRINGVALUE(var,value) const char var[] PROGMEM = value;
^
/var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/Communication.cpp:37:1: note: in expansion of macro 'FSTRINGVALUE'
FSTRINGVALUE(Com::tManualProbeX3,"Manual-probe X3")
^
/var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/HAL.h:71:48: error: 'const char Com::tManualProbeY3 []' is not a static member of 'class Com'
#define FSTRINGVALUE(var,value) const char var[] PROGMEM = value;
^
/var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/Communication.cpp:38:1: note: in expansion of macro 'FSTRINGVALUE'
FSTRINGVALUE(Com::tManualProbeY3,"Manual-probe Y3")
^
/var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/HAL.h:71:48: error: 'const char Com::tManualProbeX4 []' is not a static member of 'class Com'
#define FSTRINGVALUE(var,value) const char var[] PROGMEM = value;
^
/var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/Communication.cpp:39:1: note: in expansion of macro 'FSTRINGVALUE'
FSTRINGVALUE(Com::tManualProbeX4,"Manual-probe X4")
^
/var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/HAL.h:71:48: error: 'const char Com::tManualProbeY4 []' is not a static member of 'class Com'
#define FSTRINGVALUE(var,value) const char var[] PROGMEM = value;
^
/var/folders/fj/_3y948796_b3ms2wjsk0kzp40000gn/T/build2022692941532461976.tmp/Communication.cpp:40:1: note: in expansion of macro 'FSTRINGVALUE'
FSTRINGVALUE(Com::tManualProbeY4,"Manual-probe Y4")
^
Error compiling.

After flashing the EEPROM and uploading 0.92 onto my Davinci 1.0, I am able to see that the firmware has successfully installed on the printer, but the issue that I am experiencing is that the printer restarts every 25 seconds.

So whether the printer is idling or whether I am in a menu, it still restarts.

I have one of the newer boards that had 1.1j as the default firmware on it.

Any ideas?

Confirmation dialog is empty

decompress archived gcode file on sd card. otherwise sd uploads take forever and everyone would need a transend wifi sd card, or the swap method is required to bypass the slow spi data rates.

On dual fans printer - fans operate upside down, when left extruder is on, right fan is working, and when right extruder is on left fan is working, (http://voltivo.com/forum/davinci-firmware/40-custom-firmware-development?start=200#3146)

When loading new filament into the left extruder while the unit is at home position, the unit stays at the home position. This causes the new filament to dump out between the print bed and the right extruder's dripbox.
Luckily there is a straight opening from the left head to the base of the printer, but it would be more convenient for the old filament to go into the proper location.

I've had this kind of crash a few times on my 1.0. If you manually home the X and Y axis in the wrong order (first Y, then X), chances are you'll end up with the extruder's fan slamming into the Z-endstop. Same thing if you try to home Y with the head more or less lined up with the sensor. This is a very unfortunate design overlook, but I guess it could be fixed in the firmware.

I believe something like this was already in the early versions of the firmware (with the ENDSTOP_Y_BACK_ON_HOME thing), but it had the side-effect of not letting the head home in the right position. What if instead we'd forbid the printer head from moving into negative Y coordinates at any time unless X is in the negative too. So homing Y and then X should result in the head moving only up to Y0, and then X-HOME. Another approach would be to simply forbid any X move (around the position of the sensor) while Y is in the negative. Or rather than forbid the movement, perform it but dodging the Z-home sensor.

Does this sound doable or crazy?

Back to business with my davinci 1.0 loaded with Repetier 0.92 (latest version from master), and I see the following messages in the console when starting a print job from Repetier Host:

23:41:28.613 : X:-33.00 Y:-12.00 Z:0.000 E:0.0000
23:41:28.641 : Unknown command:N153 M107
23:54:11.151 : Unknown command:N187 M107
23:54:11.153 : Printing layer 1 of 60

00:25:31.478 : X:-33.00 Y:-12.00 Z:0.000 E:-3.0000
00:25:31.483 : Unknown command:N6707 M107

00:34:12.212 : X:-33.00 Y:-12.00 Z:0.000 E:0.0000
00:34:12.217 : Unknown command:N70 M107
00:34:21.686 : Unknown command:N100 M107

Don't recall ever seen these before, with 0.91.

Thermistor tables are not correct for AiO boards under 20 degres and give defect temp error

This is for record if anyone has this issue :
After several days without issue - got my left extruder generate several decouple issue
the extruder stick to 223 instead of 225 or 230 and then do some crazy jump to 247 then 210 then decouple
Issue happened after starting printing or when heating randomly.

the sensor connector was loose on the side of X carriage and generate wrong signal - just push it and it clipsed back to original position - then no more issue

Issue pulled from 0.91 https://github.com/luc-github/Repetier-Firmware/issues/10

Start seems reset ramdomly

Just noticed a strange issue with my 1.0 using 0.92. Was doing a print with the bed set at 90C, but over an hour it slowly climbed to 105 and the fail safe disconnected the sensors
Just did a test with the maintenance menu to preheat to table and bed. Ive tried both BangBang and Dead Time. Looking at the Repetier temperature graphs, you can see the extruder temperature is controlled, but the bed temps just slowly keeps rising. The graphs also show, if you look at the option to show power to the extruder and bed, that, no matter what the temperature is, the bed is still being supplied power, even when the temperature is well above the set point ie set temp was 90C , but at 95C the bed was still being powered. Haven't check with previous versions to see if I have the same issue. Maybe Ive accidentally altered something without knowing

Start seems not reading EEPROM data - should be linked to "virtual EEPROM" introduced
it try to read when SD is not ready yet

it does not know where the cleaning fins are on my davinci 1.0 it goes around them before printing. really annoying when trying to print PLA.

still need to get the missing pin allowing to disable the left extruder motor on 2.0A to avoid getting hot
I have modified userpins.h

   #if MODEL==0    
   #define ORIG_E0_ENABLE_PIN     128   
   #else   
   #define ORIG_E0_ENABLE_PIN     124 // no idea if it is good value but can avoid conflict with ORIG_Z_MIN_PIN for 2.0A, another value to try is 85    
   #endif   
   #endif   

now need to test unused pins, I suggest to start by 124, then 85, then all free ones in pinout.xlsx
if left motor is cold when printer is idle, then pin is correct
another solution is to use bgm test sketch to test the pins

it has been reported some USB connection issues with 1.6.0 fixed using 1.5.8
1.6.0 changed several part of code for USB and hardware serial, this could be the root cause

I have a Davinci 1.0 that worked 100% fine on Repetier .91. After upgrading to .92 I am having major issues with the printer crashing mid job. The LCD back light turns off then the printer immediately restarts and disconnects from my computer with no possibility of resuming. Does not happen after specific layers but after about 20 minutes to 45 minutes into the print. Cannot get a full successful print now. Ideas?

Edit: Not a restart loop like others are stating happening every few seconds, but possibly a watchdog issue? I am unfamiliar with the function. Sorry if this is in fact a repeat issue.

Pulled from 0.91 https://github.com/luc-github/Repetier-Firmware/issues/55

Now every Axis have an home flag instead of general one, and all home flags are reset if steppers are disabled, so confidence is 100% home flag are reliable now as no way to override them anymore.

so in several functions should not be necessary to home systematically, but home only when necessary.

Issue:

• I have uploaded 0.92 on to my Davinci 1.0 and the printer isn't recognised in Windows anymore.
• Before the upload, the device showed up as a Bossa... but now it just says Unknown Device.
• I also verified that the firmware has successfully installed on the printer by cycling through the menus on the printer itself.

Steps taken to try to resolve the communication issue:

• I had installed the Sam-ba and Due drivers but none seem to resolve the "Unknown Device" issue.

Any ideas?

I pulled down the firmware this morning and tried to compile in Arduino 1.5.8 and got this error.

Arduino: 1.5.8 (Windows 7), Board: "Arduino Due (Native USB Port)"

HAL.cpp: In static member function 'static void HAL::setupSdEeprom()':
HAL.cpp:69:8: error: 'class SDCard' has no member named 'setupEeprom'
sd.setupEeprom(sdEepromImage, SDEEPROM_SIZE);
^
HAL.cpp: In static member function 'static bool HAL::syncSdEeprom()':
HAL.cpp:78:19: error: 'class SDCard' has no member named 'syncEeprom'
return sd.syncEeprom();
^
HAL.cpp: In static member function 'static void HAL::resetHardware()':
HAL.cpp:257:21: error: 'playsound' was not declared in this scope
playsound (1000,400);
^
Error compiling.

This report would have more information with
"Show verbose output during compilation"
enabled in File > Preferences.

Any clues? I did copy the files usbcore and variants as instructed.

Got Heater Decoupled when doing manual bed leveling, then it go to temperature defect error

Change Pause position from defaut front to Xmin,Ymin, this should avoid joging error if over position is reached and simplify filament change

Status menu display only 3 lines in Z position menu

I've seen this bug several times already, as I'm experimenting with the new E3D hot-end and that involves many test prints that often get cancelled.

I think I can repro it pretty much 100% with the following steps:

• Start a print from RH.
• After a while hit the Kill Print button in RH.
• Keep the extruder turned on to maintain the temp.
• Use the manual extrusion button in RH to extrude some filament.

At this point, rather than extruded filament, the print head starts moving slowly on the Y axis and towards the home position. I haven't tried much but I believe that things get very messy from there, as in some gcode commands no longer do what they should. I remember once that the head ended up moving in the opposite direction than it was commanded.

Add watch dog status in system information

Sorry I cant be more specific. I was @ 2/20 and today went to 2/26 on a Dav1.0. After successful flash machine power cycles every 18-19 seconds. Please let me know if theres anything I can do to help narrow something down.