Lobenstein

Thanks! Works great @MoMo

Has anyone ran into this before? In turbo we had no issue downloading programs with this many labels but Power is telling us we cannot???

I am currently converting one of our machines from turbo to power and am struggling to figure out the bias position setup. In turbo we would bring the machine down to the part and do a "PSET X0 Y0 Z0". This sets positions to 0 so we can then work off position 0 for our operation. When we are finished we return to position 0 then do a PSET command using the part position we were at previously to restore machine actual position. I have been trying to do this in Power by setting the Motor[x].HomePos equal to commanded position to set my positions to 0 and it just is not behaving correctly when running the tool path. I was wondering what the best practice is in PowerPMAC for mimicing the bias position from turbo?

Thanks rsipkema, I'm having our maintenance staff loo into swapping out all the cabling now. That's the only answer I see that makes sense. We do no use cutter comp so I know it can't be that. We have 16 machines running the exact same project and one of them just started having this 1000A error happen multiple times a day no matter what I try and do to fix it.

We are using firmware 2.7 on a CK3E, but also had this issue on a CK3M. We have multi machines and it happens at random to them all. We are not using any cutter comp features. We are running at 2kHz servo update and for a short time we tested with it bumped up to 4kHz and the 1000A error happened much more often at the faster speed (this was tested on a CK3M). It happens seldom at 2kHz but does still happen randomly.

Not often and at random, we get an Ecat[0].Error = 1000A. We are configured for acontis and all their error codes are 98XXXXXX, the closest acontis error code is: EC_E_NOMEMORY 0x9811000A: CFG: No memory left (e.g. memory full / fragmented)) This is the only error we get that is not the full error code and it does not appear to do anything with memory. I believe this error code means something different that is not noted under the acontis error code list. Has anyone else came across something similar???

I can't seem to get the actual torque values to come in as a 16 bit signed value through PDO mapping. If the torque is a negative number it rolls over and I get some large value. The only way I can seem to make it work is to bring in the actual torque through the encoder conversion table and scale it there and just read the DeltaPos value. Is this the best method or is there a way to bring this PDO in as a 16 bit signed number?

Has anyone ran into the before when trying to open a project? This version of the IDE is the same version the project was created in.