Indigita AVHD IEEE 1394 Hard Disc Drive - Page 11

Works fine with the new Mitsubishi's.

My model is LC32D5U with built in Tv guide that either controls a VCR or an I-link device (I-link can only record digital programs).
When the 2160 actually records something it will always playback O.K.
The TV only has 3 setup menus for the I-link device but changing these will not make the 2160 record after it is semi-hung up (tends to hang up after a Tv guide download has occurred).
I just disconnect and re-boot the 2160 and it will work fine (for a while).
When it "hangs up" it will record some programs/channels but only a few ??
It thinks it's recording (time is counting) but there is nothing there after ?
Reset and it works fine for both manual & timer recordings on all channels !!
I think the TV sends a command that puts the 2160 in some strange mode ??

I am not too familiar with the Mitu's... Weren't some people in here complaining about all subchannels being recorded? Is this true with the new Mitu's?

It would be fine for me... However, my in-laws aren't very 'tech savvy' so I want it to be as easy as possible to operate.

Should I just make them buy the LG or Sony high def recorder instead of something like the dvr2160?...

Thanks for any replys!

any thoughts?...

To verify the problems we are having with 2004 models (xx525, etc.), what key sequence are you using to bring up the three options that allow you to put the DVR into "live TV" mode?

Thanks.

My understanding is that the "record all sub-channels" problem is unique to the 2004 model line. I have been told that prior generations NOR this year's models experience this problem. (sigh)

Wilson-Flyer- Unfortunately, the "record all sub-channels problem" is definately NOT unique to the Mits 2004 model line. It's there on my 2002 WS-65869, which I think was the first year for firewire and NetCommand on the Mits RPTVs. I don't think Mits considers it a defect since they incorporated a way to switch among the subchannels on playback (Guide Button). Bad design decision sure, but not a defect. Was there anyone reporting any model Mits didn't record all subchannels? If so, we need to confirm that it wasn't because there just weren't subchannels on what they were recording. --hourglass

PS No, my model Mits can't put the 2160 in "live" mode either (I just know you'd want to know!)

Thanks hourglass

My mistake. I think it's just the 2005 models that don't dump all subs.

I got this problem confused with another problem I'm having that won't allow me to switch inputs (watch something ELSE) while recording via FW from an ANT input. How stupid is that!!! That was the problem that didn't exist on MOST prior and supposedly all subsequent generations of sets. Sorry 'bout that.

BTW, I certainly DO consider it a defect when it reboots or locks up Mits' own recorder sometimes when it's recording. The sheer volume in the stream sends my DVHS 2000 into oblivion sometimes. Unacceptable. I certainly consider the fact that I can't switch to another input and watch something totally unrelated while I make a 4 hour recording of the Opening Ceremonies that I could watch anytime once recorded a defect too.

& Hourglass....

If I think I know what you mean about "Live Tv" is watching what you are recording....I will ASSume that...

My Mits will let me time shift but how I do it is by starting the recording, switch to the DVR "device" then go to the guide and scroll to the recording in progress (or a show that was recorded before) and hit play....it will continue to play & record and you can stop, pause etc.

Hope that was what you all were asking...

Thank you. I will give that a shot. I don't think that was RCA's intent since they provided a methodology via HAVI to put the DVR in a certain mode (1-3) with 3 being "Live Buffered TV" mode and Mits provides no ability to make that switch.

What you do certainly sounds like a somewhat workable solution. I will gladly give it a try.

Now if you could just tell me how to watch another input while FW is recording... (sigh). Ain't that the STUPIDEST thing you've ever heard of?!?!?!

The DVR has no such modes. It has 2 input and 2 output plugs.

TV connects them as it wishes, which would (theoretically) enable you to record 2 and watch 2 programs at once assuming there is enough bus bandwidth and TV firmware supports it. The DVR has no idea if you're watching live TV, recording to archive, timeshifting, etc.

I know, useless technical detail, but I just thought I'd make that clear.
If the box isn't doing something, don't look at the box - look at your TV.

I'm quite aware of that and I believe my posts reflect that.

This is my first entry. I have the Indigita AVHD250 and it works fine with my Mitsubishi WD-62628. My need is to get my HP MCE PC to communicate with this AVHD device. When I connect via the firewire my PC recognises the AVHD by nwme, but cannot locate a driver and therefore does not list the contents. Will the AVHDDPlayer accomplish this?

