Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
JVC D-ILA Driver
#1
Hi,

Looking for a driver to control my projector over LAN.  Looks like JVC is very open with their command structure.

http://support.jvc.com/consumer/support/...lGuide.pdf

I see there are some older drivers out there, but nothing for the D-ILA series of projectors.

Thanks.


Attached Files
.pdf   DILAremoteControlGuide.pdf (Size: 149.39 KB / Downloads: 3)
Reply
#2
I don't see anything immediately obvious where you couldn't use the JVC-RSn driver. Did you try it?
Mark Stega
Reply
#3
(12-02-2019, 01:59 PM)Mark Stega Wrote: I don't see anything immediately obvious where you couldn't use the JVC-RSn driver. Did you try it?

Hi Mark,  


Thanks for the reply.  Sorry I attached the wrong files.  I was actually looking to see what the differences are.  I have an NX7.  With the old driver it connects, but commands do not work.

Ideally would just need to connect and provide the ability to send the commands needed from this document.  I'm mostly interested in power and lens memory settings.  Once I get into more detailed settings of the projector, this is likely to expand.

https://www.us.jvc.com/projectors/pdf/20...t_v1.2.pdf
Reply
#4
(12-03-2019, 06:45 AM)jokermac Wrote: Ideally would just need to connect and provide the ability to send the commands needed from this document.  I'm mostly interested in power and lens memory settings.  Once I get into more detailed settings of the projector, this is likely to expand.
Put the driver in verbose mode using the fileverbosity field and then send a power on command. Send the contents of the log file. Power looks to be identical, it may be failing on one of the queries. Also, is your driver version 2.21?
Mark Stega
Reply
#5
Hi Mark, Looks like the version I'm using is 0.4. Chose this version due to the fact that I am connecting via LAN connection. Below is the result of attempting to turn on. Basically timing out.

12/04 13:36:37-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.606, Status/App Status
Sending: PowerState
}
12/04 13:36:37-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.462, Status/App Status
Sending: 3F 89 01 50 57 0A
}
12/04 13:36:39-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.485, Status/App Status
Receive TIMEOUT
}
12/04 13:36:39-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.462, Status/App Status
Received:
}
12/04 13:36:39-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.509, Status/App Status
NAK processed -
}
12/04 13:36:41-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.485, Status/App Status
Receive TIMEOUT
}
12/04 13:36:41-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.462, Status/App Status
Received:
}
12/04 13:36:43-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.606, Status/App Status
Sending: Power
}
12/04 13:36:43-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.462, Status/App Status
Sending: 21 89 01 50 57 31 0A
}
12/04 13:36:45-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.485, Status/App Status
Receive TIMEOUT
}
12/04 13:36:45-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.462, Status/App Status
Received:
}
12/04 13:36:45-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.509, Status/App Status
NAK processed -
}
12/04 13:36:51-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.606, Status/App Status
Sending: PowerState
}
12/04 13:36:51-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.462, Status/App Status
Sending: 3F 89 01 50 57 0A
}
12/04 13:36:53-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.485, Status/App Status
Receive TIMEOUT
}
12/04 13:36:53-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.462, Status/App Status
Received:
}
12/04 13:36:53-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.509, Status/App Status
NAK processed -
}
12/04 13:36:55-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.485, Status/App Status
Receive TIMEOUT
}
12/04 13:36:55-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.462, Status/App Status
Received:
}
Reply
#6
(12-04-2019, 11:49 AM)jokermac Wrote: Hi Mark,  Looks like the version I'm using is 0.4.  Chose this version due to the fact that I am connecting via LAN connection.  Below is the result of attempting to turn on.  Basically timing out.

12/04 13:36:37-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
    CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.606, Status/App Status
    Sending: PowerState
}
12/04 13:36:37-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
    CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.462, Status/App Status
    Sending: 3F 89 01 50 57 0A
}
12/04 13:36:39-CQC_Rack, CQCServer, CQCDrv_JVC-ProjectorThread572
{
    CQCGenDrvS, MEng.System.CQC.Drivers.JVC.RSn.DriverImpl.485, Status/App Status
    Receive TIMEOUT
}
I'd start by looking at the network settings on the projector itself. I suspect that either the LAN control is not enabled or that the IP address is wrong.

