Advanced Search

PCW wrote:

If you are not using reset mode (Not sure if the RPI can do this)
The step pulse width is the base period.

Drifting in a (mod) 45 degree angle suggests crosstalk to me.
Maybe a loose ground or 5V common in the step wiring?
 

That's it! Somehow the stranded wire connecting d- and p - to GND broke in the ferrule. After I replaced the wire, the drifting is gone!

Thanks! 

Hi Arciera,

use libgsl example. Remove all libdogleg related files and deps.

Hello everyone! I'm using the analog signal to determine a limit switch. Through a reading from a magnetic sensor that has an analog voltage output that is read by the 7i77 board, I developed a logic in the LinuxCNC classicladder. The logic is that when the voltage is greater than 7.5 volts then it activates the output %Q81 called MA-Z, when the voltage is less than 1.0 volts then it activates the output %Q80 called MI-Z and the home position is when the voltage is 6 volts it activates %Q82 called HO-Z.



I made a virtual connection in the HAL file

Includes the configuration to activate Home by switvch in the INI file

The machine makes the movements when pressing the + and - buttons of the home z, but when trying to do home axi with exio Z, a movement calculation error appears. As per the video below


 

Please, does anyone have any suggestions, I'm trying to find a way to make this Z axis movement stay in an initial position above the top, to avoid the movement collision of the tools. But I can't get the system and 7i77 board to interpret the virtual limit switch, could it be that I'm missing some configuration in the HAl or INI file so that the home axi Z works correctly?

 
 

Yes, 7I76E hal and ini files will work with a 7I76EU.

The added 7I76EU features (output modes and spindle mode)
would not be supported, but these are just controlled by parameters
that  can be setp'ed in the hal file.

The firmware files are however different

Moved to another PC, installed 'libdogleg-dev' and I seem to get a little further but not much:

 

Anyway, I'm afraid there is not much I can think of to help as I'm really starting a zero with these dogleg solvers.

Blender CAM 2025
Please give some inputs, is it worth the effort to learn?

Hi,

I have tried another solver: "libgsl".     ( sudo apt-get install libgsl-dev )   Using the GPU. ..

This runs way better then libdogleg. Was a luckie shot.

In this solver bigger distances are ok.
Input :


interpolated endpoint result : x: 520.049999 y: 266.500001 z: 125.500000
Converged after 370 iterations wtf? 

Now i get more convinced finally.

Appreciate the prompt action, I also got a reply from the Mesa folks that you can select and build configs with 7i76E as well.

-Aren

thanks for the reply.
It's a fresh installation of latest gmoccapy version.
I'm not a software guy, but followed the manual as much as possible.
Have no chance to dig into python stuff.
As mentioned, referencing the axis, MDI, already works. Even macros.
Its the M6 what does not work..

Yes. On the video I posted all the 4 drivers are daisy chained. My plan is to allow to declare chains when loading the module, so you can have 2 chains of 2 daisy chained drivers, for example, or 3 "chains" of 1 driver, or what ever you want as long as you stay below the max allowed drivers (6 for now, but easy to change in the code). That's true for RPi 4, where the CS pin is managed as a GPIO pin. For the RPi 5, the max number of chains will be the max number of CS pin of the selected SPI channel (2 for SPI0, 3 for SPI1).

O500 IF [#5220 EQ 1]
#1102 = [#5063 + #5223] ; G54
O500 ELSEIF [#5220 EQ 2]
#1102 = [#5063 + #5243] ; G55
O500 ELSEIF [#5220 EQ 3]
#1102 = [#5063 + #5263] ; G56
O500 ELSEIF [#5220 EQ 4]
#1102 = [#5063 + #5283] ; G57
O500 ELSEIF [#5220 EQ 5]
#1102 = [#5063 + #5303] ; G58
O500 ELSEIF [#5220 EQ 6]
#1102 = [#5063 + #5323] ; G59
O500 ELSEIF [#5220 EQ 7]
#1102 = [#5063 + #5343] ; G59.1
O500 ELSEIF [#5220 EQ 8]
#1102 = [#5063 + #5363] ; G59.2
O500 ELSEIF [#5220 EQ 9]
#1102 = [#5063 + #5383] ; G59.3
O500 ENDIF

you can do this
#1102 will have G53 Z coordinates

Hi Arciera,

Mr build? Huh.  Wich dep is that?

I am able to let the single clothoid finish at target position ~ 50% off the cases.
using example : single_clothoid_fit();

Dogleg fails to find solution very often. Tarpos in the range x20 is ok. x200 is failing all the time.

The good news is, it works partially.
The bad new is, is fails a lot.

Here it does the job ok:



So now what to do?
Maybe try another library?

interpolation endpoint result : endpoint x: 11.000000 y: 5.000000 z: 2.000000

Are you planning to add support for daisy chaining of drivers?

Like Tommylight suggested, try the RTAI kernel, here you can find the newest versions with instruction: forum.linuxcnc.org/9-installing-linuxcnc...ng-rtai-debs-for-2-9

excellent news! glad you are up and running!