- 积分
- 556
- 回帖
- 0
- 西莫币
-
- 贡献
-
- 威望
-
- 存款
-
- 阅读权限
- 20
- 最后登录
- 1970-1-1
该用户从未签到
|
发表于 2009-5-17 11:08
|
显示全部楼层
来自： 中国台湾
本帖最后由 keli 于 2009-5-17 11:15 编辑
從11.1 到 11.1.1 的bugs
所以用新版問題會少些
Defects fixed in Maxwell (3D) 11.1.1
------------------------------------
ANSft00063628 - In some electrostatic projects when plotting scalar
field quantities on the surfaces of some conductors (at the boundary
between a solved region and an unsolved region), the plot would
sometimes contain spurious 'lines' drawn from the surface to some point
not on the selected surface.
ANSft00064560 - For some electrostatic projects the postprocessor was
displaying non-zero energy (and non-uniform voltage) inside conducting
regions (regions that were excluded from the solution). This made
energy calculations in the field calculator incorrect unless filtered
to only include the solved regions. Field plots on cutplanes and on the
surfaces of conductors could also be incorrect unless filtered to only
plot within the solved (non-conducting) regions.
ANSft00064132 - For eddy current problems the Z-matrix was incorrect at
very low frequencies (around 1 Hz or less). The inductance would become
negative.
ANSft00063766 - Output variable convergence did not work correctly if
multiple parameter setups were defined.
ANSft00064290 - When viewing the model for transient designs with non-
cylindrical rotational motion in any solution context other than the
initial position, the band object was incorrectly displayed as rotated.
The band object is now correctly displayed as stationary for this case,
and only the moving objects contained within it are shown rotating.
ANSft00065244 - For magnetostatic designs using magnetization linked
from another design, there was an error in numbering the tetrahedra for
the magnets. This would cause the B-field displayed in 1 of the
tetrahedra (belonging to a non-magnet object) in the linked project to
be incorrect. To correct previously solved projects that demonstrate
this defect, both the source design and the target design will need to
be re-solved using version 11.1.1 or later.
ANSft00064455 - For transient designs with motion setup, if you visited
the motion setup dialog after the problem was solved and closed the
dialog by clicking on 'OK' (instead of 'Cancel') then your solutions
were invalidated even if you had not made any changes. Now when you use
'OK' to close the dialog solutions are invalidated only if you made
changes.
ANSft00064295 - For transient designs with rotational motion, if you
checked the 'rotate limit' checkbox things worked correctly, but if you
returned to the motion setup dialog the checkbox would be shown
unchecked.
ANSft00063517 - For Magnetostatic, Eddy and Transient designs, the
check for divergence of current on the conduction path sources was too
strict and rejected setups that should have been valid. The currents
summed to zero, but the check did not leave enough tolerance for
floating point errors.
ANSft00063645 - In version 11.1, for transient designs when adding coil
terminals to windings, if you right-clicked on the coil terminal and
attempted to 'Add to Winding' the software would crash. You could work
around by doing the assignment the other way (right-clicking on the
winding and selecting 'Add Terminals...'. This bug was introduced in 11.1
and is resolved in 11.1.1.
ANSft00064818 - Under some circumstances you could get incorrect
answers for magnetostatic designs when you were attempting to get the
magnetization from a linked design. The interface was passing the wrong
flags to the solver if the checkbox for "Compute demagnetized operating
points" was checked, even though this checkbox was disabled (and should
have been ignored) when getting the magnetization from a linked design.
ANSft00063050 and ANSft00063568 - Inductance and capacitance matrix
entries were labeled incorrectly in the solution display. This also
caused a post-processed matrix to have incorrect values.
ANSft00063056 - If you had multilumped objects in the model, the COM
engine could crash after you edited a source and attempted to re-solve
a design.
ANSft00065237 - In the transient solver, if you used the dynamic
demagnetization option, you did not get the correct results if you had
a nonlinear magnet definition in which the nonlinear curve was not
assigned to the first axis of the material.
ANSft00064299 - For transient designs with non-cylindrical rotational
motion, the solver would occasionally 'die unexpectedly' at a random
time step.
ANSft00063335 - For transient designs with rotational motion and using
anti-periodic boundary conditions and in which there is a source within
the rotating region, the solution would not be correct after rotating
through one period.
ANSft00064067 - For transient designs with rotational motion if there
was a voltage winding in the moving part of the problem that crossed a
matching boundary, the solution would be incorrect.
ANSft00063749 - When setting up an inductance matrix in a magnetostatic
design with master-slave boundaries the software made certain
assumptions about matching the conduction paths on the master and slave
boundary that could result in the solver returning fewer matrix entries
than the UI was expecting. Ultimately, this could lead to a crash. The
crash will no longer occur, but care should be taken when setting up an
inductance matrix in a design with master-slave boundaries. There are
some cases in which the master-slave boundary conduction would not be
correct during calculation of individual inductances. In those cases,
it will be necessary to model the full geometry in order to calculate
the correct inductance matrix.
ANSft00063948 - The inductance matrix calculation was incorrect for a
coil that crossed an even symmetry boundary.
ANSft00063588 - The script command GetTopEntryValue to get values from
the field calculator stack did not work correctly for variations other
than the nominal variation.
ANSft00063398 - In nonlinear materials the energy, coenergy and
apparent energy were not calculated correctly in the field calculator.
This error was not in the solution, but did exist in the post processor
operations.
ANSft00061790 - Calculator expressions that used unit vectors could not
be plotted on cutplanes.
ANSft00063070 - It was possible to crash geometry modeler if you
followed the specific sequence: create a new object, immediately delete
the new object, and then attempt to group objects by material.
ANSft00062928 - For a certain class of models adaptive mesh refinement
could become very slow.
ANSft00064979 - For eddy designs when creating a report and selecting
the matrix quantity "Z", the reporter did not recognize that Z was a
complex value and did not give you the proper options for selecting
between the real part, imaginary part, magnitude or phase. If you have
existing projects with existing reports referencing Z, you will need to
delete those reports and recreate them.
ANSft00063151 & ANSft00063153 - Using an external user control program
from a transient simulation did not work correctly.
ANSft00065146 - When using the RMxprt User Defined Primitive 'LapCoil'
to create a Maxwell model, for certain cases of a single layer coil the
model could cause Maxwell to crash. This crash did not happen
immediately when the object was created but happened later when you
saved the model or attempted to solve.
ANSft00063512 - When using an external circuit to drive a transient
solution, you could get an 'error in executing 'tdslink' message if you
had a current source in the external circuit.
ANSft00063020 - Using an ammeter connected in series with a current
source in the Maxwell Circuit Editor displayed zero current instead of
the correct current value.
ANSft00064346 - When solving eddy designs with a frequency sweep, if
your frequency values were not round numbers the solution values for
some of the frequency points would not load in the reporter. This was
due to a mismatch in precision when writing the frequency value in the
solution data files.
ANSft00064735 - When using the RMxprt user defined primitives to create
a 3D motor model with phase windings, the windings and stator would
overlap under some circumstances.
[Windows version only] ANSft00063921 - When running under Windows XP64
the maxwell.exe executable could only access up to 2GB of memory. This
meant that even though you could solve very larger problems using 64-
bit windows there was an unnecessarily low limit on the size of the
problem you could post process. Maxwell.exe will now be able to access
up to 4GB of memory when running on 64-bit Windows (maxwell.exe is
still a 32-bit executable in the Windows version; true 64-bit
executables are used for the solution process under Windows XP64).
[Windows version only] ANSft00063722 - If you recorded a script that
included the import of a GDSII file including a .tech file for layer
information, when you played the script back the .tech file was not
used. |
|
加群请注明论坛用户名及所从事专业，否则不予通过
|Archiver|手机版|小黑屋|西莫电机圈
( 浙ICP备10025899号-3|
浙公网安备33010502012192号 ) 
IP卡
显身卡
发表于 2009-3-5 15:39
发表于 2009-4-20 15:43