Agree with you regarding the input issue.....just like I commented in the other forum you have been discussing this issue....I can change inputs but I can't record OTA or Cable through the tuner due to the wonderful design of passing all of the subchannels....

As for the modes (1-3), I can't get to that either but my solution is a good workaround.... hope youe try it!

NO.unfortunately! At least with the little time I played with it last night. AVHDDPlayer will load a driver that recognizes the DVR2160 correctly but when I open the application that comes with it.I have a VB runtime error then it closes.

Anyway it looks like this app is for controlling data transfer from/to DVR and a DVHS.unfortunately not to the PC which is currently my quest! This is the one good thing about my Mits. I can already do the above with my Mits through the netcommand.

But I would love to be able to extract the files from the DVR to my PC and also find out the way to replace the drives in the DVR! Someone has to be working on this somewhere!

You are correct. AVHdd player is for controlling a network of AV/C compatible devices and managing plugs/connections between them, not for streaming to PC.

I'm kinda saddened about the VC++ runtime error on AVHDDPlayer + DVR2160, its forcing me to basically rewrite the entire AVHDD Player app just to be able to control the DVR and dubbing to DVHS/another DVR. I contacted the company who designed the software and talked with one of the programmers but they weren't really hot about fixing it... because it's "unsupported". The error is caused when the app tries to read Root Contents List on 2160, while their implementation is perfectly valid, its different from Panasonic AVHDD it was written for, so it causes a problem.

it might work with DVR250 or whatever, but its for control only.

Wonder if anyone has taken the time to remove the HD and connect it to a PC to try to find out what the OS is, copy files or at least get the info to put on a new larger drive?

(A brief follow up: HDToystore shipped a new RCA 2160 and arranged for a pickup of the original sent unit.)

The new RCA 2160 was immediately recognized by the Promise module and I was able to record a CSI episode with no errors.

There are several issues which I have been unable to resolve:
1. The only menu screens availble are those in Netcommand 2.0 There is no way to access the menu where you select between the 3 record modes as described in the RCA manual.

2. When I review the list of recordings in Netcommand the date recorded is 1/7/2001!!! There seems to be no way to set the date in the 2160, nor the Promise module, nor the ws65907.

I plan on calling both Mitsubishi and RCA to try to get some answers.

Does anybody have any suggestions??? Is the date set in the service mode in the Promise module??? The ws65907??? The 2160??? The PSIP information???

Thansk in advance

All the time/date/tv guide information is controlled by your tv. The RCA doesn't really know anything, it just does what the tv tells it to do.

Urodoc- see this post to fix the date problem-

http://www.avsforum.com/avs-vb/showt...&&#post6918896

--hourglass

I made a disk image after I received mine.
I've been busy with other things so its just sitting there.

The filesystem, as with all other AVHDD devices, is a custom job which will not be readable on a standard PC. All the content regardless of its copy status is written to hdd encrypted using C2 block cipher (by the spec, of manufacturer is free to implement their own encryption), so chances of getting that out even if you did know the filesystem structure is very low.

From what I heard/read somewhere upgrading drive is not an option either because of some special setting in drive firmware which has something to do with copy protection.

