Oppo Blu-ray Player Driver

Topics for MLServer Device Drivers

Oppo Blu-ray Player Driver

Postby CinemarDave » Sun Sep 09, 2012 2:33 pm

We have released a driver for the Oppo line of Blu-ray players. Provides full two-way control of the player. It is a member of the A/V family. If anyone has one of the Oppo players please feel free to test drive it and let us know how it works. We do not have an Oppo player here to test with.
User avatar
CinemarDave
Site Admin
Site Admin
 
Posts: 9362
Joined: Fri Feb 07, 2003 8:56 am
Location: Planet Earth

Re: Oppo Blu-ray Player Driver

Postby monteourdog » Fri Sep 14, 2012 9:05 pm

Fantastic, an Oppo driver!

I downloaded and installed but I am not sure of a few things:
1) Viewing the "Oppo Driver" in "Family Device Drivers", I cannot make the "serial port" sitck (always gets blanked) and I have the error: "PopulateDevices - Error at PopulateDevices at line #175 - Invalid key" in the log.
2) In "Family Manager", I see the Oppo driver, I can select the port - but then what? Can you provide a list of commands?

Cheers!
monteourdog
Senior Member
Senior Member
 
Posts: 164
Joined: Sat May 20, 2006 5:03 am
Location: ONTARIO, CANADA

Re: Oppo Blu-ray Player Driver

Postby CinemarDave » Fri Sep 14, 2012 10:40 pm

There should be an AV-Oppo option in command builder that has all the commands. But first I'll have to look at the serial port issue in the morning. Good to know that someone has an Oppo we can test with. I'll post an updated driver in the morning.
User avatar
CinemarDave
Site Admin
Site Admin
 
Posts: 9362
Joined: Fri Feb 07, 2003 8:56 am
Location: Planet Earth

Re: Oppo Blu-ray Player Driver

Postby CinemarDave » Sat Sep 15, 2012 10:14 am

The driver has been updated and the illegal key error is gone. If there are still issues I would like to debug this driver by remoting into your server if possible.
User avatar
CinemarDave
Site Admin
Site Admin
 
Posts: 9362
Joined: Fri Feb 07, 2003 8:56 am
Location: Planet Earth

Re: Oppo Blu-ray Player Driver

Postby monteourdog » Wed Sep 19, 2012 6:28 am

I have had a chance the past 2-nights to try the updated driver. Firstly, I just wanted to say (unrelated) that the "Command Builder" in the scene designer has come a long way since I tried it back in the early days (I had been scared off because building a command would overright the current command...all of it!) - good job!

I had some issues with identifying the port number. My Oppo had been working using a serial plugin from Tallus under ML3. ML4 has never seen my Oppo and this is what I am working on now. In any case, once I had the port worked out, selecting it from the "Family Manager" worked very well. All information entered in the FM automatically populated the Oppo driver in "Family Device Drivers". And a try of Power~Toggle (iPad) created a few variables using the prefix "AV_" followed by the item # used in the manager - as in av_1_power, status, model...(and a few more variables that gets passed from the driver or the FM).

But then something happened. I think it happened about the time I used the remote or perhaps one time I had cycled the power or tray - not clear as to when this happened exactly, but I lost all variable updates of power status and tray status. I tried restarting ML4 and then restarting the server - no difference. Then, I deleted all the "av_1*" variables and started fresh (Server restart, Oppo set to off). Once the server was up, I tried "power~on" from the iPad - no reponse. I tried eject - nothing. I used the remote to power up and stuck a disc in to see what happens. The following variables were created (but no others appeared as in power status or those supplied by the manager): audiotype, chapternumber, disctype, subtitletype, titleelapsed, titlenumber, videoresolution (all are prefixed with "av_1_") - ONLY.

Also, the control I had from the iPad (the first and only time I had power status variable and realtime status) is non-existant.

One thing I noted was the log from the Oppo driver. I can see the "ProcessCommand" and "SendCommand". It would be nice to see the reponses back from the Oppo (if anything, at least confirms sent-recieved-processed). If this is already present, then I think you are missing the "carriage return" at the end of what you are sending...maybe...it did work a few times. I have a thought that it might be the unsolicited responses (as in updates from remote control use) that might be causing an issue with the driver/server? It seems like I am stuck right now because the "control" I had at first, is not what it is now and I can't repeat the first time experience (sigh).

