Call external subroutine not working in recent versions of LCNC

More
7 years 8 months ago #126206 by shipmodeller
Pretty sure I supplied those files before .. and remember.. what you "simulated" did not seem to address the issue.. but I thank you for your effort. I have put up my ini file, and the hal files for you to look at. I don't know what is going on, I suspect rights issues... I can load those files via midi all day long, UNTIL I load up another file, then I lose it. So, the main question I will pose again, should I push this as a defect, and if so, what documentation should I upload? Very big thanks...

Right now, I am getting around all this by loading the toolchange program manually for each tool I need. PIB.. :-)

File Attachment:

File Name: custom.hal
File Size:1 KB

File Attachment:

File Name: custom_postgui.hal
File Size:2 KB

File Attachment:

File Name: my-mill_20...2-11.hal
File Size:6 KB

File Attachment:

File Name: my-mill_20...2-11.ini
File Size:3 KB

Please Log in or Create an account to join the conversation.

More
7 years 8 months ago #126218 by andypugh
Does the "metal touchoff" work properly?
One difference I do see is that there is a classicladder interlock on the toolchange3 button, that seems to be checking mode.is-mdi

What happens if you switch to the MDI tab, _don't_ run an MDI command and then press the button?

Please Log in or Create an account to join the conversation.

More
7 years 8 months ago #126219 by shipmodeller
Well, the metal touchoff .. was working in the prior release.. yes. ( 0 added for offset.. ) So when I did wood, the .625 was added. When I did metal, nothing was added to touch zero.

So.. the number 1 issue as reflected in my original post is:

1: From boot, I can go tot he Midi panel and execute the o<xxx> call tool change without problem.
2: The button doesn't seem to work till i do that .
3: But, once I load a GCODE file into the system, the midi command won't find the toolchange file anymore and the button no longer functions.

Please Log in or Create an account to join the conversation.

More
7 years 8 months ago #126220 by andypugh
Can you do a quick test? Open a Halmeter and look at halui.mdi-command-00 and make sure that it does go "true" when you press the button in the scenario where you are seeing a problem?

Please Log in or Create an account to join the conversation.

More
7 years 8 months ago #126229 by shipmodeller
Booting up and getting ready... will send you results

Please Log in or Create an account to join the conversation.

More
7 years 8 months ago #126230 by shipmodeller
Booting up and getting ready... will send you results

1: Homed unit
2: Pressed First button ... halui.mdi-command-00 == false
3: Went to mdi tab - pressed button -> halui.mdi-command-00 == false
4: entered o<toolchange3> call in mdi window. Toolchange executed correctly
5: Pressed First Button -> halui.mdi-command-00 = true and toolchange worked
6: Loaded "Checkers.ngc"
7: Pressed first buttin -> halui.mdi-command-00 == false.. No tool change
8: Mdi panel - tried to do o<toolchange3> call -> failed ..error message failed to find Otoolchange3 before EOF

Please Log in or Create an account to join the conversation.

Time to create page: 0.147 seconds
Powered by Kunena Forum