Advanced Search

Sorry, meant C007. QSB is not selected by default. Default is DC braking. Page 7-78.

Thanks for taking a look. And yeah, that manual sucks

I have no C107. It jumps from C106 to C108.

C105, I have tried different values, like 5Sec or 1.5Sec. It makes no difference. The drive is not ramping down, it got straight to 0A, and OFF as soon as it is commanded off.

I guess you're installing on Trixie.

Install
sudo apt install python3-zombie-imp

Then if you try to run you'll get another error which is related to libqt5quickwidgets5
sudo apt install libqt5quickwidgets5

Are your input terminals configured for QSP? C107
Also check C105 which is QSP decel time.

That manual is awful.

BR

I just created this from a known good download. Just remove the .txt bit of the download to check.
 

Make sure to download from here:
www.linuxcnc.org/iso/
As this is the official site and the safest option.

If you have more time than money I have complete build-yourself-a-drive plans and software, 4 drives on a pcb.

is there a link for that?


Disregard, I think I just found it:
github.com/MetalMusings/MyOwnEtherCATDevice

I (finally) installed a Lenze EMB9351-E brake module in my Schaublin, after a couple of years of annoying 15 sec waits for the spindle to coast down to a stop. 

Back when I did the original installation, I was getting over-current warnings when I tried to ramp down in less time.

I somehow set the Lenze 8214 VFD to not control the motor down, but rather to just let it coast down.  

So per the manual, I have the following control commands: Pin 7 / Pin 8 (Analog in) connected to a Mesa analog output, and jumpered for 0-10V. This is the main control. The VFD doesn't get on/ off commands, it gets speed commands. Pin 9 (Power for a control poti) Unused. Pin 62 (Analog out) Unused Pin 20 (power out for digital inputs) Unused. Pin 28. (Activate VFD) Controlled by Mesa digital output.Pin E4 (Change direction) Controlled by a Mesa digital output.
Pin E3 DC (DC braking) unused.
Pin E2 (Jog at frequency 2) Unused.Pin E1 (Jog at frequency 1) Unused.
Pin 39 (Gnd) Connected. Output Relay
K11 (NO Out) Connected to Mesa inK12 (Common) Connected to Mesa in.

assets.euautomation.com/uploads/parts/pdf/338201e.pdf
I have spent two evening going through both EN and DE user guides, reading out every single parameter, and adjusting everything which looks like it is involved with ramps, and I can't work out how to remove the coasting, and restore the C13 deceleration.

I even used parameter C02 --> 1 to restore all the default factory parameters, and went back in and set the motor current, slip and CosPhi. It is still ignoring the C13 decelerate ramp value and just free wheeling to a stop. The C12 acceleration is functional.

This is embarasing,, but I can't for the life of me remember what I did to set this VFD into coast down mode. Does anyone have experience with Lenze VFD's who can give me a tip please?
Cheers,
Mark

Hello,
is there still sombody available who knows whether there was a solution for this topic?
I own an ISEL CMP3020 with IMC4 Interface and have similar questions.
I don't own the old DOS software from ISEL so I don't can say whether the machine is running well.
Neverthless I have a free trial for the "KAY" software available and this software is at least able to do some movements. 
Nevertheless its not working 100% (has some issues with finding origin...) so I want to use linuxcnc if possible.

I alread wrote a short c# application (thanks to chatGPT) and can also control the machine via this application (some basis only).
So I can see that the motors are moving as they should do and also the end switches are working well, including movement to origin!)

I'm also very interested to get some PC software which can communicate to the IMC4 or a code converter software which can provide the IMC4 code. 
I understood that the DNC Code is needed to steer the IMC4 directly via serial port
I understood that I have to download a CNC Code to the IMC4's flash to enable the IMC4 controller to do the work without attached PC.
Nevertheless also the CNC-Code (CNC-Mode) is not compatible with G-Code, means a DNC- or CNC-Mode converter is needed anyway to steer the machine

 

Lichuan CL57E-4A en.xlichuan.com/product-xq/202.html is a ethercat stepper motor driver for four motors.
Have only seen them sold in kit with four motors though.
If you have more time than money I have complete build-yourself-a-drive plans and software, 4 drives on a pcb.

# Abilitazione PWM: attivo quando lo spindle è "on" (M3/M4)
net spindle-enable motion.spindle-on => hm2_[MESA](BOARD).0.pwmgen.00.enable

# Comando velocità in RPM dal planner
net spindle-speed-cmd-rpm motion.spindle-speed-out => hm2_[MESA](BOARD).0.pwmgen.00.value

I would in addition, check the above signals and pins to try and trace backwards
to find out  why  you don't have PWM enable and value set properly.

How can I perform this kind of verification?
I was able to add the two variables you mentioned into HALShow, but when I start the spindle or run M3 S12000, nothing changes in those values. What am I missing?

No worries, and you are welcomed, always.

happy to help! for what you are trying to do it shouldn't be too difficult. really you just need to map out the motion you will want the tool to make in relation to your tool setter, and build out that code in gcode so you know what it looks like and add in the probing motion where G1 would normally go, then review the rest of the probing routines to see what to do with the probed points captured during motion and write up a small equation to calculate the tools diameter and send it to the tool table diameter column. this is all information available in the docs in the gcodes section.

Hi,

  Is someone actively developing MTConnect support? If someone is working on this, maybe I could join the effort?  My goal would be to establish MTConnect similar to Haas, and perhaps also the MDC support for Q commands. 

P.S. Some of you might remember my previous project: installing LinuxCNC on a Cincinnati 10HC2500 HMC.

Tero

Apologies for Clumsy writing on my part,
I understand the issue and thanks for the clarification Tommy.