Advanced Search

Ok so you are using the probe as a master tool. I would advise against that, if you crash the probe you mist remeasure all tools after resetting the probe stylus with your method. Follow the method in the docs for best results so all tools measure from the spindle nose gage line. Then only the tool crashed or replaced requires remeasuring.

kcjengr.github.io/probe_basic/probing.html#probing-setup

I had to change the M600 to M5 and it loaded without complaint, so there is something i think requiring a fix for M600, you could assign a different M### between 100-199 and it would not complain, unless you've added M600 yo linuxcnc and it sees it and doesnt complain

Hi all,

i want to setup a virtual machine to test some functions.. My real machine is running with linuxcnc 2.8 and debian 10. 

How do i install older releases of QtPyVCP, probeBasic and PyQt5Designer ? It seems all the newer versions are not running anymore because of python3 and all the docs i find is only for the newest versions.. I mean i can download older repositories but for QtPyVCP there is no installer where do i need to unpack it? 

I don't want to change my machine to a newer OS yet.. 

I don't think EoE can work in LinuxCNC the way it is now unless possibly you are running linuxcnc-ethercat as a kernel module which I guess would require RTAI version. In the userspace version there is no call to ecrt_master_send_ext() which is required for EoE to work and it's only enabled if __KERNEL__ is defined. I opened a ticket on linuxcnc-ethercat so when Scott has a chance to look at it maybe there will be something.

Could you post your INI file?

There are a couple of ways that the home switch touch off can be configured. It can either be configured to only touch the joint once then slowly back off the switch to set the point where the switch changes or it can search for the joint touches it, backs off then touches again (usually more slowly) to set the home position. Which way is chosen depends on how the "HOME_SEARCH_VEL" and "HOME_LATCH_VEL" are configured (if they have the same or oposite sign value.)

If you have them configured with the same sign value (either both positive or both negative.) then it is configured for the double touch. If you have the home switch connected with the wrong polarity input and the double touch, the axis will still home but will only touch the switch once, and if combined with a limit will give the results you are seeing.

Lcvette wrote:

if you ae new to cnc, there are many pieces to the puzzle of offsets.

maybe lets start by finding out what type of spindle you have, repeatable or non repeatable holder type.

ER16/20 type spindles found on routers are an example of non repeatable holder spindles, while R8 with TTS, ISO20/30, BT30/40, CAT40 are known as repeatable holders.

both are ok to use but have different methods for setting tool/work offsets.

