Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JLCPCB_CORRECTION wrong orientation on multiple components #762

Open
3 tasks done
greenscreenflicker opened this issue Nov 11, 2024 · 10 comments · May be fixed by #767
Open
3 tasks done

JLCPCB_CORRECTION wrong orientation on multiple components #762

greenscreenflicker opened this issue Nov 11, 2024 · 10 comments · May be fixed by #767

Comments

@greenscreenflicker
Copy link

Prerequisites

  • I have read FAQ
  • I have searched existing issues (including closed ones)
  • I use KiKit at least version 1.6.0 (older version are not supported)

KiKit version

kikit, version 1.6.0

KiCAD version

8.0.5

Operating system

Windows 11

Description

May it be that JLCPCB_CORRECTION is only applied to the first element of a series?
I see that the correction is applied for one, but not for the other. In the schematic both are there.

grafik

Steps to Reproduce

Use PCB send. Apply
kikit panelize --layout "grid; rows: 1; cols: 5; space: 4mm; rotation: 0deg;" --tabs "fixed; hwidth: 42mm; vwidth: 60mm" --cuts "vcuts" --post "millradius: 0.3mm" --source "tolerance: 20mm" ../acpd_v2.kicad_pcb panel.kicad_pcb
kikit fab jlcpcb --assembly --schematic ../acpd_v2.kicad_sch panel.kicad_pcb --no-drc gerber_panel/

Thank you for checking

@yaqwsx
Copy link
Owner

yaqwsx commented Nov 12, 2024

You haven't provided all the necessary files for reproduction - acpd_v2.kicad_sch is missing.

@greenscreenflicker
Copy link
Author

@yaqwsx send you all the files right now

@yaqwsx
Copy link
Owner

yaqwsx commented Nov 13, 2024

I think your conclusion is incorrect. What happened is that JLC PCB changed the specification of the POS file. They seem to require the orientation of the components to be given when viewing from the corresponding side of the PCB. This didn't use to be the case.

I will need to contact JLC PCB and get a precise specification of what they require, so I can avoid making ad-hoc changes that can even make it worse.

@greenscreenflicker
Copy link
Author

@yaqwsx note that both sot23 are on the same pcb side, so i don't think thats it

@yaqwsx
Copy link
Owner

yaqwsx commented Nov 14, 2024

It is it. If you switch sides, the orientation of 90 degrees doesn't change, but the orientation of 0 degrees flips to 180 degrees.

@greenscreenflicker
Copy link
Author

greenscreenflicker commented Nov 14, 2024

Note that the green is correctly orientated while red is not. Both are the exact same component with the exact same jlcpcb correction parameter.
Edit: and both are on the same Side

@yaqwsx
Copy link
Owner

yaqwsx commented Nov 14, 2024

It is it. If you switch sides, the orientation of 90 degrees doesn't change, but the orientation of 0 degrees flips to 180 degrees.

@markh-de
Copy link
Contributor

Yes, it would be great if you could contact JLCPCB and try to fix this issue (#664). Even if you don't get an answer, we really know how to calculate the "correct" values, don't we? If you want to avoid regression, the changed calculation feature could be a CLI option that users need to pass explicitly.

This issue just bit me. I have some connectors that aren't rotated N×90°, and they are good on the top side, but have flipped angle interpretation on the bottom side.

Thanks for all your hard work.

@markh-de
Copy link
Contributor

I did the 180-angle conversion as suggested in #664, until I realized that this only works as long as you don't have orientation compensation != 0°. That compensation data also needs to be flipped. I hope that PR #767 helps fixing this issue.

@markh-de
Copy link
Contributor

markh-de commented Dec 9, 2024

@yaqwsx: Did you have a chance to test #767, yet? It looked very promising in my tests.

Any other users who are affected by this issue? Can you please try the patch and provide some feedback so that Jan can make a well-informed decision about the PR. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants