Jonathan Faivre

oui c'est la ou est le pb: 250000 en baudrates et je suis arrivé a faire bouger la tete 1 seul fois et aprés plus rien. je doit reconnecter l'usb pour pouvoir faire un autre mouvement.

Bonjour aprés quelque année je viens de ressortir ma discoeasy200 des cartons, je me rend compte qu'elle ne bouge plus et impossible de mettre a jour le firmware avec dagomapp "la mise a jour a connu une erreur". aprés quelque recherche je me rend compte que ca peut etre le bootloader de la carte MKS base 1.5. je me lance donc avec un tuto a connecter mon RPI en ISCP pour flasher ma carte. succée je suis arrivé a mettre a jours ma disco. j'arrive donc a imprimer ce que j'ai mis sur ma carte SD. je me rend compte que le calibrage n'est pas bon, donc je lace dagomapp "reglage parfait" et la impossible de faire bougé les tete. je lance pronterface : Connecting... start Printer is now online. echo: External Reset Marlin 1.1.0-RC6 echo: Author: Dagoma echo: Last Updated: 2020-02-06 echo: Last Compiled: Apr 6 2020 echo: Free Memory: 3776 PlannerBufferBytes: 1232 echo:Hardcoded Default Settings Loaded echo:Steps per unit: echo: M92 X80.00 Y80.00 Z2560.00 E98.00 echo:Maximum feedrates (mm/s): echo: M203 X500.00 Y500.00 Z4.00 E170.00 echo:Maximum Acceleration (mm/s2): echo: M201 X3000 Y1000 Z20 E10000 echo:Accelerations: P=printing, R=retract and T=travel echo: M204 P3000.00 R3000.00 T3000.00 echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s) echo: M205 S0.00 T0.00 B20000 X20.00 Z0.40 E5.00 echo:Home offset (mm): echo: M206 X0.00 Y0.00 Z0.00 echo:PID settings: echo: M301 P32.48 I6.40 D41.25 C100.00 L20 echo:Filament settings: Disabled echo: M200 D3.00 echo: M200 D0 echo:Z-Probe Offset (mm): echo: M851 Z0.00 echo:SD init fail echo:Rev. dans XY av.Z Attempted to write invalid text to console, which could be due to an invalid baudrate Attempted to write invalid text to console, which could be due to an invalid baudrate echo:Unknown command: "0.1" Attempted to write invalid text to console, which could be due to an invalid baudrate echo:Unknown command: "-0.1" echo:Unknown command: "Z-10" Attempted to write invalid text to console, which could be due to an invalid baudrate Attempted to write invalid text to console, which could be due to an invalid baudrate Attempted to write invalid text to console, which could be due to an invalid baudrate echo:Unknown command: "0.1" Attempted to write invalid text to console, which could be due to an invalid baudrate echo:Unknown command: "1" Attempted to write invalid text to console, which could be due to an invalid baudrate Attempted to write invalid text to console, which could be due to an invalid baudrate echo:Unknown command: "-0.1" Attempted to write invalid text to console, which could be due to an invalid baudrate Attempted to write invalid text to console, which could be due to an invalid baudrate Attempted to write invalid text to console, which could be due to an invalid baudrate Attempted to write invalid text to console, which could be due to an invalid baudrate Attempted to write invalid text to console, which could be due to an invalid baudrate echo:Unknown command: "0.1" Attempted to write invalid text to console, which could be due to an invalid baudrate echo:Unknown command: "0.1" Attempted to write invalid text to console, which could be due to an invalid baudrate j'arrive a faire bouger la tete 1 seul fois puis plus rien je doit debrancher puis rebrancher disconnect/connect. je lance curabydagoma: Baudrate test retry: 1 Send: M105 Baudrate test retry: 0 Send: M105 Trying baudrate: 19200 Send: M105 Baudrate test retry: 4 Send: M105 Baudrate test retry: 3 Send: M105 Baudrate test retry: 2 Send: M105 Baudrate test retry: 1 Send: M105 Baudrate test retry: 0 Send: M105 Trying baudrate: 9600 Send: M105 Changing monitoring state from 'Detecting baudrate' to 'Closed' Changing monitoring state from 'Closed' to 'Error: No more baudrates to test, and no s...' Connection closed, closing down monitor Changing monitoring state from 'Offline' to 'Opening serial port' Connecting to: /dev/cu.usbserial-A904QKGC with baudrate: 115200 (fallback) Connected to: Serial<id=0x106407b90, open=True>(port='/dev/cu.usbserial-A904QKGC', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=3, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor Changing monitoring state from 'Opening serial port' to 'Detecting baudrate' Recv: n&X??_r67??2]A59A?f??oH|?X??]a}]C?$-q??r?JAa?6?(N@?? Recv: JQ/ Recv: ?~Bz Recv: ?]q???7??%I?'???Ma?]Am~6?Q7f?\=^@?6f?h%?JA??JA??ZC?p%f??0?]a?H?Qf?J ?A???Kr??kB?zr?P?:&2/??]B?M`?z2J ?AAQ?JB?a?JB?: |Aa?]B?f66jO.XA??6?p|B?A??AQ?JB??AQf?\?a?&"???W(?hQ?:a??HhT?62??H?,^?(ae?*,~?(p?hTp{&2??&l Recv: r?J ?????jB?JB??JA?$h et impossible d'utilisé arduino IDE en USB je ne comprend pas trop le pb je pense que ca viens de la connection usb de ma MKS base 1.5 mais je ne sais pas comment faire pouvez vous m'aider ?

bonjour je suis un petit nouveau et j'aimerais en apprendre plus sur l'impression 3D j'avais recue pour mon anniversair un discoeasy200 en kit que j'ai monté j'ai imprimé deux object puis c'etait la panne. puis j'ai eu deux enfants et la plus le temps de m'en occupé. j'ai enfin ressortie la bete et c'est la que je me suis rendue compte qu'elle ne marchai plus. du coup je viens chercher de l'aide sur le forum bisous a tous