Advanced Search

Hi all,
I’d like to share a set of programs for automatically generating LinuxCNC configuration files for EtherCAT setups.

Github repository contains:

1. XML generator
2. HAL generator
3. INI generator
4. DOS-style to UNIX line ending converter
5. Example configuration for XYZ
6. Example configuration for XYYZ

github.com/szolkaa/Automatic-linuxcnc-co...rators-for-ethercat/

Hat sich erledigt.
Hatte die Frage auch im Englischen Forum gestellt und letztendlich eine Lösung gefunden.
XHC-WHB04B-06 rotary knob button feed rate not work

Ich bin gerade den Thread nochmal durchgegangen:

Zitat:
Folgendes Problem nervt mich gerade: Ich verfahre per Handrad die X Achse, tw mit vollem G0=7,5m/min, das läuft gut, aber beim Bremsen aus Feeds ab 4m/min kommt fast immer der Fehler motor-0-position error. Auf allen Achsen kommt dieser Fehler.
Ich habe 400W Servos von OMC Stepperonline, die autark ihre Rampen steuern, LCNC bekommt davon nichts mit, die sehen für LCNC ja aus wie Stepper. Keine Glasmaßsstäbe/Encoder zusätzlich.

Ich habe da so einen Verdacht.
Werfe mal Halscope an und beobachte die actual-position, target-position und den Schleppfehler.
Zusatzfrage: Hast du irgendwelche Einstellungen an den Stepperonline vorgenommen? 
 

I have found a solution that works for me.
After wasting a week with Mux trying to build something with 6 input pins + enable, I have now decided on a different approach. Since the rotary control does not have a direct output for the feed, I am tapping the signal from whb.axis.a.jog-scale. Now I just had to convert the value with div2 for jog, feed, and rapid.

Check out Beremiz (beremiz.org).
I equipped it with a HAL interface. Works well with LinuxCNC.
runs under Linux and is open source.

I have upgraded my linuxcnc 2.9.8 on rpi4 bookworm to 2.10pre. After installation estop_latch is not working. It was working as it is on 2.9.8. I can see estop_latch.ok-in = true, estop_latch.reset = true,  estop_latch.fault-in = false etc all good but estop_latch.ok-out never comes true.

My config for estop_latch

    loadrt estop_latch names=estop_latch
    addf estop_latch servo-thread
        
# estop loopback, SPI comms enable and feedback
    net user-enable-out     <= iocontrol.0.user-enable-out        => remora.SPI-enable 
    net remora-status      remora.SPI-status     => estop_latch.ok-in
    net estop-fault_in remora.input.09 => estop_latch.fault-in
    net user-request-enable <= iocontrol.0.user-request-enable    => remora.SPI-reset estop_latch.reset
    net estop-status estop_latch.ok-out => iocontrol.0.emc-enable-in    

But If I dont use estop_latch machine works.

    net user-enable-out     <= iocontrol.0.user-enable-out        => remora.SPI-enable
    net user-request-enable <= iocontrol.0.user-request-enable    => remora.SPI-reset
    net remora-status     <= remora.SPI-status     => iocontrol.0.emc-enable-in

estop_latch was working in 2.9.8 with same config.

setp     wj200-vfd.00.update-hz               0.1

Means you would  get 1 packet every 10 seconds
(so a 2 in 20 seconds)
 

what version of probe basic? how did you install it and when did you install it?

some good reads on edm p/s
langfordw.pages.cba.mit.edu/desktopWEDM/electronics/
github.com/Bijoo/EDM-pulse-generator
oshwlab.com/ehdesignlabs/wire-edm
the G-EDM project looks good
there have been a few updates/chgs to design
Usimg an inductor is reminiscent of the Charmilles P25
github.com/G-EDM

tomp

After some more studying, I realise that the mux2 doesn't have an output.
Not sure even now I have done that correctly.
I think I am now closer. After issuing M19 R45, the mux switches, but the spindle-output  isn't being populated.
Odd as the spindle still runs with M3 command. 

 

you can use the cheap 5Axis-BOB's

 

Firmware: 5ABOBx2D

Hey Guys,
this is Stephan from Germany. A 39 years old HW/SW Engineer without any clue about LinuxCNC.
I retrofitted my old Gravorgraph VX92 with a Mesa 7i96s and a Vdf Omron MX2 ( similar to Hitachi WJ200).
LinuxCNC was working with some USB/RJ485 Dongle, and i was able to run my Vdf without any issues.
Thank you for all these comments in this message board. Without your help with other peopleś issues, I would still have to operate my milling machine by hand.

I tried to connect my Vdf without these ModBus USB-Dongle and connected it to the Vdf.
After wasting days to get it running, i decided to write my first question in a forum.

I took my oscilloscope to measure the output of the mesa 7i96s (modbus_mesa.png, not connected with the Vdf this time).
The signal looks pretty fine, but compare to the USB/RJ485 Dongle signal (modbus_USB.png),
I saw only a few packages every 20 seconds.
The Signal of my USB/RJ485 was running every ~10ms (not connected with the Vdf either).

HAL:
#

---

SPINDLE <--->  MODBUS <---> MESACard
loadrt   wj200-vfd ports=hm2_7i96s.0.pktuart.0
addf     wj200-vfd.00 servo-thread

setp     wj200-vfd.00.address                  1
setp     wj200-vfd.00.baudrate                9600
setp     wj200-vfd.00.parity                      0
setp     wj200-vfd.00.update-hz               0.1
[...]

mod file:
/*
The format of the channel descriptors is:

{TYPE, FUNC, ADDR, COUNT, pin_name}

TYPE is one of HAL_BIT, HAL_FLOAT, HAL_S32, HAL_U32
FUNC = 1, 2, 3, 4, 5, 6, 15, 16 - Modbus commands
COUNT = number of coils/registers to read
*/

#define MAX_MSG_LEN 16   // may be increased if necessary to max 251

static const hm2_modbus_chan_descriptor_t channels[] = {
/*  {TYPE,     FUNC, ADDR,   COUNT, pin_name} */

    {HAL_BIT,   5,   0x0001,    1,  "run"},
    {HAL_BIT,   5,   0x0002,    1,  "reverse"},
    {HAL_BIT,   1,   0x0014,    1,  "is-at-speed"},
    {HAL_BIT,   1,   0x000F,    1,  "is-running"},
    {HAL_BIT,   1,   0x0018,    1,  "watchdog-out"},
    {HAL_FLOAT, 3,   0x1003,    1,  "motor-current"},
    {HAL_FLOAT, 3,   0x1019,    1,  "heatsink-temp"},
    {HAL_FLOAT, 6,   0x0001,    1,  "commanded-frequency"},
};




Does anyone knows these issue ?
Thank you so much !

Best Regards, 
Stephan
 

Testing on current 2.9.8 with the G0 move commented give me this, which is not quite correct but it's not as wrong as what you got:

 

yes you need to write an XML file now

has anybody build hardware to mesa 7i92 board, how has made all input optocoupler board and output safety wiring to stepper drivers, i think if can build own output safe board to connection port 1 and all input pin optocoupler board connection 2, and were found bit file were have all output at connector 1 and all input have at connector 2, then have logical perfect all in/out pins configured.