Advanced Search

Bunch of questions, Hopefully someone can fill in a few blanks as I formulate a plan for the lathe.

I'm using Axis for my mill and I'm completely happy with it. I'm now considering using LinuxCNC for my lathe. I definitely want to maintain manual operation capability.

Presently I have a derivative of the Clough42 ELS with feedback from the spindle and a stepper driving the leadscrew for threading. I like the simplicity of selecting various thread pitches metric and SAE electronically.
1) I don't suppose LinuxCNC has this "ELS" capability?

2) I also have DRO scales. Assuming I will use a MESA board, is it possible to connect the scales to the MESA board and use LinuxCNC as a glorified DRO without actually driving any steppers/servos?

3) Assuming for the moment I can use LinuxCNC simply as a DRO, what MESA board(s) would be a good fit for say max 3 encoder inputs and possibly up to 3 steppers later?

 I have a RaspberryPi of some sort and I might try using it for the LinuxCNC for both space and $.

4) What RaspberryPI's are likely to have acceptable latency and what versions should I avoid?

 I find the Axis GUI a good fit for my needs on the mill, what GUI is a good fit for lathe control?

Much appreciated.
 

Did I missed anything? New Dev? New tricks!? Is RIO finally able to read minds and make a part start to finish on its own yet? Or I still need to CAD, CAM, Gcode fix this, gcode fix that, gear in tooling, fixture stuff, dial feedrate, make coffee, dial more, make more coffee?

Link up, Oliver. If you think I've missed anything important since 90 days shoot me in the correct direction please, I'll have spare time during the weekend to spy on The Best Cult around!

You might try explicitly setting the high address in the hm2_7i43 command line (and the debug option)

did you try the --readhmid mesaflash option?

What kind of parallel port card do you have (what chip manufacturer?)

what does lspci report for the parallel port addresses? (trying to verify the high address)

Yo what's up Cult RIO & Awesome Fabricators! I hope Chief Technology Officer Oliver and his Lcnc crew are all doing fine?

Pardon my disappearance from my last updates, had to swing cross border to deal with pressing family issues (nothing health or negative related, only good stuff). The better news is when I came back I immediately rushed to the garage to see my gears and V O I L A , the RIO kit was shinning a led haha.

Everything werks spins moves scream slice chew cut chips its amazing to be back, it's just all full of f n dust everywhere though HELP lol

Thought to stop by and say Hello! Peace All ✌

Tutorial 20



JT

Thank you! That did the trick. I did that when I was trying to mash two files together, but when I realized that I could use the wizard i forgot about it plus the wizard lets you select the drive which gives you 500 for that value which maybe keeps you from running away or burning something up but doesn't do much for making the motors turn. I dug the other specs out of my old files for the drive and put them in the wizard and the steppers sound happy again. Now I just have to get the spindle drive to respond and I'll be back where I started :O) Thanks again for your quick replies and patience with me.

Hello!!
I have implemented mesa 7c81 on spartan 6. Raspberry pi is connected with my board (spartan 6) and we implement linuxcnc on that board, everything works good here but while we run some big files after some time it shows error Unrecognized error -1 and my python scripts stop suddenly, even estop didn't work, file will run but my scripts, estop functionality stop working. Please Suggest any solution.

Unfortunately I'm bad programmer))) But if you you will be successful (as it seems it is) in multi threaded running of g-code interpreters.
It would be good and easily to implement for user to add such possibility as "assign each axis to it's own g-code interpreter and path-interpolation with help of HAL.ini".
For example: assign axes X1,Y1,Z1, A1,B1 to thread 1.
assign axes X2, Y2, Z2 to thread 2.

This is ma hal line

Ok. The 7i43 looks like it is working.

But I have no luck with the PCI card. Right now I think I have to go with a PCI, because there is a PCI-e graphic card which seems have to be installed for booting.

Mesaflash sometimes works. Sometimes the pc freezes. Everthing ist grounded with separate cables.

Addr ist 0xD010. Whe mesaflash is working it shows 0xD010:0xD410. So high addr should be 0xD410 as I understand.

Linuxcnc shows error while startup and mesaflash with --print-pd shows an error regarding access to the flash.

Any ideas?

One difference stands out immediately.
My file uses syntax
" except Exception, e"
New version uses
"except Exception as e"

I'm beginning to think that I would be better to start with a new configuration. As you point out, probe screen has an updated version. That would just leave the spindle speed buttons to fix......

As a PS: I am currently running LinuxCNC 2.10 on Debian 13 (both pre-release versions). Although XFCE is the de facto standard Desktop Environment for LinuxCNC, in my experience KDE nowadays performs slightly better with lower latencies. Gnome, Cinnamon and others are usually worse.
As for latencies: please do not be too obsessed with low latency numbers. Only when you are using old style software based step generation or encoder counting, latency (base thread max jitter) can be a critical factor. When using MESA cards and similar solutions, only the servo thread max jitter is relevant and keeping that below 100us is usually good practice. I always keep it below 50us and never encounter any problems. Even without  full BIOS optimization it should be possible to have a very acceptable performance already on this N100 mini-PC. 

I found some code in tool_actor.py
 
I changed 
transform.RotateWXYZ(90, 1, 0, 0) to transform.RotateWXYZ(-90, 1, 0, 0)
The tool module's origin will change to bottom
 
and tool will rotate in right point
 
but, if G43, the path will draw wrong

I have poor Engilsh, and just have a little coding, forgive me

Tim
 

Maybe a look at the current version of 'stdglue' helps:
github.com/LinuxCNC/linuxcnc/blob/master...n-stdglue/stdglue.py

Hi Tom, please let me know how I can send help! More coffee and pizza, or perhaps some nice beers?   I actually have quite some time available, so if you are working on specific things for which you need help, just let me know.
As for Debian, yes of course it is a big plus to have an easy install method, especially after doing system upgrades. But that was not always the case. I remember the days that upgrading under Debian could also be quite a lot of work. After LinuxCNC was added to the  mainstream Debian repositories things became much easier. And I hope that once CL has added LinuxCNC to their collection of software bundles, the same easy install and update method will apply to CL as well.
To answer you question about compiling LinuxCNC on CL: yes, I tried that, but many of the dependencies were not available on CL yet, or perhaps they were available but in places that I was not aware of. So instead of wasting more time, I followed the advice from the CL team and submitted a request to have a bundle created by them, which is comparable to having Debian adding LinuxCNC to their mainstream repositories. It should result in a single command to install and update LinuxCNC without having to build things from cratch, similar to having LinuxCNC in the Debian repositories.
But again, for me it is not about creating an alternative to Debian. It is about finding out if LinuxCNC under CL can benefit from their processor optimizations and if so (which still remains to be seen), how we may benefit from that on Debian and other distros as well.