WadzofQuadz Registered User Thread OP

Old update posts from the ZMR250 thread



Just wanted to get some feedback from you guys .I have been designing the next gen of pdb for our zmr's for a few weeks now since oc wasnt making more .I am trying to get everything as perfect as can be with as little to no noise introduced in the fpv system as possible and all a super clean almost wireless setup. Also with every feature possible .



Heres what i got so far .

LC filtered batt voltage as well as regulated filtered 5v for running 5v cams . This is a onboard reg and not coming from a noisy Bec . connection for filtered batt ,video,audio front and back. One extra regulated 5v aux pad onboard as well. Traces on board ran in best way possible so to not introduce noise from other traces. Audio can be used as a front to back aux if not using. The filtered 5v does not go to the back of the board so there is no confusion of accidentally hooking batt voltage to 5v or damaging the 5v on your vtx.



-All motor connections are built in to board with pin header right at the FC desugned as for best placement with the naze32 and drangonfly32. This means there are no wires that need to come from the escs to the fc,



-Vbat pads also placed for closest connection to fc



-Has OSD pins so a osd can be connected under the fc,



-LC filter ,video pads and esc pads placed where they get in the way of camera placement or fc pins. Power traces are calculated for enough current so that they wont get warm or burn.



LEDs are on the bottom of the board and are programmable through cleanflight to change for orientation,arm/disarm/flight modes etc. Also is the option of running them regularly in any color one wishes by changing a jumper.



-There will be pads for a buzzer but its a option only as buzzers on board introduce noise.



Holes are on board so if running spacers and ecs inside the wiring can be routed up through the board. All isolation around standoffs etc are big enough not to come in contact.



There are some other little things here and there but thats mainly the jist of it. If you guys see something that you think is a issue or would want added in let me know. i wanted to get some feedback here before i finalize my design so anything let me know now. this post is just for feedback/changes and not ordering so lets keep it about that. Thanks.













Heres some more updates guys

i made some changes on my Pdb design after getting some input from you guys .Those who have Pm'ed me with things you would like i thank as well. i noticed there are more of you then i thought who would like a 4s option so i added one. now you can set it up for standard 3s .

pads for the vtx are setup as filtered 3s pad/ gnd / video pad. These 3 pads are what you would use for 3s . I added additional pads labeled (4sout) and (x!) These pads used in conjunction with the 3s pads

allow you to plug in a Polulu step down,step up/down regulator for 4s operation . The filtered 3s Pad becomes the Vin for the polulu. This way you are not limited to 3s or 4s and they dont conflict with eachother.



The next change i did was with the leds. some people asked for "dark versions" ,some wanted Leds on board . I originally was gonna go with programmable rgb leds. Instead i set it up for all 3 options. There are

standard PLCC2 or 1206 LEDs on the bottom of the board.White in front,red in rear. These LEDs do not come on out of the box which gives it the dark board feature. there are SMD jump pads on board which

you just have to bridge solder across the pads to activate leds.This is done very easily by anyone. What gives it the third option of programmable leds is on board there is a pin header. First pin is a single lead

to pin 5 on the naze32 and that is for Dataout which controls the LED functions. The rest of the pins on the header is so you can directly plug in proggrammable LEd strips. This allows you to add programmable

leds where you would like on your build.



Another feature that was added is pads to connect a osd directly to the board. it is based on the e-osd . The e-osd has batt1 pins,batt2 pins and video pins . All of these connect to the pdb for full functionality.

Batt1 will connect to filtered 3s .Batt two is filtered 5v.



lastly i cleaned up and optimized the traces even more to get as much copper as possible on the power and ground planes.Its amazing how clean the trace runs are with the amount of features on this pdb. Every trace is also big enough

to handle any amount of current that would be running through them, Also isolation around all holes are big enough not to come near any of the standoffs or screws.



since there is a 5volt regulator (filtered) on board there is no need to take 5v from a noisy esc or need for a 5v pad around the vtx pads.You no longer need to use the 5v cam out on your VTX. That means theres no wat

to accidentally connect your camout5v on your vtx to battery voltage thus frying it like iv read some have done before. other features include main batt pads on top and bottom. I put them on the bottom incase you want to run

your batt inside the frame and not have the wires in the way.



All in all with the motor signal wires and everything being built into the board you can acheive a super clean almost wireless setup. No servo leads have to be running across the board all the way to the fc anymore.That

