You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to cirqwizard
Hi all,
I am running the Cirqoid Machine with firmware 0.3.2 and on CirqWizard 2.0 and am noticing an issue of the isolation milling getting stuck in random locations.
The mill will still be spinning but won't be moving in any direction, and is against the copper board. I try and force stop the machine, which does stop the bit from spinning. But then after that if I release the force stop it starts right back up with the spinning. I also cannot control the machine by trying to home it or manually move the location. The only way I can get the machine out of this issue is by unplugging the power and and restarting the cirqwizard software.
Is this a known bug with this software/firmware? Or is this due to some other issue, ie: exporting something incorrectly? Please let me know what you think
Thanks,
Connor
Biju Benjamin
unread,
Dec 1, 2018, 6:28:45 AM12/1/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to cirqwizard
Hi
I am also have the same issue with 0.3.2 and on CirqWizard 2.0
thanks
BIJU
Michael John Ward
unread,
Jan 24, 2019, 3:08:46 AM1/24/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to cirqwizard
I have the same issue:
Cirqoid Version 2.0.0-RC6
OS Linux Ubuntu 18.04.1 LTS (64-bit)
Machine: Intel Core 2 Duo P8400
Could it be something to do with the g-code buffer being too small, and just cutting off half of the instructions?