Jump to content

MvdM

Moderators
  • Content Count

    95
  • Joined

  • Last visited

  • Days Won

    2

MvdM last won the day on April 8

MvdM had the most liked content!

1 Follower

About MvdM

  • Rank
    Advanced User

Profile Information

  • Gender
    Not Telling
  • Country
    South Africa
  • Are you University user?
    No

Recent Profile Visitors

1552 profile views
  1. Hello @Ranjitha Ravishankar If you attach your model file (.cfx) others could take a look at the definition of the anisotropic material in your model. From the CEM validate output, it still looks like the anisotropic material definition is not valid.
  2. Hello @Ranjitha Ravishankar Feko only supports passive media, so you should review the anisotropic medium definition. Is the defined medium a passive medium? You can run CEM validate (Solve/Run tab) in CADFEKO to see which regions (and media definitions) trigger errors. If you need further help, please add your .cfx model and/or .out file. Also, what version of Feko are you using? Kind regards Madelé
  3. @mgmv7, which variable in the model lossy.cfx are you sweeping? Is "d" the distance variable? Note that the parameter sweep does not support sweeping variables that are used in result requests. If you are sweeping "d", it would be required to change the near field request not to depend on this variable.
  4. This error is given when model creation fails. Please make the same change to the model in the CADFEKO to see what is going wrong. For instance, if you change variable "d" to depend on lambda, applying the variable change would fail. The reason for the failure is that the near field request depends on this variable and integer values need to be entered for the number of field points. You could use "ceil(lambda)" for the variable or "ceil(d/5)" on the near field dialog to resolve this issue. Glad you found a way around the problem. I trust the explanation above helps to understand why it happened. I'm not sure if this is just due to the number of points. For d=1e4, with the near field request depending on this parameter, you have 10 million near field points.
  5. Hi @mgmv7 Could you please upload the cfx file again? There seems to be a file attached to your post, but it shows "Unavailable". What version of Feko are you using? Kind regards Madelé
  6. Hi @lostarmour Please see this post: Does that help? Kind regards Madelé
  7. MvdM

    Model Extents

    Hi @pmcardle When the model extents is set to the default value of 5E+02 (500), the entire geometry must fit inside a 1000x1000x1000 box (in the model unit) centred at the origin. For 50e2 (a setting of 5E+03), the geometry must fit inside a 10000x10000x10000 box (in the model unit) centred at the origin. Please also refer to the "Model Extents" section of the Feko User Guide where this is explained. Kind regards Madelé
  8. As far as I know there is a bug in Feko 2018.2 and 2018.2.1 (fixed in Feko 2019) that causes an error when using DGFM to solve SEP regions (I responded in the duplicate thread). I would also recommend you upgrade to the latest version of Feko 2019.
  9. Sorry, Mel. I had typed the response before you had locked the thread. The duplicate thread is: https://forum.altair.com/topic/36393-dgfm-errors-sep-feko-2018/
  10. Hello Eliz Unfortunately you are using a version that will not work to solve your antenna array containing SEP regions with the DGFM. It is strongly recommended to upgrade to the latest version of Feko - the current version is 2019.1.1. DGFM is supported for SEP regions in version 14.0.430 and later, excluding versions 2018.2 and 2018.2.1. The reason for version 2018.2 and its patch being excluded is a regression that got introduced in version 2018.2. It is fixed in Feko 2019. The CEM validate message is wrong (this is a known defect) and should be updated. Kind regards Madelé
  11. Hello @SUG Please see this comment: Kind regards Madelé
  12. The model only contains model mesh parts. It does not contain any geometry. Meshes cannot be exported to geometry formats (like Parasolid).
  13. In the attached model the simulation meshes and model meshes are the same, so it does not matter which option is chosen. I have done another visual inspection and could not find differences between the attached Gerber file and the CADFEKO model. Have you used a Gerber viewer to see if the exported file contains the layout that you expect?
  14. Hello @designer First off, we need to identify if the problems you are experiencing are with the CADFEKO export. I had a quick look at the model that you attached and exported the mesh to Gerber and DXF formats using a recent version of CADFEKO. I viewed the exported Gerber file in a Gerber viewer and it seems to be complete (I only did a quick visual check, so I could have missed problems). I also viewed the .dxf file in a CAD viewer and imported it into CADFEKO and I could not identify any problems by doing a quick visual comparison. The .dfx file of course only contains the outline of the mesh (this is expected). How did you evaluate the exported files to verify whether they contain the expected layouts? Can you attach the .gbr or .dxf files that you obtained from CADFEKO with screenshots that show the issues that you are observing? I'm not familiar with HFSS and cannot comment on the best format to use for transferring your layouts between the two software packages. Does HFSS support other mesh imports like STL or NASTRAN? Kind regards Madelé
  15. Hello @Sirajudheen For others to be able to assist, it would help if you could explain what you would like to do with the data and what format the data is in. Are you using CADFEKO to import the radiation pattern to use it as a source in further simulations? If so, please refer to the "AR Card" documentation for the required format. Kind regards Madelé
×
×
  • Create New...