PDA

View Full Version : WFT-E2A - Initial Observations


cdesperado
20th of June 2007 (Wed), 18:05
Ok, so I have the WFT-E2a up and working. Here are some initial observations.


Software Goodies
For some reason, I expected an updated driver or some other form of software with the WFT. I dont know why, but I did. What you get is a CD with several folders of PDF files. The only software you need is the EOS Utility software that comes with the 1D3.

It comes with a (cheap looking) draw-string baggie and a very cool belt-clip pouch. You also get an "inclement weather" dust cap that fits over the USB port on the WFT. (The other USB port, remote port, and video ports are all easily accessible.)


Set Up/ Connection
Set up is pretty straight forward and relatively easy (unless you accidentally hit the wrong button on your camera and get to start over, which I did twice. Just pay attention, don't be in a rush, and it's pretty easy.)

You get three options: FTP, P2P, and HTTP. I set mine up as a P2P for now. I've been playing with it for about 30 mins and Im kinda digging it. Am I $1000 digging it? Hmmmmmmm. Tough question. Read on.


What do I Like?
I like being able to store an image to the card as well as to the laptop.
I like the ease of use - using the EOS Utility is pretty straight forward.
I like the responsiveness - if you change a setting on the camera, it changes on the EOS Utility immediately. (I expected a little lag)


What do I Not Like?
Being able to shoot from the PC in combination with Live View is sweet, no doubt. However, practically speaking I think it would be easier in the field just to shoot onto a card and transfer the files later. In a studio, it would be nice - I simply don't see this as being practical in the field (a sporting event, a wedding, outdoor location, etc).

The transfer rate is pretty quick, but not as fast as I thought it would be. It definitely isnt slow! I haven't timed it formally, but will do that 10 images or so later this evening.

When shooting remotely, there is a (very) slight lag when you clicked the shutter button on the laptop to fire the camera. I havent tested this in Live View mode, yet, but that is next.

The EOS Utility crashed four times as I adjusted settings from my laptop. In particular, when you make large adjustments to the aperture (say, moving from F5.6 to F11) or the shutter speed (from 1/80 to 1/4), it can cause issues. Also, the utility itself is a little slow as you have to click a button (>) to move forward incrementally.

At one point (after about an hour of testing), for an unknown reason, the camera lost connectivity to the LAN, which then caused the EOS Utility to crash. I tried re-opening the utility, but it gave an error and said no camera was connected. I turned the camera off, then on, and that re-established the connection.

Also, when using Live View and the WFT for a remote connection, I took a shot, which resulted in another lost connection. I tried several things to restore the connection, then decided I needed to turn the camera off. There were 2 images that were hung up in the ether (?) ... It's been several minutes and it still says
"Recording." The camera is off, so Im not quite sure what to do at the moment.

Hmmmmmm. If any of these non-Live View problems happened while shooting at a wedding, it would be DISASTER.


Real-World Uses
My intent is to use this in the studio to simplify the work-flow for product shots. I also plan to use it for interior architectural shots (another controlled environment). I could see this being used for astral-photography.

Many have talked about uses for weddings and macro photography. The latter does not seem very practical to me unless you were in very controlled conditions.

I cannot see the WFT and Live View being very useful for remote wild-life photography because there is a very noticeable lag between the camera and the laptop. In reality, you could use the monitor to verify your scene is what you wanted, but you would need a direct line of sight to the scene to ensure what you pop is what you get. (I have not tested Live View with a direct PC connection.)


Conclusion
This is going to sound like I am slamming the WFT. It's pretty cool, but based on two hours of testing, Im not sure I would trust this in the field.

In all honesty, the more I use this, the more I question whether this will speed up my studio workflow (for product and architectural shots) or not. I'm still testing it out. I found myself repeatedly going to the camera to make adjustments, then moving back to the PC to take the shot.

This could be user error (or inexperience?) on my part, but if you turn the camera off, then on, it seems like the camera gets a little quirky (confused) about images it has already transferred, asking to transfer "New Images" that have already been transferred. I never used the WFT-E1, so maybe this is normal.

Maybe I shouldn't draw any firm conclusions, but if any of you out there are "dying" to get the WFT-E2A, don't sweat it. Keep using your cards and manually transferring files. It's safer. (After 5 minutes, my 1D3 still says "Recording - Remaining Images = 2" ...... I turned the camera back On, and that went away. However, when I turned the camera Off, it came back. I think I am stuck in some weird loop. This happened when shooting Live View remotely through the WFT-E2A.)

Update
Ok, this is weird. Following the lock-up, I turned the camera back on with WFT still attached. There is still no connection, but the LAN light isnt red, isnt green, and isnt blinking green - it's off completely.

I waited a few minutes, then took a shot, but now the "Image Loading" light on the camera won't go off. It's just red.... as if it were still writing the image data to the card. If ANY kind of freeze happened during a wedding, it would definitely not be good.

I was expecting to have a lot of good news here, but I dont have a lot of confidence in this at the moment.

cdesperado
20th of June 2007 (Wed), 18:23
Second Update

I removed the WFT from the 1D3 - that enabled the camera to finish writing the image data. My guess is, it was trying to push the data through the WFT to the laptop, but since the WFT had no connection, the camera couldnt move the data, which resulted in the hung light.

The file was written to the card successfully.

My recommendation based on only a few hours of testing - if you use the WFT-E2a, you better be writing the data to a CF card as well, as a backup.

All of my problems happened while using a tripod mount and a direct line of sight from 1D3 to my laptop. I cannot help but wonder what would happen in a room full of other radio signals and physical objects in between the WFT and the laptop.

cdesperado
20th of June 2007 (Wed), 18:37
If anyone is interested, here is a quick timing study. It took 2 minutes and 10 seconds to transfer four images.

