About CodyGielar

CodyGielar

Hi @Drives_Uwe + @stefanAT_ctrlX, Thank you for your help on this. I will send you both the backup parameters, along with a trace. It appears that the fixed stop is detected immediately on initiating S-0-0148 Drive-controller homing, which is why Stefan probably guessed that the Clamping Torque S-0-0530 is set too low. We have raised this clamping torque value higher than the torque values we are seeing on the trace, just by jogging the motor (without hitting the fixed stop.) However, the motor still acts as though its found the hard stop, and homing completes immediately. This is why we were initially confused about what was happening, but the fixed stop was falsely triggered and our reference offset (S-0-0150) began. We have checked actual torque value (S-0-0084), along with S-0-0530 and P-0-0442/ P-0-0443, and we are still running into this issue. Cheers, Cody

CodyGielar

Hello, Initial Details: ctrlX Drive Engineering 01V22.2 AXS-V-0308 XMD2-W1010ANN-02NETM5NNNN-S0308N2NNNN3NN Motor: MSD110A-0027-NN-CS-HR0-14-R-M409 Rotary, Absolute Our customer is experiencing strange behavior when attempting to home using Fixed Stop (Axis Blocking). When positive reference travel direction is selected, the motion direction moves in the negative direction. When negative reference travel direction is selection, the direction of travel results in the positive direction. However, what's interesting is negation is set correctly in mechanics and scaling, and this is proven when jogging the motor using easy startup mode (positive command = positive travel). Only homing is inverted in what is the expected direction of travel. I have a parameter file that I can share with other Bosch Rexroth team members. Customer is using Codesys SoftMotion for motion control, and this is behaving as expected. Only homing within Drive Engineering is where we're seeing this problem. Thank you.

CodyGielar · ‎05-24-2024

Karsten reviewed my STL files, and suggested to either simplify or create new files in CAD software with less detail of non-critical dimensions/ features. These larger, more detailed STL files may also be a problem with RAM in CtrlX Core. I will make these changes.

CodyGielar · ‎05-21-2024

Hello, I'm experiencing a recurring error when either loading an existing machine, or when attempting to import a mesh/STL file to a Machine Geometry Node. The error I get is in the screenshot attached, but the message reads 'bad allocation.' I haven't been able to find any further information on what is causing this problem, or how to resolve it. I can't find any settings on Virtual Machine Builder to adjust the memory allocation of the application either. I've set VMB to 'high priority' via Task Manager, and I'm using about 33% of 32GB available memory. The STL files total up to ~46MB, and are being created from Solidworks. If I try loading the machine several times, the machine will finally generate, but I haven't been able to successfully add the last mesh needed to complete the assembly/ machine. Using 1.4.2 Any help will be greatly appreciated. Thank you!

About CodyGielar

Re: Reference travel direction inverted when homing

Reference travel direction inverted when homing

Re: Virtual Machine Builder - Bad Allocation

Virtual Machine Builder - Bad Allocation