API ParticleBodyForceV3_10_0

May I ask whether there is an example ParticleBodyForce API implemented using the IPluginParticleBodyForceV3_10_0 interface?
I have encountered several issues while updating my API, and I was wondering if you could provide an example based on version V3_10_0. Thank you very much.

Find more posts tagged with

EDEM

v2026.0

Accepted answers

All comments

Renan

Hi @Alice Sun,

What are the issues you're facing? Can you share any error messages and/or your code?

Best regards,

Renan

Alice Sun

convectiveheattransfer.zip

Hi Renan,

Thanks for the reply.

Here is my code; it seems to contain many errors.

Renan

Hi Alice,

I was able to compile the code you shared into a dll without any problems just by changing line 6 of the .h file to:

#include "HelpersV3_9_0.h"

Please let me know if that works for you.

Best regards,

Renan

Alice Sun

It still doesn’t work. Both NApiHelpers and NExternalForceTypes are highlighted in red and show errors.

I am using EDEM 2026, and although I can barely compile the code into a DLL, it still cannot be used in EDEM and results in this issue.

Renan

Hi Alice,

Here's the code I used. I was able to compile it into a dll and EDEM recognized it as expected.

Let me know if it works for you.

Best regards,

Renan

ConvectiveHeatTransfer.zip

Alice Sun

HeatConvection.zip

Hi Renan,

Thank you very much for your help and patience.

I have updated and modified the API, and the attached files contain the revised code. However, the generated DLL still cannot be used in EDEM 2026, and it is not supported by the CPU solver.

Renan

Hi Alice,

To make your API model work on CPU, you have to add the following line to the setup function:

solverFlags.enableFlag(NApi::EApiSolverFlags::eCpu);

If you also want it to be compatible with the CUDA solver, you have to add the following line:
solverFlags.enableFlag(NApi::EApiSolverFlags::eCuda);

Finally, you also have to add the following line to make it compatible with the multisphere shape:
particleShapeFlags.enableFlag(NApi::EApiParticleShapeFlags::eMultiSphere);

Best regards,

Renan

Alice Sun

I really appreciate your help—this DLL now runs well with the CPU solver. However, when I switch to CUDA, I encounter the issue shown in the screenshot. The .cu file is included in the ZIP package I just sent. Could you please advise what might be causing this and how I can fix it?

Renan

Hi Alice,

The definition of the configForTimestep functions in your cuda file are wrong. They should also include NCudaApiTypesV1_0_0::CApiTimeStepData& timeStepData. For example:

__device__

void configForTimeStepParticleProperty(NCudaApiTypesV1_0_0::CApiCustomPropertyData& particleProperties,

                                       NCudaApiTypesV1_0_0::CApiTimeStepData& timeStepData)

{}

Add this argument to all configForTimestep functions and the code should work.

For future reference, you can find the signature of all cuda functions in the example plugin located at: "EDEM_install_folder\src\Api\Cuda\examplePlugin.cu"

Best regards,

Renan

Alice Sun

cuda.zip

I have modified the .cu file following your suggestions, and the updated version is attached. However, the issue shown in the screenshot occurs. Could you please advise on what might be causing this issue?

Renan

In line 55, you need to add () after getVelocity. Make sure to add () after every get function. As a suggestion, make sure to use a text editor like VisualStudio that will help you find these small mistakes

Also, in line 90, instead of simulation.getTimestep(), you should write simulationData.getTimestep()

Alice Sun

Thank you very much. The model can now run with CUDA.

In addition, when I use Visual Studio, the .cu file does not show these minor errors. Is this because the file is not placed in the correct location?

Renan

Please check the comments of the file: "EDEM_install_folder\src\Api\Cuda\examplePlugin.cu" to learn how to enable intellisense and syntax highlighting for cu files on visual studio

Alice Sun

Hi Renan,

Thanks for your reply.

I would like the properties to be zero at every time step. Could you please help me check where the issue might be in the code? Should 0 be changed to property index 1 or 2?

Alice Sun

Hi Renan,

I have resolved the issue related to resetCustomProperty. However, I found that when using my custom API together with EDEM’s built-in Temperature Update Model, the particle temperature does not change during the simulation. In other words, the heat flux calculated by the heat convection model is not being passed into the Temperature Update Model for temperature updating. Could you please explain why this is happening?

Thank you very much.