Advanced Search

Thanks you @tommylight - I was somewhat fearful that my response was offensive and it was by no means intended to be. @PCW pointed me to the HAL documentation (I didn't discover that part of the documentation myself because I was 'spindle' focused and not 'general hardware') which was still 'over my head' because (I think) it is written from an integrator's context/viewpoint.

EDIT:
Opened and browsed the 'Integrator Manual' you referenced. It's 342 pages in length... I think that competes with 'War and Peace' for 'longest book'. BUT! definitely where I should have been focused. That document will be on my desktop and as I have time - I will be reading it.

Thank you everyone for your hints and help - my 'voyage of discovery' has exited the rough waters of the storm (my system is yet again working) and I will be gracefully sailing smooth waters as I figure out how to implement 'auto-zero' for Z (not sure that's the correct term) and maybe even some custom G-code sequences for startup and shutdown.

Arden

Oh my god, thank you, it worked.
So I can get out of e-stop now, but my drivers are still not responding, but one thing at a time.

Yes, I tried from the terminal,  same.... empty tab.    I posted the results in the terminal window in my previous post.  (errorfile.txt)

Also, I noticed in step 3 of the instructions aux_gladevcp is referenced but there is no such file  YET the verify instructions reference gladevcp  (no aux_)   aux_gladevcp is again referenced in step 9.

One other observation... step 3,  NativeCAM filder is copied into /gladevcp but later the ini file references the path as ncam,   there does not seem to be a ncam folder.     (my very old linuxcnc with nativecam has a ncam folder)

It seems to me you (bothf you) have a problem showing up the interface.
Have you tried to run NativeCAM from the terminal?

Yes, it’s a RPI.
May I kindly ask how the “Max Velocity” slider affects the machine? I initially thought that all machine controls were determined solely by the .hal and .ini files. Additionally, I would like to understand why the value needs to be divided by 60 when setting the MAX_VELOCITY parameter in the .ini file.

I’m currently using GT20 20 tooth belts, and the drive is set to 8 microsteps. May I ask how to correctly calculate and set the SCALE value based on this configuration?

Should be fixed now.
Sorry.

post your config.txt

I am having the same issue as Becksvill , that is axis launches with a NativeCAM tab but that tab is empty when opened.I ran linuxcnc from terminal as suggested,   results of that terminal window  attached here.   I also attached the INI file for reference.

George              
                

Hmm yeah the TMC drivers arent configuring, but that shouldnt be related to the SPI comms. Just remove the drivers until you can get it to connect.

The serial output looks good, and there is SPI stuff happening hmmm

in your halfile, try replacing this line to this line

Becksvill wrote:

i have a tab now with nativecam but its blank

this time i got right through the guide you did right to the end without errors

cheers

Andrew
 

I installed both the 2.9.4 ISO and NativeCAM using the guide posted here.
I got no error BUT I also have the NativeCAM tab showing on the axis sim screen AND mine is also a empty blank tab.

Not sure how to proceed so will watch here for updates

George

Unfortunately Autotune programs do no adjust the feedforward or deadzone terms so fairly useless
in real world situations.

I suspect for the best performance of a position control (stepgen or Ethercat or whatever) with an added
linear feedback device, you would need two PID loops, the local high bandwidth position loop plus a lower bandwidth
PID loop using the linear encoder feedback. This could be done in hal with two PID components with their outputs
summed.

I'm having a problem, it wants me to log in to the drive.

 

 

Are you using the mill version? I don't think I ever set up large for probing yet because I had no tool setter. Tell me more about what you're doing. The parameters are for the mill UI.

Giovanni,

Can you confirm something for me? I am going to attempt installing today.

Your guide was posted here 09/feb/2025 but when I downloaded the files from the link in the guide the files are all dated 04/oct/2024. I was expecting updated files from reading this thread. I thought there were recent file updates????

Thanks much for all the work on this.

When I started halscope, the trigger level slider worked as expected. For some reason it has become non-functional. The slider is gray, no green, no way to adjust it. I've tried restarting halscope and changing trigger channel. It doesn't matter if I'm in Normal or Auto trigger.

Thanks,
Steve