What did I wrong? and why does oshpark shows it right but makes it different…
I just did a small PCB to mount nichia 119, I used DRU to disable soldermask on the vias to get the bottom covered completely and I wanted to add soldermask free space on top like the oshpark render shows.
What did I wrong? and why does oshpark shows it right but makes it different…
I just did a small PCB to mount nichia 119, I used DRU to disable soldermask on the vias to get the bottom covered completely and I wanted to add soldermask free space on top like the oshpark render shows.
Location: A light beam away from the missus in the land of Aus.
Hi Werner. I'm sorry to see your project did not come out as planned but I'm sure that some members here including me are excited to see you give this ago. Its something I cant do and admire you for your attempt. Help will not be far away.
—
djozz quotes, "it came with chinese lettering that is chinese to me".
"My man mousehole needs one too"
old4570 said "I'm not an expert , so don't suffer from any such technical restrictions".
Old-Lumens. Highly admired and cherished member of Budget Light Forum. 11.5.2011 - 20.12.16. RIP.
I don’t have made gerberfiles because I only upload the .brd file to oshpark…
Do you always make gerber files and review these with a viewer? I thought that wouldn’t be necessary because oshpark shows a preview anyway…
It’s no big problem it’s more a confusement, I just can scrap the solder mask a bit away but I would like to know what I did wrong to make it better next time.
The big through hole is also different than I thought it would be, but it worked and the rectangular fields on the middle are in the same layer….?
I always generate Gerbers. Gerbers are subject to significantly less interpretation than a BRD file. It also gives me more control of things like what layers are included on the silkscreen.
I do not always check my Gerbers in a viewer, I only check about 1/3 or less of the time. Whenever I see anything I am unsure of on the OSH Park preview I check my gerbers using Gerbv. Also don’t forget that the renders OSH Park does are very low resolution – they may be missing some detail.
OSH Park provides a CAM job which you can use, you don’t have to make one up all by yourself.
This driver was originally an idea I had when I got sick of building 16x7135 drivers, then having the moonlight be high, unstable, or not work at all. After my failed attempts, JonnyC tweaked the STAR firmware for dual output. I built quite a few cutting traces and using a jumper on the normal 105C boards, then Mattaus helped me create the first version of this board. This is his board, with a few tweaks, and a nod to all of those who have inspired me and helped me down this path. I couldn't have done it without the help from many here! Thank you all.
Please note that this exact revision is untested, although I am 99% certain it will work.
What did I wrong? and why does oshpark shows it right but makes it different…
I just did a small PCB to mount nichia 119, I used DRU to disable soldermask on the vias to get the bottom covered completely and I wanted to add soldermask free space on top like the oshpark render shows.
I’ve examined the BRD. I have also run the OSH Park CAM job against it and examined the Gerbers that produced.
The large vias on your physical board look exactly like your BRD does in Eagle. Gerbv displays the Gerbers differently though. Like the OSH Park render, Gerbv does not show a bulge. I think this may be related to your use of square rings on the vias? I always use circular.
The top soldermask looks correct in your BRD and the OSH Park render. I think the extra mask applied around the vias is a mistake at the board house (fab). Why don’t you send an email to OSH Park’s support, they are very good about this sort of thing. They’ll either make it right if the problem is on their end or they’ll nicely explain what you’ve done to cause the problem.
It seems that you have placed an extra square on the BSTOP layer inside the large lefthand via. This should not affect anything as far as I know, but as far as I know it’s not there on purpose.
I recommend that you switch from “Proportional” text to “Vector” text and ensure that your lines are 5mil thick or greater. This is why your silkscreen text did not come out well.
This driver was originally an idea I had when I got sick of building 16×7135 drivers, then having the moonlight be high, unstable, or not work at all. After my failed attempts, JonnyC tweaked the STAR firmware for dual output. I build quite a few cutting traces and using a jumper on the normal 105C boards, then Mattaus helped me create the first version of this board. This is his board, with a few tweaks, and a nod to all of those who have inspired me and helped me down this path. I couldn’t have done it without the help from many here! Thank you all.
Please note that this exact revision is untested, although I am 99% certain it will work.
What did I wrong? and why does oshpark shows it right but makes it different…
I just did a small PCB to mount nichia 119, I used DRU to disable soldermask on the vias to get the bottom covered completely and I wanted to add soldermask free space on top like the oshpark render shows.
I’ve examined the BRD. I have also run the OSH Park CAM job against it and examined the Gerbers that produced.
The large vias on your physical board look exactly like your BRD does in Eagle. Gerbv displays the Gerbers differently though. Like the OSH Park render, Gerbv does not show a bulge. I think this may be related to your use of square rings on the vias? I always use circular.
The top soldermask looks correct in your BRD and the OSH Park render. I think the extra mask applied around the vias is a mistake at the board house (fab). Why don’t you send an email to OSH Park’s support, they are very good about this sort of thing. They’ll either make it right if the problem is on their end or they’ll nicely explain what you’ve done to cause the problem.
It seems that you have placed an extra square on the BSTOP layer inside the large lefthand via. This should not affect anything as far as I know, but as far as I know it’s not there on purpose.
I recommend that you switch from “Proportional” text to “Vector” text and ensure that your lines are 5mil thick or greater. This is why your silkscreen text did not come out well.
Thanks. I care about the stopmask in the middle because it took me some minutes to make the size and position and then it was messed up…arghh!
I will email oshpark my question, wasn’t brave enough until now because I thought I maybe made a well known mistake.
Already read the hint with the vector text in another post from CK, I will try this next time…
——
@RMM
Why is there only one capacitor on the board?
This driver was originally an idea I had when I got sick of building 16×7135 drivers, then having the moonlight be high, unstable, or not work at all. After my failed attempts, JonnyC tweaked the STAR firmware for dual output. I built quite a few cutting traces and using a jumper on the normal 105C boards, then Mattaus helped me create the first version of this board. This is his board, with a few tweaks, and a nod to all of those who have inspired me and helped me down this path. I couldn’t have done it without the help from many here! Thank you all.
Please note that this exact revision is untested, although I am 99% certain it will work.
File is here, just copy into your cam processor directory, then tell it to open the brd file, then run project…then zip all the .*** (capital letter files) files (the .GBP and .GTP files are the paste files for OSHStencils), and upload that to OSHPark
There is not much need to go through the extra step of generating gerbers, unless drc errors are causing oshpark to reject your brd (or you want to change a part outline silkscreen without actually editing the part).
There is no need to go through the extra step of generating gerbers, unless drc errors are causing oshpark to reject your brd (or you want to change a part outline silkscreen without actually editing the part).
or OSHPark shows one thing but for some reason the fab house runs em differently
(like what happened to Werner)
I have uploaded a few .brd files I found in peoples shared project folders, OSHPark rendered them all funky, traces extra wide and shorting. blah blah…when I converted to gerbers, they came out just as I uploaded them…sometimes their stuff goes squiffy…not often but it happens
or OSHPark shows one thing but for some reason the fab house runs em differently
(like what happened to Werner)
The fab makes occasional errors whether you use brd or gerbers. I’ve had equal fab errors with both.
WarHawk wrote:
I have uploaded a few .brd files I found in peoples shared project folders, OSHPark rendered them all funky, traces extra wide and shorting. blah blah…when I converted to gerbers, they came out just as I uploaded them…sometimes their stuff goes squiffy…not often but it happens
I’ve noticed that too. Honestly, if you run drc on the boards, you’ll see the problems causing it. You can only have so many drc violations before you start getting problems. Gerbers mush everything together and can hide some errors. When starting out I can understand ignoring everything to just to get a simple pcb made before you really learn eagle. But it works against you, makes designs harder if you continue like that.
There is not much need to go through the extra step of generating gerbers, unless drc errors are causing oshpark to reject your brd (or you want to change a part outline silkscreen without actually editing the part).
I dunno about all that. Generating Gerbers is definitely the tried and true way. Even Gerbers leave room for error, BRD files leave a lot of room for error.
I dunno about all that. Generating Gerbers is definitely the tried and true way. Even Gerbers leave room for error, BRD files leave a lot of room for error.
As long as one isn’t using gerbers because oshpark is refusing the brd due to a ton of design errors. Most fabs don’t even accept brds, its supposed to be helpful that oshpark does. The brd isn’t sent to the fab, they generate gerbers with eagle 6.6.
Oshpark wrote:
We are currently processing uploaded Eagle BRD files with Eagle CAD version 6.6, and have confirmed compatibility with all Eagle versions up to 7.1.
I got answer from oshpark and its like wight has said it before, fab messed it up, their files look good. No big problem anyway but good to know it wasn’t my fault.
I used gerberfiles before for itead but I like how easy it is to just upload the brd file and see a preview…
I got answer from oshpark and its like wight has said it before, fab messed it up, their files look good. No big problem anyway but good to know it wasn’t my fault.
I used gerberfiles before for itead but I like how easy it is to just upload the brd file and see a preview…
gerbers in a zip do the same thing
Get a program called grbv and it will generate a 3D image of your board as well, you can even change the default skin to the oshpark one and see the way your design will look as well
Like RMM’s Moonlight Special V2 8× 7135
Top:
Bottom:
P.S. RMM when you zip the files, don’t include the revisions in the zip…only the files with capitol letter extensions
This driver was originally an idea I had when I got sick of building 16×7135 drivers, then having the moonlight be high, unstable, or not work at all. After my failed attempts, JonnyC tweaked the STAR firmware for dual output. I built quite a few cutting traces and using a jumper on the normal 105C boards, then Mattaus helped me create the first version of this board. This is his board, with a few tweaks, and a nod to all of those who have inspired me and helped me down this path. I couldn’t have done it without the help from many here! Thank you all.
Please note that this exact revision is untested, although I am 99% certain it will work.
How does that work? I see a second diode. Does that help the moonlight mode? Or is that the Zener I have read about?
—
Flashlight designers should look at lighthouses and pottery.
这些谁设计的手电筒应该看灯塔，以及在陶器。
Interesting concept, I like that idea.
Still fine, still on a break. One day I’ll catch up with you folks! previous wight catchup
list of my drivers & variants (A17DD, FET+1 stuff, WIP stuff, etc)
Can someone of the oshparkgurus give me a hint why that didnt worked like I thought:
This is what I made in eagle:
this is what oshpark showed me:
but i got this:
brd file here:
https://www.dropbox.com/sh/k6hu1hz9uvyewpd/AACYhBRD4×5InYpOwA5eVFp_a?dl=0
What did I wrong? and why does oshpark shows it right but makes it different…
I just did a small PCB to mount nichia 119, I used DRU to disable soldermask on the vias to get the bottom covered completely and I wanted to add soldermask free space on top like the oshpark render shows.
Still fine, still on a break. One day I’ll catch up with you folks! previous wight catchup
list of my drivers & variants (A17DD, FET+1 stuff, WIP stuff, etc)
Hi Werner. I'm sorry to see your project did not come out as planned but I'm sure that some members here including me are excited to see you give this ago. Its something I cant do and admire you for your attempt. Help will not be far away.
djozz quotes, "it came with chinese lettering that is chinese to me".
"My man mousehole needs one too"
old4570 said "I'm not an expert , so don't suffer from any such technical restrictions".
Old-Lumens. Highly admired and cherished member of Budget Light Forum. 11.5.2011 - 20.12.16. RIP.
I don’t have made gerberfiles because I only upload the .brd file to oshpark…
Do you always make gerber files and review these with a viewer? I thought that wouldn’t be necessary because oshpark shows a preview anyway…
It’s no big problem it’s more a confusement, I just can scrap the solder mask a bit away but I would like to know what I did wrong to make it better next time.
The big through hole is also different than I thought it would be, but it worked and the rectangular fields on the middle are in the same layer….?
I always generate Gerbers. Gerbers are subject to significantly less interpretation than a BRD file. It also gives me more control of things like what layers are included on the silkscreen.
I do not always check my Gerbers in a viewer, I only check about 1/3 or less of the time. Whenever I see anything I am unsure of on the OSH Park preview I check my gerbers using Gerbv. Also don’t forget that the renders OSH Park does are very low resolution – they may be missing some detail.
OSH Park provides a CAM job which you can use, you don’t have to make one up all by yourself.
I’ll try and take a look at your BRD tonight.
Still fine, still on a break. One day I’ll catch up with you folks! previous wight catchup
list of my drivers & variants (A17DD, FET+1 stuff, WIP stuff, etc)
Moonlight Special V2 8x7135 Driver
This driver was originally an idea I had when I got sick of building 16x7135 drivers, then having the moonlight be high, unstable, or not work at all. After my failed attempts, JonnyC tweaked the STAR firmware for dual output. I built quite a few cutting traces and using a jumper on the normal 105C boards, then Mattaus helped me create the first version of this board. This is his board, with a few tweaks, and a nod to all of those who have inspired me and helped me down this path. I couldn't have done it without the help from many here! Thank you all.
Please note that this exact revision is untested, although I am 99% certain it will work.
Mountain Electronics : batteries, Noctigon, and much more! What's new?
Still fine, still on a break. One day I’ll catch up with you folks! previous wight catchup
list of my drivers & variants (A17DD, FET+1 stuff, WIP stuff, etc)
Still fine, still on a break. One day I’ll catch up with you folks! previous wight catchup
list of my drivers & variants (A17DD, FET+1 stuff, WIP stuff, etc)
Thanks. I care about the stopmask in the middle because it took me some minutes to make the size and position and then it was messed up…arghh!
I will email oshpark my question, wasn’t brave enough until now because I thought I maybe made a well known mistake.
Already read the hint with the vector text in another post from CK, I will try this next time…
——
@RMM
Why is there only one capacitor on the board?
Still fine, still on a break. One day I’ll catch up with you folks! previous wight catchup
list of my drivers & variants (A17DD, FET+1 stuff, WIP stuff, etc)
Is there a discussion thread for the moonlight special driver?
Three Tanna leaves to give him life, nine to give him movement. But what if he eats the whole bag?
Scott
oh wow…awesome!!!
Very cool build RMM!
Hey Werner, try using Mattaus’s CAM generator
File is here, just copy into your cam processor directory, then tell it to open the brd file, then run project…then zip all the .*** (capital letter files) files (the .GBP and .GTP files are the paste files for OSHStencils), and upload that to OSHPark
https://www.dropbox.com/sh/mnqwk08b9p4d6pu/AACkJxVSqBmWi9-rlSBAGuZTa?dl=0
That is the directory of all the custom library files Mattaus has given me and his custom CAM processor
There is not much need to go through the extra step of generating gerbers, unless drc errors are causing oshpark to reject your brd (or you want to change a part outline silkscreen without actually editing the part).
xkcd.com/1603 Li-ion battery safety 101.
or OSHPark shows one thing but for some reason the fab house runs em differently
(like what happened to Werner)
I have uploaded a few .brd files I found in peoples shared project folders, OSHPark rendered them all funky, traces extra wide and shorting. blah blah…when I converted to gerbers, they came out just as I uploaded them…sometimes their stuff goes squiffy…not often but it happens
Added the Teeny10 and MS
Three Tanna leaves to give him life, nine to give him movement. But what if he eats the whole bag?
Scott
The fab makes occasional errors whether you use brd or gerbers. I’ve had equal fab errors with both.
I’ve noticed that too. Honestly, if you run drc on the boards, you’ll see the problems causing it. You can only have so many drc violations before you start getting problems. Gerbers mush everything together and can hide some errors. When starting out I can understand ignoring everything to just to get a simple pcb made before you really learn eagle. But it works against you, makes designs harder if you continue like that.
xkcd.com/1603 Li-ion battery safety 101.
Still fine, still on a break. One day I’ll catch up with you folks! previous wight catchup
list of my drivers & variants (A17DD, FET+1 stuff, WIP stuff, etc)
Someone asked for a single mode single 7135 10mm driver…that is why I made that one…can’t find the discussion though
With the turnover these days it’s probably on page 20 by now.
Three Tanna leaves to give him life, nine to give him movement. But what if he eats the whole bag?
Scott
xkcd.com/1603 Li-ion battery safety 101.
I got answer from oshpark and its like wight has said it before, fab messed it up, their files look good. No big problem anyway but good to know it wasn’t my fault.
I used gerberfiles before for itead but I like how easy it is to just upload the brd file and see a preview…
Get a program called grbv and it will generate a 3D image of your board as well, you can even change the default skin to the oshpark one and see the way your design will look as well
Like RMM’s Moonlight Special V2 8× 7135
Top:
Bottom:
P.S. RMM when you zip the files, don’t include the revisions in the zip…only the files with capitol letter extensions
OSH Park seems to have added a cart system.
Still fine, still on a break. One day I’ll catch up with you folks! previous wight catchup
list of my drivers & variants (A17DD, FET+1 stuff, WIP stuff, etc)
Lol. Yeah, too many revisions...too little time!
I tried to run that 3D rendering program but I don't have OpenGL 3.0, so it was a no go.
Mountain Electronics : batteries, Noctigon, and much more! What's new?
How does that work? I see a second diode. Does that help the moonlight mode? Or is that the Zener I have read about?
Flashlight designers should look at lighthouses and pottery.
这些谁设计的手电筒应该看灯塔，以及在陶器。
Moonlight is pwm on a separate pin to only a single 7135.
xkcd.com/1603 Li-ion battery safety 101.
The second diode marked "Z" is for an optional zener diode, for multi-cell use with multiple LEDs in series or an MT-G2.
Mountain Electronics : batteries, Noctigon, and much more! What's new?
Thanks Halo and RMM.
The circuit is hard to see in that sort of picture, but I did begin to see what the diode is for.
Flashlight designers should look at lighthouses and pottery.
这些谁设计的手电筒应该看灯塔，以及在陶器。
Pages