forkidsleft.blogg.se - Optoma projector app

#Optoma projector app 720p#
#Optoma projector app android#
#Optoma projector app password#
#Optoma projector app tv#

It also has a fairly dim picture, however, so you'll want to set this projector up in as dark a room as possible. This device is about the size of three CD cases stacked on top of each other and has decent sound. Keeping in line with portability comes the Apeman M4 DLP projector.

#Optoma projector app 720p#

Resolution: 720p | Brightness: 200 ANSI lumens | Contrast Ratio: Not listed | Projection Size: 40 to 100 inches It's not cheap, but it's got everything you need built in.

#Optoma projector app tv#

Overall, we really like the Nebula Capsule II, and think it's the perfect solution for a pop-up cinema night or even as a bedroom TV for occasional use.

#Optoma projector app android#

The projector runs on Google's Android software, so along with the easy-to-use interface you can easily download apps like Netflix or Hulu, plus you get the added bonus of built-in Google Assistant. You can also control it using Google Assistant or via a smartphone app or the supplied remote. It's got everything you need, including a speaker built into the base and a built-in app store-just connect it to a Wi-Fi network, and you're good to go. When considering mini projectors, portability is one of the prime considerations, and when it comes to that, being the size of a soda can is about as small as you can get (especially as most bags and backpacks have pockets designed for carrying drink-sized items). Test app handles the thing differently because of the TCP connection termination every time so it gets the PJLINK 0, and projector works with the testbed and OPTOMA probably didn't notice this. Using generic TCP to send commands works because i can send the command without receiving PJLINK 0 before, does module require to receive the PJLINK 0 before sending the command ? Projector does not send PJLINK 0 ever again because the connection is not terminated ever again until closing of companion.

PJlink command button created and pressed and nothing happens on network.

for now nothing until you create button with PJlink command.

when you create the instance of pjlink module in companion and specify the IP of the projector, TCP connection gets created 2) projector sends PJLINK 0.

command get's send from the app (%1POWER 1).

creates new TCP connection for every command sent from interface.

I noticed some more differences between test apps and pjlink module me sending PJLINK 0 before command had nothing to do with this, it works with generic TCP when sending proper commands (%1POWR 1). So something is being exchanged before the %Īfter more testing. Here are two commands from test apps, first with authentication and second without. Test apps offer the option with or without authentication tests.

#Optoma projector app password#

There is no option to set the pjlink password on the projector, otherwise it has no other passwords enabled. I checked TCP traffic with wireshark and there is small difference in commands, test app sends PJLINK 0 ,than %1POWR 1 and this instance sends just %1POWR 1 and for some reason this does not work for the Optoma.įor now I configured standard TCP/UDP instance targeting projectors IP:4352(port) with the commands starting with PJLINK 0 and everything works.Īlso just configuring the PJ link instance in bitfocus prevented any controls from PJ link test app from reaching the projector at the same time, could this could also block any other app from remote controlling the projector at same time?Īm I doing something wrong with this module ,or Optoma didn't implement the thing, or the module needs a fix ? Test app can also send controls to projector and controls from PJLink app went ok. Then I tested the thing with a PJlink test app and the controls where working so there must be something wrong with the PJlink implementation on optoma ? I tried sending controls to Optoma ZU1050 but didn't work.