Advanced Search

    hi guys I bought a MESA 7I96+THCAD300 for my CNC plasma machine project a couple of years ago. So I don't really remember how and why I chose THCAD300, although I have plasma machines Stahlwerk CUT 70, as far as I know, with ARC pilot type ignition. And if I understand correctly I need THCAD 10? Is there any way to modify or adapt the THCAD300 I have to my needs? Should I buy a new one? If new, what kind?

Try to give an absolute path for the macros or play around with that value:
See linuxcnc.org/docs/devel/html/gui/gmoccapy.html#gmoccapy:macros[/color][/color][/color][/color][/code]

Ritterchen wrote:

Could be to only show elapsed time and predicted time (I did not get where this value comes from) instead of a progress number as you can already see how much the blue bar is filled.

I implemented a timer for the elapsed time myself to keep track of CAM-prediction vs. actual time as well as the spindle load which is super useful to get to know how hard you push your spindle. Not pretty but works^^

The G-Code Size I don't see much use for (if the program time is not there anymore), what I care about file size or lines of code? At least its hiding the currently used tool in the operating state. Imho more something for another layer like inside the file menu?

 

 
The predicted time is available in the G-code settings, see (2) forum.linuxcnc.org/gmoccapy/55010-gmocca...eded?start=20#319096

The reason why I put the progress and the elapsed time there is that it does not need further explanation there and is more  intuitive (IMHO).

The G-code size is usually not of big interest, I agree,  but I let it there to be consistent with the G-code properties e.g. in Axis.
And it is not hiding anything, as it is an optional tab.

Good morning everyone,

I've ran into some problems generating gcode for my linuxcnc lathe.

The lathe has following geometry:
XZ-lathe with turn-tooling on a revolver on the XZ-stack (Spindle rotates around Z)
Tailstock with drill-tooling on a revolver on a axis parallel to Z but named Y so i can use G33.1

This setup works perfectly fine for me if programmed by hand. My only problem is the CAM-programming with Fusion360. Everything works fine besides the drilling operations. The Fusion post spits out the Toolpath with the letter Z instead of the needed Y for drilling-cycles. I was unable to change this behaviour in the linuxcncturn-post.
Does anyone know a workflow or a fix to this problem? After a lot of research surprisingly few people even have a tailstock axis on their cnc lathe?

Thanks for your suggestions
Tim

Did you resolve this? I have a similar or the same problem with qtdragon and basicprobe.

thank you,
 I modified the network settings, I think I am connected, I cannot open the .ini file with linuxcnc because I do not have the option,
 the 2 hal and ini files must be copied into a configuration created by stepconf wizard?
 if I copy them in I switch to qtdragon? 

Almost perfect, thank you!

A couple minor issues:

1 - the calculator call works only for X Y and Z axis, but 4 and 5 axis are not, still drop-down menu

2 - if you enable the virtual keyboard, the “set X origin” window appears instead of the calculator window and the virtual keyboard does not work at all

If possible, make the calculator window appear regardless of whether the keyboard is enabled or not, it is much more convenient.

Readhmid returns: 


IO Connections for on-card -> 7I76
Pin#                  I/O   Pri. func    Sec. func        Chan     Sec. Pin func   Sec. Pin Dir

TB2-4,5                  0   IOPort       StepGen          0        Dir/Table2      (Out)
TB2-2,3                    1   IOPort       StepGen          0        Step/Table1     (Out)
TB2-10,11                 2   IOPort       StepGen          1        Dir/Table2      (Out)
TB2-8,9                    3   IOPort       StepGen          1        Step/Table1     (Out)
TB2-16,17                4   IOPort       StepGen          2        Dir/Table2      (Out)
TB2-14,15                5   IOPort       StepGen          2        Step/Table1     (Out)
TB2-22,23                6   IOPort       StepGen          3        Dir/Table2      (Out)
TB2-20,21                7   IOPort       StepGen          3        Step/Table1     (Out)
TB3-4,5                    8   IOPort       StepGen          4        Dir/Table2      (Out)
TB3-2,3                    9   IOPort       StepGen          4        Step/Table1     (Out)
Internal-Field-IO      10   IOPort       SSerial          0        TXData0         (Out)
Internal-Field-IO      11   IOPort       SSerial          0        RXData0         (In)
TB3-18,19               12   IOPort       SSerial          0        TXData1         (Out)
TB3-16,17               13   IOPort       SSerial          0        RXData1         (In)
TB3-13,14              14   IOPort       QCount           0        Quad-IDX        (In)
TB3-10,11              15   IOPort       QCount           0        Quad-B          (In)
TB3-7,8                16   IOPort       QCount           0        Quad-A          (In)

IO Connections for P1
DB25 pin#             I/O   Pri. func    Sec. func        Chan     Sec. Pin func   Sec. Pin Dir

 1                      17   IOPort       StepGen         5        Dir/Table2      (Out)
14                     18   IOPort       StepGen         5        Step/Table1     (Out)
 2                      19   IOPort       StepGen         6        Dir/Table2      (Out)
15                     20   IOPort       StepGen         6        Step/Table1     (Out)
 3                      21   IOPort       StepGen         7        Dir/Table2      (Out)
16                     22   IOPort       StepGen         7        Step/Table1     (Out)
 4                      23   IOPort       StepGen         8        Dir/Table2      (Out)
