Advanced Search

It's important to think of the interpreter read-ahead when you work with Gcode that depends on parameter values.

Try inserting a queuebuster before the M73 ..

Aciera thank you for explanation!
Then something is wrong there because this is beginning of tool_change.ngc (which is main subroutine for tool change procedure):

o<tool_change> sub

M73 (auto-restore modal settings on return)

(MSG, Tool change: loaded tool=#<_current_tool>)
(MSG, Tool change: selected tool=#<_selected_tool>)

(print, rack_change: loaded tool=#<_current_tool> current pocket: #<_current_pocket>)
(print, rack_change: selected tool=#<_selected_tool> selected pocket: #<_selected_pocket>)

; unload previous tool - if next tool is also in spindle 1, then have to actually unload it first, so second parameter for tool_put_move is 0;
o100 if [#<_current_tool> GT 0]
o101 if [#<_current_tool> LE 5]
o102 if [#<_selected_tool> LE 5]
o<tool_put_move> call [#<_current_tool>] [0]
o102 else
[code continues but it I am now testing with a scenario that "o102 if" statement is true and <tool_put_move> subroutine is called with first parameter as current tool number and second parameter as 0]

I get to the point where a next subroutine is called so I would expect ALL the lines before that to be executed but those (MSG) messages are not displayed.

How do I check of what exactly is wrong?

Regarding MSG/DEBUG vs PRINT:
Note that (PRINT, sometext) will be executed by the interpreter read-ahead while (MSG, sometext) and (DEBUG, sometext) messages are put in the queue and will execute during gcode execution.  

If you want your (PRINT, sometext) method to work correctly you should use an if statement to only execute it in task mode
and use a queuebuster command before to stop the read-ahead

So if your PRINT messages are displayed  but the MSG/DEBUG messages are not then the read-ahead has ingested the (PRINT, sometext) lines but Gcode execution did not reach the (MSG, sometext)/(DEBUG, sometext) lines in the program.

If you go with a sensor and use a analog input then we can rewrite the code to use a high and low pressure setting.

I just gave it a second thought.
a relay with a 220 volt coil on the compressor is a bit risky. 
If your business grows and you employ people an uninformed person could connect 220  volt on the wrong wire and then probably blow the mesa board.

i think I will go with the pressure sensor. 
So far all the analog inputs of the mesa board are free. Advantage I have full control of hysteresis of the compressor as well. Disadvantage I need to put an electric unloaded valve. I guess any normally open pneumatic valve will do.

I am getting this error when I try to install the main package

sudo apt-get install '/home/dylan/Downloads/linuxcnc_2.9.3_amd64.deb'
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'linuxcnc' instead of '/home/dylan/Downloads/linuxcnc_2.9.3_amd64.deb'
The following packages were automatically installed and are no longer required:
  libgpiod2 python3-serial python3-yapps
Use 'sudo apt autoremove' to remove them.
Suggested packages:
  onboard
The following NEW packages will be installed:
  linuxcnc
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/25.5 MB of archives.
After this operation, 89.9 MB of additional disk space will be used.
Get:1 /home/dylan/Downloads/linuxcnc_2.9.3_amd64.deb linuxcnc amd64 1:2.9.3 [25.5 MB]
(Reading database ... 185376 files and directories currently installed.)
Preparing to unpack .../linuxcnc_2.9.3_amd64.deb ...
Unpacking linuxcnc (1:2.9.3) ...
dpkg: error processing archive /home/dylan/Downloads/linuxcnc_2.9.3_amd64.deb (--unpack):
 trying to overwrite '/usr/share/applications/linuxcnc-documentation.desktop', which is also in package linuxcnc-doc-en 1:2.9.3
Errors were encountered while processing:
 /home/dylan/Downloads/linuxcnc_2.9.3_amd64.deb
N: Download is performed unsandboxed as root as file '/home/dylan/Downloads/linuxcnc_2.9.3_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
E: Sub-process /usr/bin/dpkg returned an error code (1)

The whole battle here is to stop LinuxCNC before compressor starts, so you do need another sensor set to trigger at a bit higher than the compressor low pressure, then you can use the existing switch to trigger when compressor stops.

Thank you so much 
You come faster than I could work out a concept. 
I do not fully understand the code.

does it stop at the end of a cycle?

Is there any code to start the compressor?

I was thinking of a simple way to use the original pressure switch on the compressor. 

I could add two Relais on the compressor. 
one with a 24V coil in series with the pressure switch.
one with a 220 V coil that closes when the pressure switch wants to start the compressor. 

So when the pressure drops the 220V relay is activated and sends a signal to Linuxcnc. 
linuxcnc pauses the program. And turns on the second relay. To start the compressor. 

Is full the The 220v relay gets turned off by the pressure switch. 

linuxcnc turns off relay2 and resumes cutting. 

The only question is will the Relay with the 220Volt coil turn off when the voltage drops during compressor startup?

 

Thanks for your answers, I'll try it tomorrow.

Yes it would work, just get a bunch of 1MOhm resistors 2W each, at least 6 to be on the safe side, should be very cheap.

The spindle and servo should be identical connections. but the toshiba version i remember are different than sanyo. There is another thread on a 211 here than might help.

As for vibrating, If you have no signal connected it is floating, and it could be seeing the noise as a motion command. So I think you need to connect a signal.

I don't know what r/s210 are, ET is enable I think. Sadly I only have the user manual for the 225/215, but not the electrical diagram.

Keep this one, it has pictures and less "techno babble".

I don't think I saw the pwmgen 04 enable being connected
in your hal file

Cant do this anymore bye all wrote:

tommylight wrote:

ytutgfhfgfghfg

 
Is that the i5 or Core Duo one ?

LOL

Cant do this anymore bye all wrote:

I tried the same thing a year or 2 ago.

Where is it?
I did search for that and another one with "duzie" in the tittle but could not find them, strange as i did find the "duzie" one a few days back!
I can try to gather all those into one topic, and yes i am aware this would be better in the wiki, but i do not need anymore logins, have to much as is.
-
Will delete this post and other "non related" later as we get a chance to read them.