Buffer/line driver - null pixel without pixel

[jl405304]

I've been reading about these but haven't found a straight forward answer to a few questions. I'm hoping someone here can offer some simple answers...

1. How far can this buffer be from the controller? I know this is controller specific and I'm using an E682 12V controller with 18 awg wire. From what I've read, I'm guessing 20-25 feet. Does that sound right?

2. After this buffer, how far can you run to the first pixel?

3. If the answer to #2 isn't far enough to reach my display, do I just add another buffer, or do I need to add a null pixel and then the buffer?

Thanks in advance for your help. And thank you Rob for making this possible!!!

[RobG]

1. This board should be used to "boost" signal, it should not be used as a signal conditioner, meaning it should be placed right after pixel or controller with weak output (all pixels have weak outputs.) However, since the driver has a Schmitt trigger input, it will work as a conditioner (can be placed before the pixel.)
2. In my tests, I used >100' of #18 cable and had no issues, but it all depends on the type of cable and the environment, so you should test in your setup.
3. You can daisy chain those boards, but one should do the job

Here is the wiki (still in works, but you will get the idea.)

[mikel3332]

I still have not received an invoice

[MartinMueller2003]

The buffer does the same thing as a null pixel, but the buffers output is stronger than that of a pixel. On my display, I put a buffer every 15' when the run between data source and data end is more than 20'. On some of my controller outputs I have found that the first buffer needs to be within the first 12" (weak output driver).

I don't think there can be any hard and fast rules. It all depends on the quality of the wire, the quality of the connectors, the quality of the data source and the amount of electrical noise in the surrounding environment.

[BadWolf]

I added to the spreadsheet. If it's too late to order, just delete my line. Thanks!


Sent from my iPad using Tapatalk

[CFPSystems]

The buffer does the same thing as a null pixel, but the buffers output is stronger than that of a pixel. On my display, I put a buffer every 15' when the run between data source and data end is more than 20'. On some of my controller outputs I have found that the first buffer needs to be within the first 12" (weak output driver).

I don't think there can be any hard and fast rules. It all depends on the quality of the wire, the quality of the connectors, the quality of the data source and the amount of electrical noise in the surrounding environment.

Received the drivers and am now wondering if anyone has played with using Cat-X wiring (twisted pair), to power displays instead of regular "extension cord-type" wire?

If so, how did you split the wires up between V+, V- & Data?

What kind of distances were you able to achieve over non twisted pair wire?

Thanks,
Charlie-

[algerdes]

Charlie,
This has been discussed repeatedly here on the forums. You can do a search for it and get a few different methods.

Usually, orange/white is used for data then the remaining white/stripes are used for V++. Orange is used for signal ground, and the remaining solid color lines are used for V--. Distances have been reported to be quite good.

This is DIY, and there are a dozen different ways people have done this. Make note that this is just one method.

[rstehle]

I am now using Cat5 stranded cable for all of my long runs. I can go 30' easily from a Falcon controller. I use the Orange/White for data, the rest of the White/Color for V+ and all of the Solids for V-.

[CFPSystems]

I am now using Cat5 stranded cable for all of my long runs. I can go 30' easily from a Falcon controller. I use the Orange/White for data, the rest of the White/Color for V+ and all of the Solids for V-.

Thanks. So just to be clear...

Just the Orange/White wire (single conductor), not the pair of Or/Wh & Wh/Or for data?

Charlie-

[RobG]

Use 4 wires for GND, 3 for power, one for data