Quick question about Legend charging/computer connection

[TIE543]

I haven't updated my machine at all since I got it but I just downloaded 1.07 and was reading the installation instructions when something dawned on me. It says in the install instructions to connect your machine to a PC without turning it on, but any time I charge the Legend (whether through PC connection or just plugged into the wall) it automatically powers up. Is this not supposed to happen, or am I overthinking it?

 

Amazon Forum Fav 👍

Cry Of The Eagle: History And Legends Of The Cherokee Indians And Their Buried Treasure - Grab it through Amazon!

[pamlicopanther]

The way it works for me is I plug the legend connection into my laptop and it makes a beeping noise. I then hold the plus button on the detector until uts says up. Then I can install the software on my detector using the laptop software

 

[TIE543]

The way it works for me is I plug the legend connection into my laptop and it makes a beeping noise. I then hold the plus button on the detector until uts says up. Then I can install the software on my detector using the laptop software

Thanks for the insight, I'm more wondering if the detector should automatically power up whenever I plug it in for charging though?

 

[oldkoot]

Thanks for the insight, I'm more wondering if the detector should automatically power up whenever I plug it in for charging though?

to answer your question it is not supposed to power up when you plug it in to charge or it did not used to be that way what version is in your Legend the first ones that came out was 1.04 then the new ones that are being sent out came with 1.05

 

[TIE543]

to answer your question it is not supposed to power up when you plug it in to charge or it did not used to be that way what version is in your Legend the first ones that came out was 1.04 then the new ones that are being sent out came with 1.05

I'm still on 1.04 as of now. It charges perfectly fine when I plug it in, I just thought it was odd that it completely powers up as it does it.

 

[TIE543]

Update: Just updated to 1.07 and the issue seems to have gone away. Maybe it was a bug with 1.04 that no one (or very few people) had encountered? I suppose it's possible other people had it as well, and just assumed it was how it's supposed to be.