This was a total filesize = 54.2 meg.
Average file size per image = 13.5 meg.

joegolf68
20th of June 2007 (Wed), 19:06
Thanks for the review. I have thought from the beginning that the EOS Utility program is awful. It takes a long time to load once you double click it, and it appears to be a small homemade type program instead of some slick professional one.

You said you set this up with p2p, and I'd be curious to see if the same issues arise if you set it up under the http lan. Not that I know anything about this stuff, but I thought the http thing made it more like just another website type connection. I think my wireless printer is set up under http and it works fine (fast and efficient.)

As I said in a pm to you, there are too many places listing prices under $800 right now for me to go out and buy the in stock item for $200 more. Yeah, I'll have to wait until they are in stock at the other places, but even though I was in a hurry for this thing, I am realizing it is not all that I thought it would be.

I hope you continue to play with it and keep us updated. If this thing is only practical for downloading images wirelessly, well, that is just too much $$ for that. The lag time makes it almost impractical for any live shooting except for stills, which a wired remote would be just fine. I was hoping this would be practical for something like setting it up for hummingbirds and sitting in the house looking at the laptop, and the TV and taking some images the lazy way. Not good if there is any lag time that is noticeable.

Sounds like EOS Utility software needs some more work. There will be lots of annoyed folks if this is the case because $1K is not something to sneeze at for poor performance!

joegolf68
20th of June 2007 (Wed), 19:13
If anyone is interested, here is a quick timing study. It took 2 minutes and 10 seconds to transfer four images.

This was a total filesize = 54.2 meg.
Average file size per image = 13.5 meg.

Unacceptable. :(

cosworth
20th of June 2007 (Wed), 19:45
Do a test while NOT in P2P mode and tell us the difference.

Steve Beck
20th of June 2007 (Wed), 19:47
That seems about right. Try moving 55mb over a standard 802.11 b wireless connection from a laptop to another. Then you have probably lower power in the camera than a minipci card in a laptop. Still a great feature IMO.

cdesperado
20th of June 2007 (Wed), 20:04
I'll set up an HTTP connection next and jack with it and report back in an hour or so. I thought the P2P would (theoretically) be faster, but I could be mistaken.

Aside from business uses, my main interest in this was for wildlife photography in the field - but I would be lying if I said I hadn't thought about you're living room/hummingbird scenario (or a cabin/bird or cabin/deer, etc). In my case, I planned to set the camera up near a popular salt lick and watering hole, then back away from the camera about 30 yards or so. It's not practical to do this tethered to a remote. I thought using Live View would have beeen cool bc then I would need to maintain line of sight with the camera, but not necessarily the focal plane.

After testing the WFT this afternoon, I no longer think my original plan would work with any degree of certainty for the following reasons:
1.) I'm not really happy with the transfer rate
2.) Frequently, when the EOS Utility locked up, I physically needed to jack with the camera. There is no way this would work in the field bc if I had to approach the camera, I'd scare off any wildlife. I'd be better off sitting in a blind the way I would before.
3.) Losing connectivity between the camera and the laptop requires physical intervention with the camera (turn it Off, turn it On).

Based on the results so far, there is no way I would rely solely on the WFT-E2a at a wedding or a shoot such as a business event. The camera lost connectivity too many times and the EOS Utility locked up too many times.

Here's the kicker, just for grins and giggles - I'm going to try attaching an Ethernet cable to the WFT and see what happens. That might improve the transfer rate. However, if I am going to shoot tethered anyway, I may as well use the USB2port on the 1D3. The transfer rate over the Ethernet cable should be a LOT faster, but that isn't worth $1000 to me.

(It's too bad the 1D3 didn't come with the 4-pin Firewire port, but oh well.)

cdesperado
20th of June 2007 (Wed), 20:08
I dont think I mentioned this earlier, but for all practical purposes, the only thing I can think a combo of WFT and Live View would be useful for is Architecture shots or Product shots - a still scene, basically. In my opinion, Live View simply wouldnt work for stuff that is moving (like a flower in a breeze or a paparazzi or sports shooter using Live View while holding their camera over his head.

Now, using Live View without remote (ie, holding it in your hand) wouldn't work either bc of the Manual Focus requirement. (I think the 1D3 manual specifically states you need to use a tripod, but I cant remember.)

cdesperado
20th of June 2007 (Wed), 20:12
I just talked to an IT Networker friend of mine - he suggested trying the FTP format.

So... Im gonna try that first, then HTTP.

tfiorda
20th of June 2007 (Wed), 20:13
Unless I am having a senior moment, 55MB file size needs to be multiplied by 8 to get the size in bits not bytes. So then divide that result by 11Mb/s or 54Mb/s less a bit for packet overhead and assuming that you are connected at the highest bit rate, and you get 40 seconds to transfer that amount of data at 11Mb/s.

Since we all know we NEVER get the full rated speed on any WLAN or LAN connection, I think this xfer rate is fairly good. What was the receiving end s802.1 standard b or g? And what connection speed did you have? My guess is you were not connected at the highest data rate possible.

Tony...

MDJAK
20th of June 2007 (Wed), 20:17
Come on, cdesperado, what do you expect for a grand, something that works well ;) (j/k)

Appreciate you taking the time to be the beta tester for the forum. Hope you get it worked out and reliable.

mark

cdesperado
20th of June 2007 (Wed), 20:39
Do a test while NOT in P2P mode and tell us the difference.

My next test is FTP.

