Advanced Search

Stran_ge wrote:

How does a wrong scale invert the direction for m3/m4?

It does not, uless a - sign is in front of it.
So, add a - to scale
Or
Invert the direction pin in hal.

Are the drives rated for 200V AC?
It may be possible to run from a single phase, but it is not advisable and should never be run at max power due to risk of blowing the rectifier. Rarely happens, though.
You have a bigger hill to climb, your country has 240V AC grid with +-10% tolerance, meaning it can go to 264V, rectified inside the drive that will be over 300V DC (on the phone, what is 264X1.41? ) and can easily blow the capacitors.
In short, i would not risk it.
A big 240 to 200V tranformer would be safe, but still single phase.

he Grotius ... sorry for stupid question ... not read all post of these thread .... but is possible to install these project or only rip-install? can damage somethings if try on little scara your code? custom kins is the same as 2.10?

regards

Latency related issue, so did you dissble all the power saving features in the BIOS?
Also disable hyperthrrading, TPM, turbo, etc.

 Same here, been over 3 years since i went for a ride on any of the bikes!

really when not rayn ..... so almost from 2 month not for sure .... go at workshop with my electric bycycle  ......    ..... quite a byke!!! .... I see every morning my motorbike on the garage .... and I dreams a lon trip .....  

run from line was moved above to the mdi line, if you are upgrading from an older version you need to make sure the new sunroutine folder is used and also add the new probe basic variables to the .var file in your config. the updates are up in the new docs here:

kcjengr.github.io/probe_basic/machine_config.html

parameters required in the var are shown here:

kcjengr.github.io/probe_basic/probe_basic_parameters.html

Lcvette wrote:

@PCW who would be the person group best suited to fixing it, and do they know about it? is this a linuxcnc thing or a debian thing?
 

Honestly its a Linux thing (broken driver) but would be easier to fix in a non debian compliant ISO
Ultimately it should get fixed in the kernel driver so the proprietary Realtek driver is not needed.

Grotius wrote:

Hi Bkt,

Could be missing a header include path.
But can also have other reason's. Some times hard to say what the cause is.

 

really is because if use mdi command or other trajectory command using rip-install path for rs274 is  not a good idea if you have Lcnc istalled too.... tomorrow or day after i publish here the right cmakelist.txt with opcua too .... now all work and robot moove perfectly.

Thanks again.

2.531 is still way too large (even though its ~4x better)

Are all power saving option disabled in the BIOS? (Turbo modes,C state > C1 etc)

Other options are shown in the:

forum.linuxcnc.org/38-general-linuxcnc-q...nity?start=40#300434

thread

A simple thing to try is to run this script that sets the irq affinity

 

you first need to make the script executable with

chmod +x pinirq.txt

and then run it with:

sudo ./pinirq.txt  [ethernet_device_name]

Where [Ethernet_device_name] is something like eno1 or enp0s5
(the device name can be determined with the "ip a" command)

You can check that it worked with this script:

 

chmod +x checkmask.txt

and then run it with:

./checkmask.txt  [ethernet_device_name]

checkmask also shows the kernel command line

Go to your Synaptic Package Manager.
Search (in my case) R8168-dkms
select and install package.
Reboot

There are several devices and other drivers for them. Search DKMS in package and look for the proper device.

That was the issue! Thanks

However, I now have the button "reload PGM" and "clear PGM" instead of "run from line". Is there a way to add it back in?

Another point. I tried to use the touch off on my tool probe (which worked before) but I get three errors:
1: invalid params in linear command
2: Linear move on line 50 would exceed joint 0's positive limit
3: Linear move on line 50 would exceed X's positive limit

Hello PCW,

thank you for the fast answer.

I checked the parameter of the servo with the manufacturer and he told me that the motor resolution per revolution is 1024 which is then *4 4096.
4096/60 = 68.26667 = pulse per second.

How does a wrong scale invert the direction for m3/m4?

Ah great! I'll have a look.

Hi,

Thanks TiaUnderGround for testing the script.
Glad that is run's.

I hope Arciera's install will also run now.

In the cmake dir, i changed the tinyspline source code to be libtinyspline.
It now compiles to libtinyspline.so and is installed in ~/rtlib
motmod.so uses libtinyspline to create fillets. This is temponairy.

Next will create libfilletizer wich then can be used by the trajectory planner "tpmod.so".

Then the edited motion component "motmod.so" wich we used for displaying the filletizer algoritme can be
left in the project as is. This edited component can be used to verify filletizer outputs when source code
has changed.

We can load the original "motmod.so" once again and can now focus
on the trajectory planner "tpmod.so" code.

We have soon the ingredients complete.

Sounds like either the encoder scale or the step/dir scale (or both) are wrong.