- Posts: 2580
- Thank you received: 0
Jerky Jogging (QTPlasmaC)
- snowgoer540
- Topic Author
- Offline
- Platinum Member
-
In doing so, I've discovered a weird jogging (via the keyboard) issue. I posted video below, but in a nut shell, jogging becomes very jerky and erratic, for any axis. The odd thing is that jogging via the GUI jog buttons on the MAIN tab works fine, and keyboard jogging while on the PARAMETERS tab also works fine. Keyboard jogging on the MAIN tab however, does not.
It's probably also worth nothing that jogging works fine in all cases in the old AXIS gui.
Phill mentioned he took the jogging stuffs right from QTDragon (without change).
Video:
Erratic X Y:
Erratic Z:
Proof my axes do work properly :laugh: :
Any insight is appreciated; let me know if you need any more info. Thanks for the help!
Please Log in to join the conversation.
HTH
Please Log in to join the conversation.
- snowgoer540
- Topic Author
- Offline
- Platinum Member
-
- Posts: 2580
- Thank you received: 0
persei8 wrote: It sounds like EMI issues. Are the motor wires shielded? The shield should be connected to earth ground at only one end of the cable, typically the control box end. I had this issue also and solved it by going to a wireless keyboard.
HTH
I would maybe agree, however it doesn't do it in Axis GUI, also it does not do it if I am off of the MAIN tab, and on the PARAMETERS tab.
I do appreciate the suggestion though. I have a wireless keypad I can try just to be 100% sure.
Please Log in to join the conversation.
- snowgoer540
- Topic Author
- Offline
- Platinum Member
-
- Posts: 2580
- Thank you received: 0
EDIT: This error hasnt come back since, though everything behaves the same. Also, tried a wireless keyboard just for sanity sake, not that. I can see the velocity fluctuate as I jog with the keyboard.
Please Log in to join the conversation.
- tommylight
-
- Offline
- Administrator
-
- Posts: 22010
- Thank you received: 3
Oh hell, no time, but i did install Mint 19.3 so i can run QTPlasmaC, as on Mint20 it is terribly hard to get it working. I did get it working twice, now i could not after about 6 wasted hours, so i am resorting back to 19.3. As luck would have it, i still have Beagles ISO so i gave it a run last night and QTDragon works but the rest does not complaining about QT5 not being found although it is installed and working, even the editor works on Mint 20, but by now i have 6 versions of Python installed on this PC !snowgoer540 wrote: Phill has QTPlasmaC is to the point where live table testing can happen. So naturally I've been trying to break it as often as possible :laugh:
I am utterly hating the QT cr@p .. . and python is very quickly getting onto that bandwagon !
Please Log in to join the conversation.
def add_alarm(self):
pass
That didn't come out right. It should be:
Please Log in to join the conversation.
Please Log in to join the conversation.
- snowgoer540
- Topic Author
- Offline
- Platinum Member
-
- Posts: 2580
- Thank you received: 0
persei8 wrote: I just looked at that code and indeed, add_alarm is not defined anywhere, assuming your file is the same as the one in /usr/share/qtvcp/screens that comes with the linuxcnc-uspace version. I don't see what this has to do with jogging but a quick experiment is to define it and see if it makes a difference. Try adding:
def add_alarm(self):
pass
That didn't come out right. It should be:Code:def add_alarm(self, message): pass
Thank you for taking a peek!
Add it anywhere in particular in the handler file?
Please Log in to join the conversation.
- snowgoer540
- Topic Author
- Offline
- Platinum Member
-
- Posts: 2580
- Thank you received: 0
Thanks though!
Please Log in to join the conversation.
The graphics display takes a lot of processing power.
Please Log in to join the conversation.
