I've been toying with the idea of making a small board with a SN65176 chip which takes either serial input and converts it to rs485 or takes rs485 and converts it to serial based on wether its set to TX or RX
As it stands my (untested) design is currently 1x1 inch in size and uses an optional 5v regulator to convert from 12v to 5v for the chip
The idea is I could use it to add into a pixel run using its data and power and on the other end 100ft away or more put one in receive mode and continue the pixels.
Maybe i'm re-inventing the wheel but i havent found something similar.
I estimate each board+components would cost ~3-5$ in small runs.
EDIT: here is the schematic
J1 - select wether to use voltage regulator or just pass the input to the chip
J2- select RX or TX
J3 - output if set to TX / input if set to RX
J4 - 1 - GND; 2 - Serial IN if set to TX; 3 - Serial OUT if set to RX; 4 - Vin
I've toyed with making the same thing but haven't had much time to put into it and then RobG came out with http://doityourselfchristmas.com/forums/showthread.php?39071-Buffer-line-driver-null-pixel-without-pixel&highlight=extender
A few notes:
- The 7805 outputs 5V, not 5.5V so it should be called VCC_5V_REG. I would call the supply to U2 VCC_U2. I would also add a note to the schematic saying "connect 1-2 and 3-4 to use the regulator, 2-3 to feed 5V" so it is always handy
- Output and gnd are reversed on U1
- Missing input cap on U1
- Change C1 to 100n
- Add a ground pin on J3
- The internal pin labels on U2 don't line up with the pins
/mike
n1ist wrote:A few notes:- The 7805 outputs 5V, not 5.5V so it should be called VCC_5V_REG. I would call the supply to U2 VCC_U2. I would also add a note to the schematic saying "connect 1-2 and 3-4 to use the regulator, 2-3 to feed 5V" so it is always handy
- Output and gnd are reversed on U1
- Missing input cap on U1
- Change C1 to 100n
- Add a ground pin on J3
- The internal pin labels on U2 don't line up with the pins/mike
Thanks for the recomendations!
- I'll fix the labels, the silkscreen will include the info about connecting the pins
- Thanks for the catch on the reversed pins! Will fix
- does U1 really need an input cap?
- i used the recommended C1 value ( i think? ) any reason to use 100n instead?
- will add GND and VCC passthrough ( to make daisy chaining easier
- i'll try to fix the U2 labels but unfortunately upverter has them wrong in the library 🙁
Sent from my iPhone using Tapatalk
What PCB program is that? Curious 7805 symbol
davros wrote:What PCB program is that? Curious 7805 symbol
upverter.com - its an in-browser ide, exports gerbers (and other formats) and i can send to oshpark
Sent from my iPhone using Tapatalk
So I updated the schematic with some changes recommended by n1ist.
I wasnt sure wether to connect the output cap of U1 to VCC_5V_REG or VCC_U2 since the U2 datasheet says I should have one connected to Vin I figure the way I have it now there will be a cap attached irregardless of the power configuration.
@MrSmoofy: the reason I designed this is so I could go long distances, 100s of feet, without another repeater or null pixel. AFAICT the buffer/driver has the same issues as null pixels and will be limited to 10s of feet (although I may be wrong about this)
Schematic:
PCB Layout:
so i ordered a couple of boards, will
post back in a couple of weeks how they turn out.
ill make the schematics & BOM available for anyone that wants them
Sent from my iPhone using Tapatalk
I am interested in this. I assume you expect power injection close to the pixels and not carried long distance?
I have used, looked at, considered, investigated, explored or am currently in one of those processes on:
- 4 conductor 16Ga speaker wire,
- 4 conductor 16Ga speaker wire with null pixels,
- Cat5 (3xV+, 3XGnd, 1xD)
- Cat5 (3xV+, 3XGnd, 1xD) and null pixels,
- Hybrid control cable,
- RobG's Buffer/line driver - null pixel without pixel (What a descriptive but horrible name! Is there a short form?)
- Sporadic's ESPixelStick (good name),
- DIYLEDExpress' E1.31 DMX Bridge with DIYLEDExpress' Pixel Extenders (reasonable product names but not when combined with the name of the manufacturer)
I would suggest an alternate form factor if possible. A 1x1 inch board begs for an enclosure while a long narrow board could be integrated into a cable using double-wall heat shrink (after jumpers are set). That is something I like about RobG's incredibly annoyingly named board.
(The editorial comments about names were intended as humor, not insult. I apologize if offense was taken)
Jerry-Rigs wrote:I am interested in this. I assume you expect power injection close to the pixels and not carried long distance?
Yes power would need to be injected to power the receiver and LEDs on the far end. The transmitter can use power from the near end of the string where it attaches ( you need to pass ground through the cables so you need 3 cores )
For short runs you COULD send power to the receiver through the cables but I wouldn't do it since you need power on the receiving end to drive the LEDs anyway.
Jerry-Rigs wrote:I would suggest an alternate form factor if possible. A 1x1 inch board begs for an enclosure while a long narrow board could be integrated into a cable using double-wall heat shrink (after jumpers are set). That is something I like about RobG's incredibly annoyingly named board.
I thought about that after i had sent the test boards, if I dont have any issues getting the boards to work ( big gap between theory and practice ) I will rework the board and see what can do in a narrow board layout, the limiting factor will be the size of the DIP8 package.
On that note I would love some suggestions on places that will make boards with surface mount components, I can make a slimmer design that way...
Sent from my iPhone using Tapatalk



