Vai al contenuto
  • Benvenuto!

     

Messaggi raccomandati

I need to add that there could still be issues with ZCode from Z-Suite 1.6.x at least when trying to set the fan speed in raft layers.
Problem is that Z-Suite 1.6 sits somewhere in the middle between the older ZCode style without any layer information and the newer ones with layer commands for each layer (including raft layers) since Z-Suite 1.6 creates layer commands only for model layers (not for raft layers).

Now ZTool still tries to autodetect these layers to be able to display them in the preview. As a side effect, a (theoretical?) fan command within a raft layer would be stored when exporting the fan speed profile. But as there are no layer commands for the raft and ZCode from v1.6 is handled by the algorithm for the newer ZCode format, changing the fan speed within the raft will fail. I'm not sure if I'm motivated to rework the fan speed loading again to add another workaround. Most probably nobody will ever notice this glitch anyway.

  • Like 1
Link di questo messaggio
Condividi su altri siti
  • Risposte 41
  • Creato
  • Ultima Risposta

Miglior contributo in questa discussione

Miglior contributo in questa discussione

Messaggi Popolari

As some of you might know, before RaftAway and g2z there was ZDump which I started to develop in spring 2016. It started as a way to dump and analyze ZCode (hence its name) but soon became a tool to p

About fan speed: I'm still trying to understand your use case, i.e. if you really want to override the given values completely. Like there's already the possibility to limit values and also scaling th

Uploaded a new version 1.0.3 that allows exporting/importing fan profiles to/from simple comma separated text files ("*.fpr"). First line is an identifier, followed by lines in the format &lt

Immagini Pubblicate

Actually my computer have some problem, can't run 1.6.x, so I didn't test 1.6.x.

Z-Suite is very weak and too many limitation, I do more S3D and Ztool test recently, it's very powerful, especially editing g-code can make everything, I really enjoy it, so I think good convert function is more useful and important. :grin:

Link di questo messaggio
Condividi su altri siti

Without checking in detail, I would assume this is due to a certain difference of where S3D defines the start of the layer and where my parsers does.
Since I don't want to rely on layer comments (and can't in certain conditions), my import algorithm detects Z movements and adds a ZCode layer command before the Z move that moved up to the new layer. So if S3D adds a fan command just before that Z move, my algorithm will instead define it as last command of the previous layer.
Which is I think exactly what happens here.

Secondly, the fan speed and Z positions displayed in certain views have a slightly different meaning.
So if the Z move didn't happen yet when the fan command is requested, the Z position is correct since it still applies to the last layer - even if this is the very last command (from my algorithm's point of view).

The fan graph displays the maximum Z position reached for each fan command.
In the preview window the upper Z/Fan are for the actual command. Since the command slider is at 100% by default, this is the Z position and fan speed after the last command for this layer.
The line shows the maximum fan speed as "Fan:" and the maximum Z position as "Z:" for the given layer.
So if the fan speed command is interpreted as last command of the previous layer instead of the first command of the current layer, this would explain the above display:
In layer 4, the 50% command is the last command and also the maximum value, so both values are ~50%
In layer 5, the fan speed at the end of the layer is 0% (so it's 0% at the beginning of layer 6), but the maximum is still 50% since this is the entry value.

BTW: admittedly, displaying "/15" if there are really 16 layers seems a bit confusing. It's means as the maximum value though, not as the number of layers.
Also note that Z-Suite > 1.6 creates negative layers for the raft. So the number of layers is e.g. 8 increments higher than the maximum layer.
In this case displaying "182/200" for the uppermost layer seems much worse than displaying "200/200" for the maximum even if there are really 208 or so layers in sum.

Link di questo messaggio
Condividi su altri siti
  • 4 settimane dopo...
  • 4 settimane dopo...

1.0.6
Fixed issue with empty retraction commands created with newer versions of Z-Suite.
Improved ZCode support for Inventure.


1.0.7
Added option to increase distance between raft and first model layer.
Separate speed setting for 1st model layer.
Fixed: export dialog didn't keep/display setting from previous export.
Fixed: export dialog didn't offer PLA and ASA profiles and therefore changed profile name to ABS.

 

Link di questo messaggio
Condividi su altri siti
  • 7 mesi dopo...
  • 2 mesi dopo...

Admittedly, I have been very lazy regarding Zortrax topics lately. So I haven't looked into newer versions of ZSuite etc.
Anyway, are there any issues I'd need to have a look at other than maybe displaying new materials correctly?

As a side note, I also haven't looked much into "ZCODEX". At first look, it's simply a Zip archive which still contains more or less normal ZCode data named "ZCodeData" plus a backup (?) named "ZCodeOriginalData". The header was removed and replaced by some text files (UserSettingsData, ZCodeMetadata). Then there's one file named "ConfigurationData" which is most probably crypted. I kinda assumed they would take the chance to crypt the whole ZCode file. For some reason (RAM size  probably), I guess they decided to just crypt one smaller file instead to certify the uploaded ZCode. Well, that's just my guess. I would suspect though that a m200 Plus wouldn't accept changed ZCode without a new "ConfigurationData".

Regarding ZCode -> G-Code: ZDump could do that quite some time ago but I decided to deactivate the code for ZTool mainly not to provoke Zortrax as they made very clear that they wouldn't tolerate publishing details about ZCode and a working Z->G converter would make it very easy to reverse engineer ZCode. Admittedly, I also thought the created G-Code would be unusable on other printers. It came to my attention lately that some ZDump testers really did that. Still I think that this wouldn't be a feature for normal users (which includes myself).

Link di questo messaggio
Condividi su altri siti

Unrelated to new ZSuite or firmware, but as I also looked into a bug report I received quite some time ago, there's a new version today:

1.0.9c
Fixed a crash resulting from GCode which uses a negative retations value directly after setting the extrusion value to 0.
Also fixed a command index issue in this context which could lead to removal of the wrong command in certain situation when resetting the extrusion value.

BTW: Couldn't see any new materials at least for the m200.

Link di questo messaggio
Condividi su altri siti
  • 4 settimane dopo...

I released a new version 1.1.0 of ZTool which can be found in the usual dropbox folder:
https://www.dropbox.com/sh/91jdv24taxeayof/AACiBRHvH_d0FjRbo0cKEkwOa?dl=0

The main features are support for the ZCodex format used by the M200 Plus and export of G-Code.
Please read the according sections ("Notes about the ZCodex format" and "G-Code export") in the RTF manual for details.

Anyway, as the support for ZCodex made it necessary to rework some internals, there's the chance I messed things up.
As a result, I'd consider version 1.1.0 to be somewhat experimental. Therefore, the stable version 1.0.9c is still available in parallel.
Besides, I still haven't found a volunteer with an M200 Plus. So currently I can only say that Z-Suite opens ZCodex files created by ZTool without complaining (and vice versa).
I'd be happy to hear from an M200 Plus owner if the printer accepts and prints e.g. ZCode converted to ZCodex (which I'd consider the safest scenario).
Note that it's probably a good idea to use an offset of 170µm when converting from ZCode to ZCodex due to different initial Z heights of M200 and M200 Plus. See RTF manual for details.

