-
I generate qr code externally and convert it to footprint before running KiBot. But then I run KiBot I get the old footprint in all the renders. Is there a way to refresh a particular footprint before every run? |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 2 replies
-
Hi @dariuskt ! |
Beta Was this translation helpful? Give feedback.
-
Well, I tried qr_lib but had a few problems with it. at first, I couldn't get it to make just a single kicad_mod file without directories. giving it output as a filename made a file that kicad6 complained about syntax errors, and after all this enabling update_qr just crashed KiBot every time with a Python error. At this point, I thought there surely must be a better way to update a footprint from the library as QR generating outside KiBot gives me more flexibility (I embed my logo in the QR code). As for modifying pcb, I think fill_zones does that as well, so I see no problem having the option to update a footprint. Maybe footprint update ability could be exposed somehow independently from the qr_lib? This topic kinda unintentionally turned into a feature request ;) As you didn't mention a way to update the footprint independently I assume there is no way to do that. |
Beta Was this translation helpful? Give feedback.
-
If you don't report problems they won't get fixed ...
The qr_lib output is covered by tests, so it works for at least one case. If you have a case where it fails just report it.
Don't you think other people could also need it? KiBot grows from suggestions to solve problems for projects.
Yes. But I think fixing/extending qr_lib is the way to go.
You are right. |
Beta Was this translation helpful? Give feedback.
-
About reporting problems, I'm fairly new to KiCad and all the plugins and KiBot, so I don't have a reasonable understanding of which part belongs to what. So I have no idea is that integration problem or is it upstream lib problem or most likely my configuration problem. If you care to see I could prepare a demo project with easily reproducible problem I experienced. About extending qr_lib, that definitely would be great, but at some point, qr_lib might be not the right name :D my current use case could be addressed by:
|
Beta Was this translation helpful? Give feedback.
-
Yes, please create a project. If you can do it in a repo better. |
Beta Was this translation helpful? Give feedback.
-
I made a repo to better illustrate what I'm talking about. I include my naive attempts which might be rectified in the documentation or some higher-level error messages. https://github.com/dariuskt/tmp-qr_lib/tree/minimal_config looks like all my problems arise from attempts to generate only footprint without symbol and place that footprint in the directory I want without any extra directories. looking forward to your thoughts on this. |
Beta Was this translation helpful? Give feedback.
-
I'm glad we achieved improvement ;)
So with this tool and configuration being so rigid, it would be pretty hard to use in my case.
Instead I just
In my setup looks like only |
Beta Was this translation helpful? Give feedback.
-
Why?
Why?
Why?
Why? Again: you are forcing a workflow that is too complicated.
I think this could be just part of the current qr_lib output.
You don't need separated runs, you don't need to move files and you don't need to remove files. Just add the preflight and add the generated libs to your project. And yes, you'll need to run KiBot at least once to get the first QR. |
Beta Was this translation helpful? Give feedback.
-
Now we have |
Beta Was this translation helpful? Give feedback.
Now we have
update_footprint
preflight.