PD70X available in USA

I just got my HD80.

I must say that I was just a bit hesitant earlier on, but I am very well pleased.

It came 3 days after I ordered it, just as they said it would. And it comes with everything at no extra cost - free shipping, a free set of 2500 mAh batteries, the car charger, and even a screw driver to use to install your own hard drive!

And mine must already have the new 2.1 firmware, because I inserted my 1 GB SanDisk memory stick, then turned on the power, and it started up, and copied the contents without me having to do a single thing.

I didn't even format the hard drive I used. I had a 20 GB Toshiba from an older device that would not read my 1 GB SanDisk memory sticks, and it was already formatted FAT32, so it just worked as it was.

And the HD80 is FAST. The memory stick was only about 1/4 full (250 MB), but it only took about 40 seconds or so to copy. My old one would take about 5 minutes to copy a mere 128 MB, and the battery would only last long enough to copy about 4 or 5 128 MB memory sticks.

So I am completely satisfied with the HD80. If any of you are hesitating, waiting for something, then wait no longer - order one.
 
Does hard drive speed affect download speed? Is a 7200 rpm drive provide a faster download than say a 4200 rpm drive and is heat and or power consumption an issue with a 7200 rpm drive? sorry if this has been asked before.

One more question when attached to a computer can it be used as a external HD that can be wrote to/from and mounts on the desktop?

oh and when will the mini be available ? and will it play .m4a files? ;-)

Thanks!

FOTOMAT

 
Does hard drive speed affect download speed? Is a 7200 rpm drive
provide a faster download than say a 4200 rpm drive and is heat and
or power consumption an issue with a 7200 rpm drive? sorry if this
has been asked before.
Yes, a 7200rpm drive will perform faster than a 4200rpm, about 15s faster for a 1GB transfer.

Heat is not an issue as the HyperDrive HD80 aluminum casing dissipates heat from hard disk very efficiently.

However a 7200rpm will consume more battery power than a 4200rpm, about 10~30% more.

Speed improvement is more evident when using a larger buffer cache hard disk. (e.g. 8MB & above). Hence a 5400rpm 16MB will be perform faster in the HD80 than a 7200rpm 8MB. A larger cache will not affect battery consumption in any way.

A good compromise between speed, battery consumption and price would be a 5400rpm 8MB hard disk.
One more question when attached to a computer can it be used as a
external HD that can be wrote to/from and mounts on the desktop?
Of course, it will function as an USB 2.0 external storage
oh and when will the mini be available ? and will it play .m4a
files? ;-)
We are trying to get the mini out just before x'mas, but no promises. No it does not play mp4.
 
The verification process is hardware based as the onboard
processors are used to encode bit by bit information to form a
checksum. The checksums are stored on the ROM and compared at
hardware level. This checksum represents the sequence of bit data
arrangement. A displacement of a single bit would result in a
different checksum and cause verification to fail, hence it is fair
to say that comparison is done at a bit-by-bit level.
as a computer engineer (for well over 2 decades) and someone who has done embedded systems, as well, I have to disagree with you.

bit-by-bit implies an actual 'compare' operation. technically, 2 files can be different and still have the same checksum or CRC or even MD5 sum. unlikely, but it HAS happened and can happen. very very rare, but still, not a 0.00% chance.

checksums stored in ROM? read-only memory? really? that might work once... ;)

