Advanced Search

Yes, I know what LinuxCNC *can* do with directly driving things, but that's not at all what I want. You say "it's already there", but it's not. This is the exact opposite of what I want.

COlger81 wrote:

This works well but it would be nice if i could save current tool persistently on shutdown, and recall the last tool on startup.

The PB macros use persistent parameters to keep track of which tool is in which pocket (and spindle); it's pretty graceful on re-start as once the homing routine is complete it 'remembers' the state at last shutdown.

Once homing is done, the animated screen widget updates to show the post-homed status - which tool is in which pocket, what's in the spindle, etc.

As you mentioned, I think you need some sort of 'home' sensor - a once-per-turn thing.  I know that ATC is pretty slow and homing it would be annoying each startup, but it'd be safe.

Thank you Chris for your reply. I am using Imperial. I downloaded Debian Bookworm Preempt-RT ISO 12.4 from the Linuxcnc website. The Linux version is 2.9.2I believe the Debian version. I've tried to make various changes based on percentages ext but regardless of what I change the numbers to, when the machine locates to the X and Y, it always goes to x0.0137 and y0.0208.

If you decide not to do this from scratch, a 7I92TM+ 7I77 or 6I25+7I77
will work and are available.

I would use all 6 connections (fully differential)
just because its simpler to setup, has better noise
immunity than single ended, uses the standard hal setup,
and does not require LinuxCNC 2.10

I was mainly pointing out that 1 PPR threading should work well
with servo spindles since they should run at a very constant speed
(unlike say a VFD with varying load and LinuxCNC just guessing the
speed between index pulses)

Wrong step/dir settings cannot hurt your drive.

Too long step time and step space settings will limit the maximum step rate
For example, if you set the step time and step space to 5 usec (5000 and 5000)
the maximum step rate would be 100 KHz, that is 1/(5usec+5usec)

I would try running LinuxCNC rather than the pncconf test as it will indicate if there
are other issues preventing normal operation.

one question i have is; is the spindle light on tb2, on the mesa 7i96s supposed to come on when i turn on the spindle? is that normal?

Yes, that is normal, it is an indicator to show that that output is activated.
 (all TB3 inputs and outputs have this feature)

If you have ssh you should also have scp to copy the files as-is.

The 7I96S analog output is designed to replace a potentiometer.

I felt brave yesterday and gave it a go with one of the axis motors.
- I connected the step/direction outputs to the mesa card
- I set the driver to default to enabled as long as its powered on. it then turned the fans on and set "run" in the display, which should be a good sign
- I made sure the servo drive was in position mode
- I set the "pulses pr rev" in pncconf to 10000, which is the default in the servo drive when in position mode
- I left all the step time settings as is.


