Victor

About

Username
Victor
Joined
Visits
4,659
Last Active
Roles
Administrator

Comments

  • You could set it to surface mesh only and see what it looks like. It might show this extra triangle or reveal another problem. Not sure how to solve it though, other than slightly changing dimensions of the CAD model. Mecway 4 uses the same versio…
  • Is this extra surface one triangle, and selecting it also selects a neighboring real surface? This isn't something I've seen before with the CAD import, but it's a bug that can happen occasionally with the automesher which is the same code, so it's …
  • I've heard that the product key isn't reliably recognized on Wine so just a caution for anyone who might buy it hoping to use Linux that it could be limited to the 1000 node free version. Hopefully I can get a more compatible update done later.
  • I'm flying blind here, but that error message indicates a .Net class (GraphicsPath) which is used by the graphing library in Mecway (ZedGraph) but apparently not fully implemented in Mono. So it might be happening whenever it tries to display a grap…
  • Wow. Thanks for all the effort. I need to track down what's happening.
  • Hi waluyo I don't intend to add those features natively because they're now fairly easy to use through the open source CalculiX solver. For nonlinear materials, you still have to define the material properties by hand using keywords. Contact has a …
  • Thanks for reporting on Wine whitequark, that's great news. From what I can tell, Wine already comes with its own version of Tahoma. Was it not displaying properly until you installed the Microsoft Tahoma?
  • I plan to include PEEQ by default along with adding the plastic material as a new material type so they'll go together. For now, there's the workaround of adding *EL FILE using custom step contents.
  • I'll contact you privately about the product key. Generally any Mecway product key starting with "=004-" or a number greater than 4 is supposed to activate version 4.
  • Hello cashan. This effectively happens automatically in the form of component colors. Though to get a legend, you would need to rename each material or component with its thickness so it's displayed in the outline tree. You can also use "Show thick…
  • All version 3 customers can use the same product key for version 4.
  • Good to hear it's OK now. The table should be able to do one node. Does it look like this picture?
  • Oh, it seems like t should be in minutes for the ISO 834 formula. If so, then use this instead: 20+345*log(8*t/60+1)/log(10) Which looks like the graph attached
  • Last time I looked into 3D Connexion, their SDK didn't work well with .Net, which Mecway uses. Things might have changed, so I'll try again sometime in the future. Quite a few people have asked for this from time to time.
  • In the formulas, log means log base e, so change it to 20+345*log(8*t+1)/log(10) The next version will show this in a graph as attached, so you can more easily check it. To output temperature and time for just one node, make a node selection contai…
  • Time dependent convection and radiation work correctly in version 4 beta despite the error messages. This will be a properly supported feature in the final release of version 4. Two example files are attached. The convection has a very high heat t…
  • Hello gemada It looks like you might be able to use a time dependent ambient temperature with convection and radiation in version 4 beta. I haven't tested this feature, but it might work. You would certainly need to verify the correctness yourself.…
  • 2. I'll include this in a future version since other people have asked for it too. Thanks for the suggestion. On second thought, using conduction instead won't give accurate results and will probably be difficult to set up since you'll need to modi…
  • Hello gemanda. 1. It uses the finite element method as described in common textbooks. It's probably the same as ANSYS and most other thermal FEA software. 2. The reason for no change between the two models is that the temperature constraint on the…
  • Yea, I don't think these elements is actually wrong, just quite distorted. Mecway shows an error (red X) if the element is so distorted that the solver will fail (negative Jacobian determinant, non-physical shape like self-intersecting/negative volu…
  • Thanks for the suggestion about buttons. This would need to be configurable because most people won't need them. I'll keep it in mind for a possible future UI redesign. Seeing the lines through the faces is certainly a problem with small elements. …
  • Unfortunately not. At least not yet. The closest thing would be generating models programatically by writing a .liml file and starting the solver with the command line. There's an example that generates .liml files from an Excel spreadsheet in the S…
  • Thanks for the detailed comments VMH OK to reinstating the isometric view button. 1. It only does named selections for now, not components. This should be enough to address the problem of filtering the results in the table. I realize having compon…
  • The *BOUNDARY keyword defines fixed displacements. Here "xface,2,2,1" means constrain the nodes in xface so that dof 2 (y-displacement) has the value 1 m multiplied by the amplitude. The amplitude ramps up linearly from 0 m at time 0 to 0.004 at ti…
  • Mecway's own solver can't do non-linear analysis on this because it has non-zero displacements. Instead, I solved it with CCX and the solution is very different from the linear solution, so you definitely need to use a non-linear analysis. The stre…
  • Was this originally a .liml file or .inp? If .inp, then I agree with prop_design that units don't look consistent. If it was .liml, then kg/cm^3 is OK. [EDIT: Except 8kg/cm^3 is much too high for steel - now I see that's perhaps what you meant prop_…
  • I don't think you would need to define the complete arc shape - just put an initial displacement on one node, say in the middle or wherever the load is applied to bend the pole, and CCX should solve that to bend the pole. Then you can tension the fa…
  • Thanks for the suggestion about node selections through CCX. It's not entirely trivial because CCX sometimes changes the numbering but I'll see how it goes. That file doesn't solve correctly with the Mecway solver because of the non-zero displaceme…
  • I don't want to have it store two sets of results in the same file because that starts to become a kind of file management task which would add complexity and need to be learnt without adding much power. Hopefully just saving two copies in different…
  • For strain and plastic strain, I'll look into having them turned on by default for nonlinear. Thanks for the suggestion Sergio and VMH. You can add another step using the custom step contents by inputting something like this: *END STEP *STEP,NLGEOM…
Avatar

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!