Advanced Search

Updated PB and need to re-do all the numbered parameters in my customized tool change subroutines.

While digesting the subroutines, I found that parameter #5210 is used twice:

unload_spindle.ngc
M61 Q0
G49
#5210 = 0
#3991 = 0

M13
M61 Q#3991 G43 H#3991 #5210 = 0

According to the LCNC docs, #5210 appears to be written by LCNC if G52 or G92 offset is applied.  I'm guessing this is not normally a user-writable parameter.

Is this an error, or am I misunderstanding something?

drive  have 3 control loop
the first is current loop can auto tuning with motor parameter
second is speed loop and third is position loop if need
delta C2000 look like have speed loop auto tuning, but maybe need mod by manual


 

You are welcomed, always.

Thanks all
Got it Fired up with supplying power as above.

Thanks for being a bouncing board for my out loud thoughts!

Aciera post=309633 userid=25994In that case use PncConf or MesaCT to create an XYZA config (IIRC that is the maximum number of axes supported in the configurator) and get that working in trivial kinematics (ie motors move correctly). Once that works copy/modify the A axis/joint entries in the hal and ini files to create the other axes you need and get them working as well.
 

I have a 5 axis machine working moving in joint mode so the hardware checks out. 

Can trivkins handle 6 axis, revolute, X,Y,Z,A,B,C or do I need to progress to genserkins at this point?

 

Answering the cost concerns, the prices andy shared unfortunately are not realistic now. Up to now I spend 190-200€ for each board.
I can drive 3.5-4.0W servo (the ABB arm are 4.5W) with the v5, the main problem I'm facing is the need for a proper rectifier with a decent power factor, we are working in developing one with pfc, brake resistor and maybe also bidirectional.
Going 600vdc open to 3phase rectifier and I think less capable of handling high currents for lower voltage motors. Then we should keep two different versions of the board.
Btw I think is not much difficult to make it 600v compliant, more clearance, the isolator (SI8621) should be fine, change the cap, recalculate the resistor voltage div, change the connectors...
Who knows if is possible to use these boards in a industry plant? Is possible to certify a machine using these boards? (CE for example here in Europe)

Tired of fighting Debian.  MX23 seems to be working so far.  PB works, decent ping times with Mesa, running latency now.

No, I fell at the first fence!! Failure to understand LinuxCNC, frustration in setting it up on my pc, then thinking even if I mastered the pc I'm not really sure I want to be tapping at a pc key board in the oily workshop. Time flies by and 8 years later this week I came across the Mesa 7176E, Nema 34 motors and DQ860MA drivers sitting in a drawer in my office . Actually I did mount one motor to the leadscrew but never connected it to anything. I've been using the lathe entirely manually after fitting a carriage handwheel twice the original size. I think I should buy the rocketronics.de ELS controller where I do not have to stretch the brain. Or another similar idiot proof package if there is one. I will be happy just to have carriage control for threading and general turning. Probably try to sell the Mesa 7176E on ebay.

I did the "short a pair of wire" test but there is no detent at all so must be an induction motor.
Also changing the accell to 60 seconds for example does not change the behavoir.

I have a quick chat with a delta guy tomorrow, perhaps he has some insight.

Python 3.12.5

The 'whats-new' link you posted appears to be outdated.  Deb trixie is now shipping with Python 3.12 exclusively.

Trying to figure out how to install 3.11, but I'm getting lost... something about using deadsnakes PPA.

I noticed that the pressure drops immediately after the lubrication pump is switched off. I think it is better to check the pressure switch before lubrication time end. With 30 second lubrication time, the pressure switch has to go up after 25 seconds. And after lubrication time end, no pressure is expected.
 

I have also just tested this in the default qtdragon_hd_xyza sim setup and it does the same thing there.

Hi,

problem solved.

You can have your own qtdragon_{,hd_}handler.py in e.g. qtvcp/screens/qtdragon{,_hd} and have full control over the GUI.

Regards
Carsten

what does this give you:
$ python3 --version

I wonder if using Deb 13 is the problem.  Deb 12 doesn't like my nic's or wi-fi hardware.

Assuming it's a python issue, any suggestions on what to do about it?