Advanced Search

FlaredFins wrote:

I don't think i have my Z set correctly no issues in cutting or height control, When the machine is homed for the first program run, it runs up to the Z+ Prox / Z home from their it drops down to I'm guessing an offset I put in. it than drops down about 2 inches and zeros the Z drive.

Wrong ini settings for Z axis, home switch must be up, HOME must be 0, HOME_OFFSET must be something small so it backs of off the switch, 3-5mm is ok, max limit to 0 and min limit to -100 or -150 or whatever the Z axis can do.

FlaredFins wrote:

On Probe it does this weird little double probe you can watch it come off the probe switch than go back to it than proceeds to cut height. is this normal or am I missing something in the settings?

Yes it is normal and i hate it, this should have never been implemented.

FlaredFins wrote:

Randomly had no arc signal from the Hypertherm 65. this was closer to the end of the program about 45 minutes into cutting. I'm guessing it was a Hypertherm issue as I turned it off reseated the CPC port and it came back no issues but eventually did it again. I'm running Mode 1 in QTPlasmac which I believed was the setting when there is a separate ARC ok Signal?

Try some contact spray.

FlaredFins wrote:

During that no arc ok phase I also noticed that QTPlasmac will attempt three times to fire the torch after the third round of that it powers off with the screen switch and resets the program. Is this normal if it is, is there a way to change the number of rounds it will go through before resetting the whole program. 

Yes it is and can be set in the config tab, so can time between retries. Do not forget to save after changing.

What is your idea for the GUI may be i can help I always tought a C or C++ GUI should be more fluid than Python, may be I can help..

Grotius wrote:

I need a volunteer !!!
Is someone willing to only make a gui with a designer? You don't have to have coding skills, only make the design.
It would be awesome if we can create high end controller gui's like fanuc, siemens, etc you name it.
But i need help. Eventually you may ask for public gifts yourself, In fact you did work.
 
 
 

I think first you should decide for what the GUI is for. Different machines being it a lathe, milling, plasma, laser or 3D printing require a different "style" GUI. I personally dont think you can have "the best" GUI that suits all the applications.

Then there is personal preference, some like things one way and some the other. Example, I dont know if you were serious, but I have always found the Fanuc GUI ugly and outdated. Don't get me wrong, I like Fanuc and they do excellent work, its just the GUI that for me is very off putting. Actually not entirely true, their Cobot sw was looking pretty nice, didn't play with that for more than a couple minutes though so I cant say if it was good, but it looked decent.
I personally like more "modern" looking stuff like Mazak, well maybe that a bit over the top but its completely different from Fanuc. TCI has a pretty nice GUI in their cutting machines, again something different from Mazak and Fanuc but I have always liked it.

Look like you PIN_XXXX file does not have the INM module fully supported
It needs 2 entries in the module ID section, the normal module instantiation
plus a tag that specifies the number of inm inputs (check some PIN_XXX
files for standard configurations with inm = 7I96S or pin files for a 7I36)
 

So I set P03.08 to 1 from the buttons on the amplifier. I also had DI3 jumped HI. This caused errors. I removed the jumper and it worked as normal. I then put the jumper back, and if if the linuxcnc enable button was off, the drive would start.

@PCW

Now I am trying the shared index . But I have a problem. With the old firmware, the multiplexer inputs work. With new firmware that can use the index with stepgen all Input not works.

"hm2_7i98.0.inmux.00.input-23" does not exist 3566

I am attaching a link just for clarification

forum.linuxcnc.org/24-hal-components/329...-with-7i76e?start=20

PS:  The pins inmuxAddr0Pin ...  InMuxDataPin  are read as  inputs and outputs

i have install probe basic on linuxcnc v2.9.2 but it is not showing in linuxcnc configuration selector
but if i go to editvcp probe_basic it open to edit in Qt Designer.

Wait whaaattttt..... (Researches for about 20 min....mind explodes with possibilities)...... Thanks a bunch! Will try this out in a week or two