The RSn driver is ancient. I can easily build the V2 driver as an IP driver and if needed make changes for the 2018 series. But the RSn driver should be able to get power state with no issue.
Mark Stega
Reply
#7
Okay, so I played with this some this afternoon and have it working from a PC terminal. Took a bit to find it but within the user manual it states you need to send a ASCII PJREQ within 5 seconds of connecting or the projector will not acknowledge any commands after that. Once I did this, I could send power commands and everything worked just like a serial connection.
Reply
#8
(12-04-2019, 03:57 PM)jokermac Wrote: Okay, so I played with this some this afternoon and have it working from a PC terminal.  Took a bit to find it but within the user manual it states you need to send a ASCII PJREQ within 5 seconds of connecting or the projector will not acknowledge any commands after that.  Once I did this, I could send power commands and everything worked just like a serial connection.
So where did you find that? It isn't in the protocol document that you linked. Can you post another link please?

[Edit] Never mind, I found yet another JVC protocol guide titled "JVC D-ILA® Projector RS-232C, LAN and Infrared Remote Control Guide" that describes the IP connection methodology.
Mark Stega
Reply
#9
So I've done a 'by eye' attempt at performing the IP connection. You will get log files in "Program files(x86)\cqc\cqcdata\macrofileroot". Import the attached driver pack & give it a try. Protocol has to be tcp, port has to be 20554, ip address you set.

After configuring the driver set the fileverbosity field to high.

Post the opening contents of the log file here, hopefully I added enough logging that we won't need to set up a remote session.


Attached Files
.cqcdrvpack   JVC-RSn-V2-IP-Dev-222.CQCDrvPack (Size: 28.26 KB / Downloads: 8)
Mark Stega
Reply
#10
(12-05-2019, 08:15 AM)Mark Stega Wrote: So I've done a 'by eye' attempt at performing the IP connection. You will get log files in "Program files(x86)\cqc\cqcdata\macrofileroot". Import the attached driver pack & give it a try. Protocol has to be tcp, port has to be 20554, ip address you set.

After configuring the driver set the fileverbosity field to high.

Post the opening contents of the log file here, hopefully I added enough logging that we won't need to set up a remote session.

Hi Mark,

Tried to import, but get an error saying failed to import when I try.  Been a while since I've tried to import a stand-alone driver.  You just need to download and use the File->Tools->Import tool correct?
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  RainMachine Sprinkler Irrigation Controller Driver kblagron 50 3,419 06-01-2020, 01:18 PM
Last Post: Dean Roddey
  Russound MCA-66 on TCP driver lapointe.sc@gmail.com 5 327 05-24-2020, 06:23 AM
Last Post: gReatAutomation
  Samsung SmartTV Driver George M 0 102 05-20-2020, 09:04 AM
Last Post: George M
  OpenWeatherMap Weather Driver Using OneCall API kblagron 11 532 05-18-2020, 04:09 AM
Last Post: dlmorgan999
  Tesla Driver Driver kfly 10 1,042 05-08-2020, 08:49 AM
Last Post: gReatAutomation
  LIFX Driver bobskie708 15 6,191 01-05-2020, 11:00 AM
Last Post: simplextech
  Universal Devices ISY Insteon Driver wuench 369 175,606 12-28-2019, 05:15 PM
Last Post: simplextech
  RunTimer2 driver rbroders 18 7,917 10-17-2019, 04:38 PM
Last Post: rbroders
  Writing Driver - Varying commands based on checksum gReatAutomation 3 870 07-22-2019, 01:08 PM
Last Post: Dean Roddey
  Samsung HLxxA750 DLP Beta Driver jrunde 37 21,785 07-19-2019, 01:24 PM
Last Post: gReatAutomation

Forum Jump:


Users browsing this thread: 1 Guest(s)