Not recognizing my model (VN-480PC)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Everytime I run it (compiled or not) with libsndfile-dev and libusb-dev
from the Ubuntu repos, it tells me that its an unknown device. I ran it
both as root and as normal user.

On what operating system?

Kubuntu 7.10 Gutsy Gibbon.

Original issue reported on code.google.com by baseball...@gmail.com on 9 Jan 2008 at 10:10

[GoogleCodeExporter]

Here's a development version that might fix your problem. Please copy in the 
output
of the runs, as well as trying running it with both 'odvr -l' and 'odvr -rl'. 
Please
also post the output of 'lsusb -v -d 07b4:020d'.

MD5:
a6d90b321f7d7455e1e293558251cde3  odvr-r433.tar.gz

Original comment by tristan....@gmail.com on 9 Jan 2008 at 10:30

• Changed state: Accepted

Attachments:

• odvr-r433.tar.gz

[GoogleCodeExporter]

Hmm, I got the following error when running make (didn't have it before):
http://pastebin.com/f6c3fb888

Trying to get a list of the files (sudo ./odvr -l) gave:
Couldn't query model name: timed out writing to EP2 (device out of sync?)

Running with -rl gives the same output.

Lastly, lsusb -v -d 07b4:020d:

http://pastebin.com/d10f7b5a3

Original comment by baseball...@gmail.com on 9 Jan 2008 at 10:40

[GoogleCodeExporter]

The build error is related to building the 32-bit code and libsndfile may 
require
FLAC. If you can build 'odvr' then there's no problem (the 'odvr.x86' target is
important to building a static 32bit x86 build only).

You seem to be running into the same problem that users of the VN-120PC and 
VN-240PC
are experiencing. I'd like to get a usb sniff from you if I can. Here's how to 
get
one (run as root):

$ BUSNUMBER=`lsusb -d 07b4:020d | perl -ne 'print $1 if /^Bus\s+0*(\d+)/'`
$ mount -t debugfs none_debugs /sys/kernel/debug
$ modprobe usbmon
$ tee usbmon.log < /sys/kernel/debug/usbmon/${BUSNUMBER}u

Start running odvr after the tee command. Use "odvr -rl" to get a nice clean 
dump.

I hope to get this issue resolved soon.

Original comment by tristan....@gmail.com on 10 Jan 2008 at 12:11

[GoogleCodeExporter]

Hmm, the USB sniff didn't dump usbmon.log anywhere in /sys/kernel/debug/usbmon/
(there are no subfolders). However, I got a new error (this is progress, 
right?):

Failed to open Olympus device: couldn't set configuration

So now it can see it, just not open it.

By the way, I came across odvr because someone at the Ubuntu Forums actually 
got my
device working with your software:

http://ubuntuforums.org/showthread.php?p=4104626

Original comment by baseball...@gmail.com on 10 Jan 2008 at 12:19

[GoogleCodeExporter]

Dump usbmon.log into your home folder or somewhere writable.
/sys/kernel/debug/usbmon/ should be a read-only location. As for why the device
couldn't set the configuration anymore, I don't know. It is an interesting
observation, so I'll give it a shot on my VN-960PC.

Thanks for the forum thread link (I use Ubuntu too).

Original comment by tristan....@gmail.com on 10 Jan 2008 at 12:35

[GoogleCodeExporter]

Since this issue seems related, try this updated version:

http://code.google.com/p/odvr/issues/attachment?aid=2012876708303562199&name=odv
r-r436.tar.gz

Please run this as "odvr -rl" and try "odvr -r" followed by "odvr -l" and post 
the
console log.

Original comment by tristan....@gmail.com on 10 Jan 2008 at 1:23

[GoogleCodeExporter]

