How do I create a R/O Asian environment for CATIA? |
 |
|
A. You need to apply the R/O Asian bundle that includes the required character sets to read CATIA models containing Asian characters. Please refer to Asian R/O environment for CATIA to configure your system.
|
|
How do I set up LUM and iFOR/LS for CATIA V4 and V5? |
|
|
A. Please refer to Licensing with LUM for everything you want to know about LUM and iFOR/LS. Note that starting from LUM 466, the APA (Auto Port Aggregation) environment will be supported.
|
|
How do I connect a SpaceMouse in CATIA V5? |
|
|
A. - Use the xdriver executable to configure the spacemouse (spm).
- Run xinstall to get the spm configured and then execute /usr/magellan/xdriver -test to initialize the driver (in Manual Starting mode).
- In the MCC blue window, check the availability of the spm and configure the different options. Make sure to switch the "Event Window" icon to 'Window=InputFocus'.
The '/etc/services' file has to contain the CATDeviceBroker 6668/tcp record.
In CATIA V5, change the following options: TOOLS > OPTIONS > Devices and Virtual
o- Virtual Reality Starting Mode = Automatic
o- Automatically started Daemons: select Spaceball
or Magellan/SPACE MOUSE.
You can execute the c:vr monitor command from CATIA V5 to follow the spm activities. |
|
|
How do I specify a new shell variable before starting V5? |
|
|
A. Starting from V5R8, Dassault Systèmes has changed its way to setup a V5 environment, and then some problems may occur when trying to export variables containing blank definition. The CATEnv/CATIAxxx<Rel>.sh script has been changed, and therefore a second file (txt extension) is called to export all the shell variables. The 'eval' command is executed to export each variable. However if the definition of the variable includes a blank character or if you include a space before or/and after the '=' sign, the 'eval' command will fail.
Modify the 'eval' command in the shell script to include \" characters for each variable to be exported. Do the same thing in the catstart command if used. Otherwise use CNEXT to initiate CATIA V5.
Example: Eval eval export $var=\"`awk -F= -v key= ....$CATIAV5_environmant_name`\"
|
|
Why does CAA V5 built on HP-UX 10.20 generate an Abend in shl_init()? |
|
|
A. Building a CAA/RADE V5 application must be performed on HP-UX 10.20. Note that starting from V5R10, this can be done on HP-UX 11.00 as V5R10 (and higher levels) will be HP-UX 11.00 natively built.
If you get a shl_init() type of Abend when executing the application, this seems to happen only when using aCC to build the shared libraries and the executable and only when an implicitly loaded library is explicitly unloaded (shl_unload()). When invoked for building shared libraries, aCC registers some initializer functions (used for static constructors/destructors) when it calls the linker to build the shared library. Normally when such a library is implictly loaded, the C++ runtime library (libCsup.sl) will call the initializer routines of all the libraries at termination.
But if that implicitly loaded shared library is explicitly unloaded (by doing a shl_load of the same library and getting the handle and doing a shl_unload later), the runtime library still tries to call the initializer function of this unloaded library and results in a core dump!! The user can avoid this if he does not implicitly link the shlib or uses cc instead of aCC or uses the linker directly to build the shared library. If no initializers are registered for the implicitly linked library, then there will be no problem.
Here are two suggestions: - Make sure the development system is up-to-date. Please refer to HP-UX 10.20 Configuration for more detailed information. If C++ compiler installed on the system, remove it (if possible) and keep only the aCC one.
- Test the PHSS_26945 on the runtime 11.00 system. This patch fixes a defect (JAGaa86607: Must not unload library at exit time or thru atexit(3)) which apparently refers to this issue.
|
|
|
What causes the bad performance of the Tools>Customize function on HP-UX? |
|
|
A. This is a known defect related to a V5 settings (FrameConfig.CATSettings). General performance of CATIA V5 is highly impacted (for example, opening a blank CATProduct may take almost 1mn on a PA8700 system). There is a workaround proposed by Dassault Systèmes and HP.
- Isolate and cleanup the V5 settings (actually the FrameConfig.catsettings file seems to cause the issue).
- Restart V5
- Open a blank product (if not done automatically)
- Go to Tools>Customize again
- Select the 2nd tab (User Workbenches)
- Click on New to create 2 additional workbenches (NewWorkbench001 and 002). This will create new FrameConfig.CATSettings file (approx 200KB).
- Restart V5
- Open a blank product
- Select Tools>Customize (few secs to be displayed).
|
|
|
How do I detect a CATIA V5 file on HP-UX? |
|
|
A. The CATIA V5 files have the following string at the beginning: V5_CFV
If you edit the ‘/etc/magic’ file and add the following line, the 'file' command will report "CATIA V5 file":
0 string V5_CFV CATIA V5 file
( Syntax: offset type tag <string to report> )
There is no way to differentiate a V5CATProduct because the V5 string is the same for all types of data.
|
|
How do I optimize the wide screen display with CATIA V5? |
|
|
A. When using a large monitor (23” flat screen), a circle in V5 will appear as an ellipse due to the 16:9 ratio used by the device. Below is an example of a configuration that outlines the different points to check to optimize the screen utilization with CATIA V5.
- For the monitor:
- L2335 flat panel offering a 23" viewable image area with a screen opening of 19.53"x12.24" (16:9 ratio), resolution of 1920x1200 @60Hz
- Setup: Menu > Image Control > Custom Scaling > One to One
- On HP-UX:
- C8000 with FireGL X3
- Setup: use the 'setmon' utility to change the resolution to 1920x1200 @60Hz, and restart the X Server. You can also use SAM to access this menu.
- CATIA detects the mode used by the Xserver and automatically adjusts the visualization parameters. For CATIA V5, you can switch in Full Screen mode (View menu) and display the rotation tool which will appear as a circle.
The nw8240 mobile workstation with ATI FireGL V5000 requires the 8.163.1.2 driver level to fix that issue.
|
|
|
Why does CATIA V5 Tool Capture function on HP-UX generate a black preview window? |
|
|
A. Please refer to the HP-UX Graphics section, see Additional Notes section, to get the information on the Xserver settings.
|
|
Why does CATIA V5 crash when running multiple applications on HP-UX? |
|
|
A. CATIA V5 uses shared segments in the 3rd and 4th quadrants of the HP-UX virtual memory. Beginning with V5R16, all V5 applications are q3p enabled, which means that the 3rd quadrant is used to handle private data. Then only the 4th quadrant remains to manage the shared segments. In some cases, and in particularly when running database related solutions, there is no longer enough space to address the memory mapping, and therefore the application stops. There is a workaround that allows to increase the capacity of the 4th quadrant, assuming the 3rd one is still used for private data.
In the February 2006 X server patch (PHSS_32977), HP made the allocation of the AGP aperture dynamic based on the amount of RAM in the system, and this is the rule :
o Less than 2GB will use a 32MB size,
o 2GB to 4GB will use a 64MB size,
o and 4GB and above will use a 128 MB size.
This could improve performance in display list applications using large models (like CATIA V4).The AGP memory is allocated in the shared memory segment. In return, the shared memory segment size is reduced which leaves less space for applications using extensively that segment (like CATIA V5).
There is a kernel tunable parameter that can override the dynamic allocation. This can be set with SAM, although, SAM will not alter the value if the X server is running because it can't unload the drmfglrx kernel module. If you want to use SAM to do so, make sure the X Server doesn’t run in the same time.
Other method is to :
o Edit the /stand/system file, and explicitly set the parameter by adding the entry:drmfglrx_agp_size 32
o Rebuild the kernel :mk_kernel -v -o /stand/vmunix
o Reboot with shutdown (moves the kernel into place - reboot won't) :/etc/shutdown -r 0
This sets the AGP aperture to 32MB as was done prior to February 2006.We do not recommend
going any lower than 32MB as this is the minimum value that has been extensively tested.
Note: this tunable will not exist on systems with an X server older than PHSS_32977.
|
|
|
|
Printable version
