ECMO VMC100 Retrofit with Carousel/Toolchanger
- andypugh
-
- Offline
- Moderator
-
Less
More
- Posts: 21213
- Thank you received: 4663
03 Aug 2025 19:56 #332757
by andypugh
Replied by andypugh on topic ECMO VMC100 Retrofit with Carousel/Toolchanger
You need to "addf" carousel.0 too.
Please Log in or Create an account to join the conversation.
- hitchhiker
- Offline
- Elite Member
-
Less
More
- Posts: 210
- Thank you received: 17
13 Aug 2025 15:35 #333342
by hitchhiker
Replied by hitchhiker on topic ECMO VMC100 Retrofit with Carousel/Toolchanger
sry for delay.
i have now the whole machine running with the original controller.
all works.. steppers,maindrive, all sensors and the spindleencoder.
in the next days i link up my raspberry pi 4 with a 7i92.
why the rasp? its easier for me instead a notebook.. i have the machine in my garage not in my basement...
if all works and linked to the mesa and is in my linuxcnc i came back.
parallel i would build a small model for the toolchanger to play in the apartment with the toolchanger carousel stuff.
thanks
i have now the whole machine running with the original controller.
all works.. steppers,maindrive, all sensors and the spindleencoder.
in the next days i link up my raspberry pi 4 with a 7i92.
why the rasp? its easier for me instead a notebook.. i have the machine in my garage not in my basement...
if all works and linked to the mesa and is in my linuxcnc i came back.
parallel i would build a small model for the toolchanger to play in the apartment with the toolchanger carousel stuff.
thanks
Please Log in or Create an account to join the conversation.
- hitchhiker
- Offline
- Elite Member
-
Less
More
- Posts: 210
- Thank you received: 17
28 Aug 2025 18:35 #334055
by hitchhiker
Replied by hitchhiker on topic ECMO VMC100 Retrofit with Carousel/Toolchanger
I get the carousel.comp working with the toolchanger.
It homes and couunts correct... spindle orient before lift up to the gear to dont crash.
All sensor stuff is linked in a remaped m6 ngc and communicate with m64 m65 and m66 between ngc and hal and carousel.comp.
There is a and2 fuction which gives the carousel the enable signal.
This and2 swirches when the hardware sensor gets true that tell that the carousel is in disengaged position. This means the carousel is connected with the gear to maindrive and the tool is released from the spindle sk30.
Next step is to make the stuff working with the main drive.. think its some stuff with mux2 and xor2.
The spindle is synced and can orient. Its a full servo spindle.
It homes and couunts correct... spindle orient before lift up to the gear to dont crash.
All sensor stuff is linked in a remaped m6 ngc and communicate with m64 m65 and m66 between ngc and hal and carousel.comp.
There is a and2 fuction which gives the carousel the enable signal.
This and2 swirches when the hardware sensor gets true that tell that the carousel is in disengaged position. This means the carousel is connected with the gear to maindrive and the tool is released from the spindle sk30.
Next step is to make the stuff working with the main drive.. think its some stuff with mux2 and xor2.
The spindle is synced and can orient. Its a full servo spindle.
Please Log in or Create an account to join the conversation.
- hitchhiker
- Offline
- Elite Member
-
Less
More
- Posts: 210
- Thank you received: 17
28 Aug 2025 20:15 #334060
by hitchhiker
Replied by hitchhiker on topic ECMO VMC100 Retrofit with Carousel/Toolchanger
haha.. next issue..but solved...
a second mux2 and a mult brings up the fwd and rev function to the spindle in carousel movement. now bidirectional works...but all only on the table with buttons,switches,leds.
i was wondering why i get motor-fwd and motor-rev velocity shown only as positiv value.. then i use the motor-rev pin to use a second mux2 to select the inverted value.
the inverted value i got from mult2. i give in the carousel.0.motor-vel and multiplie with -1.
then i get the negative value...
carousel.0.motor-vel 100 with carousel.0.motor-fwd true gives 100
carousel.0.motor-vel 100 with carousel.0.motor-rev true gives -100
when carousel.0.motor-rev true then the mux2.sel is active nd sends the -100 Value to the first mux2.
first mux2 change between carousel and spindle mode.
a second mux2 and a mult brings up the fwd and rev function to the spindle in carousel movement. now bidirectional works...but all only on the table with buttons,switches,leds.
i was wondering why i get motor-fwd and motor-rev velocity shown only as positiv value.. then i use the motor-rev pin to use a second mux2 to select the inverted value.
the inverted value i got from mult2. i give in the carousel.0.motor-vel and multiplie with -1.
then i get the negative value...
carousel.0.motor-vel 100 with carousel.0.motor-fwd true gives 100
carousel.0.motor-vel 100 with carousel.0.motor-rev true gives -100
when carousel.0.motor-rev true then the mux2.sel is active nd sends the -100 Value to the first mux2.
first mux2 change between carousel and spindle mode.
The following user(s) said Thank You: tommylight
Please Log in or Create an account to join the conversation.
- andypugh
-
- Offline
- Moderator
-
Less
More
- Posts: 21213
- Thank you received: 4663
29 Aug 2025 19:30 #334108
by andypugh
Replied by andypugh on topic ECMO VMC100 Retrofit with Carousel/Toolchanger
If you want a negative number for reverse operation, then just set the rev-dc pin to a negative number.
github.com/LinuxCNC/linuxcnc/blob/master...s/carousel.comp#L366
github.com/LinuxCNC/linuxcnc/blob/master...s/carousel.comp#L366
Please Log in or Create an account to join the conversation.
- hitchhiker
- Offline
- Elite Member
-
Less
More
- Posts: 210
- Thank you received: 17
09 Sep 2025 12:23 #334686
by hitchhiker
Replied by hitchhiker on topic ECMO VMC100 Retrofit with Carousel/Toolchanger
Hi andy
Yes i change the stuff from rev-dc 100 to -100... it works.
Still struggle with issues. Possible i can get help from u?
Today i look to the 3 signals from the proximity sensors.. found out that there are some spikes.. but the spikes are only a noise on the signal.. not in the area that they toggle the gpio.
I think my ngc is the issue.
Later i add some debug lines to see where it stops working.
I am xonfused about the strobe pin.. and dont understand the usage.
I use sense0 as index for homing and sense1 for the slot sensor on the slottee disc.
Some time ago you wrote i must use the strobe for the slot disc. But dont understand it correct. Can you please explain a little more please?
Thanks
Yes i change the stuff from rev-dc 100 to -100... it works.
Still struggle with issues. Possible i can get help from u?
Today i look to the 3 signals from the proximity sensors.. found out that there are some spikes.. but the spikes are only a noise on the signal.. not in the area that they toggle the gpio.
I think my ngc is the issue.
Later i add some debug lines to see where it stops working.
I am xonfused about the strobe pin.. and dont understand the usage.
I use sense0 as index for homing and sense1 for the slot sensor on the slottee disc.
Some time ago you wrote i must use the strobe for the slot disc. But dont understand it correct. Can you please explain a little more please?
Thanks
Please Log in or Create an account to join the conversation.
- andypugh
-
- Offline
- Moderator
-
Less
More
- Posts: 21213
- Thank you received: 4663
09 Sep 2025 13:16 #334695
by andypugh
Replied by andypugh on topic ECMO VMC100 Retrofit with Carousel/Toolchanger
It might be worth debouncing the proximity sensor signals in HAL. (there is a "debounce" component.
The "strobe" pin is an indication that the position inputs are valid. During positioning of a binary or gray-coded carousel there may be transient values on the inputs (caused by the sensors not all seeing new edges at the same time) that would indicate incorrect positions. The "strobe" pin is a shorter pulse that indicates that the position encoder sensors are centred on their targets and will be reporting the true position. It will also indicate that the carousel is correctly aligned on an actual pocket.
The "strobe" pin is an indication that the position inputs are valid. During positioning of a binary or gray-coded carousel there may be transient values on the inputs (caused by the sensors not all seeing new edges at the same time) that would indicate incorrect positions. The "strobe" pin is a shorter pulse that indicates that the position encoder sensors are centred on their targets and will be reporting the true position. It will also indicate that the carousel is correctly aligned on an actual pocket.
Please Log in or Create an account to join the conversation.
- hitchhiker
- Offline
- Elite Member
-
Less
More
- Posts: 210
- Thank you received: 17
09 Sep 2025 13:20 #334696
by hitchhiker
Replied by hitchhiker on topic ECMO VMC100 Retrofit with Carousel/Toolchanger
i had debounce the proxmitiy sensors in the HAL with debounce.. value is 5.
then i think we need to talk about my toolchange.ngc.
do you want it in english or german... because i wrote all comments in german).
thanks andy
then i think we need to talk about my toolchange.ngc.
do you want it in english or german... because i wrote all comments in german).
thanks andy
Please Log in or Create an account to join the conversation.
- andypugh
-
- Offline
- Moderator
-
Less
More
- Posts: 21213
- Thank you received: 4663
09 Sep 2025 13:31 #334697
by andypugh
Replied by andypugh on topic ECMO VMC100 Retrofit with Carousel/Toolchanger
Ich kann Deutsch lesen
Please Log in or Create an account to join the conversation.
- hitchhiker
- Offline
- Elite Member
-
Less
More
- Posts: 210
- Thank you received: 17
09 Sep 2025 13:39 - 10 Sep 2025 20:03 #334698
by hitchhiker
Replied by hitchhiker on topic ECMO VMC100 Retrofit with Carousel/Toolchanger
Failures in ngc.. i delete
Last edit: 10 Sep 2025 20:03 by hitchhiker. Reason: Dont want people bring to bad files
Please Log in or Create an account to join the conversation.
Moderators: piasdom
Time to create page: 0.093 seconds