I have no problem for you to browse into my computer and see if you can get this working. But, I do have a few concerns. Firstly, I am in China. For now, my home but I am not Chinese. I mention this because Internet usually is very bad here. Given the time difference, you would likely be logging in while the bulk of China sleeps...which means more bandwidth..less problem...knock on wood. Expect drops and severe occasional lag...maybe. Let me know what I need to install - this is my second concern (I have used LogMeIn back in the days my server lived in my real home - I can likely get that installed but is it even used anymore?). Just let me know what I need and PM me what I need to do.

If you think its possible to try and test by updates/testing/comments/updates/testing/comments/... - can do. BTW, if you want to try the same with an LG TV driver - yep, would be very happy to help you there as well.

Cheers!
monteourdog
Senior Member
Senior Member
 
Posts: 164
Joined: Sat May 20, 2006 5:03 am
Location: ONTARIO, CANADA

Re: Oppo Blu-ray Player Driver

Postby CinemarDave » Wed Sep 19, 2012 9:28 am

It sounds like the driver cannot access the comm port. If it was getting anything back from the Oppo you would see messages in the Oppo event log like ProcessResponse - RX: <<Oppo message>>. Since you are not seeing that it must not be communicating on the comm port. Turn on event logging to a file in the Oppo driver and restart MLServer. Try some Oppo commands and then email me the event log that gets created.
User avatar
CinemarDave
Site Admin
Site Admin
 
Posts: 9362
Joined: Fri Feb 07, 2003 8:56 am
Location: Planet Earth

Re: Oppo Blu-ray Player Driver

Postby bigDvette » Fri Jul 12, 2013 12:08 pm

Ok, last night the oppo driver worked fine. Not sure what Model to pick from the list since the driver and model boxes are not dependent drop downs.

Anyway, It seems to not be connecting.

I'm wondering if it is not sending the right baud information to the GC since when I set it to 9600 in the GC100 util and then start the driver it changes back to 19200. Anyway. Al that is in the log is

7/12/2013 12:04:01 PM TimerRefresh Family members changed. Refreshing Devices
7/12/2013 12:04:16 PM ProcessCommand Cmd=[2~Set~Verbose~3] Client=[]
7/12/2013 12:04:16 PM SendCommand TX: THEATERDVD|#SVM 3


It never receives anything. I have it talking to port 5000 on a GC100.

If I torn off the driver (uncheck), shut down MLServer, change the port to 9600 baud using the web interface for GC100, start MLServer, then go turn on the OPPO device driver while the OPPO is on, I get the stream of information and it seems to stay up.
bigDvette
Expert
Expert
 
Posts: 718
Joined: Thu Oct 12, 2006 12:19 pm

Re: Oppo Blu-ray Player Driver

Postby CinemarDave » Fri Jul 12, 2013 12:55 pm

When a GC100 device is used the drivers cannot change the baud rate set on the GC device. So the Oppo drive didn't change it to 19,200. There is probably something else going on. You should leave the Oppo driver logging to a file so we can see what happens the next time the system starts.
User avatar
CinemarDave
Site Admin
Site Admin
 
Posts: 9362
Joined: Fri Feb 07, 2003 8:56 am
Location: Planet Earth

Re: Oppo Blu-ray Player Driver

Postby bigDvette » Sat Jul 13, 2013 10:23 am

Oppo disconnected and nothing I do will have it reconnect. It is connected to a GC100 via serial

