kicad-developers team mailing list archive

[Michael McCormack <mike@xxxxxxxxxx>]

Which version of not seeing the problem -

   1. The hole is displayed
   2. The hole gets dropped for the PCB file

just curious

Mike

On Mon, Apr 16, 2018 at 9:30 PM, Jon Evans <jon@xxxxxxxxxxxxx> wrote:

> I tested on Ubuntu and Windows 10 using 5.0rc2 and don't see the problem,
> so I guess it has been fixed somewhere along the way.
>
> On Mon, Apr 16, 2018 at 8:12 PM, Michael McCormack <mike@xxxxxxxxxx>
> wrote:
>
>> OK, here is the boar file, if you need anything else, please let me know.
>>
>> On Mon, Apr 16, 2018 at 6:09 PM, Jeff Young <jeff@xxxxxxxxx> wrote:
>>
>>> Looks like a different bug (2.9mm drill is smaller than 3.2mm pad).
>>>
>>> I can’t reproduce it on 5.0rc2 Mac.  Not sure if that’s because it’s
>>> fixed in 5.0, or it only shows up on Windows, or it’s something specific to
>>> Michael’s setup.
>>>
>>>
>>> On 16 Apr 2018, at 22:44, Michael McCormack <mike@xxxxxxxxxx> wrote:
>>>
>>> This is the module snipped from the board file:
>>>
>>>   (module Ori:MountingHole_3.2mm_M3_ISO14580 (layer F.Cu) (tedit
>>> 59C8FBCE) (tstamp 5AC4E91C)
>>>     (at 138.25 141.050001)
>>>     (descr "Mounting Hole 3.2mm, no annular, M3, ISO14580")
>>>     (tags "mounting hole 3.2mm no annular m3 iso14580")
>>>     (path /583B5C0A)
>>>     (fp_text reference M1 (at 0 -3.75) (layer F.SilkS) hide
>>>       (effects (font (size 1 1) (thickness 0.15)))
>>>     )
>>>     (fp_text value "M3_Mounting Hole" (at 0 3.75) (layer F.Fab)
>>>       (effects (font (size 1 1) (thickness 0.15)))
>>>     )
>>>     (fp_circle (center 0 0) (end 2.75 0) (layer Cmts.User) (width 0.15))
>>>     (fp_circle (center 0 0) (end 3 0) (layer F.CrtYd) (width 0.05))
>>>     (pad "" np_thru_hole circle (at 0 0) (size 3.2 3.2) (drill 2.9)
>>> (layers *.Cu *.Mask)
>>>       (clearance 2))
>>>   )
>>>
>>> I am using 4.0.7 under Windows 10, if you decode this is the known bug I
>>> sincerely apologize for having wasted your time.  I did not see a bug that
>>> I thought was the same thing.  If not, I will mail it to any and all of you
>>> to look at.  I won't obfuscate, I'd be afraid to disturb the problem.  I
>>> see no real problem sharing the board with Kicad developers but can also
>>> understand why my employer is not keen to have our boards posted on the
>>> internet.
>>>
>>> Cheers
>>> Mike
>>>
>>>
>>> On Mon, Apr 16, 2018 at 5:13 PM, Jon Evans <jon@xxxxxxxxxxxxx> wrote:
>>>
>>>> That sounds like a bug (if there is invalid data like that, we should
>>>> deal with it in a better way)
>>>> It sounds like it might be easy to make a trivial test case to attach
>>>> to a bug report without using your employer's board as-is
>>>> (maybe by removing everything manually from the kicad_pcb file except
>>>> for the hole in question and the board outline?)
>>>>
>>>> I can't take a look at this right this moment, but I could in the next
>>>> few days if no one else jumps on it first.
>>>>
>>>> -Jon
>>>>
>>>> On Mon, Apr 16, 2018 at 4:35 PM, Michael McCormack <mike@xxxxxxxxxx>
>>>> wrote:
>>>>
>>>>> This might not be quite the right place to post this, but, I've found
>>>>> something that is a slightly problematic with Kicad and board file.  I have
>>>>> a PCB that has a NPH hole located off the board, I can't see it or select
>>>>> it inside PCBNew, however, it gets a hole in the gerbers and I can find it
>>>>> in the kicad_pcb file if I open the file with a text editor.
>>>>>
>>>>> As it is my employer's board, I can't see them being OK with me
>>>>> creating a bug report and posting the board file for just anyone to see;
>>>>> but, as I have used Kicad myself probably a decade I'd send it to someone
>>>>> to evaluate if it would help the project.
>>>>>
>>>>> Is anyone interested?
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list: https://launchpad.net/~kicad-developers
>>>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>>>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>