Also note that I currently don't plan to release a "g2z" version that supports ZCodex.

Link di questo messaggio
Condividi su altri siti

Relased ZTool 1.1.1

Raft removal wasn't working with generic ZCodex files (as the extrusion value is not reset to 0 by the slicer for the M200 Plus when retracting). The raft removal mechanism should now automatically use layer changes instead (note that it was originally designed before the layer command even existed).
Added some comments like "support", "raft" etc. in the exported G-Code. It's not perfect as it doesn't filter out futile/double comments but then again, S3D doesn't either. This also improves import of these exported G-Code files into ZTool a bit.

Link di questo messaggio
Condividi su altri siti
  • 1 mese dopo...
  • 1 mese dopo...

1.1.3
In pevious versions, speeding up the 1st layer didn't work after removing the raft. Background was that the initial skirt (used to start extrusion outside the raft) was patched from Raft into Support and then the search for the search for the (end of) the 1st player stopped immediately when reaching the (patched) skirt. Now the skirt is patched into "1st Layer Support", so it's identified as part of the 1st layer (and thus also sped up).
Note that if the raft was removed with an older version than 1.1.3, speeding up the 1st layer will still not work.
1.1.4
Raft removal kept a part of the raft when there was no initial skirt. This only happened for very large prints where Z-Suite didn't create an initial skirt. Added workaround that should work for all Z-Suite versions > 1.7.x.
1.1.5
Fixed a bug in raft removal for ZCodex format. Due to internal handling of the differential extrusion values, removing the raft caused a massive overextrusion at the first extrusion after the (removed) raft.

Link di questo messaggio
Condividi su altri siti
  • 4 mesi dopo...

Hi there people! Thanks for this fantastic tool👍 I would like to know how to avoid the initial retraction after the mini-skirt. It makes my prints with the bottom layer incomplete, because of the "ghost" printing as long as the retraction do. (using "no raft" and printing on custom glass bed) thanks! 

Link di questo messaggio
Condividi su altri siti
  • 2 mesi dopo...
  • 7 mesi dopo...

Do anyone else have problems using bigger GCode files? I'm currently testing a 50MB GCode-file and ZTool throws a Nullpointerexception while trying to save and g2z just says the temperatures were out of range. ZTool also doesnt recognize the temperature right.

When I'm just using the beginning of the GCode, both works again and they are reading the temperature right.

Link di questo messaggio
Condividi su altri siti

Partecipa alla conversazione

Puoi pubblicare ora e registrarti più tardi. Se hai un account, accedi ora per pubblicarlo con il tuo account.

Ospite
Rispondi a questa discussione...

×   Hai incollato il contenuto con la formattazione.   Rimuovere la formattazione

  Sono consentiti solo 75 emoticon max.

×   Il tuo collegamento è stato incorporato automaticamente.   Mostra come un collegamento

×   Il tuo contenuto precedente è stato ripristinato.   Pulisci editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Crea Nuovo...