Does anyone know if the RCA 2160 is compatible with the dual ISDB tuner built into the Sony KDL-L40HVX, or any HVX series (last year's JDM models) for the matter? I know the similar I-O Data REC POT F series recorders and Sony VRP-T5 are compatible with the HVX. Just wondering if anyone here has tried the RCA 2160 / Sony HVX combo.

Great work..what did you use to copy the image? Wonder is the image could be dropped onto a new 160Gb drive in the event of a HD failure..ever tried it? If the drive size can not be changed at lease if we can replace the drive, that would be better than having to buy a new 2160 if the drive failed.

I took the drive out (since mine had a loose screw to begin with, so I had to open it anyway) and used ghost8 to make the image.

I don't think you can just write the image on a new hdd, since like I said, some setting in drive firmware is also needed (which is why if you read earlier in the thread theres response from someone who called indigita and was told that hard drive is "not user replaceable".

Also as some have noticed (and what somewhat interested me) is that plugged into a PC the 2160 shows up as a SBP2 device with a 1gb "unknown" partition. There's also this "unknown" device that shows up on 1394 bus, with device instance ID of 1394\\30dd&1\\8b81b033ef951000.. Hmm the last number is the EUI64 of my unit inverted (0x001095EF-0x33B0818B)... Anyway, not sure what that device does, perhaps some kind of control method other than AV/C.

Unfortunately the fix does NOT work for the Promise Module. I tried it even though I knew that it would not work. The Promise Module has it's own clock setting independent from the analog clock setting. With a power outage the Promise module clock must be reset separately even though the clock setting for the main TV has already reset from the PBS channel.

I then called Mitsubishi to talk to technical support. What a waste of time and effort!!!! The woman I spoke to had no real clue and had to speak to someone else several times. She then insisted that there is no way to program the date in the Promise Module. She stated that the incorrect dates are coming from the 2160 not the Promise Module. She then stated that I do not have Netcommand. When I told her that I have a Netcommand manual, in addition to the Promise Module manual which shows the Netcommand screens I knew I was in trouble. No matter how I tried to explain to her that there were pictures of the List screen with dates (10/16/01) for AVDisc even though Mitusibishi had not even released an AVDisc at that time. I tried to get service code information for setting the date but she kept on insisting that the date was coming from the 2160.

Needless to say the issue is being bumped up to the next level of support. Fat chance that I will get any results.

I tried to locate a Promise Module service manual on google but I could not find one. Does anyone have a good source???

Is it possible that in the absence of a date from the Promise Module, the 2160 is simply starting at 01/01/01 and incrementing from there, and Netcommand is reading what the 2160 placed on the recording track?????? I'm thinking of disconnecting the 2160, reattaching the 2160, making a recording and checking the date. If it goes back to 01/01/01 wouldn't suggest that the date was in fact supplied by the 2160 in the absence of a true date????

I'm also going to call RCA so that I can be shot down there also.

I have to belief that there is a service mode setup in either the Promise Module or the 2160 which allow one to set the current date.

Any ideas?????? Is there any value to try to contact Indigita????

When I first powered up the DVR2160 its recordings were dated as 01/01/01. Now I suppose that could have come from the date in my Mits HDTV never having been set, but I would think if it were the date in the Mits it would have incremented since my last powercycle. Here's what I saw-

http://www.avsforum.com/avs-vb/showt...&&#post6916311

--hourglass

I just got of the phone with RCA Thomson support and I learned the following information:

1. There is absolutely no way to input the date and time into the DVR 2160 directly.

2. In the absence of any date information the DVR 2160 defaults to 01/01/01 and increments daily.

3. The date information is derived either from the TV or cable box. They suggested that if I hook the unit to a cable box the date will be set. Unfortunately NO cable box. OTA only.

I'm going to try to hook up the 2160 daisy chained through my Mitsubishi HD 2000 D-VHS unit. The time is set on this unit by PBS. Maybe I can extract the information from the D-VHS unit rather than the Promise Module. Who knows??

Has anyone hooked up the 2160 to a computer. Even if it's not possible to read the data on the 2160, can it read the date and time information from the computer and set it in the 2160. That would certainly resolve the issue and be useful when the analog PBS stations are shut down.

Still waiting for Mitsubishi call back.

If anyone has other ideas I'm all ears.

Thanks

I too imaged my DVR2160's drive... and took it one step further.

I just happen to have a Maxtor 160GB drive (different model number but one that has the same LBA count) hanging around and I moved the "out of the box" DVR2160's drive image to my spare drive. I used g4l (a.k.a. ghost for linux) which made a complete sector by sector image of the drive.

I then installed the imaged spare drive into the DVR2160. Most of my olympic viewing was watching what the "altered" DVR2160 captured.

So there is some hope for the "what happens when my drive dies" case.

orly, thats pretty interesting.
Well its only matter of time before someone figures out how to make this accept a smaller HDD.

By the way how big was your image? Did you do a full sector copy and compress it, or just dupe it to another drive? Mine came around ~4gb compressed using "high" compression in ghost.

I had g4l do a sector by sector copy and told it to use bzip2 on the generated image. The resulting image was also around ~4GB in size.