Feature Request

More
6 years 2 months ago #177422 by snowgoer540
Replied by snowgoer540 on topic Feature Request
That doesn't exactly work... it gives me a ton of errors about my plasma_connections.hal, and when I comment all of those lines out, it will run, but I cant turn the machine on to home it to test it...

Please Log in to join the conversation.

More
6 years 2 months ago #177423 by snowgoer540
Replied by snowgoer540 on topic Feature Request
In the meantime, I got bored and found a screen recorder... Figured I'd catch the bugger red handed! :evil:

CR Hiccups

Please Log in to join the conversation.

More
6 years 2 months ago #177429 by snowgoer540
Replied by snowgoer540 on topic Feature Request
I'll be away most of this evo (is that a thing?), it's firehouse eboard meeting night.

At any rate, I did some digging on my mill PC. I found the following pertaining to clearing programs. I follow some of it, but some of it really eludes me too. If there's a reference to another script or something I can grab that as well. I am relatively sure it refers to an empty g-code file that was in their python scripts directory, so I attached that as well.

Code:
self.error_handler.write(('Loading file from recent file drop down: ' + path), ALARM_LEVEL_DEBUG) if path == CLEAR_CURRENT_PROGRAM: self.use_hal_gcode_timers = False self.last_runtime_sec = 0 # we never have an estimate for the empty program self.ensure_mode(linuxcnc.MODE_AUTO) self.command.program_close() self.status.poll() # Keep this in superstitiously self.is_gcode_program_loaded = False # clean up the temporary copy that we always create and have linuxcnc load if os.path.exists(LINUXCNC_GCODE_FILE_PATH): os.unlink(LINUXCNC_GCODE_FILE_PATH) self.gcodelisting_buffer.set_text('') self.set_current_gcode_path('') # load the empty gcode file from the same directory as the program is running from program_dir = os.path.dirname(os.path.abspath(inspect.getsourcefile(self.__class__))) emptyfile_fullpath = os.path.join(program_dir, EMPTY_GCODE_FILENAME) # FIXME consider using redraw_gremlin rather than naked empty file draw here self.gremlin.load(emptyfile_fullpath) # must set a view to remove the old tool path # but default view for mill and lathe is different if 'Y' in self.gremlin.get_geometry(): self.gremlin.set_view_p() else: self.gremlin.set_view_y() self.combobox_masked = True # sort of a hack here - add a '' name to the top # of the list store. The previous way of doing this # caused some wonky gtk behavior. See issue #660 sort_file_history(self.file_history_liststore, path, None) self.file_history_liststore.prepend(['', '']) self.combobox_masked = False self.is_gcode_program_loaded = False # force refresh the tool list store as we color code it based on if the tools are used by the program or not self.gcode_program_tools_used = [] self.refresh_tool_liststore(forced_refresh=True) self.gremlin_options.show_all_tools() self.gremlin.clear_live_plotter() self.set_start_line_settings(1) else: self.load_gcode_file(path)

Please Log in to join the conversation.

More
6 years 2 months ago #177435 by phillc54
Replied by phillc54 on topic Feature Request

snowgoer540 wrote: That doesn't exactly work... it gives me a ton of errors about my plasma_connections.hal, and when I comment all of those lines out, it will run, but I cant turn the machine on to home it to test it...

Sorry, I forgot about the connections.hal, here is the one I am using.

Please Log in to join the conversation.

More
6 years 2 months ago #177438 by phillc54
Replied by phillc54 on topic Feature Request

snowgoer540 wrote: In the meantime, I got bored and found a screen recorder... Figured I'd catch the bugger red handed! :evil:

CR Hiccups

I am glad that you did that vid. I didn't realize that you were pausing while it was still probing while recovering, I was pausing after it had recovered. Now I know what to look for. :)

Edit: it is a good idea when doing this sort of testing to start LinuxCNC from a terminal, that way you may see some error messages.

Please Log in to join the conversation.

More
6 years 2 months ago #177443 by phillc54
Replied by phillc54 on topic Feature Request

snowgoer540 wrote: I found the following pertaining to clearing programs.

Code:
self.command.program_close()

This command does not exist in LinuxCNC, maybe they rewrote some of the linuxcnc python module as well.
github.com/LinuxCNC/linuxcnc/blob/master...ensions/emcmodule.cc
If you search for "program_" you will see there is an open but no close.


