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

Why i cant import the json file. It said cannot find SW1 footprint #8

Open
galihpd opened this issue Sep 15, 2023 · 8 comments
Open

Comments

@galihpd
Copy link

galihpd commented Sep 15, 2023

No description provided.

@zykrah
Copy link
Owner

zykrah commented Sep 16, 2023

You'll have to provide more information, the json would be a good start.

@galihpd
Copy link
Author

galihpd commented Sep 16, 2023

keyboard-layout.txt
im a 3D artist, i dont have that such knowledge in electronics. and i dont use this tools for printing real pcb, i just wanna take the 3D model and bring it to my 3D project. thank you for your support

@zykrah
Copy link
Owner

zykrah commented Sep 16, 2023

No problem, could you also share a screenshot of your schematic? Also, another thing you should keep in mind is that you need to update PCB from schematic (ie have the footprints actually in the pcb editor when you run the script)

@nitInundate
Copy link

I'm experiencing a similar issue. I aligned the initial components and run the plugin, however, I also get the same "Cannot find footprint SW1" error.
Here is the error pop-up.
image

as well as the json file.
keyboard-layout.json

The references were sourced from Joe Scotto's repositories.
https://github.com/joe-scotto/scottokeebs/tree/main/Extras/ScottoKicad

Apologies as I can't read on what's causing the issue.

@zykrah
Copy link
Owner

zykrah commented Jan 25, 2024

Did you import the footprints into the pcb editor (update PCB from schematic) before you ran the script? the footprints need to be in the actual PCB editor when you run the script

@nitInundate
Copy link

Ah I did. Turns out, the problem was occuring within the annotations.
A workaround I used is to set the "SW{}" from the plugin to only "S{}". I still get an error, however, after exiting out of the error dialogue, the footprints are configured properly. I know that with that method there would be two "S{}" annotations for both the switches and stabilizers, I assume they would interfere.
My guess is that the assets's annotations that I'm using are not compatible with the plugin.

@zykrah
Copy link
Owner

zykrah commented Jan 28, 2024

You can always use the same library as i did, marbastlib. otherwise there might be a way to change the references of the library you're using

@RivasMario
Copy link

Had this issue today, completed placement by changing SW{} to MX{}. Have latest marpatlib plugin, following Noah Kisers TKL build. Seems like just a naming convention change.

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

No branches or pull requests

4 participants