Advanced Search

@jerry
The config is meant to be upgraded when you first open it. But who really knows?
The main things that changed is that the spindle pin has changed to support multi spindle eg to spindle.0.on
And also 2.8 and on use joint axes for gantry configurations (wich may need some work)

RODW - If I save my CONFIG files and reformat the PC with the newest version... will my CONFIG still work... or do I need to redo everything from scratch?

If so... I may still do it... just a lot more work.

Jerry

Andy,
Sorry for the laaate response. This does convert APT to gcode.
APT is a generic process of machining a geometric defined object.
The PostProcessor is the tool used to convert the APT generated tool position data into a gcode (or other format) program for a specific machine tool. The PP has the machine's geometry definition and uses that to output gcode to control the machine.
You can use the generic APT tool position information to Post for machines with different geometric configurations.
The clearest example would be a Cincinnati 5 axis Hydrotel retrofit (like my cinci in the videos) and FSP120 from SNK. The Cinci spindle rides on the A axis and the A axis rides on the B axis. The SNK spindle rides on the B axis and the B axis rides on the A axis. Machining a part on machines sitting side by side will look amazingly similar but be assured the numbers in the program are very different.
StepNC was an initiative with the goal of what you describe as the better approach. I believe there was some success but a general success has been elusive. When driving a cutter around a set of geometric definitions a small change in one parameter could cause a wild variation in the resulting motion. This is rare but always a possibility.

2: enp46s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether c4:65:16:21:b4:9c brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.1/8 brd 10.255.255.255 scope global enp46s0
       valid_lft forever preferred_lft forever

Shows that the link is down which means that you have no connection with the 7I96S

Also its not suggested to use a /8 netmask, a /24 should be used instead

Not sure why adding a additional network card would cause an issue unless
its somehow affected the driver (didn't you inslal the DKMS driver for the
RealTek Ethernet previously?)

Also not sure what you mean by:

"the watchdog would come on as soon as i booted the machine and wouldnt even go off when i reset the 7i96s"

 

You can attach screenshots here as long as they are within size limit, but the editor is flaky so i click on "source", attach pictures then click on "insert all", and only after that is done i write the text.

DAMN!!!!
That is 99 degree C all cores all the time, no wonder the PC is giving up it's ghosts, slowly and painfully!
The good thing is, you have it easy to remove the CPU cooler and clean both the CPU and cooler, then find some thermal paste and apply some to the CPU and mount the cooler back.
Tooth paste works instead of thermal paste, albeit for a day or two only.

hello everyone, im having some issues after i installed debian and linuxcnc according to this post docs.google.com/document/d/1jeV_4VKzVmOI...m1x7oiw8VcLFdiY/edit. everything worked great until i had an idea to install another realtec network card. it worked for about a day and then the watchdog bite came on but it would still run. i shut it down and the next day, nothing worked. the watchdog would come on as soon as i booted the machine and wouldnt even go off when i reset the 7i96s. next, i removed the additional ethernet card but it still wouldnt work so i reinstalled everything according the preceding post. now, no matter how i configure it (through /ect/network/interfaces or through the gui) the network shows up somestimes but most of the time it doesnt show up in the list and i followed that post to the letter. ocationally i can ping the board and the ping times are >200 usec. im at a loss at this point and had to walk away from it. im wondering if anyone has any ideas. i have nothing but issues with this setup and it shouldnt be so hard to setup. i shouldnt have this many issues. what am i missing?

linuxcnc 2.9.2
mesa 7i96s
cw5045 stepper drives
 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp46s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether c4:65:16:21:b4:9c brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.1/8 brd 10.255.255.255 scope global enp46s0
       valid_lft forever preferred_lft forever
3: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether ec:5c:68:34:dd:41 brd ff:ff:ff:ff:ff:ff
    altname wlp23s0
    inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic noprefixroute wlo1
       valid_lft 40349sec preferred_lft 40349sec
    inet6 2603:7080:e936:2933::12d6/128 scope global dynamic noprefixroute
       valid_lft 601947sec preferred_lft 601947sec
    inet6 fd00:f405:95cf:605a::12d6/128 scope global dynamic noprefixroute
       valid_lft 601947sec preferred_lft 601947sec
    inet6 fd00:f405:95cf:605a:d8f0:4dfe:89e:a4af/64 scope global dynamic noprefixroute
       valid_lft 604502sec preferred_lft 604502sec
    inet6 2603:7080:e936:2933:90c0:f9fd:7e98:5239/64 scope global dynamic noprefixroute
       valid_lft 604502sec preferred_lft 604502sec
    inet6 fe80::3c3a:67a9:98f3:3549/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

 

