Site About LED Televisions

If your concern is the physical connection between your laptop and the LED TV I'm afraid there is curently no site within the SE Network that welcomes such questions.I checked the following sites, picked from the site list and added their explicit exclusion of your topic:The closest site that might take your question could be Super User as it considers question about computer hardware on-topic but could also deal with questions in regard to drivers for your laptop and your LED TV. To be sure first post a more detailed question on their meta to see if I don't interpret the on-topic-ness too liberal.

I skimmed over proposals on Area51 but coudn't find a site that deals with LED TV's yet

• Related Questions

ds4drv problem with steam

I got my hands on ds4drv this weekend, got some problems with it too(though my problem is a bit harder as I'm trying to use DS4 with Dark Souls in Wine through Steam).First, native driver can interfere with your config (it works perfectly with DS4 though, native Steam detects controller as DS4 and all seems good), so you may wants to just delete /dev/input/jsX of native driver (do not unload hid_sony module as ds4drv --hidraw seem to use it).Second, ds4drv by default starts in some sort of limited profile (just led and trackpad probably), so you may want to play with ds4drv config file to enable profile switching button (PS button by default) and configure your other profiles.

------

Homestays and a driver in Sri Lanka - will accommodation be a problem?

The driver will usually take care of his own accommodation and meals. If it means that he'll sleep inside the vehicle, he will do that. It's always better to contact the owners of the house you are renting to see if there's by any chance a place for a driver to sleep. If not, let the driver know in advance so he will be prepared. Make sure he gets some sleep. A drowsy driver is a risk you shouldn't take.You are not expected to pay for the driver for meals either. However, when I travel with my family, we usually pay the driver for several meals. Just remember to let him know that he can go and have his meals while you guys are having yours

------

Strange LED blinking problem with USB flash drives - is it just me?

The problem of LED blinking after Eject is selected in Nautilus, is very close to this Launchpad Bug Report from 2013:That bug report only has five subscribers and has been closed as a duplicate of this Bug Report from 2011: The latter bug report has 155 subscribers and:Scouring through the first bug report (the one closed as a duplicate) you see the author of udisks mentioning how patches need to be made. Two users who applied the patch reported no success however.I think in the bug report they missed some of the important aspects of one user's output. Here is the equivalent output from my system (that works):Check your own gvfs-mount -li output to mine. Also consider subscribing to the bug reports above and/or posting there

------

Setting up a VPN tunnel between a Linux box and a Cisco FW

There are two implementations of IPSec networking code for Linux. The first was FreeS/WAN's KLIPS driver for 2.4 kernels. The second was 2.6's own native IPSec driver. During early 2.6 versions the native IPSec had fairly serious problems which led to the KLIPS IPSec driver being ported to 2.

6.

The kernel-level support is only a piece of the puzzle, IPSec requires a user-space daemon for key exchange. There are a number of these for Linux. OpenS/WAN descends directly from FreeS/WAN and can use either 2.6 native IPSec or the KLIPS modules (KLIPS being preferred). strongSwan is a fork from FreeS/WAN to use native IPSec only. There are also ports of the BSD IKE daemons for the 2.6 native IPSec driver: racoon/ipsec-tools from Free/NetBSD and isakmpd from OpenBSD.

------

implementation of a large number of outputs (1024)

One approach is to use 32 or 64 channel LED driver ICs to drive the EN pins of the SuperTex HV816. AMS seems to be the key source for drivers beyond 48 channels, running all the way up to 144 channels. For instance, consider the AS1118, a 64-channel LED driver. Use the output channels to drive the enable pins, and you can control the individual EL panels that way.While these devices are designed for driving LEDs, the 1.5 Volt enable logic level of the HV816 permits an unconventional use of these devices, if a simplistic solution is desired: This is assuming that the design has separate HV816 drivers for each EL panel. If not, please share the schematic for how you have the matrix configured, for further suggestions

------

Determining whether an LED module should use a constant current or constant voltage driver

In that unit, the description implies that the necessary series resistance to control current through the LEDs is included "on-board," and that the PCB is "wired" to be connected with others in parallel "daisy-chain" circuits.With the option of adding more modules in parallel, a constant-current supply would only function properly with a fixed number of modules (i.e. a supply meant for 3 would burn up 2, or fail to properly light 4).

However, a constant voltage supply will properly light any number of parallel units, up to the number which will draw more current than your supply can provide.The "available" constant-current PSU-driven version most likely has a series connection to "daisy chain" modules, and could be made without the series resistance that's necessary in a constant-voltage driven unit.

------

27" Cinema Display Windows Drivers

I have that exact same motherboard I purchased less than a month ago. With default BIOS settings, you're right it doesn't work, but I got the 27" display to work fine without installing bootcamp drivers.Make sure you've updated all your drivers and BIOS, especially Intel Graphics 4000 and install Virtu MVP in order to use a discrete graphics card with the thunderbolt interface for gaming/performance. Make the following adjustments to your BIOS (hold delete on boot to access BIOS settings.) Obviously, you might have to plug in a non-thunderbolt display to be able to change the settings.I believe there's also a setting for Thunderbolt Bandwidth which I changed to 40, but I'm not certain if that's necessary to change to get it to work.

------

Issue driving a shift register

The code and logic analyzer output looks okay. It would not hurt to put a NOP or two before driving the clock high. The 74ACT299 is a pretty fast chip (100MHz clock at 5V). I'm guessing you're getting ground bounce between your SR and the driving circuit. This should be suspected especially if you have long wires between the two (make sure the ground wire as well as the signal wires are short and direct). You should also have the 74ACT299 power supply bypassed close to the chip with 0.

1uF to 1uF ceramic. This is non-optional in general, but especially when you're driving a lot of current into the LEDs. If all the LEDs switch at once you've got 100mA flying around with nanosecond edges

------

Does an electronic board that interfaces to a LED driver need to be safety certified?

It is likely going to depend on the power supply. If the whole thing is attached to AC mains, then it would need safety certification.If the LEDs and the controller are supplied through a limited energy and limited voltage power supply (like a laptop power brick) then the safety certification is applicable to the power brick, but the circuit after that likely does not need to be safety certified (eg. CSA/ UL). Exceptions to this would be where the DC voltage is over 42V, or where the amount of stored energy (in capacitors, batteries or inductors) after the power supply is significant (the UL certification standard specifies the energy precisely, if I recall correctly).Does an electronic board that interfaces to a LED driver need to be safety certified?

------

Circuit for supporting, common anode AND cathode RGB LED Matrices

(source)When looking at the connections for common Cathode / Anode LEDs you can see that once you connect the common node appropriately (i.e. Vdd/Gnd) then you just need to drive the RGB lines High for Common Cathode and Low for Common Anode to illuminate the LEDs.UPDATE:

If (as OP states) you're prepared to wire-link the common node to Vdd or Gnd then you just need to make the RGB drive signals selectable positive/negative logic (i.e. 1 ON or 0ON).You can do this easily with an XOR gate or a MUX.(source)Here the MUX selects line selects A or !A to so you can drive common Cathode / Anode respectively.Looking at the XOR version you can see B is inverted if A1 .(source)

------

Can a fifth dimensional being experience serendipitous moment?

Luck is, more or less, a perception of events by an individual. There are two general ideas about luck. The first identifies some supernatural force as the driver for what would otherwise be coincidence. The other is that luck is just a random series of events, either good or bad, that led to the end result.

I can't begin to detail how a fifth-dimensional being would perceive time, space, or reality. That being said, I would argue that luck is independent of time and, as such, any entity capable of rational thought can perceive a given series of events as lucky and, thus, feel lucky (or unlucky).As a side note, I can't find any sources that identify a correlation between time and luck.

------

Low Overhead Constant Current LED Driver

You could use something like the below, which requires less than 60mV of headroom. Sense voltage is only 50mV so the offset voltage of the op-amp will tend to greatly affect the current. The LED could be controlled by connecting R3 to a port pin. (R4 and C1 may not be necessary- it may be possible to omit C1 and short R4 but that would have to be determined- that phase margin is enough for good stability)simulate this circuit Schematic created using CircuitLabNote that if your supply is nominal 3.3V and your LED nominal 3.1V Vf you still may not have enough headroom if the LED happens to be on the high side and your 3.3 turns out to be on the low side

------

Uno as a composite USB HID keyboard

On UNO R3 the HID protocol is handled by the secondary AVR present on the board. Which is the one talking to the PC. So what you should modify is the code implementing the USB protocol on the secondary AVR.The main (328p) AVR interacts with it through the serial port.

You do not need to alter the Linux driver, since it already supports the driving of the usual LEDs (CAPS, Num Lock, Scroll Lock), if these are enough for you.So, to recap:1) enhance the HID implementation to understand LED status commands coming from the PC2) report such changes over serial3) on the primary AVR, monitor for such messages coming over serial port from the secondary AVR and use them to drive the LEDs

------

LED Shut Off Time

Well, movie frames are typically at 24 Hz. Normally the blinking is not very noticeable. Standard video is 30 to 60 Hz, and some folks claim to see the blinking. By around 120 Hz, nobody can see the blinking, except the same people who claim to hear the difference between $5000 speaker cable and just normal speaker cable. With that, I would argue that about 8 mS is well past the limit of what humans can detect. Now LED's, any LED except the white ones that use phosphors to make the white light, will be much faster than 8 mS. Typically an LED turn on/off time will be 1000 times faster! Some are even 1,000,000 times faster.So there you go. While these numbers are approximate, they should be good enough for your application