search

Bouni / kicad-jlcpcb-tools

Plugin to generate BOM + CPL files for JLCPCB, assigning LCSC part numbers directly from the plugin, query the JLCPCB parts database, lookup datasheets and much more.
MIT License
1.08k stars 102 forks source link

Windows Mapped Drive Problems (recent windows 11 update?) #486

Closed Nick-Doe closed 3 days ago

Nick-Doe commented 2 weeks ago

The problems I was having with assigning parts (issue #474) seems to be related mapped drives after a recent windows update. I have my work files mapped to drive I. If I open the kicad files using I:...\file.kicad_pro then I can't assign parts or generate a correct BOM Using C:\I...\file.kicad_pro everything is OK

(assigning parts seems a lot slower?)

Bouni commented 2 weeks ago

I'll see if I'm able to reproduce this issue locally

Bouni commented 2 weeks ago

I cannot reproduce the behaviour you describe ...

  1. I created a new project on a sahred drive (Synology NAS)
  2. I Added two parts to the schematic and assigned a LCSC Number to one of them
  3. I switched to the PCB editor and placed both parts
  4. I opend the plugin, the alrteday assigned part shows up correct in the table
  5. I assigned a number to the second part via the Assign LCSC number button
  6. Again the table is correct
  7. I generated the production files, BOM and CPL are both valid

Is there a difference in this workflow to whta you do?

Bouni commented 3 days ago

I'll close this. Reopen if the problem remains

Nick-Doe commented 3 days ago

Yes, things have been working fine

On Wed, Jul 3, 2024 at 12:12 AM bouni @.***> wrote:

Closed #486 https://github.com/Bouni/kicad-jlcpcb-tools/issues/486 as completed.

— Reply to this email directly, view it on GitHub https://github.com/Bouni/kicad-jlcpcb-tools/issues/486#event-13375772254, or unsubscribe https://github.com/notifications/unsubscribe-auth/A666IYOBL4HZVWBR256EJBTZKOP53AVCNFSM6AAAAABJUK2IS6VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGM3TKNZXGIZDKNA . You are receiving this because you authored the thread.Message ID: @.***>