- Posts: 2580
- Thank you received: 0
Bug on new Install
- snowgoer540
- Offline
- Platinum Member
-
Please Log in to join the conversation.
Even after waiting for a few days, upgrading LinuxCNC via the package manager still kept us on QtPlasmaC version ending in 84. Not sure what's up with the buildbot. So I set up a Debian VM here and built a deb from source to install on cutnweld's table. The QtPlasmaC version now ends with 88 and the pause issue is resolved. Thanks again for an awesome plasma control interface.
Please Log in to join the conversation.
- snowgoer540
- Offline
- Platinum Member
-
- Posts: 2580
- Thank you received: 0
At any rate, I'm glad to hear all is well again! Sorry for any inconvenience I caused. Happy cutting!
Please Log in to join the conversation.
Please Log in to join the conversation.
- snowgoer540
- Offline
- Platinum Member
-
- Posts: 2580
- Thank you received: 0
Thankyou snowgoer, I really appreciate it. In the future, if you are ever fiddling with it, I have a few suggestions. One being the material list, it seems as tho I need to select material when going from a gcode part to conversational, instead of it simply remembering the last used cut chart, IDK if that is a bug or just the way it is.
I fired up my VM machine and tried this one, it pre-populates with whatever I had chosen on the MAIN screen. Whether or not a g-code file is loaded. I believe what you are saying, but if you could find the exact steps to reproduce it, that makes fixing it 10x easier.
2 I did have it freeze on a conversational drawn and nested part, no forward or reverse, however it may have been a conversational issue, I am not sure why it stopped in first place. It was on the last part and I was able to select and run from line then so not a big deal.
My first question is: Is this an old conversational file that perhaps you saved and run from time to time? The way we did conversational Block previously, I am not sure reverse run would have worked because it was variable based and used a lot of math, etc. I think it also used sub-routines. So reverse run may not have been possible in this instance. Before Phill stepped away from the project, he made V2 block which essentially spelled out the g-code instead of using the aforementioned method. I just tried and reverse run did work when I paused in the middle of a cut.
It did highlight a bug that I cant seem to array a circle for some reason, they all have the same origin, so I will have to take a look at that when I get some time. The other shapes seemed to array just fine.
Could you share the file you are referencing?
3 Another conversational thing, again this may not be practical to change, but if you ever rotate a part then the XY moves, say you have a part in on XY zero on bottom left corner, rotate it 90 degrees in conversational, the bottom left corner is now going to be a random -XY number. Again, not a big deal, we have used it this way several years, just FYI. If after a rotate it was bottom left XY0 that would be, well, you know! Thanks again for your efforts and for the great program!
I think it does what you're asking for. But again, without the g-code file it's tough for me to tell. I have a test file I use for a lot of things, and the origin stays the same. I put it at X0Y0, and then rotated about both Shape and Pattern, and the origin stayed at the same place. That said, how it rotates is different between Shape and Pattern. Which if you are just rotating one thing, it can be a bit confusing.
Conversational was made as a quick and dirty way to do simple things at the machine and wasn't really intended to be the end-all-be-all CAM solution. Just to temper expectations a bit, that's all; sometimes it's best to re-post the cut file from the native CAM.
All of that said, I'm happy to work through bugs and consider things like this as time allows.
Please Log in to join the conversation.
