Advanced Search

thanks I'll have another look at it as I use blender for all my 3d print and cnc drawings and use cam bam or F-Engrave. Maybe start a new blog.

I have been slowly getting to a point where the Mill is working on Probe Basic. Learnt a lot about the configuration and now wanting to make sure on the latest version and taking account of the latest bug fixes etc on Probe Basic.

I am not a programmer and so need to flow a script of sorts. What is the best way to go about a Probe Basic Upgrade and take advantage of any internal changes whilst maintaining the working configurations.
 

Hi all,

So my config has a tool touch-off and a separate probe.

I have figured out that they both use the Probe-input to work, however, they are both in and both NO. Now I have tried to configure to have them both by setting Probe Input, to both but the load tells me that basically I cannot have two inputs for the probe input. So now I have validated that if I comment out each of the tools separately when connected, they work very well, but looking to have it so that the tools work if both and/or if probe is attached or not. I have attached the ini and Hal files here and input would be appreciated. I noted another thread talking about this and it mentioned using MUX. I tried the adjustments, but to no luck. Can anyone give me the solution to running dual probe-inputs in the ini and io.hal files would be great.

Hi all,

So my config has a tool touch-off and a separate probe.

I have figured out that they both use the Probe-input to work, however, they are both in and both NO. Now I have tried to configure to have them both by setting Probe Input, to both but the load tells me that basically I cannot have two inputs for the probe input. So now I have validated that if I comment out each of the tools separately when connected, they work very well, but looking to have it so that the tools work if both and/or if probe is attached or not. I have attached the ini and Hal files here and input would be appreciated. I noted another thread talking about this and it mentioned using MUX. I tried the adjustments, but to no luck. Can anyone give me the solution to running dual probe-inputs in the ini and io.hal files would be great.




 

As a close out to the topic...(unless I find other issues).

PM728VT, X Y and Z axis.

X is now positive i.e 0 to 480, homing on left corner of table, and cutter moving to the right, table moving to left. Total distance 480mm.
Y is negative. 0 to negative. Homing on front of table. This sets home in the negative. With table cutting moving towards back (i.e. table moving to front)
Z is Negative 0 to negative number. Homing at top of Mill. Distance 317mm.

Working as expected. So basically unless homing at back for Y and bottom for Z, these numbers will reference negative unless there is another way to "set" zero as home at the other end of the soft limits.

Thanks for everyones input.

unfortunately there is no mesa dealer or suppliers in india right now you have to import directly from US or any other dealer out of india. And if you dont have IEC code(Imoprt/Export) licences you may face long delay in custom clearance or almost 42% of custom duty (will taken as personal import) . I had bought from mesa's official webstore from using our compnay licence. although you could find someone who could import it for you but dont try if you dont have any experience find someone professional. or contact this guys www.electropneumatics.com/cnc-controllers-for-metal-cutting.php they use linuxcnc in theire so called self developed (LCNC Clone and 99% sure mesa hardware clone) controller. they might provide hardware.

Ok, I used hal show, and I can see that the pin changes just before hal show closes.
So I think that my componit is destroyed before it can fire the message it is designed to do.
not sure how to fix that

so i have an issue where the shutdown hal is not doing what i need.  
i suspect that when i shut down the loadusr python file may be removed befor the comand run?  
but in my testin my shutdown file runs at start up too.  

from my main hal file. 
from my shutdown hal file 
i know the setp commands work when i run them form the HAL comand  in the Gui.  

butt i all so get the data form the shutdown hal at startup. so