-
Notifications
You must be signed in to change notification settings - Fork 12
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
GUI - Mounting holes incorrect in output. #63
Comments
Hi @algocrypto, Before installing the new version make sure to remove the one installed via Package Manager. The update possibly solves also #64 |
Hi @cooked , |
Hi @cooked , Thank you for the quick updates. I have tried both manual and package manager installation, and I still getting the old GUI, please see the attached screeshot I have tried to restart KiCAD and reinstall, but same results. It looks like the kimotor_gui is not updated on github, I only see the update done on kimotor_action.py file on guthub |
Hi Stefano,
Thank you for the quick updates.
I have tried all the below recommendations, but I am still having the old GUI.
Please refer to the attached screenshots.
It looks like the GUI file on GitHub is not updated, it is still showing the last update was 5 months ago.
Kindly let me know if you need any more information to help fix these issues?
Once again thank you and best regards,
Sanjay
[Screenshot 2024-03-31 at 9.28.16 AM.png]
… On Mar 31, 2024, at 8:32 AM, Stefano Cottafavi ***@***.***> wrote:
mmm... it looks like kicad is still using the old version. the GUI in the new one is slightly different (see below)
try to (and/or):
- restart kicad
- refresh plugins (in PCB editor navigate to Tools > External Plugins > Refresh Plugins )
- check in the package manager local folder if the old plugin is really gone
- make sure that you cloned the repo to the proper kicad version folder (in the README this is 7.0 but if you are on 8.0 that is where you have to clone the repo to)
PS: in the meantime I also pushed a new version of Kimotor to the package manager... maybe you can give that I try first
[image.png (view on web)](https://github.com/cooked/kimotor/assets/1381353/98039910-6c0b-4828-b235-36c4f66341fb)
—
Reply to this email directly, [view it on GitHub](#63 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AWPG322EO5KDF3B2HPGIQ43Y3AUCLAVCNFSM6AAAAABFNPQG2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYG44TQOJVG4).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hi @algocrypto, I've hopefully fixed the code to allow for any MH count when "Circle" outline is selected. This might bring up new issues, where you have to pay attention that the MH generated do not overlap with motor terminal (that was the reason to have them fixed to 6 before). As a side note, in case you want to try other outline geometries, keep in mind that:
Let me know if that works for you. |
Thank you @cooked for the update, the new GUI seems to be working for me now and I am able to get desired MH. |
Hi @algocrypto
Default workflow for me is to select DRC rules as Kimotor PCB preset and in Kicad's Board Setup > Design rules > Constraints input all the geometrical parameters I want. If those match the JLCPCB requirements then the PCB motor should be compliant too. Note that there might still be warnings related to silkscreen. For the time being I suggest you to move text around manually, if needed. looking fwd to your feedback |
Awesome, Thank you @cooked , Let me check it out today and get back to you. I hope to complete the Stator design soon since it is delayed for long time and I am eager to test the new Axial Flux generator. |
Thank you @cooked , The DRC - Annular width error is resolved for me..I have submitted the PCB stator design to JLCPCB for review, I will let you know if there is any other issue. I really Appreciate your help and support to the community. |
Hello,
It seems that the mounting holes paramater is not working on GUI, if I select 5 holes or any number of holes, the output is always 6 holes.
Please refer to the attached screenshot.
Am I missing something or does this look like a bug?
Cheers!!
The text was updated successfully, but these errors were encountered: