I have a Shapeoko 3 XXXL ( XL and XXL y axis rails combined for extra length) I was running Carbide create and Carbide motion from several years ago because they always seemed to work. Recently I wanted to use some of the new features of Carbide create (circular array feature) so I upgraded both. With a little research I was able to find out what number in the shapeoko.json file to change for the extra Y axis movement. The machine seems to work fine except that when it starts the router it seems to "pulse like it is being turned on and off rapidly. The router is connected to a solid state relay that is activated by the controller so it’s like that output is pulsing? I connected the router directly to a power strip and turned it on manually and ran a program fine. Tech support told me to go back to the old program because of the extra Y axis length but I don’t know what version I was using and don’t know how far back I need to go for this to work again? Has anyone else run into this? Is it in the gcode or the controller since I upgraded both? Tonight I plan to try an old gcode program that worked to see if it’s in the gcode. I can also try to redo the configuration and not modify the length to rule that out.
Sounds like you need a little something more between the controller & relay that buffers/filters the PWM signal from the controller to a steadier voltage level that keeps the relay continuously ON.
Wait. Did “Tech” say how the extra Y axis length can affect how the router is turned on?
I can’t think of any way that could happen thru software. I think your router brushes are going out and it’s just coincidental timing.
it’s not the router since I can plug the router in another outlet that isn’t switched and it runs fine
With some testing last night I found that it’s how the controller handles the spindle on command M03. The command M03S18000 should turn the spindle on clockwise and at 18,000 RPM since I don’t have a VFD it should just turn the spindle on and in the past it has I looked at some old programs that worked and had the code M03S18000. Working with the new code I changed it to M03S10000 and it got worse making it more obvious that it is being turned on and off. I changed the code to M03S30000 and it runs fine so I need to find out what is needed to get the controller to handle that the same. A possible work around would be to always change the code (not ideal) or change the speed of all the tools to 30,000 RPM if that can be done? does anyone know if 30,000 is actually the max?
Interesting. I’ve used both the iot relays and C3D’s BitRunner and neither exhibited that behavior. I wonder what’s in the specs for that relay that require that.
Sorry no explanation for ya, but my observations.
This topic was automatically closed after 30 days. New replies are no longer allowed.