If the Hypertherm Arc OK output is from a relay (as opposed to a Optocoupler),
you may need to add a load resistor to provide the "wetting" current the relay
contacts require. (This current may be as much as 100 mA so requires say a 220 Ohm
5W load resistor)

 

EDIT

I fat-fingered the parameters above and forgot the closing ">".  Should look like this:
#<tool_touch_x_coords> = #<ini[TOOL_SETTER]TOOL_SETTER_X>
#<tool_touch_y_coords> = #<ini[TOOL_SETTER]TOOL_SETTER_Y>
#<tool_touch_z_coords> = #<ini[TOOL_SETTER]TOOL_SETTER_Z>

If you look at the tool_touch_off subroutine, the tool touch-off position values appear to be stored as persistent variables in the .var file.

Specifically #5181, #5182, & #5183 (X/Y/Z).

I don't have a linux machine in front of me right now, so I can't open the UI and see exactly how the 'set tool touch off position' button works, but I suspect it just writes the values of the three fields to the appropriate variable numbers without any super-complicated backstage stuff.  It also (probably) reads those values at UI launch.

I'm not sure what the value is of using the INI file to store the location vs. just using the .vars file... but far be it from me to challenge someone wanting a 'peculiar' feature or change; I'm guilty of fiddling with all sorts of stuff like this.

If you want to store & retrieve the values from your INI file, I think you could do it like this:
Edit INI file:
Edit tool_touch_off.ngc:
I think that should work, but please be careful to test at really low speeds.  Note that this 'hack' has nothing to do with the on-screen tool touch-off locations which are managed through the GUI.  You can still enter the location on-screen, but you've essentially hijacked the tool setter subroutine so it ignores the on-screen values (which are still stored are variables).

Further, if you update Probe Basic your 'hack' is likely to get overwritten and will need to be re-done.  The subroutine will need to be edited again, and if you've made any changes to the UI those will also need to be re-added to the updated version.

Possibly you could create a new 'touch off location' display field and stick it in a new user tab - those shouldn't get over-written if you update PB.

I did something similar for my ATC sequence by using INI values for the Z-movement locations and speeds rather than the values hard-coded in the tool change subroutines.

So, we ran our first production run using the 7i96s, THCad2 and QTPlasmac, and it was like jumping in a Cadillac after driving a pinto. Night and day between Mach4 and linuxcnc. Soo happy I invested in switching electronics over and making the switch. 

Couple of issues I encountered and would like to get corrected.
I don't think i have my Z set correctly no issues in cutting or height control, When the machine is homed for the first program run, it runs up to the Z+ Prox / Z home from their it drops down to I'm guessing an offset I put in. it than drops down about 2 inches and zeros the Z drive. not a big deal but when I'm trying to line the torch up it won't go below 0.00 is it better to let the Z axis home off the probe or an upper limit. 

On Probe it does this weird little double probe you can watch it come off the probe switch than go back to it than proceeds to cut height. is this normal or am I missing something in the settings?

Randomly had no arc signal from the Hypertherm 65. this was closer to the end of the program about 45 minutes into cutting. I'm guessing it was a Hypertherm issue as I turned it off reseated the CPC port and it came back no issues but eventually did it again. I'm running Mode 1 in QTPlasmac which I believed was the setting when there is a separate ARC ok Signal?

During that no arc ok phase I also noticed that QTPlasmac will attempt three times to fire the torch after the third round of that it powers off with the screen switch and resets the program. Is this normal if it is, is there a way to change the number of rounds it will go through before resetting the whole program. 

Appreciate any info on these Items 

I've got this in working order now. Seems that there were a few homing entries incorrect and missing.

Thanks Chris for your helpful input!

Andy

thank you. at the time i was trying to get a working configuration. i ended up getting it working without installing the mesact, but i will keep that in mind if i need it in the future.

Another option is to use the text installer > expert mode and manually configure the network, post installation this can be changed to DHCP or left as a static address.