And I went into the simulation window to hopefully do some jogging. But nothing happened.
I Played around a little with the "step-on time", "space", "direction hold" and "direction setup" settings, with no real thought behind what I did (i still really don't understand what they do), to no avail.

 

I was actually going to ask if anyone knows more about their new (1500MX) EtherCat support... Have they made any changes they have given back to the community or have they just consumed the EtherCat group's work and its now "good enough"?

I tried to run the servo with twincat and the esi config file. This worked. Then i tried to remap the pdo´s in twincat so that they match with the ethercat-config.xml. Still the same issue.

Then i deleted the PDO mapping with command:
Now im able to get the servo in OP mode using:
After starting linuxcnc, the pdos are remapped and the same error (previus post) occurs.

Really dont know what to do now, that doesnt make sense to me, espacially that it doesnt work when i set the pdos with twincat.

Thank you PCW, I also see your post edit that I can actually just connect my 1PPR signal to the Mesa, though to both A and I connector.
PS: I suppose i would use ENCA+ and IDX+ on the Mesa card, and OA+ and OZ+ on the servo drive.

If you wouldn't mind PCW, just for the sake of learning something new today; why do you suggest doing this? Will there be an advantage over just connecting them all up? I mean, I have all 6 outputs readily available on the driver, and all 6 corresponding connections on the mesa card.
or what about using it as a single ended encoder, with just A+, B+ and Z+ connected, which to a newbie liek me seems like a more "complete" setup, but still saving a little on connections.


 

 
 

Hi Thommy,

back from the PC modification front.
PC completely disassembled and the thermal paste between the processor and cooling element.
Replaced PC case modified so that the air inlet is not or less restrictive and the pseudo centrifugal fan actually blows through the cooling element
PC reassembled (very delicate work)
All components plugged in
Start PC, Debian/LinuxCNC starts, works perfectly.
Open the terminal and query sensor values (see below).
The temperature values at the beginning are promising.
Start Linux CNC with temp. values below 60°C.
The exact same error message still appears.
Leave the PC with LinuxCNC open and continue working.
Temp. values still climb to 92°.
So I think that the temp value around 60° showed that LinuxCNC still gives the error message.

What is fact is that temperatures drop below 50° relatively quickly. It is also a fact that the temperatures rise relatively quickly to 95° when starting linuxCNC.

I would now be more than grateful if I could get some information as to whether I should operate with a different PC?

Are there any other ways to find out where the error comes from?
thanks in advance


cnc@cnc:~$ sensors
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +30.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +35.5°C  

nvme-pci-0400
Adapter: PCI adapter
Composite:    +27.9°C  (low  =  -5.2°C, high = +79.8°C)
                       (crit = +84.8°C)

amdgpu-pci-0500
Adapter: PCI adapter
vddgfx:        1.28 V  
vddnb:       774.00 mV
edge:         +32.0°C  
PPT:           8.00 W  

cnc@cnc:~$ sensors
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +33.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +32.8°C  

nvme-pci-0400
Adapter: PCI adapter
Composite:    +31.9°C  (low  =  -5.2°C, high = +79.8°C)
                       (crit = +84.8°C)

amdgpu-pci-0500
Adapter: PCI adapter
vddgfx:      712.00 mV
vddnb:       774.00 mV
edge:         +32.0°C  
PPT:           5.00 W  

cnc@cnc:~$ sensors
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +37.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +61.0°C  

nvme-pci-0400
Adapter: PCI adapter
Composite:    +33.9°C  (low  =  -5.2°C, high = +79.8°C)
                       (crit = +84.8°C)

amdgpu-pci-0500
Adapter: PCI adapter
vddgfx:        1.31 V  
vddnb:       774.00 mV
edge:         +54.0°C  
PPT:          15.00 W  

cnc@cnc:~$ sensors
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +43.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +67.5°C  

nvme-pci-0400
Adapter: PCI adapter
Composite:    +35.9°C  (low  =  -5.2°C, high = +79.8°C)
                       (crit = +84.8°C)

amdgpu-pci-0500
Adapter: PCI adapter
vddgfx:        1.31 V  
vddnb:       774.00 mV
edge:         +60.0°C  
PPT:          16.00 W  

cnc@cnc:~$ sensors
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +50.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +92.0°C  

nvme-pci-0400
Adapter: PCI adapter
Composite:    +40.9°C  (low  =  -5.2°C, high = +79.8°C)
                       (crit = +84.8°C)

amdgpu-pci-0500
Adapter: PCI adapter
vddgfx:        1.26 V  
vddnb:       774.00 mV
edge:         +70.0°C  
PPT:          15.00 W  

cnc@cnc:~$ sensors
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +51.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +76.2°C  

nvme-pci-0400
Adapter: PCI adapter
Composite:    +41.9°C  (low  =  -5.2°C, high = +79.8°C)
                       (crit = +84.8°C)

amdgpu-pci-0500
Adapter: PCI adapter
vddgfx:        1.28 V  
vddnb:       774.00 mV
edge:         +67.0°C  
PPT:          16.00 W

cnc@cnc:~$ sensors
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +43.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +44.5°C  

nvme-pci-0400
Adapter: PCI adapter
Composite:    +40.9°C  (low  =  -5.2°C, high = +79.8°C)
                       (crit = +84.8°C)

amdgpu-pci-0500
Adapter: PCI adapter
vddgfx:      712.00 mV
vddnb:       681.00 mV
edge:         +43.0°C  
PPT:           5.00 W

 

Mesa firmware is open source, the 7i92 & 7c81 schematics are floating around on the forum. The mesa firmware is available for download on the product page of each board.

Here's one I made earlier:
forum.linuxcnc.org/show-your-stuff/51142...pga-card-9d60#289226

One of the best ways to learn C is to read some C code.
This folder is a treasure trove of hal component examples
github.com/LinuxCNC/linuxcnc/tree/master/src/hal/components
And read these docs. linuxcnc.org/docs/stable/html/hal/comp.html
When you are ready, pick a real simple example (like and2.comp), compile it yourself, then use it for a template for your first component.
Try writing a component that lights up a pin when th X axis is > 50% of its travel or some other trivial example.
Or pretend your x axis is slightly crooked (say 3%). Compensate for this error by moving the Y axis based on X axis position.
 

I've been holding my tongue all this time. I have observed many people failing to get the Gecko's going. Whilts it is evidently possible, the additional cost vs a DM556 or similar is just not worth it. I would try and sell it to a Mach3 user