Advanced Search

Great project, and nice workmanship! The control panel looks great in the photo!

Is the board with the orange heat sink an HDMI to LVDS board for the display?

Regarding the dots problem.
I changed the dot limit to 10 in qt_action.py
 "if os.path.basename(fname).count('.') > 10:"
Also in qtdragon_handler.py
" if os.path.basename(filename).count('.') > 10:" , and everything works normally. I haven't noticed any negative effects so far.
It is possible that such restrictions are no longer necessary.

(on Debian 12 it was enough to change only the handler file)
edition
(I tested something wrong, changing the qt_action.py file on Debian 12 is also necessary)

 

Hello,
I used MB2HAL to communicate with my VFD for a long time already. I use a USB to RS485 converter on my PC and a 2-wire cable to the VFD.

Now I added an arduino to to the same line. The arduino is used to switch cooling and a vacuum cleaner on and off with M7 and M8 commands.

Everything works well, as long as the configuration takes care of one of both. I have a test configuration, which only talks to the arduino wich works fine, and the VFD also works on its own. But as soon as I combine both in one configuration, the problems are starting. I have attached two screenshots. The first one is the initial state. No errors, no problems.
When I then let the Spindle rotate, the increase of the spindle speed and the feedback has a delay of a couple of seconds and in the Halshow window you can see that the arduino has en error - see second screenshot. As soon as I stop the spindle, the error is gone.
With the spindle running, the M7/M8/M9 command don't reach the arduino. So, when I call M7 with the spindle running, my vacuum cleaner starts working just after I stopped the spindle.

Does anyone know, where the mistake is hidden? In the attachment, you can find the relevant configuration files.

Thanks for your help
Dominik
 

I don't think the FIR s-curve generation will really work for this after messing with it for a while. I have found some papers on s-curve generation with other analytical methods instead of resorting to an iterative solver. It gives a time-optimal solution given the constraints: max velocity, max acceleration, max jerk, path length, starting velocity, and ending velocity. I think this might be much faster than anything else. So far it's looking very promising and its mostly working. There were some errors in the paper that I'm working through.

I think for path blending arcs have to be avoided because there is a curvature discontinuity where they meet a line or different radius arc. It's not possible to limit jerk at the transition unless you come to zero velocity at the transition point. I think the best way to blend a path is using clothoid curves because their radius changes linearly with the curve length which allows curvature continuity which results in smoothly changing acceleration in a transition. There are also algebraic solutions to calculating radial acceleration and jerk at a given velocity and point on the curve. The solutions to fitting the curve to the path geometry are closed-form. I've done a little work on this that I can share soon.

Thanks, Craig.  Over the weekend, I managed to get a half decent tune with the drive in velocity mode (analog input).  Velocity loop closed on the drive, tuned using the DMM software, and position loop closed on the LinuxCNC side using the drive's encoder output only for feedback (no table scales yet).

I finally feel like I am gaining understanding and confidence with the loop topologies and tuning process.  Taking my time with it and getting my brain wrapped around it has proven valuable so far.  Next up will be resuming experiments with adding the table scales back into the mix, and maybe later if I'm feeling bold I can try my hand at switching the drives to torque mode as you suggested a while back.

I'm also keeping an eye on ebay to try to find a mate to this single 750W DMM servo motor + drive that I have.  I can't really justify buying new for this conversion when the original DC servos are honestly probably fine for my intended use, but I would like to ditch them in the name of modernity (and electrical cabinet real estate) anyway.



 

I love it 

Isolation and that's quite an LPF for motor control 

My compliments.

Craig

OK so still mysterious. Might be a hardware issue on the 5I24/PCI slot
(the analog data is in the second RX transfer register, if there was
a PCI access issue, this might be a possible symptom)

Reverse motion might open up the door to replicating the "Traking" feature on Prototrak CNC lathes. It lets you use one of the MPG wheels to move forward or reverse through the program motions.

 

Gentlemen,
there must be a problem somewhere with my minimal basic configuration for the 2 Mesa cards 7i92H an 7i76.

Is it possible that not all combinations and the latest firmware for these two cards are available for selection when configuring with the wizard?
Is the configuration page with P1 and P2 correct? Please see the Pics.
Is the selection of contacts shown on P1 and P2 correct?
Why do I only see P1 and P2 and not also TB1/2 of the 7i76 card and so on?
How must a connection be written in the HAL so that I can see and check the contacts?
Isn't it intended that the PncConf Wizard writes this at the end of the configuration?

Is the HAL/INI file responsible for the connection and communication between the two Mesa Cards?
If so, what must be in the HAL file so that the two cards can see each other and I can monitor the signals with LinuxCNC?

If everything is not correct, what is the mistake I am making?

Thanks again for your support
Claude

 

Yes, but if you click e. g. other components and then comp
you geht a 404 error..

You will find its source code here github.com/LinuxCNC/linuxcnc/tree/master/src/hal/components
Best way to learn C is to read it!

Not sure if it will help but try changing  your if statement. Sometimes int and bool are not interchangeable.

FUNCTION(_)
{
if (sel_in) {
  out = in0;
}
else {
  out = in1;
}
}

Your link works for me. Maybe there was a transient fault.

The video of today.

- Jogging scurve.
- Run sample program.
- Pause, resume.
- Jog while pause.
- Motion reverse.
- Look ahead 20 lines.

Next week i will test it on the production machine.



lcnc scurve source code

I skipped one very important setup question:

What are the scalemax parameters for the 7I76 analog inputs?