Advanced Search

i am thinking this would also open up the ability to have a monitoring system pickup info from every linuxcnc on the shop floor as i have many linuxcnc machines running

so like my other controls do mitsubishi , fanuc etc you can tie them into a monitoring software suit, which shows alarms, running statues, job its on etc etc .. which then you also use for job scheduling etc..

intresting times

then all we need is the ability to run multi interpreters and superimposed control

Hi, I have a really strange issue with random banging noise from a rack/pinion axis when using continuous jogging (on axis).  Jogging velocity is 500mm/min and I haven't tried higher numbers since I don't want to do any damage if it's some kind of servo reversal or something like that.  I've done G0/G1 moves at up to 3000mm/min with no noise at all.  I also tried Twincat and it jogs without any strange issues.  Any ideas what I might be looking for?

 

no joy.
even changing the polarity of the pin and using "M66 P26 L1 Q10" fails to work

My component issues an ohmic-probe signal which plasmac will then pause the program, and sometimes the "Pause" button is still shown instead of what should be a "Resume" button, so maybe that has something to do with it. However, this is not the only case when the cut recovery panel doesn't work. If I hit Pause (spacebar) manually during a cut, it is not guaranteed to have cut recovery work appropriately still.

I could try instead linking the nozzle short condition to the program-pause signal and see if that helps with the timing aspect.

changed to the version in my reply, now heading out to test... expecting failure... hope nothing breaks...

It might be helpful to turn on debugging in terminal to see exactly what point in the sequence its getting stuck.

INI file
[DISPLAY]
DEBUG = 0x10

And then start LCNC from the terminal.

Attempt your tool change (M6 T1 or T1 M6) and when it gets hung up, use ALT-TAB to switch to the terminal window.  You should be able to see what commands are going on in LCNC and likely a hint as to exactly what is hanging up.

I have found that when sending config pdos to the drive it is successful in LinuxCNC but then lcec dies because it can't map some of the pdos that were just configured.  If you do an "ethercat rescan" then the pdos are shown and LinuxCNC starts just fine.  I'm not sure if this is an linuxcnc-ethercat or etherlab ethercat-master issue.  This may still be some type of interaction with EoE but out of curiosity @endian could you please try seeing if that works for you as well vs disabling EoE?

LinuxCNC was not running during the following commands:
cnc@shaper:~$ ethercat pdos -p 19
SM0: PhysAddr 0x1800, DefaultSize  234, ControlRegister 0x26, Enable 1
SM1: PhysAddr 0x1a00, DefaultSize  234, ControlRegister 0x22, Enable 1
SM2: PhysAddr 0x1000, DefaultSize    0, ControlRegister 0x64, Enable 1
  RxPDO 0x1600 ""
    PDO entry 0x6040:00, 16 bit, ""
    PDO entry 0x607a:00, 32 bit, ""
SM3: PhysAddr 0x1100, DefaultSize    0, ControlRegister 0x62, Enable 1
  TxPDO 0x1a00 ""
    PDO entry 0x6041:00, 16 bit, ""
    PDO entry 0x6064:00, 32 bit, ""

cnc@shaper:~$ ethercat rescan

cnc@shaper:~$ ethercat pdos -p 19
SM0: PhysAddr 0x1800, DefaultSize  234, ControlRegister 0x26, Enable 1
SM1: PhysAddr 0x1a00, DefaultSize  234, ControlRegister 0x22, Enable 1
SM2: PhysAddr 0x1000, DefaultSize    0, ControlRegister 0x64, Enable 1
  RxPDO 0x1600 ""
    PDO entry 0x6040:00, 16 bit, ""
    PDO entry 0x6060:00,  8 bit, ""
    PDO entry 0x607a:00, 32 bit, ""
    PDO entry 0x60ff:00, 32 bit, ""
SM3: PhysAddr 0x1100, DefaultSize    0, ControlRegister 0x62, Enable 1
  TxPDO 0x1a00 ""
    PDO entry 0x6041:00, 16 bit, ""
    PDO entry 0x6064:00, 32 bit, ""
    PDO entry 0x6077:00, 16 bit, ""
    PDO entry 0x6061:00,  8 bit, ""
 

