Advanced Search

@ Rüdiger,

Max acc scurve = 2 x acc.
at scurve inflection point the
Scurve acc = 2 x acc.
see  scurve lib abstract.
 

Hello,
I tested further and apparently the acceleration is not limited. In the ini it says 'MAX_ACCELERATION = 5000' in the halscope at approx. -10000.

Gruß Rüdiger

 

So i received the card back with no reported problems but i still cant get any output to my drives. I completely reinstalled Linuxcnc, Mesa flash and Mesa CT with the same results. I'm at a total loss with this thing.. I tried to use the Pncconf wizard but it doesn't support the card I bought. Would i be better off sending this on back and getting some of the older ones that are a little more user friendly?

Have you had a look at the included rosekins?
linuxcnc.org/docs/html/man/man9/rosekins.9.html

There is is a sim config:
github.com/LinuxCNC/linuxcnc/blob/master...s/rose_engine/README

I really appreciate you guys looking at and commenting on this. I would not have thought of that, but I never touched that part of the Maho wiring, so it still has the hardware inhibits on the main 3Ph contactors.
 

Output-03 only runs one of the 24V relays to control 24V to one of the little gearbox shifter motors.
 

I have had the shared memory warning too. I don't think that's related to ethercat, it is something else. I ignored the warning and well it didn't go away but I can't see it causing a problem.

So the drives are in OP, good.
But you use that minimal hal file, the four lines hal file you attached?
You now need to have a hal file describing the movements and limit switches and so on. From a real linuxcnc system.
I guess you have a lathe in mind.
Your drives are cia402 drives, one way is to start from the cia402 example, link here. github.com/dbraun1981/hal-cia402/tree/main/example
You can have a look in the example ethercat-conf.xml for inspiration, but use your own.
The hal file you can use. It's for one axis, you extend it to a Z axis.
 

I still get the shared memory buffers warnings (as before) but linuxcnc will start. The drives show to be in OP status and the linuxcnc shows the axis moving, but the steppers do not move

Is it not possible that the blown 7i84 output resulted in a constantly on state, possibly causing the fwd and rev 3 phase contractors being active at the same time? That would cause the 3 phase CB to trip.

The relays should however be hard wire interlocked to prevent this from being possible

Thanks PCW, that works fine.

Looks like StepConf did not connect parallel port 0 pins 8 and 9 (probably confused by the dual definition)

If you just want to drive the X and X2 outputs in parallel (not on separate joints),
you would need to add:

net xstep => parport.0.pin-08-out
setp parport.0.pin-08-out-reset 1
net xdir => parport.0.pin-09-out


To your hal file.

Thanks a lot.

I just rechecked. You are right. There is no single phase breaker on 3Ph power in this cabinet. It was Q2, a 3ph 16A breaker which tripped.

 
Downstream of this, the 24V rail of line 204 is powered through the 2A 6F2 breaker, which did not trip this time.

 

The field power of the 7i84 is powered off line 204 (incorrectly marked here as 200).
 
It is the output-03 (TB3-20) which appears to have blown, according to the damage trace on the housing of the IC.
In my search for root cause, I dont understand why a 16A 3Ph breaker would trip if there was a short in a downstream DC circuit protected by a 2A CB.

After dinner I will work back from the 24V control relay 11K6, moving back along the wiring until I get to Q2 looking for shorts. Any other trouble shooting recommendations are much appreciated.
Cheer,
Mark

 

Here it is. I don't *know* of any changes I made.

One more thing I notice that wasn't there before, on opening Axis I get:
Unexpected realtime delay on task 0 with period 39370
before I actually do anything, like enable the motors.

 

Hello,
attached is the hal file with the jerk pins. 

Gruß Rüdiger
 

 

Much better.

In the second line, the "<master idx="0">" line
add so it becomes <master idx="0" appTimePeriod="1000000">
that 1000000 number must match your SERVO_PERIOD setting in the ini file. It is normally 1000000 (= 1 millisecond)
Let's see if that is enough or if you also need to specify distributed clock settings.


 

I am looking for guidance on how to setup the C axis as a second spindle.  This is for a rose engine lathe (otbok.info/index.php?n=Main.RoseEngineLathe) where we need to use:

1. the Spindle to rotate the piece, and
2. the C axis to rotate the rosettes used to impart the design

We turn these quite slowly, certainly less than 10 RPM, and at times speeds approaching 3 or 4 minutes per revolution.  Thusly we are using stepper motors for both axes.

The end goal is to drive the spindle and the C axis simultaneously, but specifying a relationship percentage for their rotational speeds.  For example,  Is there some documentation I can read which describes 

1. How to setup LinuxCNC to treat the C-axis as a secondary spindle, and
2. The G-code I would use.

Apologies if this is already been asked and answered:  I searched the forum and could not find it.