Advanced Search

the on screen button and physical button cannot remain synchronized as the screen cannot physically change the mushroom buttons state. so you will need to add in some hal NOT allowing the UI estop button in probe basic to be in a state different from the physical mushroom button.

github.com/LinuxCNC/linuxcnc/issues/3717

(No solution yet)

You could quickly check if those have the desired affect by opening halshow, opening the "watch" tab and picking those pins from the tree. Then you can set values directly.

If that works then link them up in HAL.

One advantage of the Pi is that it is perfectly reasonable to have an identical spare to swap in in case of trouble.

This feels like possibly a race condition, I wonder what happens if the queue-empty check is just disabled?
(ie, I wonder if it indicates a real problem?)

I use gmoccapy.

So far, I have found that these two signals control the feed rate:
gmocacapy.spc-feed.value
gmocacapy.spc-speed.value

Which GUI are you using?

If this is your whole HAL file then the problem is that you have connected the HAL "net" to the VFD but not to the motion contoller.

This creates "nets" with names like "spindle" enable but there is nothing at the other "end"

Try:

The => are optional and ignored by the computer.

linuxcnc.org/docs/stable/html/man/man9/m....html#SPINDLE%20PINS

Sorry, I must have got distracted when changing the variable name and didn't finish changing every occurrence. The bug has been squashed.

JT

I have sent a query about how it interfaces. If it is USB HID then it will probably work fine with hal_input. Otherwise it might need a specific driver.

Hi,

dein Fehler könnte möglicherweise noch eine weitere Ursache haben.
Da dies beim abbremsen und hohen Geschwindigkeiten passiert, kann es sein, dass dein Servotreiber die überschüssige Generatorenergie 
vom Servomotor nicht wegbekommt und sich dabei der Zwischenkreis entläd.
Hast du Bremswiederstände installiert?

Hi,
I have a question about the configuration of the XHC WHB04B-06.
I already asked this question in the German forum but unfortunately did not receive an answer.
First of all, the handwheel works perfectly except for the rotary knob button.
Here I can only set the increments. But I also want to control the feed rates.

I think the settings need to be adjusted here:

# GUI feed rate related signals can be used when program is running moving GUI slider
net pdnt.feed-override.scale whb.halui.feed-override.scale halui.feed-override.scale # needed for both FeedOverride+/- and rotary knob button
net pdnt.max-velocity.value whb.halui.max-velocity.value halui.max-velocity.value # needed for Mpg mode : button feed position% * max-velocity = Mpg feedrate

# take feed override min/max values from/to the GUI
net pdnt.feed-override.value halui.feed-override.value whb.halui.feed-override.value # GUI feed rate related signals
net pdnt.feed-override.increase whb.halui.feed-override.increase halui.feed-override.increase
net pdnt.feed-override.decrease whb.halui.feed-override.decrease halui.feed-override.decrease


I just don't know which ones?
 

After a break, when running my machine, i can load a gcode file. But trying reload or edit crashes with following error:
 

Hi, I have now made some changes and am not experiencing any more problems for the time being.
1. I had Ethercat running on two network cards.
I have now combined them into one card and made sure that it has an Intel chip.
2. I have made the following changes in ethercat.xml: 
appTimePeriod="1000000" >>> appTimePeriod="2000000"
sync0Shift=“25000” >>> sync0Shift="50000"
Since then, the errors have disappeared and the servos are ready immediately.
3. I have attached ferrite cores to the Ethercat cables.
The ferrite cores for the servos have been ordered.

 

As I understood open loop drivers and motors are existing and are kept in the system. (for the time beeing)

It is probably difficult to answer the question. What makes a controller better (best)?

• cheap? (two parallel ports (PCIe cards) in old office PC)
• least amount of re-wiring? (existing parallel port machine?)
• cheaper? (but not a bit of documentation) ( FPGA cards of unknown origin)
• Is wasted time cheaper than money spent?
• easy to set up? ( pnc config)
• upgradable? (linear scales, tool changer, rigid tapping, closed loop positioning, linear motors)
  
  I used an old parallel port machine, changing form mach3 to LinuxCNC was 90% figuring the "charge pump" out (no re-wiring, all in software), then the computer quit service and the replacement had no parallel port. (a 10$ PCIe card fixed that). 
  Having problems to get an encoder running a Mesa card (6i25 with daughter card) went into the machine. (solving the spindle encoder issue)   (it still is a Frankenstein mixed Mesa and Parallel port). 
  
  Greetings Timo 
  
  p.s. the UC300ETH is that working with linuxcnc? Some older threads stated it does not work.
  forum.linuxcnc.org/27-driver-boards/2982...moothstepper-to-mesa