[chrono] Re: Import CAD assembly from SolidWorks to Multicore

You may want to provide here the changes you applied to demo_MCORE_Cratering and its CMakeLists, otherwise it might be difficult to give suggestions. Moreover, it is better to try to change the template project to adapt it to your need, not the demos: you might easily miss all the required link

[chrono] Re: Can I find resonance frequencies and model shapes?

Hi, are you talking about something like this? https://api.projectchrono.org/development/manual_modal.html Il giorno giovedì 1 agosto 2024 alle 17:55:20 UTC+2 cor.janse...@gmail.com ha scritto: > Hi, > I used Chrono a long time ago and was very pleased with it. I used it for > a kinetic simula

[chrono] Re: Import CAD assembly from SolidWorks to Multicore

Hi Gianni, I reuploaded it. There was still a missing piece! Try now! Dario Il giorno lunedì 22 luglio 2024 alle 13:59:29 UTC+2 eldest...@gmail.com ha scritto: > Hi Dario, > > thank you for your kind reply! I tried to reinstall again the Chrono > add-In but nothing changed. The error is always

[chrono] Re: Import CAD assembly from SolidWorks to Multicore

Hi Gianni, the SolidWorks plugin had a bug that was not allowing running the simulation withing SolidWorks. You should now be able to get the new version and make it run in SolidWorks. About the motor: please try to make it run directly from SolidWorks. I would recommend you to remove any link

[chrono] Re: Problem with building project in CMake

You have probably used backward slashes when you built the Chrono library. The log is cut so I cannot tell you where, but please revisit your Chrono CMake (not the one of the project that seems to be fine) and replace all the backward slashes \ with forward slashes / Il giorno domenica 7 luglio

[chrono] Re: Import CAD assembly from SolidWorks to Multicore

Hi Gianni, - can you please share the CMakeCache that is found in your build folder? - what the "Dettagli" panel returns when the "Run simulation" button is pressed? - can you please try to remove the motors in Solidworks and do them manually in Chrono? There is something wrong,

[chrono] Re: Import CAD assembly from SolidWorks to Multicore

Ciao Gianni, motor frames are defined in SolidWorks through *Reference Geometry>Coordinate System* entities. As any other link in Chrono, the Z axis of the Coordinate System is taken as the revolute axis. No additional change is made at the code level. 1. your "Sistema di coordinate", the one

[chrono] Re: Writing Chrono::System to file

you have to make sure that the model is exactly the same and also that can be additional relevant variables (e.g. some variable in the timesteppers) that is not retrieved in this way thus making a slight difference when you load back the state. Il giorno giovedì 20 giugno 2024 alle 23:18:46 UTC

[chrono] Re: Writing Chrono::System to file

Hi, yes there is. You may find more references by searching for the "archive" keyword instead of serialization. *demo_CH_archive *is a starting point, but it's probably showing many more features that just s

[chrono] Re: Failing to build Chrono

P.S. as mentioned in other posts CUDA 12.5 is not currently working fine with Chrono so you may need to downgrade to 12.3 or 12.4 or wait for the appropriate fix to Chrono (in the coming days probably) Thanks, Dario Il giorno venerdì 14 giugno 2024 alle 23:37:54 UTC+2 Dario Mangoni ha scritto

[chrono] Re: Failing to build Chrono

Hi, - do you *really *need both MPI and CUDA? - does a simple plain compilation of Chrono *with no modules enabled* work fine? - which modules did you enable? Can you please *share the CMakeCache.txt* inside your build folder? - you are showing errors during *compilation*: was

[chrono] Re: Problem compiling ProjectChrono on Linux with CUDA 12.5

Hi MDP, Chrono is not currently compatible with CUDA 12.5. We recommend sticking with 12.3 until the fix will come! Dario Il giorno mercoledì 12 giugno 2024 alle 12:46:57 UTC+2 MDP ha scritto: > Dear all, > > I'm writing here to ask your help with my installation of ProjectChrono, > that fails

[chrono] Re: Installation problem. Errors LNK1181 and C1083.

Thrust is not distributed as a standalone product anymore and it is now bundled together with CUDA. You should still be able to download and link to the *older *versions of Thrust available on their GitHub page, but since you had problems I would recommend you to just pick the one coming from C

[chrono] Re: Installation problem. Errors LNK1181 and C1083.

Hi Alessio, what CUDA version do you have? Is it >=12.4? The CUDA API changed in the latest release and we didn't push the fix for it yet. Dario Il giorno lunedì 10 giugno 2024 alle 16:18:55 UTC+2 Alessio ha scritto: > Hello everyone. > > I'm a master student and I'm trying to download Chrono