would i be better with:

whole config: github.com/travis-farmer/linuxcnc
my routine using it: github.com/travis-farmer/linuxcnc/blob/m...files/toolchange.ngc
(line 11)

the signal sits at LOW, but when the spindle VFD is running or braking, it goes HIGH, and falls back to LOW after the spindle stops.

what i experienced is a program hang when the routine is started with a spinning spindle, but even when the spindle completes the stop, the program then continues, but aborts for some reason, while it is probing down.

what i observed with the GUI (FlexGUI by JT) is that when M66 starts, the GUI hangs, even after the M66 passes with success. i know it hangs because i watch the hal-pin on the GUI, and it doesn't change for the signal in question (motion.digital-in-26). but as soon as it does, the tool-setter probing operation (remapped as M201) aborts.

if i change the line to "M66 P26 L2 Q7", it hangs the GUI and operations permanently, if the spindle is not turning.

what is going wrong here? is it my error? the GUI error, or a LinuxCNC error? my errors are easier to fix...
 

Also watched this... Try to understand... But... not really... What to use in my case...

If there are no disadvantages to using the 7I97T I will just go that way. I will look at the different IO boards you've suggested. Thanks

And if I understand correctly, all pins must be connected to motion I/O, to be possible to manipulate them from G-code.
Is that correct?

(40.5 is the Z bounds of 3D_Chips)
Opinions?
To avoid crashing into the material, if you move "back" to the absolute position at which the offset was cleared, with the same velocity at which the Z axis is sinking, it stays in place at the same Z height. Is there a better way that wouldn't require sending an MDI command?
 

A few words more....
To the main spindle's VFD 2 output signals (alarm and spindle stop) connected also to the mesa card. The spindle stop signal is high, when the spindle run. So the first check will be this.
There are also sensors (S12-S14) for rotary head position "0°", or "180°" (the head must move cw, or ccw sensing the head position)
For the "clamps" (catching the tool, rotates the head and release it) not sure if there any sensor (i will figure it out later)
Also there are a head top and bottom position sensor + tool lock/release in the spindle.
If needed, i will add tomorrow my config, but there are nothing about the carousel, only I/O pin names

The first question is:
Which pins i have to use from the carousel component, to see only how it rotates and find the commanded pocket number.
pockets - The number of pockets in one toolchanger - 24.
encoding - The position encoding. - ? (not sure - Index, or count)
num_sense - The number of position sense pins. - 3 (but if use Index just 2)
dir  - Set to  2 for bidirectional operation.
carousel.N.pocket-number
carousel.N.enable
carousel.N.ready
carousel.N.sense-0 
carousel.N.sense-1
carousel.N.sense-2
carousel.N.index-enable (sense-0 if i understand correctly will wait for high, or i will invert it if needed low)
carousel.N.motor-fwd
carousel.N.motor-rev
carousel.N.homed (i have no idea how to home the carousel)


An other issue with the "message". Some why it's triggering the pop up message at LCNC startup. (they are high, but i'm used the inverted pin "-not")
+ at startup, before showing the main screen pop up a message "negative tool number id not found" (trying it on a raspbery pi 5 with the raspbian OS with LCNC 2.10 pre, on this forum found the image file)

Here are some photos...

I have seen those problems. When I'll have some spare time, I'll try to fix them.

Since at this moment I have no much time I attach a text I have found recently.
Maybe the author is Fernand.
You have a standalone version of NativeCAM working, so I think you have only to made changes to embed it in LinuxCNC.
And I suppose you can run ncam from any place in the terminal simply by typing ncam.

You could follow that guide in the first 4 points to try to have NativeCAM in a LinuxCNC tab.
Remember to verify your paths.
In my case they were different respect those writtten in the guide and I had to adjust them.
One of the differences is the path:
/usr/share/pyshared/gladevcp
on my Raspberry is:
/usr/lib/python3/dists-packages/gladevcp

You can firstly verify the situation listing the directories.
If you write down the changes you make (I haven't... ) the guide could be written by you.

Regards
Giovanni