I am relatively sure it refers to an empty g-code file that was in their python scripts directory, so I attached that as well.

Code:
(empty program to clear tool path display) M30

Conversational does it in a similar way:
Code:
(new wizard) M2
Does theirs not display that code when it is loaded?

Is their GUI GPL?

I should also mention that all the above applies to "gremlin" which is the preview that conversational uses but Axis has it's own preview so work differently.

Please Log in to join the conversation.

More
6 years 2 months ago #177455 by snowgoer540
Replied by snowgoer540 on topic Feature Request

phillc54 wrote: Sorry, I forgot about the connections.hal, here is the one I am using.

So that hal file ended up being close to mine, but when I start the sim, I still cant do anything with it because I cant turn on the "on" switch to get to homing or anything..? Do I need the regular hal file as well?


I am glad that you did that vid. I didn't realize that you were pausing while it was still probing while recovering, I was pausing after it had recovered. Now I know what to look for. :)

Edit: it is a good idea when doing this sort of testing to start LinuxCNC from a terminal, that way you may see some error messages.

Good deal, I apologize, I probably didn't explain it well enough. I figured it was the closest thing to a failed torch fire.

Can you remind me how to run it from a terminal?


If you search for "program_" you will see there is an open but no close.

Ok, makes sense. I guess I could ask, I am part of their beta test group, I have a pretty good rapport with them (I've brought them a lot of bugs to squish too ;)) I know one can request the source code due to all the licensing stuffs.


Does theirs not display that code when it is loaded?

Correct, it goes back to a blank slate.


Is their GUI GPL?

They use Glade. Not sure if Glade = GPL?

Please Log in to join the conversation.

More
6 years 2 months ago #177456 by phillc54
Replied by phillc54 on topic Feature Request

snowgoer540 wrote:

phillc54 wrote: Sorry, I forgot about the connections.hal, here is the one I am using.

So that hal file ended up being close to mine, but when I start the sim, I still cant do anything with it because I cant turn on the "on" switch to get to homing or anything..? Do I need the regular hal file as well?

No, I just click estop then power and away it goes.


Can you remind me how to run it from a terminal?

Code:
~/linuxcnc-dev/scripts/linuxcnc ~/linuxcnc/configs/my_sim_dir/plasma.ini


Does theirs not display that code when it is loaded?

Correct, it goes back to a blank slate.

I wonder how they do that. I don't think it would be possible in Axis.


Is their GUI GPL?

They use Glade. Not sure if Glade = GPL?

Glade is just a WYSIWYG UI designer


I have just pushed some changes. When you commit to a Resume Cut then you are committed, the only way out is a stop or disable the torch and pause after the offsets are cleared. It is due to the timing constraints we have in relying on some userspace pins from halui.

Please Log in to join the conversation.

More
6 years 2 months ago #177457 by snowgoer540
Replied by snowgoer540 on topic Feature Request

phillc54 wrote: No, I just click estop then power and away it goes.

Oh right, estop. I didn’t try clicking that because I don’t have to on my table...


Code:
~/linuxcnc-dev/scripts/linuxcnc ~/linuxcnc/configs/my_sim_dir/plasma.ini

Thanks!


I wonder how they do that. I don't think it would be possible in Axis.

I’ll fire off an email tomorrow.


I have just pushed some changes. When you commit to a Resume Cut then you are committed, the only way out is a stop or disable the torch and pause after the offsets are cleared. It is due to the timing constraints we have in relying on some userspace pins from halui.

I’m good with commitment... just ask my girlfriend :laugh: sounds good, maybe I’ll wake up early again and have a go at it before work.

I’m pretty sure I understand what you’re saying. Only thing I can think of off the top of my head is, is would there be a problem if the torch went to fire again and paused from failing without any movement in the X or Y? Would that clear the offsets? Or would it cause similar issues to what I’ve been seeing?

Please Log in to join the conversation.

More
6 years 2 months ago #177458 by phillc54
Replied by phillc54 on topic Feature Request

snowgoer540 wrote: I’m pretty sure I understand what you’re saying. Only thing I can think of off the top of my head is, is would there be a problem if the torch went to fire again and paused from failing without any movement in the X or Y? Would that clear the offsets? Or would it cause similar issues to what I’ve been seeing?

It would pause goto the top and give an error. You could then either fix the issue and resume or press stop which will clear the offsets.

Please Log in to join the conversation.

Time to create page: 0.328 seconds
Powered by Kunena Forum