[chrono] Re: How should I select scene objects by mouse?

No interaction with the mouse. The GUI is intended to render objects, not to interact with them. Il giorno venerdì 22 marzo 2024 alle 10:18:52 UTC+1 zanx...@126.com ha scritto: > There are too many places involving mouse in the example, and the > corresponding reference code is not found. I wo

[chrono] Re: Rotation around an axis.

Hi Massimiliano, did you get a look at demos? demo_MBS_motors, case A-1 Please mind that *ChLinkMotorRotationSpeed *includes *by default* the revolute link (if you don't disable it). You can change its behaviour through ::SetSpindleConstraint, but I would recommend you to remove the ChLinkLock

[chrono] Re: error C1060: compiler is out of heap space - Visual Studio 17 2022

Hi Haifei, that's really unfortunate. I previously had a 16GB laptop of few years ago and it was working very slowly but fine with only 1 parallel build. As you can see from the installation page we don't have the test Chr

[chrono] Re: 【Build Python modules from the C++ API】ERRO: core.vcxproj---failed

uhm, strange things; can you please post the entire CMakeCache and CMake log (not only a screenshot)? Il giorno martedì 5 marzo 2024 alle 02:58:21 UTC+1 Zed Sun ha scritto: > Computer system: Windows 11 > CMake version: 3.27.4 > Python version: 3.9 > Visual Studio version: 2022 > > When I was b

[chrono] Re: error C1060: compiler is out of heap space - Visual Studio 17 2022

Hi Haifei, this is indeed quite an annoying problem: due to the heavy usage of templates in the Eigen library and in some parts of the Chrono code (mainly FEA) the compilation requires big amount of RAM. The options are few: - *reduce the number of parallel builds*; I'm afraid you have to go

[chrono] Re: tiny_obj error message: Cannot open file

Prabas, please always provide a reference to the script that throws issues, not just the error itself. Second: I wrote to you in the previous post " I think you are also missing *vehicle::SetDataPath(CHRONO_VEHICLE_DATA_DIR);"*Did you do it? Il giorno martedì 27 febbraio 2024 alle 15:50:13 UTC+

[chrono] Re: ChronoEngine_irrlicht.dll not found

>From your CMake log: -- ...D:/chrono/chrono/libraries/irrlicht-1.8.5/irrlicht-1.8.5/bin/Win64-VisualStudio/Irrlicht.dll -- ...D:/chrono/chrono/build/bin/Debug/ChronoEngine.dll -- ...D:/chrono/chrono/build/bin/Release/ChronoEngine.dll -- ...D:/chrono/chrono/build/bin/Release/ChronoModels_robo

[chrono] Re: ChronoEngine_irrlicht.dll not found

Prabas, did you go through the Chrono installation procedure ? Did you ENABLE_MODULE_IRRLICHT? You sent the CMake of *your project* but not the one *of Chrono itself*. And also: please look at the template project. You shoul

[chrono] Re: Load-In for High Velocities

Hi T-Lind, This usually happens when the initial position of bodies is violating constraints. Might be your case? You may want to try to call *DoFullAssembly()* before starting your simulation (or *DoAssembly*): this will try to close all joints before starting, but I would encourage to actually

[chrono] Re: Assertion failed: ChTriangleMeshConnected.cpp, line 269

And also please don't throw same questions twice. Il giorno lunedì 26 febbraio 2024 alle 15:53:46 UTC+1 prabas...@gmail.com ha scritto: > Hi, > > I am trying to build a very simple project where a MAN truck spawns in a > rigid terrain. The build is successful. but when I run the exe the > fol

[chrono] Re: error LNK2019

Ah, that's not the error I was mentioning. If you forgot to add Vehicle module that's a totally different story. I think you are also missing *vehicle::SetDataPath(CHRONO_VEHICLE_DATA_DIR);* Anyway: you are in Debug mode. You can easily understand what is causing you issues. Please take your tim

[chrono] Re: error LNK2019

Hi Prabas, there might be a couple of issues: - it seems that you didn't call *SetChronoDataPath(CHRONO_DATA_DIR)*; - if the issue persists it might be due to a wrong linking to VisualStudio runtime libraries (but that's assumes that you are on Windows, with VisualStudio and you are

[chrono] Re: Basic Motor Example In An Assembly

I don't know what you are trying to do: in your latest example 'shaft' and 'base' have two links pointing in two different directions. Did you want to link to ground instead? Moreover, the motor already provides the revolute joint embedded. So you are duplicating the joint. And also, you enable

[chrono] Re: Basic Motor Example In An Assembly

Hi T-Lind, the "nothing seems to work" means that the rotating axis is not matching your expectations? Can you show a picture? Maybe one with CoG drawing enabled, one with Link frames enabled? Why don't you try with something simpler first? Without many rotations in between? We also have plenty

[chrono] Re: Collision issues with custom module imports

Hi Jay, about collisions: did you went through the documentation about collision settings and tried to tune the parameters before asking on the forum? about detecting forces: if you are using simple rigid bodies di

[chrono] Re: multi-core collisions is strange

Hi Page, I'm sorry but in the latest months we changed the Chrono API quite a bit, so I cannot easily compile your code that is referring to an old version. I would recommend you to recompile Chrono with latest version if you can. While you others' answers, I can just broadly suggest to: - r

RE: [chrono] Unresolved External Symbol in project

Hi Daniel,Indeed many things changed especially in the recent past, so it's a great time to update old code. It's surely better to look directly to the code instead of the error only, but I would recommend to check few things:- call SetCollisionSystemType on your ChSystem (if you have contacts) 

[chrono] Re: About real-time simulation

Hi Page, the answer about collision parameters has a very simple answer: *no, there are no one-fits-all parameters*. If you understand what they are meant for (if not, please refer to docs ) you can easily understan

[chrono] Re: How to remove a module

Hi, the problem is that, by removing only the bodies, the links that are bound to such bodies will have dangling pointers. For the time being you can remove the relative links by doing something like: Before the simulation loop: *myfoot = mysystem.SearchBody('M-410iB-300 -3/M-410iB-300-

[chrono] Re: installing chrono(c++)

Hi Henry, did you downloaded the *Irrlicht library*? Actually the guide is giving this step as granted, I'm going to improve it. You can pick it from here: https://irrlicht.sourceforge.io/?page_id=10 BTW, please always attach the CMakeCache.txt when you report some issue. You can find it in the

[chrono] Re: Installing Chrono (C++)

2024 alle 01:43:21 UTC+1 Dario Mangoni ha scritto: > Hi Henry, > sometimes (but I don't remember why) you need to specify the location of > the Eigen library through the EIGEN3_INCLUDE_DIR variable that is not shown > by default in CMake. > So, please click on *Add Entry *and

[chrono] Re: Installing Chrono (C++)

Hi Henry, sometimes (but I don't remember why) you need to specify the location of the Eigen library through the EIGEN3_INCLUDE_DIR variable that is not shown by default in CMake. So, please click on *Add Entry *and specify it manually, like this: [image: 2024-01-14 01_41_58-Add Cache Entry.png]

[chrono] Re: TypeError ChForce.SetAlign(), PyChrono

BTW, for future readers, we added a new page about Loads in Chrono. Check it out <https://api.projectchrono.org/development/loads.html>! Il giorno sabato 23 dicembre 2023 alle 15:36:52 UTC+1 Dario Mangoni ha scritto: > Hi Dash, > yes, of course you can implement the behaviour m

[chrono] Re: TypeError ChForce.SetAlign(), PyChrono

Hi Dash, yes, of course you can implement the behaviour manually! The ChForce class is surely something that would benefit a nice refactoring, but the TODO list is always full. In any case I would still recommend you to use classes derived from *ChLoadBodyBody *(you then need to put it into a *

RE: [chrono] Error building my_example.cpp

Hi Alessandro,Before building the demo did you compile Chrono properly with no errors?At which commit is your code?Are you using the template_project right?Where and when did you pick the template project?Because for example the ChCollisionModel is not in the collision namespace anymore, thus su

[chrono] Re: TypeError ChForce.SetAlign(), PyChrono

Hi, as you mentioned the *SetAlign *accepts an *AlignmentFrame *type. In C++ it would have been quite easier to spot that his definition is encapsulated in *ChForce *itself, so it should have been : *spring_force_2->SetAlign(chrono::ChForce::AlignmentFrame::BODY_DIR);* However, the wrapping just

[chrono] Re: Segmentation fault in reduced order model

Hi Victor, I'm not an expert on modal reduction, but in the meantime can you be more precise about the problem? For example: 1. you say "some of the input matrices are wrong". What "wrong" means to you? Are there missing coefficients? Is the size wrong? Does the stiffness matrix have d

[chrono] Re: URDF and ROS2 support

Hi Riddhesh, while we wait for more insightful answer please double check the Changelog at the New URDF parser notice. Regards, Dario Il giorno venerdì 1 dicembre 2023 alle 11:31:54 UTC+1 riddhes...@gmail.c

Re: [chrono] Re: Misconfiguration

Hi, looks like there is a big confusion here. Please answer this very big question first before anything else: *are you really sure to need ALL these modules*? That's hugely unlikely. Even if so, you need to make one step at a time: so please follow this procedure to compile the core library an

[chrono] Re: Misconfiguration

Just a preliminar question: you said you enabled "all" the modules. Given the amount of errors looks like you really enable many... but* do you really need them*? You need URDF, VSG, MUMPS, MULTICORE, all enabled? In general I would recommend to *enable ONLY those modules that you really need*.

Re: [chrono] Re: Debugging problem

is program and I'm trying to figure out how to use it properly. > Thank you for your support! > > > Il giorno mar 17 ott 2023 alle ore 23:11 Dario Mangoni < > dariom...@gmail.com> ha scritto: > >> Hi Davide, >> probably I misguided you: by sending the CMake log

[chrono] Re: Debugging problem

Hi Davide, probably I misguided you: by sending the CMake log I meant to copy and paste all the text that you find below the *Configure|Generate|OpenProject* buttons. Moreover, it would be great if you can also attach the *CMakeCache.txt* file that you can find in your *chrono_build *folder. An

[chrono] Re: Debugging problem

Hi Davide, the wording "I downloaded the tutorial demo_CH." sounds a little awkward to me: you cannot download just a single file and compile it. So maybe it's really a stupid question but: did you compile the Chrono library first? Did you follow the install instructions? https://api.proje

Re: [chrono] CMake version problem for chrono tutorials

Thanks, I think I need to make a run on a Linux machine. I didn't have the chance yet Messaggio originale Da: Prakhar Gupta Data: 11/10/23 21:21 (GMT+01:00) A: ProjectChrono Oggetto: Re: [chrono] CMake version problem for chrono tutorials Here you go: PrakharOn Wednesday, 1

RE: [chrono] CMake version problem for chrono tutorials

Hi Prakhar,we just changed the template project and the relative chrono-config file so we surely need some feedback. Could you update CMake to latest version?  Dario Messaggio originale Da: Prakhar Gupta Data: 10/10/23 22:51 (GMT+01:00) A: ProjectChrono Oggetto: [chrono] CMa

Re: [chrono] Re: DLL 'ChronoEngine.dll' in package Chrono is not installed properly

Oh yes, I found this error also in my code! I fixed it in my local copy and it will be pushed soon. I forgot about it. @Radu, it's actually quite strange: if I look at the log for the cmake/chrono-config.cmake.in it does not seem that the line was changed but I found that also on my pc there was

[chrono] Re: DLL 'ChronoEngine.dll' in package Chrono is not installed properly

Hi, did you make sure that both your project and Chrono were built with *same configuration type*? We are currently rewriting the files that are used for linking from external projects so this info might change in the very next future, but as for now I would recommend you to *compile both Chrono

Re: [chrono] Installing PyChrono and Chrono on the same PC

Hi Luis and Radu, just last week my colleague (the other Dario) tried to install PyChrono through Anaconda while he already had Chrono::python built from source. He reported some corruption of the latter, so I think he just uninstalled Anaconda right away. So please mind that there could be prob

[chrono] Re: can not find irrlicht.h

Can you please share with us your CMake configuration? Especially the IRRLICHT related variables IRRLICHT_INSTALL_DIR and IRRLICHT_LIBRARY. I assume that you had installed Irrlicht library before, right? Dario Il giorno sabato 9 settembre 2023 alle 04:09:02 UTC+2 winte...@gmail.com ha scritto

[chrono] Re: FMU models

Hi Vincent, I just really started last Saturday in some spare time so I don't have any specific suggestion to give you yet. As you probably may want to do, I just set up CMake to work with some generic code without even linking Chrono, just *rapidxml *to generate the *modelDescription.xml.* I st

[chrono] Re: FMU models

Hi, you come at almost the right time: in the next few weeks I'll start looking into some *general/automatic way to export FMUs out of Chrono* and I plan to be able to generate the first *Cosimulation FMUs *within September. I recently spent some time upgrading and fixing the Chrono serializatio

Re: [chrono] irrlicht 1.8.5 have not lib file of Linux

As it is reported by the compiler, you should recompile with -fPIC Il giorno giovedì 17 novembre 2022 alle 15:44:42 UTC+1 yaoyiyao ha scritto: > Thank you for your replay. > I build the library under Linux successfully. > then I generate in cmake . > I run command make in the same build direct

[chrono] Re: Reduction of CPU time with SIMD option

Hi Camille, I'm not sure if it is the same issue I encountered, but might be worth you to just briefly visit this issue: https://github.com/projectchrono/chrono/issues/290 In my case the Eigen::SparseLU solver was having issue, at the point that solutions themselves were off and it was due to m