Yes, you can extend the range of any THCAD by adding an external resistor
The calculation of the value required is shown in the THCAD manual, for a THCAD-10
it would be:

REXT = (VFS - 10V)/100 uA  Where REXT is the external resistor added to VIN-
and VFS is the desired  full scale voltage.

This is for example 2.4M for 250V full scale

Something seems off in the code for this widget. I've highlighted the two lines below and looked at the code briefly.

My setup is XYYZW. The code is placing "8:4" into the dict.

I believe that line 73 may be where the error is occurring:  

Can you
1. use you original (qi) setup
2. decouple the motor from the linear axis
3. set the following error limits to huge numbers
4. See if the d term causes a multi-turn runaway

 

will the THCAD10 also work? I think I have a guy that has one I can buy for cheap, I ended up ordering a plamsa cutter that has a 1:1 voltage ratio, so can I use the THCAD10 with an external high voltage resistor?

Alright, I found the solution already.

Firstly:
I was able to get debug information out of LinuxCNC by having xinit instead loading a script, that calls LinuxCNC and redirects its output to a file.

Secondly:
It turned out LinuxCNC cannot run as root, however xinit must run as root, which means the script needed to use "sudo -u cnc linuxcnc" to run it as a normal user even though xinit runs it as root.

And thirdly:
There was also an issue where it did not load forever and apparently it was waiting for user input in the console, which was not visible.
In the end it turned out it's a lot easier to run "sudo xinit" in one terminal, to run the xorg server, and in another terminal run linuxcnc manually, thereby not having an issue with root and you can also do user input.

I cannot attach a Screenshot here but it works now and I have LinuxCNC running fullscreen on a Raspberry PI, without a desktop environment.

I tried "q" mode.
I am pretty sure that there is something missing in the procedure that I was doing.
I commented out 2 lines that link bldc index-enable pin and sets encoder-offset value.
Started LinuxCNC, let the init process finish, observe bldc.0.offset-measured value, write it down, close LinuxCNC and repeat 2 more times.
Values that I got: 39984, 24798, 49060. Since that is 1000 PPR encoder that would give 4000 counts per shaft turn (1000 counts per electric turn), then those differences of ten thousand counts do not make sense to me.
And what does this offset-measured mean exactly? Distance in encoder counts between what 2 locations? One should be electrical zero of rotor, but what is the other if index is ignored in "q" mode?
Or should I place the motor on index manually and then start LinuxCNC and let it do the init process?

as two straight segments will always form a planar corner.
Yes this makes it easyer to create a plane from 3 input points and perform fillet operations on that plane.

Edit:
As long as they are not colinear.

github.com/krcwrhvgyxzqelljes/hal-core

So it seems that 2D fillets are still the norm in tool path segment blending, which gives me the impression that even modern controllers can't blend non-planar segment corners including anything that involves a helix (which is often used for tool entry moves).
I really have no idea. We now can do 95% of blending using clothoids for normal gcode.
For helix and non-planar stuff like tooldir blending, we can use b-spline blending. I think this is logical as long
as the Italian mathmeticians have not provided us the 3d clothoid algo. hihi.


as two straight segments will always form a planar corner.
Yes this makes it easyer to create a plane from 3 input points and perform fillet operations on that plane.

Also it seems kind of silly to have to segment an entire helix when it is really just the beginning and the end that need fillets.
Yes i agree. Just let it be an arc with a z value.

Note, the tool orientation vector and the current TA knot already define a plane:
Yes.

This crossed my mind as well but will only work for small changes in orientation angles. If we have a simple move like this:
G1 X0 A0
G1 x100 A180
To blend this spiral move, we use the b-spline at the X0 and the previous attached curve's end.

Ok i think i have a lot to do tommorrow, i think without wasting a lot off time in investegating as now we know what to do.