Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

KiCost GUI mode not working - Win7x64

See original GitHub issue

Use a simple and clear title.
Do not mark as “ISSUE”, “FEATURE” on title, this will be tagged by the development group.

Issue / Problem report

Add the KiCost version. Type kicost --version at terminal. KiCost 1.1.5
Add a terminal error report / txt, use --debug option on KiCost call; kicost -w -i %YOUR_FILE% --debug 8
Write the command used to call KiCost (or the graphical interface configuration); kicost
One BoM to reproduce the error (with the EDA version).

Feature / Enhancement request

Explain how it will help the other users. Hi @set-soft ,

The KiCost GUI mode not able to start, please refer the attached error report. gui_error.txt

The team thanks your contribution.

Issue Analytics

State:
Created 2 years ago
Comments:26

Top GitHub Comments

1reaction

sujitthcommented, May 30, 2021

Hi @set-soft ,

Thank you very much for resolving the issue.

0reactions

set-softcommented, May 27, 2021

Hi @sujitth !

If KitSpace is saturated it will just time-out, see #417 ,The time-out is long.

The kitspace API limit was reached and @kasbah has reset it. This debug info is from my another test file:

Sorry, I don’t follow you. This looks like KitSpace failing. Do you mean that you have a BoM that can generate it even when other BoMs are working? If this is the case please send me it by mail so I can try to find where is the problem.

I added a command line option --force_en_us please tell me if using it solves the problem.

This works now:

Ok. So now we have a workaround for systems where wxWidgets locale misserably fails. Thanks for testing it.

I have selected only 2 distributors only, what is the Local generated on the XL sheet?

This is the mechanism that allows defining your own prices. The SW1 component defines:

        <field name="manf#">RS-282G05A3-SM RT</field>
        <field name="kicost:pricing">1:0.10;10:0.03</field>
        <field name="kicost:link">http://www.xess.com</link>

So you get a Unit$ of $0,03 buying 10 parts. And the URL for the part is http://www.xess.com