st7 compatibility with old files

[vespa_83]

I installed the upgrade with st7.
working with various old files that you exploit as much as possible if I have to create similar pieces, I find myself some problem with the new holes and material tables.

for the lossella fori, I was 7-8 years ago custom holes.txt adding some whitworth fillets and perhaps formatting gas fillets like "g 1 1/2". with st7 I have already copied and linked the table from programs to my server, but I did not make changes.
if I open a part with a hole "g 1 1/4" tells me that it does not recognize it, because in the file it is written "g1 1/4" that I sincerely do not like.

for the materials. with the pdm (edm) discharge the material property, then in the part, it was (and it still seems) automatic setting of the density, color of the part, hold for the sections in draft. the most obvious problem (I have not deepened) is that on many part the colors are written in English e.g. "steel" face style, the program writes to me "stainless steel" and the piece does not change color because the name indicated is not in the intended styles.

I would self-sustain a mass update of all the archived parts, also because there is no official procedure to realline styles and other, but it doesn't seem right to continue using obsolete styles.

how did you move for these two problems?

 

[Be_on_edge]

table holes: I tried the import tool but in the end, since it was not so many customizations, I made them from scratch.
Material: are already 2 versions that I refer to the update of mass styles, at the moment I use a macro that updates me open ones. but sooner or later I launch the mass update.

Hi.

 

[vespa_83]

for holes I suppose it is better to use the "iso" that is international. table one are tempted to neutralize it (.bak)

for styles I would find more logical that not all the files were mapped but to program and if you select a style in the program, then the information is saved and overwritten in the file, however you can not change the program.. .

the opensave.exe offers a "update styles 3d" and a sourcestyles.asm, I will try. . .

 

[vespa_83]

from the readme of opensave it seems that 'update styles 3d' affects only on asms. :frown:

 

[vespa_83]

lossella fori latest updatesSince we have 4 whitworth threads, I have adopted the following solution.
I mapped a copy of the new holes folder on the server.
I have neutralized all the files I don't care about by adding to the file name the extension ".zzz", I left ansi inch and iso metric.
I copied iso metric into a personal file, and here in each sheet I removed all values from the second row down.
I put my 4 custom threads in the "filettato" sheet.
for utility and compatibility I opened iso metric and I made a find and replace on column size from "g" to "g".

in the next updates I should have no problem updating files and repeating the last step.

Style in the source code of opensave it seems that update3dstyles() is also called for .par and .psm

 

[Be_on_edge]

Style in the source code of opensave it seems that update3dstyles() is also called for .par and .psm

for flight updates I use this macro:
http://c-k-m.info/it-dienstleistungen/programmierung/54-solid-edge-modell-styler.html

 

[vespa_83]

in v.20 i materials, the styles and colors were indicated in Italian. from st1 template styles are only in English.
Unfortunately by default the material.mtl file and now materials.mtl, have the face style in Italian, veteran of the v20, I suppose.
so you lose the material->style match face, if in the current template there are no names in Italian (that same solidedge has removed from st1).

I personally propose to create a new file of materials starting from the current materials, indicating the name in English, since in the files stored over the years, there is already.

in the meantime I noticed a few things, unfortunately not very interesting:
- from the custom folder, they removed "material table editor" that I repureted from a station with st6, but it doesn't work anymore (it doesn't find the file) and it doesn't seem convenient to recompil it.
- in the custom folder they put a holedatabaseconverter that converts the old holes.txt into excel.