• Announcements

    • Rahul Ponginan

      Please click here for a short but important announcement   03/26/17

      Dear Users Our Commercial and Academic users around the world can use these same forums here as before i.e. the Altair Support Forum , Commercial users from India with solver queries can go to the Solver Forum for India Commercial Users , Academic Users from India and AOC India Participants are requested to go to the Forum for India Academic Users and AOC India Participants , We will be tending to all queries in all the forums promptly as before, thank you for your understanding. 


  • Content count

  • Joined

  • Last visited

About td

  • Rank

Profile Information

  • Country
  • Are you University user?
  1. I just tried to use COUP_KIN instead of KINCOUP and it works! I don't know why, but it does. For reference, my version is 14.0.110.
  2. I tried that and it persists within all my models. I think I don't define the coupling in HM properly since it's the only thing that does not work when imported. My workflow is as follows: 1. Create mesh 2. Create temporary node, move to set "refnode" 3. Create node set "loadset" to be coupled 4. Go to 1D → Rigids, elem type = KINCOUP. Independent = "refnode", dependent nodes = "loadset" 5. Move KINCOUP elements to collector "rigids" 6. Create solid property card for part with material card, assign property to solid and material to property 7. Create rigid property card, assign it to "rigids" collector, assign material to the property, under Elset options: Component name = "rigids" 8. Set temporary node "refnode" as reference node 9. Create CLOAD in load step browser, with node set = "refnode" I tried not assigning a material to the rigid property and I tried deleting the temporary node and assigning the created node from the rigids as reference node. No couping is imported into Abaqus. I don't see where the error is. Error: WARNING: Unknown assembly level element set RIGS. This occurred while processing rigid body definition. The rigid body definition will be ignored. WARNING: The following keywords/parameters are not yet supported by the input file reader: --------------------------------------------------------------------------------- *KINEMATICCOUPLING
  3. Hi, the sets are active. The boundary condition is imported properly into Abaqus. The only thing missing in Abaqus is the nodeset the concentrated force is applied on, which is odd.
  4. Hi again, it's been a while since I used Abaqus and I am facing the same issue. Abaqus tells me: The model "test" has been created. The part "PART-1" has been imported from the input file. WARNING: Unknown assembly level element set RIGIDS. This occurred while processing rigid body definition. The rigid body definition will be ignored. WARNING: The following keywords/parameters are not yet supported by the input file reader: --------------------------------------------------------------------------------- *KINEMATICCOUPLING The model "test" has been imported from an input file. Please scroll up to check for error and warning messages. When trying to run a job, the following pops up: The job "Job-1" has been created. The job input file "Job-1.inp" has been submitted for analysis. Error in job Job-1: NODE SET ASSEMBLY_LOADSET HAS NOT BEEN DEFINED Error in job Job-1: A CONCENTRATED LOAD HAS BEEN SPECIFIED ON NODE SET ASSEMBLY_LOADSET. THIS NODE SET IS NOT ACTIVE IN THE MODEL Job Job-1: Analysis Input File Processor aborted due to errors. Error in job Job-1: Analysis Input File Processor exited with an error. Job Job-1 aborted due to errors. So, why is the set not defined or exported from HM? Where's my error? HM version is 14, Abaqus version is 2017. test.inp test.hm
  5. I got Acusolve 2017 installed locally an a machine to test a few things. By the way, I went to an Acusolve training session a few months ago and we were told to pick fixed time stepping over adaptive time stepping. After asking why, since every other program I know supports adaptive time stepping without a problem, we were given no details unfortunately. Maybe this was the reason. Also, I just tried opening a test run of AS2017 in Hyperview 14 using the .log file after the same case done with adaptive and fixed time stepping. When I try to apply the velocity contour plot, Hyperview just crashes and closes without a message. Using Ensight is no problem.
  6. Hi again, I was wrong in my previous reply. The version installed on the cluster is 14.0 while my local version is still 13.0, so no wonder there might be compatibility issues. Sorry for that, no more searching needed I guess. I just tried H3D and while it did convert with AcuTrans without errors, Hyperview tells me this after a few messages: Error: Failed to attach results.
  7. There is only one version of Acusolve suite installed, which is v13.0
  8. Hi, Thanks for your answer. Acusim.dir exists of course. With the Reader Options tab, I did get all my output options to show up, but I still got the "Time does not match" error. Until now, it only occured when I ran shear thinning (power law) cases, newtonian setups were no problem. When this happens, the displayed time steps do not match the results I expect. For example, the case at hand was the full geometry I am examining and I already ran parts of it (1 degree, 5 degrees of the rotationally symmetric body), so I know what to expect. The last displayed result of the full body is not what the other cases showed, which I ran on my local machine and exported to Ensight using AcuOut. I just tried acuTrans. I opened Acusolve CMD prompt, navigated to my case and typed "acuTrans -translate_to ensight" to test it. Unfortunately, it told me this: acuTrans: *** ASSERTION in Function <iopCheckStr> File <iopLow.c> Line <2074> acuTrans: *** data out of order: expected <nAoutVecs> found <nFields> in binary file <ACUSIM.DIR/acusolve.2_0_x.out> token <8> near <nFields> Is the message "data out of order" maybe related to the issue I have described above? As far as I know, there is no GUI access.
  9. Hi, I was sent here coming from this topic right here: I ran a case on our cluster and now want to export the results to Ensight format to postprocess in Hyperview, but AcuOut does not seem to find the results. I tried to open the case (.acs file) in Acusolve and export it using AcuOut. I assume this way only works right after a case as been solved locally. However, I need to export the files coming from another machine. How can one do this? By the way, I can't just open the .log file in Hyperview. I run shear thinning fluid simulations and when I try to open these in HV via the logfile, I get an error saying "Time does not match" and I can't display all the time steps. Also, velocity and pressure are the only displayed values this way, although I set more than these. So this way is not an option, unfortunately.
  10. Hi again, another question regarding this topic. I ran a case on our cluster and now want to export it to Ensight format using the way you described. Unfortunately, this only seems to work for cases treated locally. When I open the completed case in Acuconsole and try to use AcuOut, the new window loads for a few seconds and disappears again. How can I export the results?
  11. Hi, I'm using Hyperview of course. Your procedure worked, thanks a lot. I previously only opened the log files in Hyperview as it was the suggested option of HV. This works wonderfully though, so thanks again.
  12. Hi, I'm using a full version (HW 14). I just tried a lid-driven cavity flow with shear-thinning fluid behaviour (it's HDPE, so very low Reynolds-number and thus difficulties solving for diffusion, I've got some problems with this in OpenFOAM as well) and it was unfortunately the same error. I've attached the case so you can take a look. The first log file is a newtonian oil, the second one the shear-thinning HDPE. liddriven_cavity.rar
  13. Hi, I just tried a CFD simulation with shear-thinning behaviour using Acusolve and tried to view the results in Hyperworks 14. Unfortunately, when I try to view a time step after the initial condition, a window pops up saying "Error: time does not match" and I can only see a single step. Whether it is the last or the first or somewhere in the middle is unknown. I tried different methods of output (i.e. after n steps or after n seconds) and different time scales, but it was the same. I've never gotten this error when using newtonian fluid behaviour. Does anyone know how to handle this?
  14. Just another thing I found out: The main problem was that I enabled the option "Clip elements" in the cutting plane tool. The consequence was, that the pathing went all haywire and the path calculation took forever. With "clip elements" disabled, it works a lot better.
  15. I did try that, but apparently I didn't choose enough nodes at first. With 15 nodes along the axis, it works. Thank you for the hint.