Advanced Search

wenn du 2 MDI befehle hast, einer für 'an' und einer für 'aus',
dann kannst du zuerst ein 'toggle' machen und dann mit 'edge'
das jeweilige mdi triggern, je nachdem ob an oder aus.

im prinzip müsste es auch einfach mit der 'not' komponente funktionieren,
als mdi 'an' an das toggle und 'aus' über 'not'

Gruß,
Olli

Thanks for the sugestion. As I now dsided to go full Linuxcnc i will not use the system as is wary mutch. But i will seranly keep it running for now to find some stuff about it out.

Today, I’ve got my setup running with 3× Delta ASDA-B3 servos, a BK1100, and several EL1xxx DI / EL2xxx DO terminals.
I’m using the already implemented DeASDA driver (not CiA402), and the servos run fine.

My homing procedure uses HOME_USE_INDEX = TRUE. Everything works as expected: once the servo hits the index pulse, the homing routine completes and the position resets to zero.

I should mention that I’m fairly new to LinuxCNC, and this is also my first time working with EtherCAT, so I might be missing something obvious in the configuration.

There’s only one thing I still struggle with:
I’m getting a relatively large following error when I jog the servos using the keypad on the drive. Because of that, I had to increase the following-error boundaries significantly. (See INI-File)

At the moment, I don’t have any mechanics attached — the servos are running completely without load. I also auto-tuned the drives, so in theory the gains should be appropriate. What I don’t understand is whether this behaviour is caused by the EtherCAT cycle time (2 kHz) or by suboptimal tuning parameters (gains, filters, etc.) inside the servo drive despite the auto-tuning.

Does the following-error configuration need to be set differently when using EtherCAT communication compared to pulse/analog control?

I’m also not sure which exact HAL pins I need to connect to the Probe_Basic UI to make everything safe and fully functional. Any guidance on the required pins, signals, and safety interlocks would be extremely helpful for someone who’s still new to LinuxCNC.
I’d also love to see some example HAL/INI configurations of fully set up 3-axis machines, ideally with a carousel-type tool changer and a 3D probe — that’s what I want to configure next 

Thankfully I have a nice bench power supply from my bench flashing for ECUs / binary reversing, so stable power from 5-24v DC isn't an issue

Mark,

My spindle drive enable pin is tied to a 'machine-is-on' signal, and not to the M3/M4/M5 0-10v signal.  The drive isn't disabled at M5.

Check your HAL file (and watch the VFD enable pin in halshow) to see if you've got something connected funny.

I will go read some more about G52, thanks!

No its Mach 3. The seller of the Mashin did not include the hard drive so i had to install windows and Win11 was just wat i downloaded.

I wanted to be sure ... HAL_BIT will always return 'TRUE' or 'FALSE':

getp evokes the function do_getp_cmd, and inside it calls data_value2 to format the response:

github.com/LinuxCNC/linuxcnc/blob/73337a...cmd_commands.cc#L883

here is where HAL_BIT goes to 'TRUE' or 'FALSE':

github.com/LinuxCNC/linuxcnc/blob/73337a...md_commands.cc#L2473

So checking for '0' is probably unnecessary, but it doesn't hurt either.  

Really don't see what could be different between configurations that affect basic communications.

unless there is some marginal power issue (does the 7I96S reset when starting the 5 axis configuration?)
Or maybe a memory fault of some kind in the PC, the reported error really has nothing to do with the number
of axis.

And as I said, your 5 axis hal/ini files work fine here with a 7I96S

A pncconf created configuration might be worth a try, just to see if a quite different
5 axis configuration changes the symptoms.

 

Thank you for the help, I had narrowed it down to the rewrite_material_file method before I left for Thanksgiving dinner.  You definitely saved me time getting the rest of the way there.  From what I can tell without doing a bunch of digging, getp will return 'TRUE' or 'FALSE' when the halpin is setup as a 'bit'.  

I pushed your fix for this to the master branch:  github.com/LinuxCNC/linuxcnc/commit/7333...d08fd2855851c8ee91b3

I also found a copy/paste bug and fixed that as well.

Thank you again!

I’ll post my wiring diagrams once I’ve got them more organized, I’m working out of a google sheet that’s set up for tracking the status and purpose of each wire. 

Try in MDI
S0
Before
M5

Okay, I think I understand why it is doing what it does. 

The brake is working, but only during a speed change. So with C13 = 0.5S, and C023 at 110% current, the spindle speed change from 70 Hz to 20 Hz is braked (nicely). So that solves my decel between CSS facing cuts.

But switching spindle off, makes the spindle coast down. Since I am commanding the VFD with analog 0-10V, I thought spindle off just meant 0V commanded, but now I think about it, I sort off remember being surprised that is not the way LinuxCNC works. I suspect the spindle stop actually  deactivates the spindle drive enable signal which I have connected to VFD Pin 28,  and therefore the VFD is disabled every stop.

Since I controlling the VFD with a 0-10V analog signal, what can I do to have  LinuxCNC set that analog signal to 0V when I command a spindle stop?

I thought I was only only using Pin 28 it for machine start up and shut down, and E-Stop. It looks like I need to put a delay onto that disable to give the VFD time to be braked down to stop with the analog speed command, before the VFD is disabled.

RotarySMP wrote:

Those are the thermal overheat switch, which with that wiring will cut power to the main VFD in the case that the brake module overheats. To test it, that connection is not necessary.
 

Makes sense now that I look at the diagram more closely.

Are the LED's on the brake module illuminated?  Green for ready, yellow for braking active?  Just trying to work out if your #2 (dead component) theory is true.

OFF topic/rant

RotarySMP wrote:

3/ I only have 16A feed at 400V.

Just to make Americans green with envy (i was granted American citizenship but i never went there ):
I have that in every room in the house, that is 3 phase, each capable of 400V at 16A!
And in the shops there are everywhere 3X400V/32A sockets, so yes we can charge electric cars very fast at home, but we do not have many of those cars. I would like one that can do about 50-100KM on a single charge as that is sufficient for my daily use, but i would need another car for longer distances, so i am sticking to my diesel for now...until i build one with some drone batteries and some servo motors i have around the shop!