Closed flynneva closed 3 years ago
fixes #23
Hello, I found that this is caused by the grbl version. Replace the grbl source code to 1.1. It seems that the grbl variable referenced in SIM is the name in version 1.1.
Oh ok that makes sense. Should I still keep this PR open though and bump the version number somewhere so people know which one it targets?
Oh ok that makes sense. Should I still keep this PR open though and bump the version number somewhere so people know which one it targets?
I think so. But I have another problem, I successfully compiled the SIM. How to use it to visualize the running process of grbl? I only saw the same serial palindrome interface as running on arduino. Do you have any suggestions?
How to use it to visualize the running process of grbl? I only saw the same serial palindrome interface as running on arduino. Do you have any suggestions?
once compiled there should be a grbl_sim.exe
file to execute. you can run that directly to interact with a grbl virtual device or run the shell script provided simport.sh
that runs it as a virtual device on the /tmp/ttyFAKE
interface. I updated that script also in my PR since there was a typo.
to visualize it......i think any GRBL visualization software could be directed to use that /tmp/ttyFAKE
interface and it should work. I personally love using the open builds control software and is what I use on my CNC.
i'm working a way to connect GRBL to ROS2 though to allow for more robotics integration too down the road. still a work in progress but....hey ill share it just so you know about it.