For those who are interested, first you need to set up IIS on your laptop. (This is an optional install on WinXP Pro.

To install IIS,
1. Go to Start > Control Panel > Add/Remove Programs
2. Add/ Remove Windows Programs
3. Select the IIS checkbox.
4. Let the wizard install.

I'm having issues with the camera's FTP settings, but will report back once I resolve the issue and can start testing again.

joegolf68
20th of June 2007 (Wed), 20:41
Do a test while NOT in P2P mode and tell us the difference.

Gee, maybe I will add a "please" to that as I'd like to hear also, please.

joegolf68
20th of June 2007 (Wed), 20:47
Unless I am having a senior moment, 55MB file size needs to be multiplied by 8 to get the size in bits not bytes. So then divide that result by 11Mb/s or 54Mb/s less a bit for packet overhead and assuming that you are connected at the highest bit rate, and you get 40 seconds to transfer that amount of data at 11Mb/s.

Since we all know we NEVER get the full rated speed on any WLAN or LAN connection, I think this xfer rate is fairly good. What was the receiving end s802.1 standard b or g? And what connection speed did you have? My guess is you were not connected at the highest data rate possible.

Tony...

Wow, you know more in a senior moment than I would in full bore youth! Sounds like you are knowledgeable as heck. So, which is faster, if any, FTP or Http? I just suggested http as I have it on a printer, I don't know squat about the others. Lol.

Great_Cookie
20th of June 2007 (Wed), 20:50
Thanks for the public beta test cdesperado... I thought I'd want to pick up one of these myself, but now honestly might wait a while until I can justify the need (or urge).

Do let us know how you're getting on with the http/ftp method. Still might prove useful yet, but the initial 'previews' of the E2a I read seemed to revolve around the fact that connectivity had to be established whilst the camera was still within reach. Definitely makes the thought of setting up walking away and then losing connectivity a potential nightmare.:evil:

Once again, thanks again for time taken to review this new piece of kit!:D

cdesperado
20th of June 2007 (Wed), 21:04
Unless I am having a senior moment, 55MB file size needs to be multiplied by 8 to get the size in bits not bytes. So then divide that result by 11Mb/s or 54Mb/s less a bit for packet overhead and assuming that you are connected at the highest bit rate, and you get 40 seconds to transfer that amount of data at 11Mb/s.

Since we all know we NEVER get the full rated speed on any WLAN or LAN connection, I think this xfer rate is fairly good. What was the receiving end s802.1 standard b or g? And what connection speed did you have? My guess is you were not connected at the highest data rate possible.

Tony...

Maybe I'm confused. Can you check my math? I don't typically measure data transfers, but I think (thought) my math was right. I guesstimated before, but I calcualted it below.

(Quick aside)... it's an 802g router and the laptop wireless card is "g" as well. (Tech history..... "A" is slower than "B" is slower than "G"). I was at a maximum transfer rate. (Laptop and wireless router in line of sight... laptop and camera in line of sight).

I can test this full math on this later, but I did expect the transfer rate to be slightly faster than it was.

Basically....
1 byte = 8 bits
54.2 Megabytes (MB) = 433.6 Megabits (Mb)
2 mins 10 seconds = 150s

Therefore, in my case, I had 433.6 Mb transferred in 150s.

The wireless transfer rate is 54 Mb per second.
54 Mb x 150s = 8,100 Mb could be transferred.

This means, in 150 seconds (2m10s), 8,100 Mb could have been transferred. I got 433 Mb transferred.

Am I calculating this wrong? (Keep the math simple for the rest of us!)

Steve Beck
20th of June 2007 (Wed), 21:14
just download servu or radentfp or something and use the 30 day demo, easier than IIS etc...

cdesperado
20th of June 2007 (Wed), 21:21
The laptop FTP isnt the issue... it's the camera wizard that is throwing me off. I'm still hacking at it though.

cdesperado
20th of June 2007 (Wed), 21:27
<grin> I think I figured out the problem and I am posting this in case anyone else tries it.

I originally created a P2P connection. I then tried to create an FTP connection. However, you have to use the 1D3 menu to manually Disconnect from the previously established P2P connection before creating any other connection.

I am assuming the same holds true of any of these - if you successfully create one type of connection, you have to manually disconnect before creating a new connection type.

I dont know if that will solve the problem, but it does seem like something that is required but isnt covered in the User manual.

cdesperado
20th of June 2007 (Wed), 21:52
Ok, sorry guys - I am having technical difficulties here. Setting up the FTP side from the camera is causing a problem for me and I am not exactly certain what is causing it.

I am going to keep trying for a bit longer, but it may be tmrw before I have it set up correctly.

khkohl
20th of June 2007 (Wed), 22:38
I used the Pixagent software for my FTP server software, that is designed for photo workflow. FTP worked great the first time at full G speed.(54mbps) You have the option of sending a jpeg to the WFT and recording the raw to the card. If there is an issue with the wifi it queue's up the selected images until you are in range. You can send every image you shoot, or select the image you want to transfer using the set button, with or without a caption. You can also review your images and select the image with a checkmark and send the selected images in a batch.

I plan to use the wft-2 transmitting to a Sprint rev-a smartphone with wi-fi. I am currently shooting Pro Baseball MLB. I will report on my workflow success or not in the next week,

cdesperado
20th of June 2007 (Wed), 23:05
Sorry guys.. I am giving up for the night. I've worked through everything within the camera - it simply won't connect to the FTP server.

Either something is wrong on my FTP side or I am not doing something correctly in the camera. I will take another stab at it tmrw.

joegolf68
21st of June 2007 (Thu), 00:30
I used the Pixagent software for my FTP server software, that is designed for photo workflow. FTP worked great the first time at full G speed.(54mbps) You have the option of sending a jpeg to the WFT and recording the raw to the card. If there is an issue with the wifi it queue's up the selected images until you are in range. You can send every image you shoot, or select the image you want to transfer using the set button, with or without a caption. You can also review your images and select the image with a checkmark and send the selected images in a batch.

I plan to use the wft-2 transmitting to a Sprint rev-a smartphone with wi-fi. I am currently shooting Pro Baseball MLB. I will report on my workflow success or not in the next week,

Excellent, I look forward to your and everyone else's results on this. Thus far, the fact that the connection keeps licking up is not a good sign. Time will tell I guess.

joegolf68
21st of June 2007 (Thu), 00:30
Sorry guys.. I am giving up for the night. I've worked through everything within the camera - it simply won't connect to the FTP server.

Either something is wrong on my FTP side or I am not doing something correctly in the camera. I will take another stab at it tmrw.

That's ok, thanks for everything you've done thus far. You'll get it!

joegolf68
21st of June 2007 (Thu), 20:55
Awfully quiet today Desperado, what gives? You were going great guns yesterday, either it is working now, you got too frustrated, or busy with "real life," lol.

So, I just couldn't resist. I just bought, three minutes ago, the Canon WFT-E2A transmitter. I got it from OneCall.com which I found through Amazon. Instead of buying it out of Amazon, I went directly to their site and used their summer07 coupon for an extra $25 and instead of free 2-day Fed-Ex, I paid $3.89 or so for two-day air. The total was $778 and change for EVERYTHING. Shame on BH and others for charging $999. I figured this was gonna happen soon, but maybe not this soon. The other places should drop VERY soon as supply comes out for more stores, which I expect in the next week.

I know your review, and even my comments show this unit is still shaky at best for what it does, but I wanted to get one anyway and give it a try.

Now, next week, I'll have to add my own review. Here little hummingbird, lol. With the lag time you mentioned, I guess I will have to hit the shutter button about the time the little bird leaves the next and starts the three hundred foot journey to the feeder. Oh well, maybe it will improve with software upgrades, I hope.

Joe

cdesperado
21st of June 2007 (Thu), 22:09
Lol... sort of a combination of frustration and needing something fun to do and wanting to keep testing. I spent Four hours trying to get the FTP connection to work and I never could. I gave up for now and will try again over the weekend. (I went out and shot kids playing golf today, which was pretty cool.)

I have to go out of town on a business trip this weekend and will have plenty of lonely time in the hotel to do more tests. The big test for me is going to be thru an Ethernet connection to the camera. I am very interested in how Live View will perform in this method. I am very very interested in a direct Camera-Laptop connection. I would prefer wireless, but I could live with a tether in many situations. (I have a friend build me long Ethernet cables.)

Btw, the lag I mentioned is VERY noticeable.... IMO, it's lag to the point of un-usable thru the P2P connection, which is the wireless connection I was most interested in.

Call me when you get yours and I can walk you thru the FTP set up. I should have it figured out by then. (And congrats on saving $200! Buy me a beer!)

EpHeSuS
22nd of June 2007 (Fri), 01:41
54.5mb in 130s is ridiculously slow! That's only 420kB/s.

I remember doing work experience last year with a photographer and he had the old wireless transmitter with a 1ds Mk II and it only took (roughly) 15 seconds per photo and they're 17mb each. With a 54mbit router, your actual sustained transfer rate will be probably closer to 16-17mbit, which is just over 2mB/s.

cosworth
22nd of June 2007 (Fri), 02:01
Is the machine with ftp running a firewall?

dpastern
22nd of June 2007 (Fri), 02:31
Maybe I'm confused. Can you check my math? I don't typically measure data transfers, but I think (thought) my math was right. I guesstimated before, but I calcualted it below.

(Quick aside)... it's an 802g router and the laptop wireless card is "g" as well. (Tech history..... "A" is slower than "B" is slower than "G"). I was at a maximum transfer rate. (Laptop and wireless router in line of sight... laptop and camera in line of sight).

I can test this full math on this later, but I did expect the transfer rate to be slightly faster than it was.

Basically....
1 byte = 8 bits
54.2 Megabytes (MB) = 433.6 Megabits (Mb)
2 mins 10 seconds = 150s

Therefore, in my case, I had 433.6 Mb transferred in 150s.

The wireless transfer rate is 54 Mb per second.
54 Mb x 150s = 8,100 Mb could be transferred.

This means, in 150 seconds (2m10s), 8,100 Mb could have been transferred. I got 433 Mb transferred.

Am I calculating this wrong? (Keep the math simple for the rest of us!)

mmm last time I looked, 2 mins 10 seconds = 130 seconds, not 150...

Dave

leedslad
23rd of June 2007 (Sat), 07:40
Hello guys, sorry about this, but I have a simply question, to which I can't seem to find a definitive answer! Hoping you can help.

Can I simply take a shot, and have the WFT-E2 send the image to my laptop with a wireless connection, but, without a wireless 'internet' connection. All the things I've seen on the net, seem to imply I need a router!

If I can, I guess all I need to do, is have the wireless card in the laptop activated, and link it to the camera?

Thanks

joegolf68
23rd of June 2007 (Sat), 22:55
Lol.. I went out and shot kids playing golf today, which was pretty cool.



Didn't even hear about it in the news. So, you hate golfers or kids or both? I better stay clear of you. ;)

The Ethernet connection will be interesting. I already have a very long cable to use which would work for me and the hummingbirds at least. Thanks for your efforts, it will save us all many hours.

joegolf68
23rd of June 2007 (Sat), 22:59
Hello guys, sorry about this, but I have a simply question, to which I can't seem to find a definitive answer! Hoping you can help.

Can I simply take a shot, and have the WFT-E2 send the image to my laptop with a wireless connection, but, without a wireless 'internet' connection. All the things I've seen on the net, seem to imply I need a router!

If I can, I guess all I need to do, is have the wireless card in the laptop activated, and link it to the camera?

Thanks

Good question, I wish I had an answer for you. My GUESS would be you need a router.

Jon
24th of June 2007 (Sun), 13:06
Hello guys, sorry about this, but I have a simply question, to which I can't seem to find a definitive answer! Hoping you can help.

Can I simply take a shot, and have the WFT-E2 send the image to my laptop with a wireless connection, but, without a wireless 'internet' connection. All the things I've seen on the net, seem to imply I need a router!

If I can, I guess all I need to do, is have the wireless card in the laptop activated, and link it to the camera?

Thanks
Just a wireless connection in the PC as long as both have the same IP subnet. It's easier with a wireless router doling out IP addresses to camera and computer though.

leedslad
24th of June 2007 (Sun), 15:32
Just a wireless connection in the PC as long as both have the same IP subnet. It's easier with a wireless router doling out IP addresses to camera and computer though.

Thanks John, but does this wireless router have to have access to the internet, or is it simply taking images from the camera and sending them to the laptop?

I do have an old D-Link router which I guess I could use to act as the 'middle-man' between them.

cdesperado
24th of June 2007 (Sun), 15:34
Just a quick update... I tinkered with the FTP settings again, but only for a little while. Still no luck. I decided I really need to take a day off and just relax, but I am going to hit this hard and heavy Monday and Tuesday.

The next tests are:
1. FTP connection (Wireless)
2. HTTP connection (Wireless)
3. Ethernet connection (Tethered)
4. Wireless thru tethered laptop/router connection

cdesperado
24th of June 2007 (Sun), 15:38
but does this wireless router have to have access to the internet.

No, it doesn't. The router acts as an Access Point with an IP address that you assign to it.

I'm going to be playing around with this over the next few days bc I want to do some speed tests. I will post instructions on how to do it bc network administration can be a little tricky.

Sincerely... I know what I am doing and I STILL can't get my camera to recognize my FTP. I am sure I am missing something obvious, but Augh! LOL

Jon
24th of June 2007 (Sun), 16:30
Thanks John, but does this wireless router have to have access to the internet, or is it simply taking images from the camera and sending them to the laptop?

I do have an old D-Link router which I guess I could use to act as the 'middle-man' between them.The only reason you'd use a router would be to set it up so it could assign the IP addresses for the WFT2 and the computer. Otherwise you'd have to configure both with addresses yourself along with all the other setup needed. If you do use a router, the signal will go from camera to router to computer and vice versa. Without a router the signal will go from camera to computer directly.

leedslad
24th of June 2007 (Sun), 17:01
Cheers guys - I think I'll be keeping a close eye on this thread! Good luck with all your tests!

joegolf68
26th of June 2007 (Tue), 14:59
Mine just arrived five minutes ago! Here I go.............. fingers crossed!

joegolf68
26th of June 2007 (Tue), 18:53
Well, I've played with it for a short while, not impressed but not upset at this point. I am not all that happy that there is no manual except a pdf file. What, we all want to sit at our desks or laptops and peruse the instructions? Not me, I often want to kick back in a LazY-Boy chair and read some before I even start. Oh well, no biggie I guess, we pay between $800 and $1,000 (tax, shipping, etc)and Canon wants to save a buck or two on a manual!

I immediately hooked up the transmitter and connected to my LAN using the http connection. It took about ten minutes to get it going and actually begin shooting remotely from my laptop. The problem came when I wanted to download my images. In the http method, I am suppose to use my browser to determine how to download the images. Using this method, thus far, I've only been able to download one image at a time. Seems that if I want to batch download, I must use the FTP connection. I'm not sure if if I can keep multiple style connections stored in my laptop and camera, and just switch between them according to my needs. But it seems that each style connection has its limitations and each has its own pluses. There are the three types of connections, I believe, FTP, P2P, and HTTP. Why each function is not available with each type of connection is beyond me, or maybe it is possible and I haven't found it yet. I tried to sue the EOS Utility while in HTTP and couldn't get the laptop to recognize the camera. I played with the setting for a while and gave up.

The user manual, for someone who has never played with networks must be a nightmare. I've been forced to learn a bit of this junk simply because I've been wireless for a long time, but what a hassle.

One thing that made it MUCH easier for me in this task, as well as other tasks I have previously performed, is that I have no safeguards on my network. Yeah, yeah, someone will come in and steal my birthday probably, but I found setting up firewalls, passwords, encryption keys, etc., to be such a nightmare, I just decided to go with an open, unlocked home network. I don't know how risky it actually is, so ignorance to this point has been bliss. My neighbors have probably logged in to my router more than once, lol.

Hope this helped someone, or someone reads the http stuff here and sets me straight.

Joe

cdesperado
26th of June 2007 (Tue), 20:40
The user manual, for someone who has never played with networks must be a nightmare. I've been forced to learn a bit of this junk simply because I've been wireless for a long time, but what a hassle.
Joe

Funny.... I thought the EXACT same thing. The more I think about this, I don't understand why the EFT-E2a doesn't come with a proprietary software that would enable it to simply independently recognize a wireless laptop.

I think in most cases, what shooters really want, is to have their camera sync to their laptop like a PDA does. I know there would be a cost associated with developing this software, but it wouldn't be a year-long effort.

Interesting about your HTTP issue, Joe... I haven't gotten back to testing things yet bc I've had to focus on other stuff, but manually transferring one image at a time would be a huge hassle.

joegolf68
26th of June 2007 (Tue), 21:50
Funny.... I thought the EXACT same thing. The more I think about this, I don't understand why the EFT-E2a doesn't come with a proprietary software that would enable it to simply independently recognize a wireless laptop.

I think in most cases, what shooters really want, is to have their camera sync to their laptop like a PDA does. I know there would be a cost associated with developing this software, but it wouldn't be a year-long effort.

Interesting about your HTTP issue, Joe... I haven't gotten back to testing things yet bc I've had to focus on other stuff, but manually transferring one image at a time would be a huge hassle.

Anyway one else there have one of these yet?

Oh, you can find them for $775 if you try. I bought mine for Onecall with an instant $25 off and free or super cheap shipping and my bottom line was around $775

sbressler
19th of July 2007 (Thu), 00:16
Just read through this thread (obviously not nearly as long as some others on here...) and it would seem that FTP is best and everything I've read about the previous wireless transmitter talks about FTP (maybe that's all that's available on that one?).

Regardless, have you guys or anyone else done any more testing in recent weeks - this thread has stayed quiet for a while...

joegolf68
19th of July 2007 (Thu), 00:19
I haven't, I gave up. The software seemed so unprofessional, not user friendly at all. Kind of like going back to Windows 3.1 or DOS. The hardare might be the best, but I couldn't get through the software and I'm selling the WFT-E2A and going with the LC 5 wireless. If anyone in the meantime figures this out, great, but no more beta testing for me.

B3SEO
19th of July 2007 (Thu), 01:17
Maybe I'm confused. Can you check my math? I don't typically measure data transfers, but I think (thought) my math was right. I guesstimated before, but I calcualted it below.

(Quick aside)... it's an 802g router and the laptop wireless card is "g" as well. (Tech history..... "A" is slower than "B" is slower than "G"). I was at a maximum transfer rate. (Laptop and wireless router in line of sight... laptop and camera in line of sight).

I can test this full math on this later, but I did expect the transfer rate to be slightly faster than it was.

Basically....
1 byte = 8 bits
54.2 Megabytes (MB) = 433.6 Megabits (Mb)
2 mins 10 seconds = 150s

Therefore, in my case, I had 433.6 Mb transferred in 150s.

The wireless transfer rate is 54 Mb per second.
54 Mb x 150s = 8,100 Mb could be transferred.

This means, in 150 seconds (2m10s), 8,100 Mb could have been transferred. I got 433 Mb transferred.

Am I calculating this wrong? (Keep the math simple for the rest of us!)

Those calculations look right to me, having been working with some kind of computer since 1975. 54mb per second is probably the highest transfer rate you will get with wireless..

Good job!

sbressler
19th of July 2007 (Thu), 01:27
Those calculations look right to me, having been working with some kind of computer since 1975. 54mb per second is probably the highest transfer rate you will get with wireless..

Good job!
Wireless-N promises much faster - almost up to 250 Mbit/s (although I'm waiting for reviews of the newest wave of products which seem far superior to the previous ones to come out before I pull the trigger). Anyway, that all seems off-topic - I want to hear about the Wireless Transmitter!

Also, can you remotely control the Mk.3 with a USB cable without the transmitter at all? Can you control all the same features?

One nice use of the transmitter (although seemingly not useful enough to spend almost a grand) would be to hook up an external 2.5" hdd and shoot almost infinitely with a small hdd in your pocket. Anyone try this?

bobcov
19th of July 2007 (Thu), 02:26
I think you're seeing part of an error condition I produced twice tonight. Set up the camera to do ftp via Ethernet, slap in a 2 gig card (or bigger), then lean on the shutter until you fill the buffer. Keep shooting until the camera stops and pull out the ethernet cord, then keep shooting some more and put the cord back in. If you do this a few times, under as yet determined conditions, the camera will lock up in a very very bad situation which will result in loss of images.

The record light will stay on, but the camera will not finish writing to the card, at least not in any reasonable amount of time. I was reluctant to leave it on over night as that might damage it. I was able to get the error twice. I was left in a situation where I could shoot up to eight frames at a time, but i could not finish writing to the card. Plugging in the ethernet cable didn't fix it. In the end, you have to pull the battery and that's when you lose the frames.


Second Update

I removed the WFT from the 1D3 - that enabled the camera to finish writing the image data. My guess is, it was trying to push the data through the WFT to the laptop, but since the WFT had no connection, the camera couldnt move the data, which resulted in the hung light.

The file was written to the card successfully.

My recommendation based on only a few hours of testing - if you use the WFT-E2a, you better be writing the data to a CF card as well, as a backup.

All of my problems happened while using a tripod mount and a direct line of sight from 1D3 to my laptop. I cannot help but wonder what would happen in a room full of other radio signals and physical objects in between the WFT and the laptop.

joegolf68
19th of July 2007 (Thu), 09:10
This thread is suppose to be about the WFT-E2A but I'm not sure now what the recent posts are about any more. Have you all tried the unit, your impressions, settings, etc. would be interesting. If you want to discuss hard-wire connections for the M3, please start another thread. Thanks.

bobcov
19th of July 2007 (Thu), 10:06
The calculations overlook the actual throughput vs the channel speed. On consumer wireless, depending on conditions, much of the bandwidth is taken up by housekeeping, retransmits due to interference and error correction. I would be surprised to get even half of a 54 megabit link in terms of throughput. There are reviews of some routers where they will do tests to determine the actual throughput of a given link with a specific router and client wireless card.


Those calculations look right to me, having been working with some kind of computer since 1975. 54mb per second is probably the highest transfer rate you will get with wireless..

Good job!

sbressler
19th of July 2007 (Thu), 12:00
This thread is suppose to be about the WFT-E2A but I'm not sure now what the recent posts are about any more. Have you all tried the unit, your impressions, settings, etc. would be interesting. If you want to discuss hard-wire connections for the M3, please start another thread. Thanks.

While bobcov's remarks seem off-topic, my question about using portable harddrvies attached to the WFT-E2A are perfectly on topic - this thread is about the device and all uses of it, not just wireless ones...

joegolf68
19th of July 2007 (Thu), 12:06
While bobcov's remarks seem off-topic, my question about using portable harddrvies attached to the WFT-E2A are perfectly on topic - this thread is about the device and all uses of it, not just wireless ones...

Ok, sorry. The posts made no sense to me, but that is not unusual. lol

So, are you all using the WFT-E2A? How are you using it, do you like it, and is it working like you want it to? For me, as you might have seen, I have found it incredibly slow and I didn't find how to download all images within the camera in one fell swoop. I hope you share your techniques if you found a way to use this effectively, as I am disappointed and going to sell mine if there is any market for them. Thanks.

bobcov
22nd of July 2007 (Sun), 14:58
Let me know when you're ready to sell your WFT-E2A. I might buy it.

Someone felt my post on throughput was off topic. Sorry, I was responding to a previous post on how fast the WFT-E2A is on wireless. I guess then that post must have also been off topic. :lol:

Ok, sorry. The posts made no sense to me, but that is not unusual. lol

So, are you all using the WFT-E2A? How are you using it, do you like it, and is it working like you want it to? For me, as you might have seen, I have found it incredibly slow and I didn't find how to download all images within the camera in one fell swoop. I hope you share your techniques if you found a way to use this effectively, as I am disappointed and going to sell mine if there is any market for them. Thanks.

joegolf68
22nd of July 2007 (Sun), 21:32
Let me know when you're ready to sell your WFT-E2A. I might buy it.

Someone felt my post on throughput was off topic. Sorry, I was responding to a previous post on how fast the WFT-E2A is on wireless. I guess then that post must have also been off topic. :lol:

Hi, I am ready to sell it now. I think I'll go with the LC-5. The WFT-E2A has lots of potential, and the live view shooting is very cool, but I was hoping that the downloading speed from camera to laptop was much quicker, as that was my primary purpose when I bought it.

Let me know if you want it, make me a decent offer. I have the unit, original box and my unit was used only a couple of times, so it works as new.

A PM or email to joegolf@gmail will get my attention the fastest.

Joe

Mgsa
13th of September 2007 (Thu), 02:26
Can I via my laptop connect direct to the camera and copy all the pictures from the card meanwhile I continuous shooting the sports game like I copying files from another computer on ethernet?
Then one person can photograph and another copy pictures from the camera meanwhile and edit them at the same time.

Will it works?

/Mgsa

DwightMcCann
20th of September 2007 (Thu), 17:12
Hi, I am ready to sell it now. I think I'll go with the LC-5.

Joe
You do realize that the LC-5 is just an infrared trigger/cable release? I have one and use it to do remote shooting from a lighting truss at boxing. And you do realize that the LC-5 is off topic.

As for transfer rates, you can't take the bit transfer rate and start dividing into your filesizes ... there is HUGE overhead in TCP/IP transfer as there are several levels of packets created each of which adds a fair amount of additional header/packet information which might even double the total data being transferred.

Doesn't this device have an RJ-45 port? I'm wondering if you can hardwire connect a 100' CAT-5 cable and what the transfer times are in this configuration.

Finally, I have noticed that these things aren't available still via the "regular" channels such as B&H so I am wondering/hoping that there is a WFT-E2B coming with some improved software. My personal feeling about Canon software (as a software designer for over 30 years) is that it is crap, written by somebody's ten year old, poorly supported (if at all) and the manuals have gross errors that Canon makes no effort to correct.

bestbyte
30th of October 2007 (Tue), 12:18
Ok so where is the post "how to make your WFT Work" for dummies at. Do I have to start up the pairing software on my computer first? Is it v1.00? I put in my ssid and security code it gives me an address and then says it fails. Does anyone have a step by step run through written? ...Thanks

mridley
30th of October 2007 (Tue), 14:31
Hi Guys am I allowed to post my findings on the WFT-E3A as it is bascially the same thing?

Jon
30th of October 2007 (Tue), 14:39
You might want to make it a separate thread to avoid confusion and make it easier to search.

DwightMcCann
13th of December 2007 (Thu), 18:44
Did I miss the final conclusions about FTP? My WFT-E2A came today but I am up to butt in alligators for the foreseeable future so want to avoid reinventing the wheel.

BLS439
4th of January 2008 (Fri), 21:45
My WFT-E2 will be here Monday! Any update as to how it's working or tricks to make the connection better?

I searched several forums but can't seem to find the answer to this question: What's the difference between the WFT-E2 and the WFT-E2A?

Thanks!

DwightMcCann
4th of January 2008 (Fri), 22:15
I took mine out of the box, looked at it, put it back in the box! I have every intention of making great use of it but have decided to wait and take it to work after the holidays to get my co-workers who are intimately familiar with networking and WiFi to help me set it up, sigh! I am a mere assembler programmer and backup system admin.

SirBrontes
18th of January 2008 (Fri), 16:41
What's the difference between the WFT-E2 and the WFT-E2A?


To answer an earlier question, the only difference between E2 and E2A is the transmission frequency:
WFT-E2: 2412 - 2472 MHz (central frequency, 13 channels total)
WFT-E2A: 2412 - 2462 MHz (central frequency, 11 channels total)

Now to add more to this discussion, I've been using WFT-E2A since October in my studio and have no complaints. It took me about an hour to make it work because I didn't want to open up my network and had to reinstall my FTP server on the laptop since my last clean XP install.

The instructions are decent for a computer savvy user. Someone who can setup their own secure home wireless network should be able to follow the manual. The most frustrating part is the fact that making a single mistake in the process requires starting from scratch.

Connectivity is good for a studio space. I used the unit indoors (studio) and outdoors (near the studio) all the photos uploaded to the FTP server. From time to time there is a slight delay in upload because the connection is reestablished every time you press the shutter button and dropped once all the images are transmitted. This is done to save the battery. Speaking about the batter, having the WFT-E2A on camera drains the battery noticeably faster.

The camera also gets a little oddly shaped with the unit attached, but I have no problems holding it. It was fairly easy to get used to it.

I can definitely see a number of areas for improvement. However, overall, I am satisfied with WFT-E2A.

BLS439
21st of January 2008 (Mon), 21:44
However, overall, I am satisfied with WFT-E2A.

I've been playing with mine as well for some time now. It works very well and was worth the $500 I spent. :D

I have the camera send files to the laptop and copy to my card so I've got a backup. I use a secured Network for mine and plan to play with FTP to see how much of a difference there will be.

DwightMcCann
21st of January 2008 (Mon), 22:18
I've been playing with mine as well for some time now. It works very well and was worth the $500 I spent. :D

I have the camera send files to the laptop and copy to my card so I've got a backup. I use a secured Network for mine and plan to play with FTP to see how much of a difference there will be.

I still haven't fired mine up. Do you go directly to the laptop or through a wireless network?

sbressler
23rd of January 2008 (Wed), 17:52
plan to play with FTP to see how much of a difference there will be.
What have you been using? PTP? And I'm also eager to hear more about it, along with Dwight.

dbean
7th of August 2008 (Thu), 22:27
the WFT-E2A is smoking fast if you do one simple thing. the same thing will work for any kind of tethering.

if you use 2 cards ( a CF and a SD card) in the camera and set the menu to the following:

Under "Record func+media/folder sel" choose "record seperately." underneath is an option that says "playback."

i set my CF card to record RAWs and the SD card to record small jpgs. i set playback to 2. that means the camera will send the image on card 2 to the computer and the image on card 1 stays on the camera.

this way your tethering is blazing fast because only the small jpgs are going to the computer.

you also need to set the EOS Utility to record to both the camera and the computer.

it makes the WFT-E2A SUPER fast because you keep the large RAW files on the CF card.

fashioneyes
4th of January 2009 (Sun), 07:45
I ordered the WFT-E4 (5D Mk2) version of this and its an awesome piece of kit.

I primarily wanted it for studio work so the clients can see the images as they are being taken. I looked at the settings and FTP is the way to go for me. Firstly I believe it reduced the amount of work EOS utility needs to do (a good thing IMO) and secondly you can configure the camera to shoot RAW+sJPG and FTP can be configured to transmit only the small JPG. Transfer times are approx 3 secs a file ...

Of course at the end of the session I take the RAWS directly from the CF card as normal, but the client has already viewed and selected the images as soon as the shoot has finished.

FTP is the way to go for transmission of the data
HTTP is ideal for remote triggering
P2P ... avoid IMO

jharms1
6th of June 2009 (Sat), 10:55
Did anyone ever write up a step-by-step "how to" on how to get the WFT-E2A to work in FTP mode? I've been trying to get it going for a couple of days now with no luck. My guess is that the problem is on the PC side of the equation.

DwightMcCann
6th of June 2009 (Sat), 11:28
I ordered the WFT-E4 (5D Mk2) version of this and its an awesome piece of kit.

I primarily wanted it for studio work so the clients can see the images as they are being taken. I looked at the settings and FTP is the way to go for me. Firstly I believe it reduced the amount of work EOS utility needs to do (a good thing IMO) and secondly you can configure the camera to shoot RAW+sJPG and FTP can be configured to transmit only the small JPG. Transfer times are approx 3 secs a file ...

Of course at the end of the session I take the RAWS directly from the CF card as normal, but the client has already viewed and selected the images as soon as the shoot has finished.

FTP is the way to go for transmission of the data
HTTP is ideal for remote triggering
P2P ... avoid IMO

Sounds good.

Did anyone ever write up a step-by-step "how to" on how to get the WFT-E2A to work in FTP mode? I've been trying to get it going for a couple of days now with no luck. My guess is that the problem is on the PC side of the equation.
I'm interested in this, too, as well as how to do it directly to laptop rather than through router (if that's possible.)

fashioneyes
7th of June 2009 (Sun), 05:39
First off

I would check the FTP side of things from another PC/laptop to ensure that the FTP server etc. is behaving the way it should. And make sure you can upload a file OK.

Note the upload path too ... as you'll need that in the WFT setup.

Once that's done, it's pretty simple really with a little knowledge of networking/IP addresses. Happy to answer specific questions if you want to PM me.

OldA1
7th of June 2009 (Sun), 09:46
Did anyone ever write up a step-by-step "how to" on how to get the WFT-E2A to work in FTP mode? I've been trying to get it going for a couple of days now with no luck. My guess is that the problem is on the PC side of the equation.

Short answer is yes. Doing a search on the forum and checking out the 1D3 official link stickie was very helpful for me.

Sounds good.


I'm interested in this, too, as well as how to do it directly to laptop rather than through router (if that's possible.)

You can go directly to a laptop as long as the laptop has built in wi-fi. I have not installed any server software on my laptop (or desktop machine) so I set it as an ad-hoc connection (on laptop) and used PTP mode instead of FTP.

I have only experimented with PTP mode to see how the remote control worked in EOS Utility.

PTP as worked without issues with both the WFT-E2 and WFT-E3 on my desktop machine (through the router).

Using PTP and ad-hoc connection on my laptop was a different story. The WFT-E3 worked without issues but the WFT-E2 constantly drops the connection while transferring the raw image. When I have more time, I will try dbean's suggestion to only send jpegs and see if that solves my problem.

Peace
Mark

MDJAK
26th of December 2009 (Sat), 18:26
someone here (Dwight) hasn't read the rules which require posts to be in the English language. ;)

Oh, if I could only understand this technojargon. :(

me