Did The Vortex Release Meet Your Requirements?

[phrunt]

2 minutes ago, canslawhero said:

yep, guess it's a mute point anyway. as soon as the Vorti are released we should see a lot of comparos, some good and more bad. I do know if I was the designer (I have an EE degree, lol) I would want to compare 'my baby'. 

I'm sure they've compared their baby a lot during development 🙂  But a manufacturer doing demos of theirs vs other brands is never a good idea, even if it is better.  They're best to ignore competition in their promotion, Nokta learnt that the hard way.

[The Lama]

2 hours ago, Chase Goldman said:

 (well at least until the Apex falls in the water and drowns) because it has a Multi Salt setting whereas the VX5 does not.

You wouldn't believe how many times my Apex has been dunked in the ocean with no problem

[Mirda]

12 hours ago, phrunt said:

The beauty of them all running the same base hardware and button configurations (all the same detector) is sofrware upgrades between all 3 versions can be done with one set of code, it's not hard to do a change to one and port it across to all 3, a couple of minutes work but since when do we corncern ourselves with how hard a manufacturer has to work to keep their firmware up to date across models?

There is probably common core, that is shared, but then, there are different code parts between all three models. This can be handled in many different ways. But you will, for sure, not have same code on VX5 that is also on VX9. As the time goes, especially VX9 will receive more and more bugfixes and feature updates and it's codebase will diverge even more. You have to take care of 3 branches, instead of one. Changes in core can potentially break all 3 versions. So testing should be made on 3 models, instead of one. In the real world, not everything is unicorns and rainbows...

When a few thousand people start upgrading firmware literally at the same time - that's a challenge. If they start to compile all firmwares for separate machines? They can obviously handle it, but it's not cheap. As far as I know, Garrett doesn't have any experience with updateable metal detectors, so we will see, how they handle this.

I don't have to care, for sure. But that's what is discussion for - isn't it?

It's about decisions. They made decisons, and I will not buy Vortex.

But it makes me sad, I believed in enhanced Spectra, this is disappointment.

[Mirda]

12 hours ago, phrunt said:

I'm sure they've compared their baby a lot during development 🙂  But a manufacturer doing demos of theirs vs other brands is never a good idea, even if it is better.  They're best to ignore competition in their promotion, Nokta learnt that the hard way.

That's why I mentioned comparison with their own Apex. Even Apple does this - compares new processor to previous generation.

When they don't say it's better then Apex, it probably isn't. Then whole hardware platform stuff is even bigger nonsense.

[phrunt]

1 hour ago, Mirda said:

That's why I mentioned comparison with their own Apex. Even Apple does this - compares new processor to previous generation.

When they don't say it's better then Apex, it probably isn't. Then whole hardware platform stuff is even bigger nonsense.

Apple do it to sell you the new model as they're discontinuing the old model and want you to upgrade, it's how they make their money, entirely different scenario.  

Your previous posts demonstrate you don't understand coding at all. Firstly, firmware differences between models with the same code base isn't an issue, they just have extensions (modules) of that code for different models.  It's almost a copy and paste scenario between models to enact changes that are shared and differences between models are using modules, but really, leave that to the people that know what they're doing rather than speculating with unfounded theories that they can't handle it.  I have a funny feeling for Garrett to take this approach they know what they're doing, certainly with a far better understanding than we have.

It is no challenge people upgrading at the same time, injecting a serial number into a firmware file isn't a challenge, it's a small portion of generated code to each model in the firmware upgrade's file, and realistically if you think thousands of people are going to be paying for a Vortex upgrade at the same time, you're on a different planet to me and even if they did, I'm sure if Garrett applied the right hardware to handle it the worst case is you will have a few seconds of delay before your firmware upgrade is ready to download, it's not an issue, not even a slight challenge.

[Hamid]

Good luck Garrett metal detectors🥇

[Doc Bach]

2 hours ago, Hamid said:

Good luck Garrett metal detectors🥇

They are going to need it....

Just a few days ago a certain YouTuber that I or we cannot mention by name fired all of their technicians and engineers.😂

[Mirda]

23 hours ago, phrunt said:

Apple do it to sell you the new model as they're discontinuing the old model and want you to upgrade, it's how they make their money, entirely different scenario.  

Your previous posts demonstrate you don't understand coding at all. Firstly, firmware differences between models with the same code base isn't an issue, they just have extensions (modules) of that code for different models.  It's almost a copy and paste scenario between models to enact changes that are shared and differences between models are using modules, but really, leave that to the people that know what they're doing rather than speculating with unfounded theories that they can't handle it.  I have a funny feeling for Garrett to take this approach they know what they're doing, certainly with a far better understanding than we have.

It is no challenge people upgrading at the same time, injecting a serial number into a firmware file isn't a challenge, it's a small portion of generated code to each model in the firmware upgrade's file, and realistically if you think thousands of people are going to be paying for a Vortex upgrade at the same time, you're on a different planet to me and even if they did, I'm sure if Garrett applied the right hardware to handle it the worst case is you will have a few seconds of delay before your firmware upgrade is ready to download, it's not an issue, not even a slight challenge.

If you release a new firmware, many people try to upgrade at the same time. If you just serve one static file for all of them? No problem. If you have to manipulate/compile each firmware specifically? I'm not sure it's about injecting serial number into the same firmware file - that could be done by anyone. So it will either take time or processing power.

We'we seen this with XP's new update procedure. You had to login with your user/password to be able to update. They're servers took a break. We discussed it here, e.g. www.detectorprospector.com/topic/22965-deus-2-update-v10-released/

 

And they even don't use this kind of serial number magic. Even XP had a lot of issues with updates down the road. But as you said, it was no challenge for them. It just didn't work.

If you know how their's code is structured, it means one thing. You're part of the development team. There is no other way to know that. There is a gazillion possibilities of how to do it.

[phrunt]

8 hours ago, Mirda said:

If you release a new firmware, many people try to upgrade at the same time. If you just serve one static file for all of them? No problem. If you have to manipulate/compile each firmware specifically? I'm not sure it's about injecting serial number into the same firmware file - that could be done by anyone. So it will either take time or processing power.

Injecting a serial can't be done by anyone, firstly, how would they know their serial number? It's a processor serial number, not their detectors serial number, and no they can't go pop the hood and read it off their processor 🙂   It literally takes under a second to patch small file like firmware.

Moreover, the firmware would be encrypted so nobody is going to be putting their serial number which they don't know into the firmware which they can't decrypt.   If it wasn't encrypted you would likely have a Garritt Vortox out of China before they could get the original ones to all of their dealers.

Pointing out another manufacturer's problems doesn't mean all will have the same issues.  I'm not going to refresh my memory on XP's problem but I think it was they had registration issues with confirmation emails being sent out, so their web developer did something wrong, not related.

Either way, you're worried about something that hasn't happened and assuming they don't know what they're doing.  For all we know they're just going to manually sell the update, not have it automated, it's not like they're going to be selling every second, and then they can take their time, email you the patched ready to roll update locked to your serial number and say go for it, but I think it's likely going to be intergraded into their firmware upgrade tool they use with the Axiom and Apex or have a similar tool for the Vortex to do its upgrades.

The backend is not something we as customers need to worry about, that's Garrett's problem and I have no doubt they have it under control.  It's just new to us as customers, so obviously a bit of pushback and fear about it.