Author Topic: Altium Library footprint not found [SOLVED]  (Read 423 times)

0 Members and 1 Guest are viewing this topic.

Offline Ribster

  • Regular Contributor
  • *
  • Posts: 202
  • Country: be
  • Electronics enthousiast. Mostly on STM32
    • Ash Labs
Altium Library footprint not found [SOLVED]
« on: June 03, 2019, 10:00:25 pm »
So i'm moving my MySQL database from AD16 to AD19.

I've got my DBLib up and running, coupled and everything.
When i browse my library in components, everything comes into view. So Schematic gets rendered, Footprint also.
I've updated the components in my schematic from my library, everything imported great.

When i try to import them in the PcbDoc -> Failed to add component class.
So take im taking a look at the component itself, looking at the properties.
The footprint is coupled, id is coupled, footprint is found.
Except, when i click on the edit footprint it says that the footprint is not found.
Anyone knowing what this issue is about ?

My paths do not contain spaces.. I'm scratching my head here..
« Last Edit: June 03, 2019, 10:32:48 pm by Ribster »
 

Offline Ribster

  • Regular Contributor
  • *
  • Posts: 202
  • Country: be
  • Electronics enthousiast. Mostly on STM32
    • Ash Labs
Re: Altium Library footprint not found
« Reply #1 on: June 03, 2019, 10:32:10 pm »
Ok, this is due to the table name changing.
There does not seem to be an easy way to change the table name for each component when the database changed a bit.
Casing matters also!
 

Offline Ribster

  • Regular Contributor
  • *
  • Posts: 202
  • Country: be
  • Electronics enthousiast. Mostly on STM32
    • Ash Labs
Re: Altium Library footprint not found [SOLVED]
« Reply #2 on: June 03, 2019, 11:41:54 pm »
For reference:
The component table needs to be correct /w the correct case.
AD16 let's you overwrite to a new table name, while AD19 does not let you do it via the update from libraries function.

On AD19 i had to move all my SchLib and PcbLib files into 1 folder where my DBLib resided.
Else it could not resolve the path for the PcbLib file.
There is another thread on this forum where a user suggests this as a solution. So if you're having this issue, try it.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf