I have recently started learning the tool in order to do a bachelors thesis. Initially all went well. I followed the 20 part steel frame tutorial without any issues. However, I couldn't find many tutorials on geotechnical design. I followed the webinar on pile design (dlubal pile design webinar - Search Videos), however, I consistently recieve the 1327 error. It occurs during the calculation phase for the 3 load conditions (those being soil self weight, pile self weight and for the applied load). I have followed the steps precisely but I cannot find what my flaw is. I understand that the webinar is a bit outdated, but unfortunately I was not able to find a replacement.
I have attached the model to this post: Single Pile from webinar.rf6 (1.9 MB)
I would greatly appreciate your help and potential feedback!
Regarding the issue you described: The error is caused by instabilities in the model. This can occur, for example, due to a missing linearization (nil phase) of the soil.
In the webinar model, the load cases were actually set to inactive, although this was not explicitly shown during the session. The following screenshot illustrates this setting clearly.
Regarding your question about additional webinars on bored piles: Currently, the webinar you mentioned is the only one available on this topic. However, I recommend the following Knowledge Base article on pile modeling: https://www.dlubal.com/en/support-and-learning/support/knowledge-base/001955. The modeling approach described there allows for faster calculations of bored piles.
If you have any further questions or need assistance with your model, feel free to reach out – I'm happy to help!
Thank you very much for your reply. I understand it well now and I managed to fix this specific issue. However, the results that are created from this model are still wrong in some way. Even when I increase the applied point load to a massive or very small value the results do not change and the stresses visible in both the soil and pile do not reflect this force. Previously I thought it can be attributed to this error but that's not the case anymore. I assume I have done another modelling error but I am not quite sure where.
Additional Context