OK, three things. First, it dumped a bunch of files in ~/debug (where I sent 
the log
files). A ZIP will be uploaded, it's just taking forever to copy from ~/debug.
Second, the tee command sent a bunch of stuff to the terminal
(http://pastebin.com/ff35d39c). Third, running the ./odvr -rl as root command 
gives
the following error:

Couldn't query model name: timed out writing to EP2 (device out of sync?)

Running as a normal user still gives:

Failed to open Olympus device: couldn't set configuration

Original comment by baseball...@gmail.com on 10 Jan 2008 at 1:26

Attachments:

[GoogleCodeExporter]

Sorry, that was in reply to comment #5. I'll try the things in 6.

Original comment by baseball...@gmail.com on 10 Jan 2008 at 1:26

[GoogleCodeExporter]

First, it "maked" without error. Here's the commands you told me to run:
http://pastebin.com/f16e75e79

The usbmon stuff is still copying...

Original comment by baseball...@gmail.com on 10 Jan 2008 at 1:32

[GoogleCodeExporter]

You need to install "41-odvr.rules" into /etc/udev/rules.d/ and reload udev in 
order
to run as a regular user (it changes the permissions on the DVR USB-to-userland 
device).

I really should make this more clear and have an install target :P.

Original comment by tristan....@gmail.com on 10 Jan 2008 at 1:38

[GoogleCodeExporter]

OK, it's installed. Now both root and normal user give this on running ./odvr 
-l:

Couldn't query model name: timed out writing to EP2 (device out of sync?)

The usbmon.log is still missing. I can't find it anywhere. Even though I told 
tee to
spit it to ~/debug.

Original comment by baseball...@gmail.com on 10 Jan 2008 at 2:15

[GoogleCodeExporter]

What about "odvr -rl" output?

As for the log, I don't know why it's taking so long. Try dumping it like this 
(w/o tee):

$ cp /sys/kernel/debug/usbmon/${BUSNUMBER}u ~/debug/usbmon.log

Use CTRL-C to stop it from logging.

Original comment by tristan....@gmail.com on 10 Jan 2008 at 2:19

[GoogleCodeExporter]

Now it's starting to copy... but it's currently frozen at copying 0 bytes. I 
think
something's messed up with the file, because nothing can seem to access it.

The -rl gives:
Resetting...
Model: VN-480PC
Couldn't get file count on Folder A: unknown DVR status code
Couldn't get file count on Folder B: unknown DVR status code
Couldn't get file count on Folder C: unknown DVR status code

Original comment by baseball...@gmail.com on 10 Jan 2008 at 2:30

[GoogleCodeExporter]

I'd really love to get a copy of that usbmon log when you get that "unknown DVR
status code" error. Keep whacking at it until it works.

Original comment by tristan....@gmail.com on 10 Jan 2008 at 2:55

[GoogleCodeExporter]

Updated to print unknown DVR status codes:

11520f8cf60a3ac7355ffb067fac3e19  odvr-r437.tar.gz

Original comment by tristan....@gmail.com on 10 Jan 2008 at 4:39

Attachments:

• odvr-r437.tar.gz

[GoogleCodeExporter]

Scratch that old one. Here's a version with tracing built in (not as much 
information
as a wire sniff, but good enough for now).

7036fc9d885b2ea32076470ee20a4443  odvr-r438.tar.gz

Original comment by tristan....@gmail.com on 10 Jan 2008 at 9:31

Attachments:

• odvr-r438.tar.gz

[GoogleCodeExporter]

I forgot to add that you should run it as "odvr -rlD" (-D is the new option).

Original comment by tristan....@gmail.com on 10 Jan 2008 at 9:32

[GoogleCodeExporter]

OK, here's the new output:

Failed to open Olympus device: couldn't locate device (unknown product ID?)

Both for sudo and normal users.

Original comment by baseball...@gmail.com on 11 Jan 2008 at 2:19

[GoogleCodeExporter]

If odvr says that, make sure the device is plugged in and Linux can see it 
(check
with "lsusb"). It could be that the firmware on the DVR got locked up, or as 
simple
as the connector was loose.

Original comment by tristan....@gmail.com on 11 Jan 2008 at 8:37

[GoogleCodeExporter]

Here's the latest snapshot too.

1a26ce848118ed3f33e64e2c3b528815  odvr-r441.tar.gz

Original comment by tristan....@gmail.com on 11 Jan 2008 at 8:43

Attachments:

• odvr-r441.tar.gz

[GoogleCodeExporter]

No duh... it wasn't plugged in! I'll get the output as soon as possible.

Original comment by baseball...@gmail.com on 11 Jan 2008 at 8:54

[GoogleCodeExporter]

I've gotten positive feedback on issue #5, so I'd like you to test out this 
latest
snapshot. Try with and without "-r" options. If you manage to get it working, 
give it
a good workout. I'd like to release a new version on the front page soon. As a 
note,
this will reset your device at the end, so you'll get that "couldn't locate 
device"
error if you try to run them back-to-back without a small delay.

db95aa60638c3292ff40837d20e322b9  odvr-r445.tar.gz

Original comment by tristan....@gmail.com on 11 Jan 2008 at 11:51

Attachments:

• odvr-r445.tar.gz

[GoogleCodeExporter]

There's a new release (v0.1.2) out. I suspect it'll fix your issue since it 
fixed the
 VN-120PC and VN-240PC model problems.

Original comment by tristan....@gmail.com on 14 Jan 2008 at 2:36

[GoogleCodeExporter]

YES!!!!!!!! It finally works. Thank you so much.

Original comment by baseball...@gmail.com on 15 Jan 2008 at 10:23

[GoogleCodeExporter]

Awesome. :)

Original comment by tristan....@gmail.com on 15 Jan 2008 at 10:27

• Changed state: Fixed