|
Hi, I'm just getting started with KiBot, trying to use v1.9.1 from a docker image. I'm only running it from docker as KiBot's documentation suggests this as the simplest way to get started. On the host side (Pop OS!), I have KiCad v9.0.9 managed by apt AND KiCad v10.0.3 (appimage). I created a very simple project in KiCad V10, to learn how to use KiBot. The project contains only three standard KiCad parts and one custom part. I faced a few issues while using it: Issue 1: The schematic pdf export is sometimes missing.
Edit: I did not manage to make it work with just "kibot --quick-start" but it does work with a custom yaml file launched using kibot -c, so that's probably not an issue as custom yaml files are likely to be always used anyways. Edit 2: upon further use I observed that the file is created but sometimes is deleted while the workflow runs, i.e., I put the sch pdf generation early in the workflow, followed by blender output. While kibot / blender generates the export files I navigate to the folder structure and open the sch pdf file, which works fine. Further down the workflow, a little longer after blender out is generated, the pdf sch disappears from the folder structure. I have not yet found what causes it. Edit 3: commenting out the reports sections seems to eliminate the disappearing pdf issue, though new error appears. New error: Issue 2: KiBot cannot generate/find the drill file:
Edit 3: there were no NPTH in the design. Adding one resolved the issue. Issue 3: KiBot fails to download 3D models After running "kibot --quick-start" on the docker, KiBot fails to load the 3D models (as expected and warned by KiBot's documentation) so it attempts to download Standard KiCad 3D models via GitLab API. Unfortunately that download fails. Messages: Some investigation on the container: And on the host: I did try using the 3d install script (/usr/bin/kicad_3d_install.sh) but it fails due to no root. I suppose the container could be launched with root permissions to run the script, however if I understand it correctly, that would not be persistent and I'd have to run the script and download the models every time. With some help from LLM's the solution to that was to download the 3d models on the host with following additions to launcher script: My full launcher script is then: |
Hi @FLRHW !
Issue 1 should be fixed by a6bbf4a
This problem was found only in the current development code, thanks for reporting.