alone significantly cleans up the overall look of the build and has some weight savings to go with that. The position of the pins around the fc ( motor pins,bec,buzzer,prog leds and vbat are in locations optimized for both

the naze 32,dragonfly32 and kk2.1. All three get positioned/connected a little differently. The naze32 gets orientated where the usb faces the left side of the pdb so all pins on the pdb line up with the related pins on the fc

The dragonfly32 is orientated in it standard orientation. I set it up so you have your 90 degree motor pins mounted on the bottom of the fc so the leads can plug in straight under the fc and buzzer/vbat are on the right side. .The

KK2.1 gets mounted in its standard orientation as well. All of the make for the shortest servo lead runs.You really only need a cable 1.5-2" long.



Other little things i designed for is not having any pins come in contact with the lc filter components , front esc pads dont come in contact with fpv cam and cam connection pads arnt sitting under the cam either.

The ESC pads were turned 90 degrees so now esc's mounted on the arms can have the wire going in a straight run to the pads not turned. That makes it a little cleaner looking and a little easier to solder. There will be holes

for the wires to run to the top side of pdb as well for those who run spacers and the escs inside the frame.



Everything on the pdb is clearly labled in the silkscreen to make it easy to know where and how everything gets connected. Error proof!I tried to think of everything with this Pdb and i think it will fit everyones

build style.

The last thing i need to do is add the pads for a buzzer. I will include it on the pdb if i can.I am still trying to source a good active Piezo buzzer that is small and also cheap so it doesnt increase the cost too

much and is also loud enough. If anyone has any ideas of where i can find one that would be great. I have been searching. They are either passive buzzers or too big or magnetic or not loud enough or too expensive, its proving hard

to find one thats just right. When i find one i will add it to the Pdb.







Heres some pics and diagrams



Diagram of functions





Top





Bottom





with component rendering.















Ok guys ,Heres a pretty much final update on my PDB before i get ready to send it out for manufacturing. I made a couple more changes/additions . whats new from my previous post on page639 is i got the buzzer location and pads done. Also added some ziptie holes for securing the battery leads. Lastly i rmoved all the copper from under the arm mounts. Also logos and silkscreen finished. Logos not shown in pic. What i would like to also do is add a QR label to the silkscreen so you can scan it with your smart phone and it brings up a PDF manual with links also to the PDB thread and vendors product page. Im not having good luck with getting it on there yet but ill keep trying.



Let me know what you think or anything i should add or change. Not much more that really can be added .It has everythinglol.



You should hear news in the next week or two of where it will be sold and preorder information . Hoping to have them ready to ship by early jan the latest . Christmas time would be nice.















12/19/14 update

Nucleus PDB diagram and 3d rendering:





Just wanted to get some feedback from you guys .I have been designing the next gen of pdb for our zmr's for a few weeks now since oc wasnt making more .I am trying to get everything as perfect as can be with as little to no noise introduced in the fpv system as possible and all a super clean almost wireless setup. Also with every feature possible .Heres what i got so far .LC filtered batt voltage as well as regulated filtered 5v for running 5v cams . This is a onboard reg and not coming from a noisy Bec . connection for filtered batt ,video,audio front and back. One extra regulated 5v aux pad onboard as well. Traces on board ran in best way possible so to not introduce noise from other traces. Audio can be used as a front to back aux if not using. The filtered 5v does not go to the back of the board so there is no confusion of accidentally hooking batt voltage to 5v or damaging the 5v on your vtx.-All motor connections are built in to board with pin header right at the FC desugned as for best placement with the naze32 and drangonfly32. This means there are no wires that need to come from the escs to the fc,-Vbat pads also placed for closest connection to fc-Has OSD pins so a osd can be connected under the fc,-LC filter ,video pads and esc pads placed where they get in the way of camera placement or fc pins. Power traces are calculated for enough current so that they wont get warm or burn.LEDs are on the bottom of the board and are programmable through cleanflight to change for orientation,arm/disarm/flight modes etc. Also is the option of running them regularly in any color one wishes by changing a jumper.-There will be pads for a buzzer but its a option only as buzzers on board introduce noise.Holes are on board so if running spacers and ecs inside the wiring can be routed up through the board. All isolation around standoffs etc are big enough not to come in contact.There are some other little things here and there but thats mainly the jist of it. If you guys see something that you think is a issue or would want added in let me know. i wanted to get some feedback here before i finalize my design so anything let me know now. this post is just for feedback/changes and not ordering so lets keep it about that. Thanks.Heres some more updates guysi made some changes on my Pdb design after getting some input from you guys .Those who have Pm'ed me with things you would like i thank as well. i noticed there are more of you then i thought who would like a 4s option so i added one. now you can set it up for standard 3s .pads for the vtx are setup as filtered 3s pad/ gnd / video pad. These 3 pads are what you would use for 3s . I added additional pads labeled (4sout) and (x!) These pads used in conjunction with the 3s padsallow you to plug in a Polulu step down,step up/down regulator for 4s operation . The filtered 3s Pad becomes the Vin for the polulu. This way you are not limited to 3s or 4s and they dont conflict with eachother.The next change i did was with the leds. some people asked for "dark versions" ,some wanted Leds on board . I originally was gonna go with programmable rgb leds. Instead i set it up for all 3 options. There arestandard PLCC2 or 1206 LEDs on the bottom of the board.White in front,red in rear. These LEDs do not come on out of the box which gives it the dark board feature. there are SMD jump pads on board whichyou just have to bridge solder across the pads to activate leds.This is done very easily by anyone. What gives it the third option of programmable leds is on board there is a pin header. First pin is a single leadto pin 5 on the naze32 and that is for Dataout which controls the LED functions. The rest of the pins on the header is so you can directly plug in proggrammable LEd strips. This allows you to add programmableleds where you would like on your build.Another feature that was added is pads to connect a osd directly to the board. it is based on the e-osd . The e-osd has batt1 pins,batt2 pins and video pins . All of these connect to the pdb for full functionality.Batt1 will connect to filtered 3s .Batt two is filtered 5v.lastly i cleaned up and optimized the traces even more to get as much copper as possible on the power and ground planes.Its amazing how clean the trace runs are with the amount of features on this pdb. Every trace is also big enoughto handle any amount of current that would be running through them, Also isolation around all holes are big enough not to come near any of the standoffs or screws.since there is a 5volt regulator (filtered) on board there is no need to take 5v from a noisy esc or need for a 5v pad around the vtx pads.You no longer need to use the 5v cam out on your VTX. That means theres no watto accidentally connect your camout5v on your vtx to battery voltage thus frying it like iv read some have done before. other features include main batt pads on top and bottom. I put them on the bottom incase you want to runyour batt inside the frame and not have the wires in the way.All in all with the motor signal wires and everything being built into the board you can acheive a super clean almost wireless setup. No servo leads have to be running across the board all the way to the fc anymore.Thatalone significantly cleans up the overall look of the build and has some weight savings to go with that. The position of the pins around the fc ( motor pins,bec,buzzer,prog leds and vbat are in locations optimized for boththe naze 32,dragonfly32 and kk2.1. All three get positioned/connected a little differently. The naze32 gets orientated where the usb faces the left side of the pdb so all pins on the pdb line up with the related pins on the fcThe dragonfly32 is orientated in it standard orientation. I set it up so you have your 90 degree motor pins mounted on the bottom of the fc so the leads can plug in straight under the fc and buzzer/vbat are on the right side. .TheKK2.1 gets mounted in its standard orientation as well. All of the make for the shortest servo lead runs.You really only need a cable 1.5-2" long.Other little things i designed for is not having any pins come in contact with the lc filter components , front esc pads dont come in contact with fpv cam and cam connection pads arnt sitting under the cam either.The ESC pads were turned 90 degrees so now esc's mounted on the arms can have the wire going in a straight run to the pads not turned. That makes it a little cleaner looking and a little easier to solder. There will be holesfor the wires to run to the top side of pdb as well for those who run spacers and the escs inside the frame.Everything on the pdb is clearly labled in the silkscreen to make it easy to know where and how everything gets connected. Error proof!I tried to think of everything with this Pdb and i think it will fit everyonesbuild style.The last thing i need to do is add the pads for a buzzer. I will include it on the pdb if i can.I am still trying to source a good active Piezo buzzer that is small and also cheap so it doesnt increase the cost toomuch and is also loud enough. If anyone has any ideas of where i can find one that would be great. I have been searching. They are either passive buzzers or too big or magnetic or not loud enough or too expensive, its proving hardto find one thats just right. When i find one i will add it to the Pdb.Heres some pics and diagramsDiagram of functionsTopBottomwith component rendering.Ok guys ,Heres a pretty much final update on my PDB before i get ready to send it out for manufacturing. I made a couple more changes/additions . whats new from my previous post on page639 is i got the buzzer location and pads done. Also added some ziptie holes for securing the battery leads. Lastly i rmoved all the copper from under the arm mounts. Also logos and silkscreen finished. Logos not shown in pic. What i would like to also do is add a QR label to the silkscreen so you can scan it with your smart phone and it brings up a PDF manual with links also to the PDB thread and vendors product page. Im not having good luck with getting it on there yet but ill keep trying.Let me know what you think or anything i should add or change. Not much more that really can be added .It has everythinglol.You should hear news in the next week or two of where it will be sold and preorder information . Hoping to have them ready to ship by early jan the latest . Christmas time would be nice.12/19/14 updateNucleus PDB diagram and 3d rendering: Images View all Images in thread Views: 257





Views: 2182



