Advanced Search

Tried standalone NativeCAM again after installing python3-lxml.     Terminal screen info attached in file 

Noticed inifile =N/A in terminal.    I think this is because I launched linuxcnc in terminal without specifying in some way thataxis sim is to be used.

Also tried launching Linuxcnc the normal way with axis sim selected.     There is a NativeCAM tab but still remains a empty tab

ok good,
the octopus you need to have power on the 2 spots in the power rail, the motor power and the main power

the jumpers so the 2209, i think there should just be the 1 jumper

not positve about python3-lxml, I know I verified python3 was there from the fresh 2.9.4 install. I am going back into my shop right now to recheck this. Answer soon

Yes, I ran NativeCAM standalone from terminal, that was the "errorfile" I posted.
I have also ran it entering LCNC the normal way.

I meant run NativeCAM standalone from terminal.

Yes, in step 9 there is an error. Excuse me.
No "aux_gladevcp", but "/usr/share/linuxcnc/gladevcp/", it has to be the same path referenced in step 3.

Watchng the error file you posted, it seems LinuxCNC can't load lxml module as a python module. Have you installed python3-lxml in your system?

Regards
Giovanni

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