New ethercat / probe basic control for minimonster

Hakan wrote:

A lot of pins starting with spindle.0 should be created. Check in halshow.

Those were already there as I said before. no change. They are read only though so I don't know how they get used to turn the spindle on and off.

Thanks

Component Pins:
Owner   Type  Dir         Value  Name
    29  s32   OUT          2540  motion-command-handler.time
    29  s32   OUT         34125  motion-controller.time
    29  float IN              1  motion.adaptive-feed
    29  float IN              0  motion.analog-in-00
    29  float IN              0  motion.analog-in-01
    29  float IN              0  motion.analog-in-02
    29  float IN              0  motion.analog-in-03
    29  float OUT             0  motion.analog-out-00
    29  float OUT             0  motion.analog-out-01
    29  float OUT             0  motion.analog-out-02
    29  float OUT             0  motion.analog-out-03
    29  bit   OUT         FALSE  motion.coord-error
    29  bit   OUT         FALSE  motion.coord-mode
    29  float OUT             0  motion.current-vel
    29  bit   IN          FALSE  motion.digital-in-00
    29  bit   IN          FALSE  motion.digital-in-01
    29  bit   IN          FALSE  motion.digital-in-02
    29  bit   IN          FALSE  motion.digital-in-03
    29  bit   OUT         FALSE  motion.digital-out-00
    29  bit   OUT         FALSE  motion.digital-out-01
    29  bit   OUT         FALSE  motion.digital-out-02
    29  bit   OUT         FALSE  motion.digital-out-03
    29  float OUT             0  motion.distance-to-go
    29  bit   IN           TRUE  motion.enable
    29  bit   OUT         FALSE  motion.eoffset-active
    29  bit   OUT         FALSE  motion.eoffset-limited
    29  bit   IN          FALSE  motion.feed-hold
    29  float OUT             0  motion.feed-inches-per-minute
    29  float OUT             0  motion.feed-inches-per-second
    29  bit   IN          FALSE  motion.feed-inhibit
    29  float OUT             0  motion.feed-mm-per-minute
    29  float OUT             0  motion.feed-mm-per-second
    29  float OUT             0  motion.feed-upm
    29  bit   IN          FALSE  motion.homing-inhibit
    29  bit   OUT          TRUE  motion.in-position
    29  bit   OUT         FALSE  motion.is-all-homed
    29  bit   IN          FALSE  motion.jog-inhibit
    29  bit   OUT         FALSE  motion.jog-is-active
    29  bit   IN          FALSE  motion.jog-stop
    29  bit   IN          FALSE  motion.jog-stop-immediate
    29  bit   OUT         FALSE  motion.motion-enabled
    29  s32   OUT             0  motion.motion-type
    29  bit   OUT         FALSE  motion.on-soft-limit
    29  bit   IN          FALSE  motion.probe-input
    29  s32   OUT             0  motion.program-line
    29  float OUT             0  motion.requested-vel
    29  u32   OUT    0x002CA523  motion.servo.last-period
    29  bit   OUT         FALSE  motion.teleop-mode
    29  float OUT             0  motion.tooloffset.a
    29  float OUT             0  motion.tooloffset.b
    29  float OUT             0  motion.tooloffset.c
    29  float OUT             0  motion.tooloffset.u
    29  float OUT             0  motion.tooloffset.v
    29  float OUT             0  motion.tooloffset.w
    29  float OUT             0  motion.tooloffset.x
    29  float OUT             0  motion.tooloffset.y
    29  float OUT             0  motion.tooloffset.z
    29  bit   OUT         FALSE  motion.tp-reverse

Misunderstood you there.
Which one to start with?
 

I'm lost now. haha
All those spindle.0 pins have been there from the beginning. They are all read only so I cant connect them to for example my mb2hal pins.

The only thing I am trying to do is to have m3/m5 run my spindle.

From halshow i can directly set the pins to turn the spindle on. Now I just need whatever commands m3/m5 in the ui/gcode to change those.

When I typo M3 S3000 in the mdi I do not see any hal pins in halshow change at all. So I assume that means m3 is not connected to anything yet... OR, I'm missing something.

I don't think you have set the spindle at speed pin anywhere......

Clues.... so i have now connected (i expect) the spindle correctly, it was actually connected before, however that is done, my ethercat drives wig out and repeatedly cycle on and off.

Hmmmm. So there is a conflict with the spindle.0 pins.

Apparently the net naming was conflicting with the ethercat naming. renamed and now its fine. had to mess with the spindle scaling but now its perfect.

So ultimately in my custom.hal the pins were simply not connecting the to the spindle.0 commands, and the names had to be changed so they didnt conflict with ethercat.

So chatgpt DID get it right, it just didnt not know (how) to resolve the conflict and went on a bizarre hallucination.

Thanks guys, I think at the end of it I actually understand this all now, and am not just slapping random code in going "why's it borked?"