repeatable holders measure the tool length against the spindles gage line (or a repeatable point of the spindle nose that will never change. this allow use to set the tool length offset as the distance below the spindle gage line for all tools and store each tool's cutting tip to gage line distance in the tool table as the tool length offset. in theis scenario the touch probe also has a tool length offset which is the triggered point of the probe to spindle gage line. when you have these set correctly and probe the work piece with the touch probe loaded and its length offset active, it records the z touch point less the probe tool length offset to set the active work offset G54-59 as being zeroe'd to the spindle gage line. all subsequent tool calls will then use the tool tables stored length offsets to adjust the spindle's height so that the currently active tool and its length offset will put the tool's tip at the same work offset zero height when at Z0.0000. from there the cam program will move each tool's tip relative to the work offset zero point.

if yhou have any of those numbers incorrect you will experience deviation from that expectation. remember, the machine can only operate with the information you give it and if that information is incorrect the result will be incorrect.

the second type of spindle is the non repeatable spindle which means that the length of the a tool you use will not be mounted reliably with the same length offset for each instance of loading the tool in the collet. for this instance most people will reset the work offset z height after each tool load in the spindle. this ensures that the program will move the tool as expected with the tool's tip being reference against the work offset zero plane.

that said why don't you explain how your machine falls into those categories and your work flow for setting up to cut the part.

1- which spindle type

2- how are you setting the tool offset / probe length offset / work offset

3- what are you entering into the tool table

First of all, I want to thank you for your interest in helping me.

My milling machine is PM25MV but with a different name. The spindle is MT3, I also had the option of R8 but at the time of buying it I didn't know which one was better. I have the option of buying the R8 spindle at some point and changing it. (I think I will do it in the future).

I use ER20 tool holders with an MT3-20mm collet, I have modified them so that they maintain the height. I have checked it and it has a repeatability of 0.035mm +-.

I configure the tool displacement by touching the spindle without tools and marking Z0, then I put the tool (3D probe) touch the same point (I use a thin paper to feel) and I enter that distance in the table with the corresponding tool, and so on with the others.

I enter the diameter of the 3D probe in the table, but for the other tools I enter the diameter in Fusion 360.

Sorry for my English, I'm from Spain and I use the translator, so when I translate the translation is so bad that I don't understand many things.

Hi all.

I am almost ready with a project to communicate from and to linuxcnc trough websockets
to exchange realtime io.

In other words, interact with a running linuxcnc machine from a remote webbrowser.
Linuxcnc can be controlled remote by any device like a android phone, i-phone, tablet etc, you name it as
long it has a webbrowser on it.

You can connect multiple phones at the same time to one linuxcnc machine, no problem. So your employees can
even monitor the linuxcnc machines during lunch time over multiple machines.

You can connect to multiple running linuxcnc machines on the local network from one phone, or multiple phones.

It's already working, very responsive, but i want to expand the controls for the web browser gui.

The setup:
There is a fresh linuxcnc repository hosted on codeberg, i added 2 cmake directories in the top dir.
1. nml_websocket_server
2. nml_websocket_client

In a later post i will add a readme how to install and run the project on your phone or tablet.

Running on my pc:

Running 2 androids:


How its done in a nutshell:
1. The nml_websocket_server connects to the linuxcnc nml server as a new client.
The nml_websocket_server has mapped 95% off the entire nml status & command channels.
When a new nml_websocket_client connects, the server sends the status, and recieves the commands from the client,
where the client can be a smart-phone.
For info the websocket_server starts a python server once linuxcnc has started to provide the client with the .html, .js, wasm files. So the client has no files on it.

2. The nml_websocket_client has no files on the device (phone). To retrieve the files we must connect to the python server of the linuxcnc machine.
On the device open a web browser and type in the ip & port of the linuxcnc machine. This is a fixed ip adres of the cnc machine.
Then the phone can select the index.html file, and the app will start running webassembly. (wasm)
When the app run's it only using the websockets for realtime data traffic. The python server is then obsolete

This editor is no ones friend. I'll second the toggling the "source" button in the Editor menu. It is the only way to achieve anything functional with it.

Yes it has homing switches please see attached photo.
I will try what you suggested and let you know.

Hi,

yesterday I realised that it is possible to switch to teleop mode just by trying to start a nc program (also a button via pyvcp panel with an MDI cmd works like this) while the machine is not homed. I made a video and uploaded it to YT:



In the viedo I am using an VM with a install via the standard iso (2.9.1) an upgraded it to 2.9.3. Yesterday I had this behavior on a real machine with 2.9.2. Also 2.9.1 is the same. So in my opinion this sholud not be possible because the machine is not homed in this situation and switched to teleop mode after trying to start a program and joging afterwards. Is this behavior wanted?

Best regards
Julian

From your ini file and from the inability to move more than f-error value, it does not look like the tuning is done.
Also,

The only time I can't get the axles to come to a standstill is when I'm stationary.

does not come across correctly.
The Aciera (machine, not the respected member of this forum with the same name ) 0.01-0.005mm dither is OK, that is the servos/PID maintaining position, can be even less but that depends on encoder resolution and how tight the tuning and dead band is.

Thanks Lcvette,

yes the M600 error is a followup from my toolchange remap. I´ve deleted all Comments from Fusion360 in the file, and test ist tomorrow. Maybe there is a problem. 

Thanks for your help and patience 

Check that the, say, switch for X axis is actually wired to X axis/joint 0 in hal and physically, easily done by starting LinuxCNC and watching the DRO on screen, when triggered a sign shows in front of the axis value.
If they are not correct, you can change them in hal, it is easier that rewiring.

robocidalmaniac wrote:

The 4th axis (3: -1305.7399)     keeps going negative when I try to Home the Scorbot-ER-3 see attached photo.

If it is supposed to move the other way when homing, add a - in front of the HOME_SEARCH_VELOCITY in the ini file for that joint.
Might also need to add it to HOME_LATCH_VELOCITY, or it might not.
Wait, does it have homing switches?

Water tray, otherwise your shop will be completely black in a week.
Is that in inches?
Get a 2-3mm thick plate, some 10cm wide strips on the sides, some 50x50mm L shaped profile with cuts on one side every 5cm, then add 5-8cm wide slats from 1.5-2mm wide plates.
See here for ideas
forum.linuxcnc.org/show-your-stuff/38547...-5m-cnc-plasma-build