将型线图上的型线导入到tribon过程中时,由于型线上的点过多,系统报错,点数不可以超过1000个。解决方案为:讲型线图上的型线分成前后及左右两边,分段导入tribon中,生成AFT,FORE之类的分类,这样点数就可以尽可能控制在1000以下,若仍超过1000个点,则删去一些临近的点或者隔点删除一个
分类目录归档:tribon
TRIBON线形光顺学习心得
学习tribon线形光顺技术已经两天了,总体来讲线形技术相对于船体模块还是较为困难的。首先新建一个文件夹,将肋骨型线图及型值图复制到文件中。在做线形光顺前要做的准备工作就是将LINES(型线图)中的中纵`中横及水线面型线挑出来,紧接着需要将各个型线图随基点进行复制,并移动对应的距离(型值表中有,目的是为了将二维图拉伸到三维空间中去,为后期导入tribon做准备)。保存生成的图形(可以通过CAD中三维查看器观察型线是否拉伸开),保存的路径为之前新建的文件夹,格式为.dxf。打开tribon初步设计INITIAL DESIGN_UTILITIES-DXF CONVERTER,将刚做的DXF文件通过TRIBON软件转换成.3D文件(此步骤目的在于将型线图上的个点的型值通过.3D文件展现出来,亦可以通过EXCEL表格打开,打开之后需要对数据进行重新排列,按照X,Y,Z顺序展开,并保证不存在负值,若存在负值,则用其绝对值替代),处理完的数据用于后面导入TRIBON中,生成型线,进行下一步的光顺工作。准备工作已经做了一部分,下面需要新建PROJECT,打开TRIBON-INTIAL DESIGN_PROJECET TOOL,输入对应的数值(需要填写的数值较多,此处不再赘述)。。。
TO be continued……
TRIBON帮助文件之TRIBON Applications
A number of different tribon applications are availible, each adressing its specific discipline and phase within shipbuilding.
A separate brochure describes the various shipbuilding phases – from concept to delivery.
More detailed descriptions of the various applications are availible on the tribon site on Internet.
A simplified view of the relation between various tribon applications is shown below. Each function in the schema can normally be found in the start menu. The arrows between functions indicate, in some sense, the main flow of information between the functions, i.e. the dependencies between functions.
2 Tribon的应用程序
Tribon中有一定数量不同种类的应用程序,每一个应用都是运用在不同的造船过程。
一个独立的手册描绘了变化多样的造船技术——来自于交货通知的概念。
M3手册
更多的多变的应用程序的细节描述可以从Ttibon在网上的信息获知。
一个简化了的、多变的关于Tribon功能的关系已经在下面显示。模式内的每一个功能可以在开始的菜单中正常的找到。在作用显示之间用箭头表明,在一些检测中,信息主要用于描述功能,比如:功能的依赖性。
TRIBON帮助文件之Introduction to Tribon
The tribon system has been specifically designed to provide a structured way to develop and improve the information flow between the different tasks within the shipbuilding process, where many design development tasks are performed in parallel. The requirements of the complete information flow have been considered and so the system is not just a computerisation(计算机化) of a conventional(常规)manual(手工)process.
The tribon system is based on the use of a Product Information Model (PIM) database, which has been designed to handle in an efficient way all of the structural and outfit objects found in the shipbuilding industry. The information in the Product Information Model contains all the technical data that is needed to define the final product. It addresses all phases in the design and production process. Information from one stage can be used in the next stage. All types of drawings and reports can be derived from the model.
This concept(概念) with one common product information model or “ship database” for each project being used by all designers and production planners means that the information stored in the database is immediately available to the entire organisation. This source of consistent information ensures that no errors can develop between design and production functions. It leads to a very efficient flow of information and which results in reduced man-hours and elapsed time for a project.
The purpose of this document is to present and explain the tribon concept and to give a general overview of the Tribon M3 Shipbuilding System. The document covers the main applications, features and concepts in Tribon, but for the purpose of clarity, explanations have been simplified. Detailed documentation can be found in the user documentation pertaining to each application. Consequently, this document can not replace proper training in the use of Tribon.
Tribon软件的介绍
Tribon软件已经被明确的设计为:在造船过程之内去提供一个被构造的方式开发和改进区别任务之间的信息流,在那里很多发展任务可以平行执行。TRIBON要求完全的信息流程,所以系统不仅仅是常规手动程序计算机化。
Tribon软件系统是基于产品信息模型(PIM)数据库的使用,也是设计用于处理所有结构的有效方法以及发现造船工业中成套装备对象。在产品信息模型的信息包括所有需要最终产品定义的技术数据。它地址在设计的所有阶段和生产过程。信息可以从一个阶段用于下个阶段。所有类型的图画和报告可以从模型获得。
这个概念是一个常规的产品信息模型或者“运输数据库”正在被所有设计者和生产计划者使用,这个也意味着对于整个组织在数据库存储的信息是立即可用的。这个一致信息的来源促使在设计和生产功能之间没有错误的产生。这使之有非常高效率的信息流、减少人工作的时间相对减少。
这个文件的目的是介绍和解释Tribon的概念和提供Tribon M3造船系统常规概述。这个文件包含Tribon主要的应用和产品的特征,也用于清晰地目的和已经简化了的解释。详细的文件材料可以从用户关于每一个应用文件中找到。因此这个文件不能被适当的Tribon培训所代替。
关于船厂技术发展的路线思考
从各大厂应用tribon系统发展来看,其技术设计人员是一个倒金字塔结构。其中线型光顺、外板展开、曲面建模是塔尖,形成船体的主要领导力量,工艺人员、设计管理人员、图纸标准制定人员是塔腰,平面建模、零件建模、出图是塔基。如下图:
鉴于国内某造船大厂的技术发展路线,我们可以看出其技术设计发展以tribon系统的应用为切入点,走消化吸收、自我完善、自主创新、技术扩张的道路。
- 其中消化吸收是打基础,多采取联合设计,尽可能让联合设计队伍驻厂开展设计工作,这样可以更多的消化吸收其设计技能、设计管理技能。
- 自我完善是夯实基础,以工艺标准化为切入点,对设计工作的标准化,每位设计人员的工作范围、工作目标、工作标准进行固化,从而有利于技术设计管理、技术工艺的管理。将生产设计转向工艺设计,将零件制图转向装配制图,从而降低生产现场施工的难度。
- 自主创新是工艺创新,在自我完善的基础上方有能力应对工艺创新,让技术设计人员更多的关注工艺创新,来领导现场工艺的变革,提高现场施工质量与效率,从而降低生产成本。
- 技术扩张是指核心技术(技术管理模式、技术工艺标准、技术图纸标准固化、具有线型光顺及曲面建模能力)稳定的基础上,大量外包金字塔的塔基工作量,降低技术设计成本,提高技术设计的效率,使船厂的技术设计能力得到量变,能够在短时间内高质量完成某型船的生产设计,从而具有快速影响市场的应变能力。
Finished Curved Hull model construction
Tribon shell profile generating and Unsolved problem.
Unsolved problem:
When generate the shell profile ,,this error encountered.
Error 20507 signalled when creating profile JAT23:
The space curve consists of more than one curve branch.!
Now ,the profile is generated like this. It’s used Bulb bar (230,13),
Error when define the edge of shell plates and the solution
This log message show the error about there are no intersections in the edges of the shell plate when create the shell plate.
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
No intersection between the edges 1 and 2
_DP2 STRIP= X NUMBER OF STRIPS= 8
_DP2 GAP= 0.00 AT EDGE 1
_DP2 GAP= 0.02 AT EDGE 2
_DP2 GAP= 0.00 AT EDGE 3
_DP2 GAP= 0.02 AT EDGE 4
_DP2 GAP= 0.02 AT THE BASELINE
No intersection between the edges 1 and 3
No intersection between the edges 1 and 2
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
Error 11005 occurred when defining edge 3
the solution : extend your seam or butt about 50mm , it could ensure the intersections is existent when system calculate the edges of shell plates.
Tribon Curved Hull shell Seam and Butt define
This is a sample about the Shell Seam and Butt define. The highlight part show that it’s a shell plate , The sketch nearby is the shell plate developed sketch.In tribon the designer could check the developed sketch realtime. It help that the designer could adjust the seam and butt arrangement to save the material and manhour.
this is the pic about it.
About tribon TID server log file content.
This message shows the Server is started normally.
========================================================================================================================
tribon Surface Server version 3, 0, 5, 24
Started Sat Aug 21 14:24:04 2010
Logging information will be printed below
This message shows the error when the server can’t find the DML file
—————————————————————————————————-
tribon Surface Server version 3, 0, 5, 24, started Sat Aug 21 14:24:04 2010
Current time is Sat Aug 21 14:24:52 2010
Surface : MYHULL
Folder : C:\Tribon\M3\Projects\MY\TID\
Box : -1000000.000 0.000 -1000000.000 1000000.000 1000000.000 1000000.000
Surface folder: C:\Tribon\M3\Projects\MY\TID\
Surface name: MYHULL
Ambiguous name MYHULL. Access (dml/dms/dm/sat) = -1/-1/-1/-1
Loading MYHULL
Opening model MYHULL
ERROR: cannot open MYHULL
This message shows the server servie the client successfully.
—————————————————————————————————-
Tribon Surface Server version 3, 0, 5, 24, started Sat Aug 21 14:39:51 2010
Current time is Sat Aug 21 14:40:25 2010
Surface : MYHULL
Folder : C:\Tribon\M3\Projects\MY\TID\
Box : -1000000.000 0.000 -1000000.000 1000000.000 1000000.000 1000000.000
Surface mapped to MYHULL.dml
Surface folder: C:\Tribon\M3\Projects\MY\TID\
Surface name: MYHULL.dml
Loading MYHULL.dml
Opening model MYHULL.dml
File type is DML, source 0
PLANAR INTERSECTION Intersecting MYHULL.dml with plane 1.0000 0.0000 0.0000 18950.0000 Opening DML: MYHULL.dml Raw data: 200 points across 11 curved patches. 2 points across 1 plane patches Intersected with tol= 0.000500, Thinned with tol= 0.000500 Number of contours = 1 Contour 1 . X Y Z dX dY dZ . 1 18950.000 0.000 0.000 0.000000 1.000000 0.000000 . 2 18950.000 586.064 0.000 0.000000 1.000000 0.000000 . 3 18950.000 827.355 11.998 0.000000 0.995559 0.094144 . 4 18950.000 1411.268 110.644 0.000000 0.975053 0.221970 . 5 18950.000 1620.101 161.826 0.000000 0.967241 0.253859 . 6 18950.000 2362.602 383.143 0.000000 0.958322 0.285690 . 7 18950.000 2767.010 489.338 0.000000 0.978324 0.207080 . 8 18950.000 3000.000 527.557 0.000000 0.994333 0.106314 . 9 18950.000 3000.000 527.557 0.000000 0.975510 0.219954 . 10 18950.000 3224.779 576.931 0.000000 0.976828 0.214026 . 11 18950.000 3403.990 620.286 0.000000 0.962962 0.269636 . 12 18950.000 3657.842 720.555 0.000000 0.876068 0.482188 . 13 18950.000 3996.469 1014.821 0.000000 0.632749 0.774357 . 14 18950.000 4221.738 1346.601 0.000000 0.503711 0.863872 . 15 18950.000 4457.530 1800.000 0.000000 0.431649 0.902042 . 16 18950.000 4457.530 1800.000 0.000000 0.509716 0.860343 . 17 18950.000 4560.312 1950.543 0.000000 0.590499 0.807038 . 18 18950.000 4632.418 2049.459 0.000000 0.582080 0.813131 . 19 18950.000 4840.605 2360.202 0.000000 0.546179 0.837668 . 20 18950.000 5046.285 2700.000 0.000000 0.471634 0.881794 . 21 18950.000 5046.285 2700.000 0.000000 0.448536 0.893765 . 22 18950.000 5215.380 3043.745 0.000000 0.450761 0.892645 . 23 18950.000 5480.669 3508.026 0.000000 0.540749 0.841184 . 24 18950.000 5721.855 3830.647 0.000000 0.664354 0.747418 . 25 18950.000 5785.979 3900.000 0.000000 0.694992 0.719018 . 26 18950.000 6000.000 4109.988 0.000000 0.727537 0.686068 . 27 18950.000 6354.406 4414.577 0.000000 0.791015 0.611797 . 28 18950.000 6888.679 4768.924 0.000000 0.866357 0.499425 . 29 18950.000 7380.019 5033.305 0.000000 0.891693 0.452641 . 30 18950.000 8063.873 5356.022 0.000000 0.917262 0.398284 . 31 18950.000 8451.559 5522.410 0.000000 0.915386 0.402578 . 32 18950.000 9000.000 5812.491 0.000000 0.825994 0.563679 . 33 18950.000 9000.000 5812.491 0.000000 0.855004 0.518621 . 34 18950.000 9293.611 5993.888 0.000000 0.846026 0.533142 . 35 18950.000 10126.320 6559.392 0.000000 0.803914 0.594745 . 36 18950.000 10804.766 7105.598 0.000000 0.752444 0.658657 . 37 18950.000 11324.114 7591.044 0.000000 0.708432 0.705780 . 38 18950.000 12000.000 8332.877 0.000000 0.633030 0.774127 . 39 18950.000 12605.158 9161.275 0.000000 0.551897 0.833912 . 40 18950.000 12930.607 9679.715 0.000000 0.511085 0.859530 . 41 18950.000 13406.640 10565.402 0.000000 0.432846 0.901468 . 42 18950.000 13783.842 11454.700 0.000000 0.346974 0.937875 . 43 18950.000 13992.473 12064.226 0.000000 0.305153 0.952303 . 44 18950.000 14330.000 13156.619 0.000000 0.300845 0.953673 . 45 18950.000 14510.628 13752.479 0.000000 0.282516 0.959263 . 46 18950.000 14762.328 14646.378 0.000000 0.254767 0.967002 . 47 18950.000 15000.000 15648.329 0.000000 0.208095 0.978109 . 48 18950.000 15023.984 15762.089 0.000000 0.204509 0.978865 . 49 18950.000 15244.386 16888.232 0.000000 0.181897 0.983318 . 50 18950.000 15401.588 17784.530 0.000000 0.162708 0.986674 . 51 18950.000 15559.663 18829.341 0.000000 0.135080 0.990835 . 52 18950.000 15609.118 19208.108 0.000000 0.123874 0.992298 Processing time was 0.05/0.05 seconds Process size 29.3/29.3 Mb Totals: Lines Ints(1), Surface Ints(0), Foreign Ints(0), Gen Cyls(0), Ext Curves(0) ----------------------------------------------------------------------------------------------------
By the way ,the TID server log file is in ($windows)\temp\ floder.
LEARNING DIARY FOR TRIBON CURVED HULL
The first of work of using Curved hull is generating hull curves for checking the surface .Because maybe there are some errors in the surface created by other software such as tribon. If those curves could be generated, it show the surface is suitable for Curved hull model. Those pictures is of a bulk ship.
Next, I will define the beam and butt .
TRIBON M2系统文件及其应用
刘二双
(广船国际技术中心)
摘 要:本文主要介绍了tribon M2系统的系统文件D065文件的组成。结构、作用过程、及其在舾装设计中的应用。
关键词:项目 子项目 系统文件 关键字 数据库 指针
在tribon M2系统中.有一个极为重要的系统文件,这个系统文件的文件名格式为d065<project>.sbd。其中<project>为船舶产品的工程代号,一般为两位字母(最多可以达到八个字母或数字)。每一个船舶产品的项目对应着一个d065<project>.sbd文件。TRIBON系统对所有船舶产品模型的数据以及系统本身所用到的系统变量文件的访问都是通过这个文件来控制的,可以说,d065<project>.sbd文件是TRIBON M2系统的灵魂,没有这个系统文件,TRIBON M2系统的程序就无法正常运行
1 dO65<project>.sbd:~件的组成结构dO65<project>.sbd文件是一个文本文件,由关键字(也就是系统变量)及其参数值组成。每个关键字及其参数值单独占一行,关键字和它的参数值之间用空格隔开。不同的关键字在文件中出现的先后次序对其作用没有什么影响.但是如果同一个关键字在文件中出现了两次.则系统以最后出现的关键字值为准。
d065<project>.sbd文件中的关键字可分成几类:
数据库文件指针
环境变量文件指针
数据服务器及数据库文件路径指针
其它文件路径指针
系统变量
initial design standalone project transfer data to PIM
standalone project must be tansfer to PIM for the next wroks.
five key points:
1 SB_TID should be set up and point to a databank.
2 SB_NAVARCH should be set up and point to a standalone project folder.
3 Export the TID project by using the Initial Design Project Tool
4 Import the TID export file into the PIM.
5 Using Initiate Hull Standards, register the names of any released Hull Forms, Envelopes or Surfaces which are to be used as sculptured surfaces in Basic Design or Hull.
I have transfered it successfully.
tribon line 学习总结
前段时间开始利用业余时间学习tribon,给自己定的一个目标就是从0开始把整个工程从线型开始到最后的梄装结束整个流程做完。每天必须首先保证日常工作完成后才能顺用一些空余和休息时间来学习。在接下来的时间里,我会将的我学习中遇到的相关问题记录下来,同时也与大家分亨一下经验。
我总共花了五星期业余时间把46000T油船的线型光顺完成,直至生成曲面。当然其中也还存在一些问题。我只是把整个流程走完,如果有更多的资料和时间应该能做得更细致一些。今天有点时间把线型这块的内容学习过程写出来和大家分亨。
学习准备工作的第一步就是准备资料。tribon面向船舶专业,不是通用型的设计软件,因此相关资料很少,即使有,也只是简单的翻译一下原文,这样的手册还不如看英文原版。我主要是参考了tribon M3 line Training Guide.这本资料是官方的资料。官方资料主要是对软件的功能进行了描述,而我们最需要的是能将如何将型线图及型值表中的数据直至生成曲面的整个过程 的资料。可惜找不到这样的资料。只能从这本资料下手了。
1、型值数据输入
通常我们都会有CAD版的型线图,我们需要一个工具来采样条曲线上的每个点。这些点在LINE中用来拟合曲线(水线,侧剖线,纵剖线等)。沈哥给予了我很大帮助,他给了我一个采集程序,这个程序在CAD中采集可以直接输出到EXCEL中,然后由EXCEL处理后导出为TXT,再RENAME为DAT文件,最后导进LINE中。一条水线上有上百个点,而且水线在投影面上很密集,采集点很容易出错。每次采集我都把这条线变个颜色后再采集,可以减少错误。采集后在EXCEL中进入处理,主要是增加坐标,因为采集的是平面点,而输入LINE中是大部分是需要三维点。46000T大约80条线,花费了十多小时采集处理。
另:到后来我发现用CAD的LIST命令比那个程序采集要快,LIST后复制出来替换,就行了。等我有时间了我会用ARX编一个自动采集处理的程序来解决这个问题。 继续阅读