7/12/2013 11:44:12 PM ProcessResponse RX: <<UTC 000 183 T 02:51:25>>
7/12/2013 11:44:13 PM ProcessResponse RX: <<UTC 000 183 T 02:51:26>>
7/12/2013 11:44:14 PM ProcessResponse RX: <<UTC 000 183 T 02:51:27>>
7/12/2013 11:44:15 PM ProcessResponse RX: <<UTC 000 183 T 02:51:28>>
7/12/2013 11:44:16 PM ProcessResponse RX: <<UTC 000 183 T 02:51:29>>
7/12/2013 11:44:17 PM ProcessResponse RX: <<UTC 000 183 T 02:51:30>>
7/12/2013 11:44:18 PM ProcessResponse RX: <<UTC 000 183 T 02:51:31>>
7/12/2013 11:44:19 PM ProcessResponse RX: <<UTC 000 183 T 02:51:32>>
7/12/2013 11:44:20 PM ProcessResponse RX: <<UTC 000 183 T 02:51:33>>
7/12/2013 11:44:21 PM ProcessResponse RX: <<UTC 000 183 T 02:51:34>>
7/12/2013 11:44:22 PM ProcessResponse RX: <<UTC 000 183 T 02:51:35>>
7/12/2013 11:44:23 PM ProcessResponse RX: <<UTC 000 183 T 02:51:36>>
7/12/2013 11:44:24 PM ProcessResponse RX: <<UTC 000 184 T 02:51:37>>
7/12/2013 11:44:25 PM ProcessResponse RX: <<UTC 000 184 T 02:51:38>>
7/12/2013 11:44:26 PM ProcessResponse RX: <<UTC 000 184 T 02:51:39>>
7/12/2013 11:44:27 PM ProcessResponse RX: <<UTC 000 184 T 02:51:40>>
7/12/2013 11:44:28 PM ProcessResponse RX: <<UTC 000 184 T 02:51:41>>
7/12/2013 11:44:29 PM ProcessResponse RX: <<UTC 000 184 T 02:51:42>>
7/12/2013 11:44:30 PM ProcessResponse RX: <<UTC 000 184 T 02:51:43>>
7/12/2013 11:44:31 PM ProcessResponse RX: <<UTC 000 184 T 02:51:44>>
7/12/2013 11:44:32 PM ProcessResponse RX: <<UTC 000 184 T 02:51:45>>
7/12/2013 11:44:33 PM ProcessResponse RX: <<UTC 000 184 T 02:51:46>>
7/12/2013 11:44:34 PM ProcessResponse RX: <<UTC 000 184 T 02:51:47>>
7/12/2013 11:44:35 PM ProcessResponse RX: <<UTC 000 184 T 02:51:48>>
7/12/2013 11:44:36 PM ProcessResponse RX: <<UTC 000 184 T 02:51:49>>
7/12/2013 11:44:37 PM ProcessResponse RX: <<UTC 000 184 T 02:51:50>>
7/12/2013 11:44:38 PM ProcessResponse RX: <<UTC 000 184 T 02:51:51>>
7/12/2013 11:44:39 PM ProcessResponse RX: <<UTC 000 184 T 02:51:52>>
7/12/2013 11:44:40 PM ProcessResponse RX: <<UTC 000 184 T 02:51:53>>
7/12/2013 11:44:41 PM ProcessResponse RX: <<UTC 000 184 T 02:51:54>>
7/12/2013 11:44:42 PM ProcessResponse RX: <<UTC 000 184 T 02:51:55>>
7/12/2013 11:44:43 PM ProcessResponse RX: <<UTC 000 184 T 02:51:56>>
7/12/2013 11:44:44 PM ProcessResponse RX: <<UTC 000 184 T 02:51:57>>
7/12/2013 11:44:45 PM ProcessResponse RX: <<UTC 000 184 T 02:51:58>>
7/12/2013 11:44:46 PM ProcessResponse RX: <<UTC 000 184 T 02:51:59>>
7/12/2013 11:44:47 PM ProcessResponse RX: <<UTC 000 184 T 02:52:00>>
7/12/2013 11:44:48 PM ProcessResponse RX: <<UTC 000 184 T 02:52:01>>
7/12/2013 11:44:49 PM ProcessResponse RX: <<UTC 000 184 T 02:52:02>>
7/12/2013 11:44:50 PM ProcessResponse RX: <<UTC 000 184 T 02:52:03>>
7/12/2013 11:44:51 PM ProcessResponse RX: <<UTC 000 184 T 02:52:04>>
7/12/2013 11:44:52 PM ProcessResponse RX: <<UTC 000 184 T 02:52:05>>
7/12/2013 11:49:16 PM Network Remote player THEATERDVD has disconnected.
7/12/2013 11:49:16 PM tcp_Connect Error at tcp_Connect at line #627 - Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
bigDvette
Expert
Expert
 
Posts: 718
Joined: Thu Oct 12, 2006 12:19 pm

Re: Oppo Blu-ray Player Driver

Postby bigDvette » Sun Jul 14, 2013 10:39 pm

New version of oppo driver seems to be staying connected using the heartbeat. If it does disconnect will you try and reconnect?
bigDvette
Expert
Expert
 
Posts: 718
Joined: Thu Oct 12, 2006 12:19 pm

Re: Oppo Blu-ray Player Driver

Postby CinemarDave » Tue Jul 16, 2013 1:22 pm

Yes if it disconnects the next heartbeat request will try to reconnect.
User avatar
CinemarDave
Site Admin
Site Admin
 
Posts: 9362
Joined: Fri Feb 07, 2003 8:56 am
Location: Planet Earth


Return to MLServer 4 Device Drivers

Who is online

Users browsing this forum: Bing [Bot] and 1 guest