-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DaVinci AiO Feedback (no scanner) #80
Comments
bonsoir avant tous je tiens a remercié tous ceux qui ont participé a ce projet. bien vu vous avez raison j'ai mesurer et je suis a 6.8mm |
ok ca fait pas mal de questions ca 😄 : Sinon sur AiO il y a une lamelle de metal pour nettoyer la buse ? Je me rappelle avoir lu que les DripBox avaient ete enleves pour laisse la place au scanner, du coup comment l'imprimante nettoie la buse de l'extrudeur? |
bonsoir merci encore.. pour le nettoyage de l'extruder il étais dans le menu sur l'imprimante mais comme elle étais nouvelle je ne l'ai jamais employé il n'y a pas longtemps que je suis sur les imprimantes 3d quand je l'ai acheter j'ai étudié blender et ensuite l'imprimante 3d je cherche a comprendre tous et c'est pas facile mais j'y arrive pour l'instant j'étudie configuration.h Repetier |
pas de soucis pour voltivo je ne sais pas desole, je peux me connecter donc ce n'est pas le forum |
Bonjour, problème 1 : avec le scanner j'ai dans le bas de l'imprimante un plateau tournant et en faisant des essais d'impression, qui ont donné d’ailleurs de bon résultats le lit chauffant a la fin de l'impression c'est abaisser mais j'ai du intervenir car il descendait beaucoup trop bas il a touché le plateau tournant, j'ai vérifié dans le configuration.H mais beaucoup de paramètre et comme je ne tien pas a craché mon imprimante je ne sais ou modifier pour que le lit chauffant ne descende pas si bas . |
bonjour merci pour tous pour la question 2 je vais sur main menu ,sd card,imprim fichier,et la j'ai toujours retour mes fichiers ne sont pas la, il sont pourtant sur la carte sd |
il n'y a aucun fichierqui apparait ? ou il manque juste les votres? |
bonjour et encore merci bien vus car je n'avais pas mis l'extension .gcode c'est pour cela que je ne pouvais pas les voire. slic3 les avais envoyé en binaire sur la carte SD |
oui j'ai mis cette securite pour eviter que l'on efface depuis l'imprimante un fichier comme l'EEPROM virtuelle ou les fichiers du stock FW |
Je viens au nouvelles |
Anyone has optimized setting for AiO ? |
I am using this firmware on my AIO I am not sure what information you need but I certainly am willing to help. I do know that the top sensor doesn't work correctly in this firmware on the aio it is always indicating that it is open even when it is closed. The AIO doesn't have the cleaning box like the others do so I added this gcode to make it clean the tip. G1 Z3 F5000 ; lift nozzle I have my x home as x -33 y as -12 z 0 I have since then put in the e3d-v6 and the z probe doesn't ever work with it. it now just thinks it touches as soon as you start the probe. so I have the auto level turned off. I also now have the filament sensor off since the board isn't guiding the filament. |
Hi thanks a lot for your feedback - really appreciated about cleaning noozle - if no cleaning box what is the action of your code ? is moving x front and back but no cleaner ? do you use the side of bed as the cleaner if I read well ? thanks a lot |
The z did = 0 when it hit the probe plate when I had the original print head. I did have to change the position where it probed since originally it was hitting the screw not the plate. Once I adjusted the x,y position it worked fine for the z probe with the stock hot end. Instead of the cleaning box there is a wiper that is on the side of the bed. I can take a picture of it if you want. I think with the scanner the cleaning box would interfere with the scanner when scanning.. so they removed it and just have the wiper that is on the side of the bed. The wiper that is mounted to the bed isn't to much higher then the top of the bed its about 5mm above the bed height. however the height shifts some when in use the low is about 3mm and the high is 6 mm. I created that code when I had the stock hot end and it is working with my current E3D hot end. My code moves the hot end to the wiper and then makes it move back and forth over it. Which cleans off the excess plastic from the nozzle. You can speed up the moves if you wanted and don't have to go fully back to home going back to about -17 would work but I moved it to the home since I knew that would work. The other reason I created that code is that the first print I did after flashing the stock head had the print head move over the heated bed hold down screws. banging the hot end nozzle across it . I was using slicer and so I put in the custome g-cod after manually using repetier to find the position to wipe the hot end clean. I can bring it fully to 202, but it is almost bottomed out I might be able to go slightly more but I didn't dare to do so. Perhaps the connecter that joins my z axis screw is slightly different in position. then who you got the original feed back from? I am still using the same carriage that came with the printer so the x and y is still the same position ( at least I think it is it certainly seems that way from my tests. My z may have shifted a small amount from stock but its well within the build plate adjustment. so my z is still 0 from the end stop. I obviously can't do the z probing any more. If I knew what wires I needed to hook up in the current setting to make it work I could do that and try it if you want. Currently if I try it, the probe thinks the hot end has touched the plate no z movement and it just moves to the next probe point. The z-probe currently always reads high. |
Yes a picture would be great Thanks again for your feedback |
The top sensor did work correctly when I had the stock firmware. But current firmware always reads it as open. If you need any other photos or want me to test something I will be happy to do so. |
ok thanks so I will add your code to M100 clean nozzle command when will add formal AiO support this week so about z max what is your recommendation ? follow specs=190 ? about top sensor looks like pin is not correct for AiO so need to find out which one is it |
I will build a test sketch to help to find out the right pin |
After this print I am doing right now I will lower the bed to the 202 and take a picture of the clearance for you and post it up here. 202 is really close if I remember right so the 190 is a safer bet. the print has 32 min to go. I figured it wasn't the right pin but I am not sure how to find out what one it is. I can trace it back from the sensor to the mother board if that will tell you anything. |
thanks a lot, or I can provide you a test fw to read different pins values when you open and close top to identify which one is reacting if you have time |
Sure I will be happy to. |
thanks a lot will send it tomorrow |
ok, and not a problem. I still haven't received the email notification from github and I am not sure if that is publically listed any way. so let me know if you need to send it via email and I can give you my email address |
specs says :
so may be A6 is locked and so 101 which should use only Peripheral B |
like change in variant.cpp:
to
I will test if I can reproduce issue first using AiO FW then test variant.cpp modification |
you may disable the test of M42 on sensitive pins on pins.h change to :
this should not generate anymore error - do not forget to restart your printer after test to ensure no command interact with your tests |
??? Erreur lors de la compilation #define SENSITIVE_PINS {0, 1} X_STEP_PIN, X_DIR_PIN,ect... |
ben oui faut tout enlever et ne rien laisser apres le } 😄 #define SENSITIVE_PINS {0, 1} il faut juste: |
ok après le flash redémarrer l'imprimante et la sans aucune commande de ma par le laser encore éclairé a moitié alors j'envoyé command M42 P101 S0 alors laser c'est éteind (plus allumer) |
au demarage la pin est dans un etat disons inconnue - et apparement il y a du courrant passe a l'initialisation de la carte. ce qui est bien c'est que : |
content que ca te fais plaisir mais a moi aussi (projet laser) et il n'est pas logique que le laser éclair a moitié loll maintenant tu sais pas mal de choses aussi |
ca peut aussi etre un bug du core Due je suis en 1.6.7 pour la branche experimentale 0.92.9 et je n'ai pas de soucis, par contre je ne peux pas utiliser le master apparement avec le 1.6.7 ca ne boot pas - il faudrait que je desinstalle l'ide et installe le core 1.6.5 en attendant tu peux chercher quelle entree dans : est l'entree qui pose probleme - en les rajoutant une par une, ou 2 par 2 ou en travaillant par dichotomie genre si : si c'est OK alors rajouter la premiere moitiee de la partie que tu n'as pas mis quand c'est OK petit a petit tu vas isoler l'entree qui genere le conflit une fois trouvee tu remets tout sauf celle qui pose soucis pour confirmer qu'il n'y a que celle la |
bon courage 😄 |
#define SENSITIVE_PINS {0, 1, X_STEP_PIN} M42 P101 S0 Set output: 101 to 0 #define SENSITIVE_PINS {0, 1, X_DIR_PIN} M42 P101 S0 Set output: 101 to 0 #define SENSITIVE_PINS {0, 1, X_ENABLE_PIN} M42 P101 S0 Set output: 101 to 0 #define SENSITIVE_PINS {0, 1, X_STEP_PIN, X_DIR_PIN} M42 P101 S0 error #define SENSITIVE_PINS {0, 1, X_DIR_PIN, X_STEP_PIN} M42 P101 S0 error #define SENSITIVE_PINS {0, 1, X_STEP_PIN, X_DIR_PIN, X_ENABLE_PIN} M42 P101 S0 error #define SENSITIVE_PINS {0, 1, X_STEP_PIN, X_ENABLE_PIN} M42 P101 S0 error #define SENSITIVE_PINS {0, 1, X_DIR_PIN, X_ENABLE_PIN} M42 P101 S0 error voila il accepte 1 mais pas 2 |
houla c'est pas coherent ca |
ben non c'est pour ca que je te le donne |
Je vais faire un ide 1.6.5/ DUE 1.6.4 pour verifier le comportement vs 1.6.8/Due 1.6.7 |
ici arduino 1.5.8 c'est de ca que tu parles |
Ok je ferais un 1.5.8 alors - c'est meme plus simple pour recapituler a par ce bug : |
oui M42 P2 S255 pour la pin 138 MCU: laser1 M42 P101 S255 M42 P26 S255 plateau scanner désactivé |
Ok je vais rajouter ca dans le setup alors - bravo belle trouvaille |
mais de rien Sir |
Dsl - je vais ajouter l'initialisation des pins cette semaine - j'ai ete occupe sur d'autres choses I was not able to revert to 1.5.8 on my dev PC - cannot launch it - I need to find a clean PC to check if the 101 pin issue is due to core as cannot reproduce it with 1.6.7 |
Is there any guide on using 1.6.7 you know of? I used 1.5.8 as there was a straight forward step by step guide to follow. |
Not yet, I am currently working on new release based on repetier 0.92.9 using IDE 1.6.8 and Due 1.6.7, will add better wiki page to explain how to setup all 1.6.8 use board manager to add due support : https://learn.adafruit.com/add-boards-arduino-v164 |
here a video : https://www.youtube.com/watch?v=ogXQIYnI8qE |
file locations are in C:\Users\AppData\Local\Arduino15 - steps are same than 1.5.8 |
OK thanks for the info. I guess my printer has been working fine so I have never really looked. However I made lots of changes but had very little experience of git back then, not much more now! I need to fork the repo to make it easier to manage my changes. What are the advantages of using 1.6.7 ? |
Also, is it time to close this thread and start a new one with a reference back to this? It is a bitch to navigate now! |
Yes plan to close it an create new one |
Add better default setting for AiO, bed size, plate positions, homing position, etc
The text was updated successfully, but these errors were encountered: