Welcome! Log In Create A New Profile

Advanced

BUG: export-settings affect ALL profiles

Posted by MarcusWolschon 
BUG: export-settings affect ALL profiles
January 31, 2010 03:13AM
When I changed the export-settings of the profile milling-end mill
this also changes the export-settings of the profile extrusion->repman
and vice versa.

Verson of Skeinforge: 2010-01-30

PS:
For milling I need to manually remove many lines with self-destruct
coordinates like Z-91234567280 .
Seems to habben just before each layer.

Edited 1 time(s). Last edit at 01/31/2010 03:31AM by MarcusWolschon.


-------------------------------------------
* homeprototype free 3d design repository
* Blog
* Google+
Re: BUG: export-settings affect ALL profiles
February 01, 2010 01:36AM
Hi Marcus,

you wrote:
> When I changed the export-settings of the profile milling-end mill
this also changes the export-settings of the profile extrusion->repman
and vice versa.

I made the export profiles global, because I assumed that people would always be using the same machine with different materials. Since you want export profiles to be local, I will change them to local in the next update, unless a majority of people want to keep it global.

> For milling I need to manually remove many lines with self-destruct
coordinates like Z-91234567280 .

Thanks for pointing out that bug, it is fixed in the latest version at:
[members.axion.net]

> I just cannot seem to find the place in skeinforge to set the volume milling is to be performed in.

There is no milling volume. Instead there is 'Loop Outset over Perimeter Width' in mill. The greater the Loop Outset, the greater the volume which will be milled.

> It is a voronoi-milling of the RepRap opto-endstop.
> ComponentTraces.gcode

The ComponentTraces.gcode file incorrectly uses commas instead of decimal points, so it can not be read at all until the commas are all replaced by decimal points. Skeinforge can only manipulate its own gcode files, so it can not craft a gcode file from another program.

Skeinview is more accepting and can read gcode files from other programs, but since the ComponentTraces.gcode file does not have M101 and M103 commands to indicate tool start and ends, everything looks like extruder travel. Skeinview does not read the other kinds of M codes in the file, so skeinview is not useful for viewing this kind of gcode. To run skeinview alone anyways, you can open it from the Analyze menu, or the Analyze frame.
Re: BUG: export-settings affect ALL profiles
February 01, 2010 01:41AM
Enrique Wrote:
> I made the export profiles global, because I
> assumed that people would always be using the same
> machine with different materials. Since you want
> export profiles to be local, I will change them to
> local in the next update, unless a majority of
> people want to keep it global.

Thanks a lot.
Are there any other settings that are global?
If so I would like to update the pages in the BfB-Wiki
to point that out as it may not be obvisous for users.


> > For milling I need to manually remove many lines
> with self-destruct
> coordinates like Z-91234567280 .
>
> Thanks for pointing out that bug, it is fixed in
> the latest version at:
> [members.axion.net]
> anshell.zip

Cool. Thanks.
I was really worries that I may have configured something
very wrong somewhere.

> There is no milling volume. Instead there is
> 'Loop Outset over Perimeter Width' in mill. The
> greater the Loop Outset, the greater the volume
> which will be milled.

Thanks. I´ll update the documentation I started for
the milling.

> The ComponentTraces.gcode file incorrectly uses
> commas instead of decimal points, so it can not be
> read at all until the commas are all replaced by
> decimal points. Skeinforge can only manipulate
> its own gcode files, so it can not craft a gcode
> file from another program.


Thanks for pointing that out.
As for the commas and some other issued with visolate,
I´ve taken over for the original developer to fix these
in a new version of visolate to make it compatible with
the RepMan.

>
> Skeinview is more accepting and can read gcode
> files from other programs, but since the
> ComponentTraces.gcode file does not have M101 and
> M103 commands to indicate tool start and ends,
> everything looks like extruder travel. Skeinview
> does not read the other kinds of M codes in the
> file, so skeinview is not useful for viewing this
> kind of gcode. To run skeinview alone anyways,
> you can open it from the Analyze menu, or the
> Analyze frame.


Thanks.


-------------------------------------------
* homeprototype free 3d design repository
* Blog
* Google+
Re: BUG: export-settings affect ALL profiles
February 01, 2010 03:46AM
OK,
Documentation at
[www.bitsfrombytes.com]
is updated.


-------------------------------------------
* homeprototype free 3d design repository
* Blog
* Google+
Sorry, only registered users may post in this forum.

Click here to login