I provide gerber file of allegro cadence(drill file with .txt and .drl is exit) I want convert it to pcb file in Altium Designer but drills of vias and pads not show, resault of it can't convert to pcb file
What's the problem?
How do import drill file to Altium Designer?
How do convert gerber file to pcb file into Altium Designer?
Please help me
Thank's
you can convert Gerber and drill files to pcb , the Gerber files is requirement file for cnc and ... to build pcb . there is no netlist , footprints , or via definitions in gerber files. gerber file for layout and gerber file for drill are separate from each other and you cant marge them.
Related
Anybody knows how to export an Ansys structural data file to ParaView?
It is read that ParaView has an Ansys reader, but it does not work. Errors always come up when loading the *.inp file.
Is there any script to convert .inp files to .vtk?
Thanks
Based on the video from Czech-based SVS FEM s.r.o., I wrote an input file for Ansys Mechanical APDL, that creates a VTK file, which can be opened in ParaView.
In the input file vtk.inp, the user has to specify the argument arg1, for which the nodal values are to be written to the vtk file via the command *get,my_results(j),NODE,n_j,..., p.e.
arg1='S,EQV' ! for equivalent stress or
arg1='TEMP' ! for temperature
For further nodal results, refer to the specifications of the *GET command in the Ansys Commands Reference.
The vtk.inp file should be placed in the current working directory. It is called with the APDL command /input,vtk,inp. In Ansys Mechanical, this command can directly be inserted in the command line. In Ansys Workbench, the command can be pasted in the feature Commands (APDL) under Solution.
The output file output.vtk is written in the same location as the input file.
The code was tested with a structural analysis in Ansys Mechanical APDL 17.2 and Ansys Workbench 17.2. The vtk file was tested with ParaView 5.4.1.
Explanation:
The array e_types_Ansys_to_VTK maps the Ansys element types (p. e. SOLID186) to VTK cell types (see also Ansys Element Types).
Limitations:
The input file is yet limited to write only one scalar parameter result in the vtk file, but it can easily be extended for vector or tensor results as well as for multiple results in one vtk file, following the VTK File Format Specification.
Since Ansys stores nodal results only in the corner nodes, only linear VTK elements are used. There could still be some minor mistakes in the e_types_Ansys_to_VTK map, since I could only test some element types. Please feel free to report any corrections or extensions to the code in the comments.
Here is the link to the source code. Use at your own risk.
In case you would like to export a vtk file directly from Ansys Workbench, a Python result converter was introduced in a Youtube video here. Unfortunately, the source code only appears in the video and is explained in Czech language.
Thus, I typewrote the code from screenshots and made some minor improvements.
You will need two files to install the macro as an Ansys ACT extension:
main.py and vtk.xml.
Place the file vtk.xml in the folder C:\Program Files\ANSYS Inc\v###\Addins\ACT\extensions, where ### is your Ansys version, p.e. 172
Create a new folder vtk in C:\Program Files\ANSYS Inc\v###\Addins\ACT\extensions.
Place the file main.py in the created folder.
Start Ansys Workbench.
Register the path C:\Program Files\ANSYS Inc\v###\Addins\ACT\extensions as additional extension path under Tools > Options > Extensions.
Restart Ansys Workbench, go to Extensions > ACT start page > Extension manager > VTK and load the extension.
In a structural analysis, go to Results, right-click and insert My results. Three inputs have to made by the user:
Under *get,my_results(j),NODE,N,..., , give the desired nodal result according to the Ansys Commands Reference, p.e. S,EQV for equivalent stress.
Under VTF file name, give the full path to the vtk output file to be created, p.e. C:\temp\output.vtk
Under Load step, give the load step number (p.e. 1 for last load step unless not stated otherwise).
For larger models, I experienced that the automatically generated file makeresult.mac is not instantly transferred from the project_pending folder to the actual working directory, thus, causing the macro to throw an error. Maybe, anyone can make a suggestion on how to fix this?
ParaView cannot read .inp structure files (I guess this is the Abaqus file format). You could try to export your files as Nastran (.nas) files, since ParaView has a Nastran reader.
I want to manipulate Office Open XML format of Excel, but even just conversion between the .zip and .xlsx generates errors:
create a very simple test.xlsx by Excel
Right-click test.xlsx => Rename as text.xlsx.zip
Right-click text.xlsx.zip => Extract all to a folder named text.xlsx
Right-click text.xlsx folder => Send to => Compressed (zipped) folder named text_2.xlsx.zip
Right-click text_2.xlsx.zip => Rename as text_2.xlsx
open text_2.xlsx with Excel, then I got the following errors:
Does anyone know what's wrong there?
Xlsx files are just ordinary zip file and it is definitely possible to do what you are trying to do.
Does anyone know what's wrong there?
I would guess step 4:
Right-click text.xlsx folder => Send to => Compressed (zipped) folder named text_2.xlsx.zip*
You will need to zip the contents on the folder and not the folder itself. The resultant zip file should have the [Content_Types].xml files at the top level with no parent folder.
.***x files are zip files, but the method of compression is different than the standard one used by Windows Explorer. Windows Explorer does absolute compression (whatever it can compress safely, it will), MS Office and OpenXML leaves necessary pieces uncompressed to be used by the application when it is read.
Edit: I should add that you can zip the files back up and use them as an xlsx again but you have to make sure you're using the same compression method as Excel or OpenXML.
I want to create new excel sheet with .xlsm extension by using softartisan dll, however in create method of softartisan does not have xlsm format. It has only .xls and .xlsx formats.
My new excel contains macros hence I need .xlsm format.
Code is as follows
Dim xla As New ExcelApplication
errWb = xla.Create(FileFormat.Xls) ''Or errWb = xla.Create(FileFormat.Xlsx)
I want file in .Xlsm format
If anybody knows please suggest.
OfficeWriter does not support manipulating or creating Excel macros/VBA through the API because of the potential security risks. Creating a new XLSM file that doesn't contain any macros has limited usefulness. Hence the XLS and XLSX are the only file formats that can be created from scratch using OfficeWriter.
OfficeWriter does support manipulating existing XLSM files, but the macros/VBA are not accessible. If you need to create a new report that contains certain macros, we recommend that you create an XLSM file in Excel that contains the macros that you need. Then open and modify that file with ExcelApplication. The XLSM file can event be blank, except for the macros that you need.
Dim xla As ExcelApplication = new ExcelApplication()
Dim wb As Workbook = xla.Open("myStartingTemplate.xlsm")
...
Note: I work for SoftArtisans, makers of OfficeWriter.
So, in my project I have 10 languages, and 10 Localizable.strings files.
I just created Localizable.strings files, a file for each language. Now they contain "key" = "value" pairs, and both keys and values are in English (default language).
My languages are all translated and stay in Excel files.
The question is, how can I insert all my languages in those files faster than just copying each word manually or writing a script for that?
Maybe there is a existing tool for this already?
Thanks.
I found an easy way to compose localizable.strings files from Excel documents.
In the Excel document, in specific columns I insert " " = " " symbols. It's easy to do for all the words by dragging Excel cell down from the corner, so that it copies stuff from that cell to all the cells you drag it to. (sorry for messy explanation)
Thus the document contains the same symbols and words as localizable.strings does.
Than I just copy everything to the text file, remove tabs, change extension to .strings.
(no comments saved unfortunately).
EDIT:
You can copy the stuff from Excel to Sublime Text, then Find & Replace tabs if any. Copy resulted stuff into proper Xcode .string file.
One application that will really save you a lot of time by automating and streamlining localization procedure is Localization Suite. I do not know if they support importing from excel (to save you time transferring your string pairs) but it's free and seems like a complete solution.
I had an internal script at work for doing that tasks in iOS and Android, and I've just opensourced it as a Gem. You can take a look at it here: http://github.com/mrmans0n/localio
It can open spreadsheets from Google Drive and local Excel files as well, like requested.
You just would have to install the gem
gem install localio
And have a custom DSL file in your project directory, called Locfile, with the info referring to your project and the localization files. An example in your case, where an Excel file is used, could be as simple as:
platform :ios
source :xls, :path => 'YourExcelFileGoesInHere.xls'
output_path 'Resources/Localizables/'
The .xls file should have a certain format, that probably is very similar to what you have right now. You just have to clone the contents of this one and fill it with your translations: https://docs.google.com/spreadsheet/ccc?key=0AmX_w4-5HkOgdFFoZ19iSUlRSERnQTJ4NVZiblo2UXc
Hope this helps.
Here are the steps i followed:
change the extension of .strings to .txt on windows
open excel and go to File > Open
Choose the file to open. This should present an import wizard
Follow the steps and specify the delimiting character as =
You're done
I have problems to view report. first, when I try to click view button on the excel button in 'build'. it not view out the report but it is just generate excel files in a folder only. Secondly, Can I get the file .Jasper and .bak after I view the report.
The main problem is when i want to view direct my report for excel. The error show:-
Exporting XLS to file (using POI)... .\senarai_cpp_4(1)_tnsparthis_pembaharuanPenangguhan.xls.
Error exporting print... Sheet name cannot be blank, greater than 31 chars, or contain any of /\*?[]
Can't find the translation for key = iReportCompiler.errorExportingPrint: using default (Error exporting print... {0} ) java.lang.IllegalArgumentException: Sheet name cannot be blank, greater than 31 chars, or contain any of /\*?[] at org.apache.poi.hssf.record.BoundSheetRecord.setSheetname(BoundSheetRecord.java:162) at org.apache.poi.hssf.model.Workbook.setSheetName(Workbook.java:464) at org.apache.poi.hssf.usermodel.HSSFWorkbook.createSheet(HSSFWorkbook.java:540) at net.sf.jasperreports.engine.export.JRXlsExporter.createSheet(JRXlsExporter.java:147) at net.sf.jasperreports.engine.export.JRXlsAbstractExporter.exportReportToStream(JRXlsAbstractExporter.java:393) at net.sf.jasperreports.engine.export.JRXlsAbstractExporter.exportReport(JRXlsAbstractExporter.java:221) at it.businesslogic.ireport.IReportCompiler.run(IReportCompiler.java:1329) at java.lang.Thread.run(Unknown Source)
Export running time: 1,212
The old version of iReport uses an outdated version of POI. The library doesn't have the ability to truncate sheet names for excel. The solution is to rename you report (jrxml) to have a short filename.
You can change the location of the backup file by going into Tools -> Options.