--
bryan ( http://www.grateful.net ) pics: http://www.flickr.com/photos/linux-works ,
(sample fz30 raw files: http://www.netstuff.org ) ~
 
What a terrible design suggestion and for all the wrong reasons to
boot.

Formatting the card in-camera is an easy 3 second process. There
is no reason for you to be formatting the card in anything other
than the camera. It ensures that the card and the camera will work
together pefectly.
well-stated and you're spot-on. let the camera (the best device for encoding a format, since it is the primary USER of said format) do the work. camera should be the ONLY device to have write/delete access. all others - ALL - pc and drive-unit should be treated as read-only for least chance of screw-ups or corruption.
Formatting anywhere else is asking for trouble. Not every camera
implements FAT the same way.
or even special folders. some cams has a 'misc' folder and I'd rather the camera place it there, in its 'known good location' than some pc trying to be generic.

--
bryan ( http://www.grateful.net ) pics: http://www.flickr.com/photos/linux-works ,
(sample fz30 raw files: http://www.netstuff.org ) ~
 
manuf's make bad judgement calls all the time...

because some user asked for this, or some marketing droid though it would 'be cool', is no reason to assume its a good DESIGN and that its safe..

(MS has a history of adding features 'for fun' that end up being very dangerous. there are more examples in the industry like that, too)
What a terrible design suggestion and for all the wrong reasons to
boot.
Well, that's a bit rough! To be honest, you both are right, because
as users you want to operate in your preferred way, whioch happens
to be different.

The Epson P-2000 has the OPTION to delete files after transferring
from the CF, and it sounds like this is what HyperDrive should
offer ...
--
bryan ( http://www.grateful.net ) pics: http://www.flickr.com/photos/linux-works ,
(sample fz30 raw files: http://www.netstuff.org ) ~
 
With due respect, the auto delete feature in question here is disabled by default and will have to be manually enabled by the user if he so requires this feature.

We understand some photographers' need to streamline their workflow and we are just offering advanced users more options to make the HD80 more suitable to their needs, while a casual user can easily use the HD80 straight out of the box without needing to bother about these advanced features which are disabled by default.
manuf's make bad judgement calls all the time...

because some user asked for this, or some marketing droid though it
would 'be cool', is no reason to assume its a good DESIGN and that
its safe..

(MS has a history of adding features 'for fun' that end up being
very dangerous. there are more examples in the industry like that,
too)
 
With due respect, the auto delete feature in question here is
disabled by default and will have to be manually enabled by the
user if he so requires this feature.
that's the right design decision, I think. disabled by default but for the user who really demands it, fine, he can use it with some manual over-ride.

my only objection was to have it on, by default, since a lot of users probably don't realize the chance of data loss of doing any kind of write operation on data that hasn't been fully copied (to a safe area) yet.

since its not on, by default, on your product, I think that's a fair compromise.
We understand some photographers' need to streamline their workflow
and we are just offering advanced users more options to make the
HD80 more suitable to their needs, while a casual user can easily
use the HD80 straight out of the box without needing to bother
about these advanced features which are disabled by default.
manuf's make bad judgement calls all the time...

because some user asked for this, or some marketing droid though it
would 'be cool', is no reason to assume its a good DESIGN and that
its safe..

(MS has a history of adding features 'for fun' that end up being
very dangerous. there are more examples in the industry like that,
too)
--
bryan ( http://www.grateful.net ) pics: http://www.flickr.com/photos/linux-works ,
(sample fz30 raw files: http://www.netstuff.org ) ~
 
bit-by-bit implies an actual 'compare' operation. technically, 2
files can be different and still have the same checksum or CRC or
even MD5 sum. unlikely, but it HAS happened and can happen. very
very rare, but still, not a 0.00% chance.
A checksum is a summation of encryted blocks of binary (bit) data. While in theory, it is possible for 2 different files to have the same checksum, we employ a strong hashing algorithm that uses a comparably complex set of operations to generate a data digest or signature. While not every file will have a unique signature, the statistical likelihood of duplication is so small that, in practice, it does not happen. It's not 0.00% but it's lesser than 0.000000001%.
checksums stored in ROM? read-only memory? really? that might
work once... ;)
I stand corrected by you and my engineer, the hard disk space is used instead.
 
agreed.

its not a 100% guarantee of a clean file compare, but its very very close. I personally would feel safe with an MD5sum (or similar) saying that 2 files are the same.

but for the sake of accuracy in concepts, you still can't beat a TRUE bit for bit file compare.

you could have some speed boost if the files are all contiguous and you don't have to seek the drive heads back and forth as you go byte by byte, between the files. streaming a full file's worth of read requests SHOULD be faster and I'm sure that's why you/they chose this as their fastest verify mechanism. I'm assuming you don't have enough working memory to fully buffer a photo file, in its entirety, twice (once for the card version and once for the drive version of the same file). otoh, you could read 1/4 of the memory size worth of fileA and 1/4 of fileB, compare them, then dump the buffers and get the next chunk from each. or something like that.

also, I wonder which algorithm would detect bad compares faster. I think mine might. with the checksum method, ALL the file's contents have to be read, even if the bit error was on the first byte. on the true file byte-by-byte compare, the error would show up to the user right away with no need to keep reading further. just an idea for you..
bit-by-bit implies an actual 'compare' operation. technically, 2
files can be different and still have the same checksum or CRC or
even MD5 sum. unlikely, but it HAS happened and can happen. very
very rare, but still, not a 0.00% chance.
A checksum is a summation of encryted blocks of binary (bit) data.
While in theory, it is possible for 2 different files to have the
same checksum, we employ a strong hashing algorithm that uses a
comparably complex set of operations to generate a data digest or
signature. While not every file will have a unique signature, the
statistical likelihood of duplication is so small that, in
practice, it does not happen. It's not 0.00% but it's lesser than
0.000000001%.
checksums stored in ROM? read-only memory? really? that might
work once... ;)
I stand corrected by you and my engineer, the hard disk space is
used instead.
--
bryan ( http://www.grateful.net ) pics: http://www.flickr.com/photos/linux-works ,
(sample fz30 raw files: http://www.netstuff.org ) ~
 
Got my HD80 today as stated, Thank you.

The files started to copy about 5 seconds or so after I inserted the CF without me touching a knob. I guess that means I don't need to update the firmware.
Q1: is the copy verification ON by default?

Q2: will it harm anything if I leave the batteries in the "charging state" overnight. The manual stated that one has to disconnect to end charging, it also stated the the intelligent charger will end if battery is full etc... so I am a little confused.

Thank you. I must say I like the unit. .I'd say I am 100% satisfied if the screws and HD bracket are a notch higher in quality and align better. But no big deal as the HD installation won't happen too often.
 
If I may be so bold as to answer...

Q1 no verify is not on. You have to choose it each time.

Q2 The timer for charging turns off after a fixed time. No problem with leaving the unit plugged in. I´m pretty sure based on tests some users have made that there is very little checking of the batteries after it has started the charging process. The checking that happens at the beginning checks to see if you have alkalines or lithiums in. Once the unit deems the batteries as rechargeables (and not alkalines or lithiums) then it starts charging on a timer. The unit won´t charge after the timer runs out. So you are safe.

Stop reading here unless you want more info on batts and my situation.

If you truly want your batteries to charge fully, then you will need a charger that charges the batteries individually. Fancier chargers measure each battery before and DURING the charging process. This unit is trying to be OVERLY careful while charging batteries. They are so careful, that my batteries almost never get charged by the PDX70. The unit tries to analyze my batteries, and because it is a little unsure, it won´t start the process. It´s being too cautious. If it were not too cautious then the result would/could be disasterous. I accept that. I know they are working on firmware to be able to check batteries before charging even better, and that´s cool, too. It will be nice to charge my batts from the power adapter, but it´s no big deal for me to get juice from my 1 hour charger AS I use the pdx70 as an external hard drive. As far as I can see, charging batteries while one uses the unit will never be a feature.

Guy Moscoso
Got my HD80 today as stated, Thank you.
The files started to copy about 5 seconds or so after I inserted
the CF without me touching a knob. I guess that means I don't need
to update the firmware.
Q1: is the copy verification ON by default?
Q2: will it harm anything if I leave the batteries in the "charging
state" overnight. The manual stated that one has to disconnect to
end charging, it also stated the the intelligent charger will end
if battery is full etc... so I am a little confused.

Thank you. I must say I like the unit. .I'd say I am 100% satisfied
if the screws and HD bracket are a notch higher in quality and
align better. But no big deal as the HD installation won't happen
too often.
 
Actualy... from what I've read in the manual, and at the eastgear site, etc... The PD70X does have a delta-V (change in voltage) peak detection charging scheem... however based on posts to this fourm, it seems it also has a maximum charge time that is generaly shorter then the amount of time it actualy takes to fully charge most of todays higher capacity rechargables... so what typicaly happens is the user starts charging, the PD70X reaches it's time limit for charge, before it ever sees the Delta-V it's looing for...

One realtively easy resolution to that issue would be to start the charge process more then once... With any luck, the Delta-V would be reached during the second charge cycle, before it reached it's second charging time limit.
Q1 no verify is not on. You have to choose it each time.
Q2 The timer for charging turns off after a fixed time. No problem
with leaving the unit plugged in. I´m pretty sure based on tests
some users have made that there is very little checking of the
batteries after it has started the charging process. The checking
that happens at the beginning checks to see if you have alkalines
or lithiums in. Once the unit deems the batteries as rechargeables
(and not alkalines or lithiums) then it starts charging on a timer.
The unit won´t charge after the timer runs out. So you are safe.

Stop reading here unless you want more info on batts and my situation.

If you truly want your batteries to charge fully, then you will
need a charger that charges the batteries individually. Fancier
chargers measure each battery before and DURING the charging
process. This unit is trying to be OVERLY careful while charging
batteries. They are so careful, that my batteries almost never get
charged by the PDX70. The unit tries to analyze my batteries, and
because it is a little unsure, it won´t start the process. It´s
being too cautious. If it were not too cautious then the result
would/could be disasterous. I accept that. I know they are working
on firmware to be able to check batteries before charging even
better, and that´s cool, too. It will be nice to charge my batts
from the power adapter, but it´s no big deal for me to get juice
from my 1 hour charger AS I use the pdx70 as an external hard
drive. As far as I can see, charging batteries while one uses the
unit will never be a feature.

Guy Moscoso
Got my HD80 today as stated, Thank you.
The files started to copy about 5 seconds or so after I inserted
the CF without me touching a knob. I guess that means I don't need
to update the firmware.
Q1: is the copy verification ON by default?
Q2: will it harm anything if I leave the batteries in the "charging
state" overnight. The manual stated that one has to disconnect to
end charging, it also stated the the intelligent charger will end
if battery is full etc... so I am a little confused.

Thank you. I must say I like the unit. .I'd say I am 100% satisfied
if the screws and HD bracket are a notch higher in quality and
align better. But no big deal as the HD installation won't happen
too often.
 
Good suggestion Glenn. That seems like a simple way to acheive a good result.

Guy
 
The manual did say charging will stop is voltage starts to drop, or reached 4h. and one more, which I don't recall now. In my first charge last night, it stopped at 4h. I am going to charge it again tonight and see what happens. thank you all for help.
 
The manual did say charging will stop is voltage starts to drop,
That is the -dV detection at work. NiMH battery voltage are observed to increase during charging and plateaus when nearing full capacity. Most detection methods stops when the voltage plateaus but a more accurate method of detecting full capacity is to observe this slight dip in voltage which only occurs at the late end stage of full charge.
reached 4h. and one more, which I don't recall now. In my first
charge last night, it stopped at 4h. I am going to charge it again
tonight and see what happens. thank you all for help.
The charging current of the HD80 is 800mA, theoretically, it will take 2500/800 = 3.125 hours to charge discharged 2500mAh cells, hence a 4 hr cutoff time is reasonable to ensure that overcharging does not occur.
 

Keyboard shortcuts

Back
Top