Advanced Search

PCW wrote:

I get 3600PPR @3000 RPM = 50 RPS* 3600 = 180 KHz A/B signals and 720 KHz count rate (4X 180KHz)

at 5 mm/turn and 4X3600 counts per turn that's ~0.347 microns per count

I do not understand why 180kHz is multiplied by 4.

I've updated the kernel deb, you could try to install that one and post the result of "ls -l /boot" before you reboot. At least at the Orange Pi 5 plus it (already) worked fine to boot from nvme.

Just cloned your repo and tried to build linuxcnc. I get this error:

Tutorial 05


JT

Hi,

Do you have a link for me? Where to find you on github?
 

Hi Rob,

But probing is just a straight line feed that triggers a sensor event? How is this related to smoothing?

Attached a validation gcode file. You could test this in linuxcnc. It's result of a G64 P20 Q0.
To visualize this, the fillets are drawn as G1 linestrip.

This was hard work, because what you see is a filletized path using clothoids.
To use them in 3d space, i had to add logic to project 3d planes to xy planes and back to do the clothoid calculations.

At one point in the original gcode file it sees a transition from arc on xy plane to a line that goes z up.
This is a situation where segments points are not all in the same plane.
This situation is then reverted to use a bspline.

So far no tiny segments are filtered out.

For the source code, Clothoids-1 is added. This cmakelists file has to be reviewed as it is quite a mess now.

The clothoids lib integration was quite a lot off alien obstruction. But at least is works now !

repository

 

 

do you have HALUI = halui in your ini still?

With my experience of my last setup, it is safer way to opt for inbuild GPU with higher RAM and more importantly two identical RAM on both slot of motherboard.
It really improved latency.

Hi,

I managed to get VFDMod to run using the good ol' Wayback machine. A bit slow but everything available (even the installable download package mentioned above).
web.archive.org/web/20230123060705/https...ub.com/aekhv/vfdmod/

 My BD600 Spindle is running (when pushing the button) and I can also issue the GCode Command to change the spindle speed but I can not change the speed using any button. Nor Do I see the speed or Spindle Load. Did anyone get VFDMod Working in QTPYVCP?

I'm sorry for the confusion it seems to be regarding the dev version. If i change to stable everything works.

But this leads to antother dumb question.. If i change to stable by using the apt manager probe_basic_mill_designer will use the normal src and not the venv (It starts with the normal UI and not the one in dev/probe_basic/src). As soon as i uninstall probe basic and qtpyvcp via dpkg it works again.. But if i would build a .deb file out of my changes i guess that i will also have all the bugs which are not fixed so far from the dev version.. Is there a way to run the designer launcher on the stable version?

Mh if i delete qtpyvcp from my dev/ folder its working.. So i guess the installer uses the non stable version? 

Ok i just added a git tag of qtpyvcp to 4.0 in the installer to manually choose the versions of QtPyvcp and probe-basic for my venv the git tag in the installer and now everything is working. At least its not throwing an error, but the plotter seems to have an issue with drawing the preview where it should be when changing the WCS

I updated the docs to include the postgui hal edits, I also removed the link back to the old docs in the forum and directed readers to the docs config section to help avoid future confusion, thanks for the heads up on that.. missed it since it was in a section i wasn't updating!

link below to the updated docs page:

kcjengr.github.io/probe_basic/machine_config.html

Thanks for the help guys, But I wasn't being sarcastic in my thread title my brain is as smooth as glass. like a surface plate almost so forgive me. Included is my edited postgui.hal file that I have added the commented out parts for the probe and the spindle speed (hopefully I've done it correctly.

And the new error pop up I'm now getting.

comment out the net in the postgui hal I just realized i missed the post gui hal edits i the docs and will add. you may also want to comment out the spindle feedback line if you arent using it or it will be your next error pop up.

You can omit it by adding # in front of the line containing that pin, but that might limit functionality.

Yes! The problem is gone, even without the r8168.aspm=0 and r8168.eee_enable=0 settings. Before I also tried quiet isolcpus=2,3 on its own, and although the latency improved, it did not resolve the EtherCAT servo following errors.

From what I can conclude now is that updating the realtech drivers according to Rodw's document did the trick.

Some additional info. For my implementation, the EtherCAT reading and writing combined takes 14% of the 1 ms servo loop time.
To check that you can get the number of CPU ticks for each with:
halcmd show param lcec.read-all.tmax
halcmd show param lcec.write-all.tmax
Add those together and multiply by 1/CPU frequency, that gives you the total time for each servoloop iteration that EtherCAT requires.

Now I can finally write a detailed update/installation procedure for my customers and release my new EDM components.
Many thanks again! Great way to start the weekend