17                     24   IOPort       StepGen         8        Step/Table1     (Out)
 5                      25   IOPort       PWM              0        PWM             (Out)
 6                      26   IOPort       PWM              0        /Enable         (Out)
 7                      27   IOPort       PWM              0        Dir             (Out)
 8                      28   IOPort       SSerial           0        TXData2         (Out)
 9                      29   IOPort       SSerial           0        TXEn2           (Out)
10                     30   IOPort       SSerial           0        RXData2         (In)
11                     31   IOPort       QCount           1        Quad-IDX        (In)
12                     32   IOPort       QCount           1        Quad-B          (In)
13                     33   IOPort       QCount           1        Quad-A          (In)

IO Connections for P2
DB25 pin#             I/O   Pri. func    Sec. func        Chan     Sec. Pin func   Sec. Pin Dir

 1                     34   IOPort       None
14                     35   IOPort       None
 2                     36   IOPort       None
15                     37   IOPort       None
 3                     38   IOPort       None
16                     39   IOPort       None
 4                     40   IOPort       None
17                     41   IOPort       None
 5                     42   IOPort       None
 6                     43   IOPort       None
 7                     44   IOPort       None
 8                     45   IOPort       None
 9                     46   IOPort       None
10                     47   IOPort       None
11                     48   IOPort       None
12                     49   IOPort       None
13                     50   IOPort       None


Then for the pullups I get: 
mesaflash --device ethernet --addr 10.10.10.10  --rpo 0x1005
0001FFFF

mesaflash --device ethernet --addr 10.10.10.10  --rpo 0x1004
0001FFFF
 

Thank you for reply.

So to change the firmware rather than using the software PWM is the way to go?
linuxcnc.org/docs/html/man/man9/pwmgen.9.html

I will give the the firmware change a try.

I hope I will not "brick" the card.

ihavenofish wrote:

Sooo, now i will have ethercat servos. This will be fun....

Bold move!

Just check out the stickies and maybe the Linuxcnc ethercat driver repo github.com/linuxcnc-ethercat/linuxcnc-ethercat

One thing I wondered is how thick the material is you used for the gantry?

So the 9v battery tells you it's working, The light in the board should flash faster at 9 volts

Make sure the scaling link on the board is set to 1/32. Next step is to check the encoder velocity in halshow. It should be hovering around the 0 volt frequency (1/32 thereof). if not, debug the reason

There are some encoder settings in hal but they appear to be set OK

Next step is to ensure the thcad calibration settings are set for qtplasmac. There is a link to an online calculator to determine the correct settings in the QTplasmac docs.

I'll order some filters and stick them on.

I've got some big ferrites in a box here too so I'll stick them on but looking online all of the motor chokes I can see are bloody huge, bigger than the VFDs supplying them so I suspect my ferrites are in the wrong league.

Thinking of it now I believe I get the same behaviour with the VFD not acutally running, so analog voltage being supplied but with no direction signal it will still display the commanded frequency on the screen, I'll test this afternoon

No. I went back to the instructions and did see a page (kcjengr.github.io/probe_basic/probe_basic_parameters.html) saying to copy the file (The Probe Basic Sim Config Folder contains the sim.var file), which I don't recall seeing that instruction page.

In the folder: linuxcnc/configs/probe_basic/ I saw the sim.var file and also a bak and log version of that file. I copied those to my working folder but it did not work. Opening the file shows the lack of the lines which control touch off speed, based on the chart of the instructions page. What I do have is linuxcnc.var in my config folder and my ini file has that listed under rs274ngc section for line: parameter_file=linuxcnc.var

Also, after reading which files and folders to copy, it seems I am missing two other folders and I don't see them in the simulation folder. One is user buttons and and I don't recall the other one.

If I'm missing folders from the simulation, do I need to completely reload linuxcnc?

When I converted to probe basic, there was one error and I had to read the debug and change an item, but that was months ago, so I don't recall what it was. It took many, many, hours to figure out how the ini and hal files worked to get something to happen and I did not have the ballscrews to run the machine so was at a disadvantage.

At this point, I'm not sure if the probe basic simulation folder is complete any longer.

I have backed up changes made to my hal and ini and may have a backup of my folder from when it was AXIS. Maybe I need to start over and either reuse or copy and paste the important parts from my hal and ini files and make sure all the files and folders are there. At least now that the mill moves, I have all the data to put in for travel, direction, pins, and so on. While I was afraid I might have to start over with probe basic, some time back, it might not be too bad now that I know more about how to navigate the different parts.

So, start over or do you think I can salvage my install?

Thanks for the help, just the short line you typed sent me in a great direction. I knew there was a missing link like that somewhere.

Thanks mate! Will do for sure though I don't know when. Do you know this mental disfunction when someone is starting 100 different projects and then not finishing 99 of them for the next 5 years?

Don't know how it happen but i've bought stahlwerk double pulse 200 mig welder, then AC/DC TIG combined with 50A plasma cutter and then decided to buy separate plasma - CUT 70p. And then machine torch for it. And then... "stop!" <- that was my wife:D So now i have to make use of it;P

Have a good day!
Wojciech

It looks good BUT the file
~/linuxcnc/configs/sim/gmoccapy/macros/change_g43.ngc
is created after load sim configuration. For example in my computer this file dont exist.

In my RIP installation file is here:
/home/zdenek/linuxcnc/linuxcnc-master/configs/sim/gmoccapy/macros/change_g43.ngc

This scripts must work also in debian instalation.

It is defined here:
github.com/LinuxCNC/linuxcnc/blob/1c72d4...ipts/linuxcnc.in#L53
But I dont know, how to use it.