So it’s hard for anyone to make clear recommendations for another’s needs. You want this post in the fb group.There are many factors to consider when choosing a controller not the least of which is identifying the toolchain do you plan to use. In the smoothie firmware you can define switches to do things (gCodes) in the config file. Read the articles at /start, the z table one shows how to hook As long as you didn’t have to go into menus on a GLCD each time to get them working.Īnd as an extra bonus its preferable, almost a requirement, that the buttons are connected to the controller and not the host running Lightburn as we want to be able to jog the machine without having the computer online One option would be dedicated rotary encoders for each axis instead of buttons. Adding a GLCD where you have to click into menus and use the rotary encoder to move axis around isn’t an option. So does anyone have experience with adding physical buttons and how well it works? I figured the switch module in smoothieware has to be used as the jogging module isn’t released yet - (and compiling a new firmware with jogging just for us isn’t an option as it would mean no one but me can update the firmware in the future) If I replaced the current controller those functions would have to work on the new controller or the other makerspace members would be quite upset with me and demand that I switch back.
The current controller has physical buttons to move the X & Y axis around, set origin, move Z up and down. Thought I’d try replacing the TopWisdom controller with a Cohesion3D card as we already have one. Movement isn’t what it should be and iI’m thinking it’s related to the TopWisdom controllers stepgeneration not playing nice with the ClearpathSD servos.
We’re having issues with the RedSail laser at our makerspace.
0 kommentar(er)
