Anycubic Photon Printer Owners 造訪社團 » g code

原文網址 Artur Kawa
2019-05-14 10:08:05

Photon Resin Calibration 1.2

(Link: https://github.com/altLab/photon-resin-calibration )

I looked over the files. There is a "test-mode.gcode" - file which executes gcodes on the Photon. After the test, the user has to execute "print-mode.gcode" on the Photon, to remain to normal printing condition.

Here is what I do not understand:

In "print-mode.gcode" are the following lines:

### ### ###
;(Acceleration)
M8008 I700
; The higher the acceleration the faster the overall print time. Too high risks losing steps.
### ### ###

Command "M8008" is setting parameter "I700".

And here it is: Some Photon firmwares includes such parameters files to set standard parameters on Photon after firmware update.

All firmwares i could see, uses the parameter "I900" for the "M8008" command. That is so in firmware 4.2.5 and in firmware 4.2.12 too.

So why does the "Photon Resin Calibration"-Utility sets this command back to "I700" instead of to "I900".

Do I see it right, that the "print-mode.gcode" should / could be changed, so that to command "M8008" parameter "I900" is set?

What is your opinion to this matter, Vinicius Silva ?

I would like to use the "Photon Resin Calibration" Utility and not knowing about changing the "print-mode.gcode" or not?

Thank you for your answer.

Artur

翻譯年糕

Vinicius Silva
2019-05-14 10:11:42

Vinicius Silva
2019-05-14 10:11:45

Artur Kawa
2019-05-14 10:14:07

Vinicius Silva
2019-05-14 10:15:03

Artur Kawa
2019-05-14 10:15:18

Vinicius Silva
2019-05-14 10:16:10

Artur Kawa
2019-05-14 10:18:35

Artur Kawa
2019-05-14 10:24:43

Vinicius Silva
2019-05-14 10:24:44

Artur Kawa
2019-05-14 10:25:57

Vinicius Silva
2019-05-14 11:01:47

Vinicius Silva
2019-05-14 20:16:22

Artur Kawa
2019-05-14 22:13:12

Vinicius Silva
2019-05-14 22:16:31

Vinicius Silva
2019-05-14 22:17:02

Artur Kawa
2019-05-15 01:06:12

Raphaël Gerber
2019-05-15 15:37:48

原文網址 David Nicholls
2019-05-13 14:25:45

Can anyone right me a short gcode script to mix the vat?

Just want a series of 10 homes/+10mm moves of the build plate to mix the vat...

翻譯年糕

Blake Moody
2019-05-13 14:29:19

Dan Cannon
2019-05-13 14:43:16

David Nicholls
2019-05-13 14:49:17

Dan Cannon
2019-05-13 14:50:51

Chris Visser
2019-07-15 15:27:01

原文網址 Aaron Chambers
2019-05-12 02:15:22

Hey all, random question- when using chitubox and selecting the photon profile the “Gcode” box is gone. How do you get it back to be able to add the gcode to turn the fan off ?

翻譯年糕

Clinton Hoines
2019-05-12 02:17:34

Aaron Chambers
2019-05-12 02:18:17

Clinton Hoines
2019-05-12 02:21:22

Clinton Hoines
2019-05-12 02:22:49

Aaron Chambers
2019-05-12 02:23:29

Clinton Hoines
2019-05-12 02:24:57

Aaron Chambers
2019-05-12 02:25:16

Clinton Hoines
2019-05-12 02:25:30

Chad Elstad
2019-05-12 02:49:37

Artur Kawa
2019-05-14 04:54:31

Thorsten Lüpertz
2019-10-21 01:32:55

Thorsten Lüpertz
2019-10-22 23:56:54

原文網址 Flint Read
2019-05-09 23:15:44

Ok All you new Phontonsters out there here's a tip that's not in the manual (You did read the manual, right?)

If you mess up an exposure setting in your slice It's not too late.

Just hit the cog Icon in the menu and fiddle with the settings (you need to be quick, do it while the plate is on it's way up for maximum time.)

And hey presto settings fixed even though it was already printing and in g code form.

That is all. Now go make some cool stuff.

翻譯年糕

Nate Nelson
2019-05-09 23:22:27

John Stanford
2019-05-10 09:01:29

Chad Elstad
2019-05-11 22:33:57

原文網址 Bryan Golden
2019-05-08 21:00:36

I've seen so many posts about continually failed parts lately. Until yesterday I was one of them.

I was attempting to change the settings in the g-code to slow the lift speed when I realized the current website firmware release has a typo in the parameter file.
M8015 P1 and M8016 P2
SHOULD BE
M8015 T1 and M8016 T2
(The number after the last letter is a speed setting, yours may be different)

These two settings control the peel and lift speed which is why, if you have updated the firmware with your new printer, it's ripping off the plate at high speed and supports are failing.

HOW TO FIX: search for the GitHub repository within the Facebook group, download firmware 4.2.5 and follow the install instructions.

Also: download the "Updated factory default translated g-code" from the GitHub. It will explain what all the g-code means and you can use it as a direct replacement for the Chinese g-code parameter file in the firmware by replacing it on your firmware USB stick.
To change any setting at any time, all you have to do is open it in any text editor such as note pad, then save and print the gcode file on the photon (you will have to reset your zero every time you do).

SECONDLY: I sanded my built plate and realised it was 1-2mm bowed on the perimeter from the casting process (proof pictures attached). This absolutely does not qualify as "flat" and afterwards I have no parts coming off the build plate.

If after you sand your plate flat (using a piece of sandpaper placed on a sheet of glass) you are still having problems, replace your FEP film and wipe a thin layer of pure PTFE grease (no rust inhibitors like would be in bike chain lube) on the resin side of the film. This will solve all sticking issues during normal exposures and increase overall toleraces by reducing stresses. This will not affect the resin performance as PTFE is highly stable.

LASTLY: Properly tighten your Z axis rail! Search on YouTube for a how to video. Mine shipped much too loose and I wasted time getting less than expected resolution. I now have zero play and no clicking when I wiggle the plate.

I'm shocked that this thing has the good reviews that it does, it's been a nightmare. But then again most of us bought it for the pricetag, post engineering is to be... expected?

翻譯年糕

Bob Ivan
2019-05-08 21:13:50

Hoffman Panameño
2019-05-08 21:25:07

Simon Stedman Ingerson
2019-05-08 21:28:30

Ben Mueller
2019-05-08 21:30:46

Hoffman Panameño
2019-05-08 21:32:01

Ben Mueller
2019-05-08 21:32:35

Andy Eakin
2019-05-08 21:42:47

Tom Allen
2019-05-08 22:00:37

Jeff Putney
2019-05-08 22:01:36

Bryan Golden
2019-05-08 22:07:17

Zalrohg Lekgolo
2019-05-08 22:15:41

Bryan Golden
2019-05-08 22:18:34

Alwin Chan
2019-05-08 22:29:40

Jeff Putney
2019-05-08 22:36:08

Alex Clarke
2019-05-08 22:36:47

Bryan Golden
2019-05-08 23:17:28

Sen Kun
2019-05-08 23:21:42

Alex Clarke
2019-05-08 23:38:04

Angelus Nox
2019-05-09 02:37:08

Bryan Golden
2019-05-09 02:39:45

Shane Graber
2019-05-09 04:18:42

Jaime Blalock
2019-05-09 04:22:02

Joshua Byerly
2019-05-09 12:04:43

John Smith
2019-05-09 13:38:31

Richard Ashley
2019-05-09 15:00:23

Artur Kawa
2019-05-10 06:29:27

Bryan Golden
2019-05-10 09:47:52

Bryan Golden
2019-05-10 09:49:54

John Smith
2019-05-10 11:25:45

Hoffman Panameño
2019-05-10 12:24:37

Artur Kawa
2019-05-10 22:15:14

Bryan Golden
2019-05-10 23:24:15

Artur Kawa
2019-05-10 23:35:57

Vinicius Silva
2019-05-13 05:41:09

Vinicius Silva
2019-05-13 05:42:23

Artur Kawa
2019-05-13 05:50:17

Vinicius Silva
2019-05-13 08:05:35

原文網址 Juan Camilo Herrera
2019-04-26 03:04:03

Who has the .gcode to turn off the print chamber vent to reduce useless noise? Who has the .gcode to turn off the print chamber vent to reduce useless noise? 翻譯年糕

Brian Morin
2019-04-26 06:42:59

原文網址 David Nicholls
2019-04-23 07:46:18

How can I send a single "m" gcode command? Can I just create a plain txt file with a .gcode extension? How can I send a single "m" gcode command? Can I just create a plain txt file with a .gcode extension? 翻譯年糕

Lane Taylor
2019-04-23 07:52:03

Dustin Scott
2019-04-23 08:09:19

原文網址 Zach Kirk
2019-04-01 02:40:55

UPDATE: Thank you David McGyver for sharing your custom resin mix gcode file. I've uploaded a video demonstration of it in action. Works great. And thank you Sen Kun for the original mix file which also works great.

Original post: Is there a safe way to stir the resin remaining in the vat without risking any scratches to the FEP?

翻譯年糕

Stefan Giudici
2019-04-01 02:42:19

Sean O'Hayer
2019-04-01 02:44:58

Todd Jones
2019-04-01 02:46:07

Sen Kun
2019-04-01 02:46:46

Marvel Mendoza
2019-04-01 02:47:21

Mark Wardle
2019-04-01 02:53:24

Matt Solomon
2019-04-01 03:12:28

Patrick Nixon
2019-04-01 03:20:11

Zach Kirk
2019-04-01 03:25:46

Zach Kirk
2019-04-01 03:26:34

Jean-François Meloche
2019-04-01 03:44:40

Curt Pangracs
2019-04-01 03:46:11

Reynald Lorenzo Dalangin Ilagan
2019-04-01 03:50:02

Matt Paul
2019-04-01 03:50:54

Matt Paul
2019-04-01 03:51:29

Kaylee Rivera
2019-04-01 04:20:44

Richard Burrell
2019-04-01 04:34:31

Zach Kirk
2019-04-01 04:35:46

Sen Kun
2019-04-01 04:47:33

Vinicius Silva
2019-04-01 04:49:34

David McGyver
2019-04-01 05:29:40

David McGyver
2019-04-01 05:33:38

Zach Kirk
2019-04-01 06:00:11

Sen Kun
2019-04-01 06:05:34

Violet Fer
2019-04-01 06:07:49

Sen Kun
2019-04-01 06:09:53

Zach Kirk
2019-04-01 06:12:27

Zach Kirk
2019-04-01 06:13:09

Sen Kun
2019-04-01 06:15:22

Zach Kirk
2019-04-01 06:16:29

Craig Burrows
2019-04-01 06:43:26

David McGyver
2019-04-01 07:19:37

Sogeth Grimley
2019-04-01 10:03:43

Kevin Boogaard
2019-04-01 21:01:54

Zach Kirk
2019-04-01 21:12:07

Kevin Boogaard
2019-04-01 21:13:27

Zach Kirk
2019-04-01 21:15:21

Kevin Boogaard
2019-04-01 21:16:04

Derek Reihe
2019-04-02 02:45:56

Kevin Boogaard
2019-04-02 02:50:38

Don Roberts
2019-04-07 07:25:22

David McGyver
2019-05-25 21:19:05

原文網址 Ocie Ward
2019-03-27 13:38:47

Howdy, y’all. I have a new Photon S, and I can’t get it to print. I have a lot of FDM experience, but this is my first resin printer. I will contact Anycubic tomorrow, but I figured I’d post here to see if anyone has had a similar experience:
Whether I slice in the Photon slicer or ChiTuBox (exporting to filetype .photons), I have the same problem. The sliced file looks fine if I re-open it in the slicer - the layers have images that step through correctly. When I load the files on the printer, I see them correctly in the print screen, including the little 3D thumbnail image. But when I print any of them, I get zero curing. I confirm that the UV lamp is coming on correctly for the amount of time per layer that I set in the slicer - I can see it through the crack in the case above the UI screen. But the LCD is fully masked - the whole screen is activated to block the UV. So no curing happens. This happens with every file I slice in either slicer. This same thing happens with the PHOTON.photons presliced lattice cube that came with the printer. Also, I think the image on the UI is supposed to show an image of the mask for each layer, right? Well it shows a solid black layer each time, so that and the LCD are in sync.

Additional information:
- build plate is level and zero’d. I tried both the paper method and the Flint Read method. Anyway, this is irrelevant because the problem is with the mask and not with the leveling.
- the LCD test is successful. I see the rectangle. It just doesn’t work right when reading a sliced file.
- I tried using the Photonsters sliced file editor to see if I could figure out what is wrong inside the .photons files. But the tool only works with .photon and not with .photons files.
* another possibly important piece of info is that after I run a print, whether I cancel it or let it run to completion, the printer UI freezes on the print screen. The UI screen is unresponsive and I have to flip the power switch.
- power cycling the printer will reset things, but I still have the same issue the next time around.
- I checked the cat to see if I somehow missed a protective liner sheet that was on the FEP and somehow blocked UV, but no. Also, I can see that the LCD is masking every pixel when the UV lamp comes on.

* one idea - in order to export to .photons from chitubox, I had to set up a new generic printer config from scratch. I set all the parameters to be the same as the settings that come up if you select a default Photon config. The only exception being that on the advanced tab on a new config, there are gcodes defined so you can make your files talk correctly to your given printer. The default Photon config does not even show these gcodes, so I have no idea of what is automatically populated for a generic printer config. I left them as they were auto generated and sliced the file. Then, the FIRST sliced file I ran on the printer was one that I sliced with this config in chitubox. I wonder if those gcodes were wrong, and were saved to the printer EEPROM. Now perhaps every print that I run, even if sliced in the photon slicer, doesn’t work because there’s a bad gcode for “activate lamp” or something saved in there. That doesn’t actually make sense with how I understand gcode to work, but I’m grasping at straws here. Actually, do these Photon printers even use gcode?

Anyway, sorry for the novel, but I’m pretty frustrated with my resin experience so far. At least now I figured out that the mask is the issue - I just need to figure out WHY it’s not actually following the layer images in the sliced file...

翻譯年糕

Stefan Giudici
2019-03-27 13:47:10

Ocie Ward
2019-03-27 13:49:53

Ocie Ward
2019-03-27 13:51:19

Ocie Ward
2019-03-27 13:51:51

Jeremy Lauzon
2019-03-27 14:17:18

Graham Leek
2019-03-27 14:34:47

Sen Kun
2019-03-27 14:35:44

Ocie Ward
2019-03-27 14:53:50

Jeremy Lauzon
2019-03-27 14:56:35

Björn Ståhlnacke
2019-03-27 14:57:38

Ocie Ward
2019-03-27 15:00:26

Sen Kun
2019-03-27 15:01:43

Ocie Ward
2019-03-27 15:03:57

Ocie Ward
2019-03-27 15:04:25

Jeremy Lauzon
2019-03-27 15:04:27

Ocie Ward
2019-03-27 15:05:30

Kevin Boogaard
2019-03-27 16:10:55

Dylan Hancox
2019-03-27 16:25:05

Norbert Kupeczki
2019-03-27 17:25:22

Adrian Petre
2019-03-27 17:52:16

Patrick Nixon
2019-03-27 18:55:44

Bradley VanScoyk
2019-03-27 19:19:08

El Ner Endem
2019-03-27 20:30:03

Mike Roof
2019-03-27 21:38:28

Ocie Ward
2019-03-27 21:50:54

Ocie Ward
2019-03-27 21:53:57

Ocie Ward
2019-03-27 21:55:01

Ocie Ward
2019-03-27 22:26:46

Ocie Ward
2019-03-27 22:44:09

Ocie Ward
2019-03-28 00:02:31

Piet Hoton
2019-03-28 00:31:37

Ocie Ward
2019-03-28 00:51:39

Ocie Ward
2019-03-28 01:20:10

Ocie Ward
2019-03-28 01:23:59

Sen Kun
2019-03-28 05:55:30

Ocie Ward
2019-03-28 06:04:22

Jeremy Lauzon
2019-03-28 06:06:01

Alex Varley
2019-03-28 06:07:59

Ocie Ward
2019-03-28 06:13:21

Stefan Giudici
2019-03-28 06:21:32

Ocie Ward
2019-03-28 06:27:47

Ocie Ward
2019-03-28 06:30:49

Sen Kun
2019-03-28 06:39:36

Ocie Ward
2019-03-28 06:52:21

Alex Varley
2019-03-28 15:32:55

Ocie Ward
2019-03-29 04:05:08

Patrick Nixon
2019-03-29 04:49:25

Sen Kun
2019-03-29 13:22:16

Ocie Ward
2019-03-29 13:33:37

Sen Kun
2019-03-29 14:40:13

Ocie Ward
2019-03-29 21:44:56

Ocie Ward
2019-03-30 02:14:38

Ed Wilson
2019-03-30 02:27:19

Jeremy Lauzon
2019-03-30 02:29:57

Ocie Ward
2019-03-30 02:51:38

Ocie Ward
2019-04-30 06:36:37

Ocie Ward
2019-04-30 06:36:46

Sen Kun
2019-04-30 12:10:49

Ocie Ward
2019-05-01 01:29:56

Jose Elizondo
2019-05-03 11:35:27

Ocie Ward
2019-05-03 11:55:57

Mark Wardle
2019-05-03 12:02:11

Ocie Ward
2019-05-03 12:04:47

Ocie Ward
2019-05-17 03:07:37

原文網址 Jarrod Smith
2019-03-22 01:12:30

I just updated firmware to 4.2.12 and started a print. As others have reported, wow the z-axis is sooo much quieter. I also believe the font that shows elapsed/remaining/total estimated print time is a lot smaller. or maybe there is less contrast? I have a lot of trouble reading that little guy now! Firmware devs, have mercy on the old folks please. ?

My method (do this at your own risk, I have not completed a successful print yet. Posting this hoping the experts will sanity check it):
1: Extract all files to the root of a known good USB stick.
2: Plug the stick in and power the machine up. I believe this flashes the update.LCD file.
3: Print the 1-fpga27_V22_101.bin file.
4: Print the 4-parameter.gcode file.
5: Home and re-level the build plate.
6: Profit!

翻譯年糕

Sen Kun
2019-03-22 01:39:56

Giuseppe La Capra
2019-03-22 02:07:03

Jarrod Smith
2019-03-22 02:08:22

全不選發文排行