Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New control frames #1577

Closed
wants to merge 13 commits into from
Closed

Conversation

rschell
Copy link
Contributor

@rschell rschell commented Mar 23, 2021

PR for Issue #1572.

Here are two new control frames, both using slider controls to adjust the step size or step rate. The first commit adds fixed step size sliders for the Z and XY axes. The second commit adds a continuous control frame using a single slider to adjust the step rate for all three axes. Either or both can replace the current control frame by making the appropriate selection in the bCNC startup files.

No pride of authorship here, take it if you like it, adjust it or I'm happy to make any suggested changes.

Ron

@blayno
Copy link

blayno commented Aug 12, 2021

This is the idea i was looking for, well done, how do i install your code ?

@rschell
Copy link
Contributor Author

rschell commented Aug 20, 2021

This is the idea i was looking for, well done, how do i install your code ?

If you down load the code from my fork rschell/bCNC using the New_Control_Frames branch, you will be using the code that I have been running on my raspberry Pi based machine.

@blayno
Copy link

blayno commented Aug 21, 2021

Thank you. I really like the features you have implemented, brilliant work

@bosd
Copy link
Contributor

bosd commented Jul 4, 2022

@rschell Thanks for your work. Could you attend to the codefactor issues?

@rschell
Copy link
Contributor Author

rschell commented Jul 7, 2022

Happy to, if there is a plan to merge the branch

@bosd
Copy link
Contributor

bosd commented Aug 26, 2022

Just simple GUI test here. Is it on purpose to show all new control frames as default?
On some screens we might run into insufficient screenspace.

image

@@ -8,6 +8,8 @@
import time
import Utils

OV_JOG_CANCEL = chr(0x85)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you remove the extra spaces here. To silence codefactor.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already fixed in my local version, need to push the change

@bosd
Copy link
Contributor

bosd commented Aug 26, 2022

Testing this code..
Pressing a button in continieus control results in:

Traceback (most recent call last):
  File "D:\Users\user\AppData\Local\Programs\Python\Python310\lib\site-packages\bCNC\Utils.py", line 526, in __call__
    return self.func(*args)
  File "D:\Users\user\AppData\Local\Programs\Python\Python310\lib\site-packages\bCNC\ControlPage.py", line 1985, in jogcancel
    self.app.mcontrol.cjogcancel()
  File "D:\Users\user\AppData\Local\Programs\Python\Python310\lib\site-packages\bCNC\controllers\GRBL1.py", line 49, in cjogcancel
    self.master.serial_write(OV_JOG_CANCEL)
  File "D:\Users\user\AppData\Local\Programs\Python\Python310\lib\site-packages\bCNC\Sender.py", line 479, in serial_write
    ret = self.serial.write(data.encode())
AttributeError: 'NoneType' object has no attribute 'write'

@rschell
Copy link
Contributor Author

rschell commented Aug 26, 2022

Just simple GUI test here. Is it on purpose to show all new control frames as default? On some screens we might run into insufficient screenspace.

image

I didn't want to presumptuous that my controls were better so I just added them.

two options.

  • One can edit the .bCNC file and adjust the control.page entries to your preference.
  • click on the blue titles of the control frames to collapse (minimize) them
    bCNC_control frames

Been contemplating a more interactive method of selecting the desired frames on the left.

@rschell
Copy link
Contributor Author

rschell commented Aug 26, 2022

It appears you were not connected to the grbl controller, I get this error too when disconnected. Will look into trapping this condition. It is a more generic issue than the continuous control frame.

Could add to bCNC/Sender.py serial_write routine:

        if self.serial is None:
            print("Serial Write ignored - Not connected to controller")
            return False

@Git-Bruno
Copy link
Contributor

FYI, I had to change spaces to tabs in Sender.py lines 472-474 to get your fork running.

@rschell
Copy link
Contributor Author

rschell commented Aug 30, 2022

FYI, I had to change spaces to tabs in Sender.py lines 472-474 to get your fork running.

sorry, dealing with two versions one with tabs and one without. Editor defaults to inserting 4 spaces.

@bosd
Copy link
Contributor

bosd commented Sep 1, 2022

FYI the codefactor PR is merged now.
So the version with spaces can be used.

@rschell rschell closed this Sep 2, 2022
@rschell rschell deleted the New_Control_Frames branch September 21, 2022 23:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants