XP DEUS PROBLEM very strange

[WM6]

The same trouble in re-loading software. Deus remote control unit can not communicate with coil and earphone unit as well.

Sorry but this is pretty unbelievable.
Did you really try to register coil on Remote according procedure from user manual?

Take battery of your phone unit.
Take battery of your Remote, wait a minute and put battery back in Remote.
Put one of your coils in some sort of metal box.
Find coil registering procedure in your manual.
Follow registering procedure and register your coil.
Repeat registering procedure with other coil.

Please try this steps and report.

[multieagle]

Whew! After reading this, guess my question would be, "Who really needs a machine that must be registered to coil with head office, before use?" When you buy something, it is yours, and should work without a lot of interaction with the seller. Or am I missing something here?

[Pishdari]

"Who really needs a machine that must be registered to coil with head office, before use?"

multieagle hi,
No, No, Please, Don't take it wrong.
Please try to understand what I mean by word of "register". simply means you enter the coil's serial Number to the device.
Here me and I guess all others have read or replied, understand "register coil" means that: the coils serial number must be entered into the remote control unit as well as into earphone unit.
These terms regarding to XP DEUS have the same meaning:
Register Coil = Record Coil = Pairing Coil = identifying Coil. All the less means you have to enter (the serial number written on deus searching coils) into remote unit and then would automatically be sent to earphone unit and recorded. That is how you register coils within XP DEUS, not to register in office or any where at all.......... (at least as far as I understood) ....

Hope you get DEUS one day, and you will be surprised with deus performance. It is new versatile machine that you can changed to the DETECTOR you like.

Anyway thanks to all who replied.

[Pishdari]

Sorry but this is pretty unbelievable.
Did you really try to register coil on Remote according procedure from user manual?

Take battery of your phone unit.
Take battery of your Remote, wait a minute and put battery back in Remote.
Put one of your coils in some sort of metal box.
Find coil registering procedure in your manual.
Follow registering procedure and register your coil.
Repeat registering procedure with other coil.

Please try this steps and report.

Dear MW6 thank you very much for your interesting.
That is why I said very strange!!
I did all points you kindly mentioned above including take off (dis connecting) battery for 2 minutes to let any eeprom/eprom memory or RAM chip or flash chip to be re-setted.
But all without succession to solve the problem. (Remote control unit can not make coil respond until earphone unit does).
As you can see it in the video above the coils work fine and too normal but ,of course, after switching the earphone unit ON.
That is why I didn't say strange but very-strange. Isn't (Is it not)????

Anyway I emailed XP today they kindly and thankfully replied very soon after hours. They say "it is the first time we here such a problem". They suggested might be the unit have different Versions, but they are NOT different they were all updated with V3.2 several months ago. They also advised to get an other remote unit from a friend to check and decide the trouble unit then send back the them for repairing. Unfortunately I can't get any other deus here in my location, so I have to wait until I get some guidelines to do it here myself.
I look forward to hear more from them. The worst problem is that "it nearly impossible for me to send it back to the XP or the distributer, because I might lose the device for ever and never it reaches XP.

Thank you all for kind helping and sharing.

[Ism]

Pishdari, very sorry to hear of this dilemma, especially the difficulty of sending your control box or entire unit back (through customs I suspect).
But after all that you did, I suspect you have a bad control box. One thing you may wish to try as a last resort. Reload version 2.0 and see what happens.
If that works, then you might be able to reload v3.2 with success. If I am suggesting something you already tried, forgive my ignorance.

[multieagle]

multieagle hi,
No, No, Please, Don't take it wrong.
Please try to understand what I mean by word of "register". simply means you enter the coil's serial Number to the device.
.

Thanks for clearing this up. Good luck with your build.

[Funfinder]

> I did all points you kindly mentioned above including take off (dis connecting) battery for 2 minutes to let any eeprom/eprom memory or RAM chip or flash chip to be re-setted.



Hi Pishdari,

after flashing alot stuff already like sat-receivers, DVD-burners, smartcards, common access-interfaces, routers, chips, BIOS etc. -
I guess the crucial point of your problem could be:

There is a difference in usual reset and in fully clearing of the eeprom before the new, old or alternative firmware flashing starts.

Usually firmware-devices are containing a bootloader region, an area with the default and backup firmware (Rom or eeprom
area with a copy of the default firmware) and the rewritable memory where the used firmware and the user-settings are stored.

A simple reset just will replace the faulty or hanging firmware of the eeprom with the safety-backup from the flash.

But some devices are not working correctly if the eeprom area wasn't cleared completly before the upgrade.
This can happen if the firmware has occupied special areas of the storage-chip which must be free if the device
should work correctly with the replaced internal backup-firmware.

Simple solution: mail XP that they should send you a little program that clears completly the eeprom before
the inbuilt backup or a new firmware gets installed!



Seems there went something wrong while upgrading or replacing the firmware so that now there is
written some at the moment undeletable data-junk somewhere at the eeprom which causes those problems.
Thats also the reason why the firmware-writing stops near the end - the memory is already full
before the complete data was able to get written into the IC.


Perhaps its also a bug inside the firmware that only gets triggered under very special circumstances,
in that case you should downgrade the XP deus if possible or try out different firmware-versions.



Good luck and if nothing helps perhaps you better think about a different (analog) detector,
this little XP-deus coil accu that gets used for the wireless-connection and the EM-field for the coils
isn't strong enough for real depths, anyway. It works great at e-smog free and low-mineralic areas
but not under tougher conditions. But of course I hope you can get this stuff fixed, would be a waste
of alot money. As a very last trick you may upgrade or replace the bootloader, but if something
goes wrong at this stage the hardware will be beyond any help, so better forget it directly.


For the moment try to get a program from XP that erases completly the eeprom (the location of the active in use firmware)
before the backup or new firmware gets written there. If they don't have any or refuse to send it to you, better forget about them.

[Ism]

From personal experience, I find Alain Loubet to be most concerned about making his XP customers happy.
I'm sure he will do everything he can to remedy the situation within reason.

[Funfinder]

We really should force new users to give us the promise to inform us about the further
developments after we gave them any advice here or they can "exploit" someone else!

They simply shouldn't leave their more or less interesting story without an end.

And I doubt XP will or can help this guy because otherwise they would
have sended him directly the needed files to fix it or told him something like:
"No prob, send us your faulty XP deus device and we will repair or replace it for you."

[Pishdari]

They simply shouldn't leave their more or less interesting story without an end.

Hi Funfinder
There is not an end to write here, the problem is not solved yet.

And I doubt XP will or can help this guy because otherwise they would
have sended him directly the needed files to fix it or told him something like:
"No prob, send us your faulty XP deus device and we will repair or replace it for you."

XP did not helped with any thing to mention it here in this thread, they thankfully did reply to my emails but DID not send any file, or any simple instruction even no info. sharing like WM6 or other member did here on this forum. Simply they just said "Send us your device, we will repair it under the warranty".
This may be "Metal Detectors Mentality" not only XP alone but may be all other manufactures as well. I really appreciate there invention of making Metal Detecting digitally and wireless, but they should also pay attention to customers supporting more Why? because of digital and software including. As you may all know digital devices are more vulnerable to trouble than analogue, I mean software related troubles.
Other manufactures, "of course not metal detectors makers", like cellphone, computer makers, software publishers, they all have lost a huge efforts to support and solve end users problems by releasing small applications or even complicated software applications to help trouble-shooting by end-users, Not simply send back your device to the manufacture.

I was expecting from XP they would help and at least they would send me a file "as mentioned to solve it, especially when I announced here and send XP by email that I never can send back the device to France because of local laws and even costs it may cost about its price to send and repair it. I have already paid twice of its price, and cant make it three times.

In short the trouble is as it was, there is no hope from XP, no hope to be able to send back for repairing under XP warranty.
I will write down here if I could get any good-end of the story even bad-ends story.

Thanks to all who shared their info and experiences here in this forum just for their being with kindness not for simply making profit.

[Pishdari]

Last email to XP and their reply:
"Hi SAV XP

You are absolutely right, GSM doesn't use 2.4GHz. GSM uses 800MHz -900MHz in here my city. As far as the BTS is very close to my location, and frequency upper band filterization might be not used in FDM, TDM modulation, there is high possibility of Harmonics 800 * 2 >> 800* 3 = 2400MHz and so on starting from LO oscillator frequency multiplication. That is only guessing and rough estimation, and other rf noise devices are very common in 2.4GHz band.

To be honest, I don't know what might be the nature of the interference of RF noises to DEUS's WiFi channels, anyway I mentioned when I thought of possible sources of RF noises.



The reason that I had estimated halting of DEUS by RF noises is; the last time I tried up-dating deus in rural place far of potential RF Noises and magnetic fields, the remote control unit and the 22.5cm were updated successfully, (the coil 22.5cm was updated for the first time since the problem found). Then when updating-process came to Earphone Unit, it had halted and did not updated and not yet.



For sure, what I can confirm the small coil 22.5cm is now re-updated with V3.2. The same thing for 34cm coil is updated with V3.2. (I mean after trouble found re-loaded with fresh V3.2).



The only unit could not updated yet (fro time problem found until this moment) is Earphone Unit. But it was updated several months ago to V3.2 and now it shows 32 on LCD at starting.



Finally, what do you suggest to do, I feel confident and I am enough qualified technically related to electronics and software to check it (hardware related checking) if you recommend it. "I never take a step unless I am 100 of 100 sure I know what I do. So what do you suggest.



Regarding what you wrote ""Also you will see nothing with spectrum as signal is not permanent and difficult to scan"". I thought by use of spectrum analyzer I might can roughly estimate the differences between the strengths of the 4 units signals, if there were any differences.




I have already tried by using some sort of "software wifi spectrum analyzer programs found for free on the internet" installed on my laptop. But could not see any of DEUSs signals. just saw of my laptop and my wireless router, my smart mobiles I mean those near to me inside the building in 2.4GHz. example of the programs , (as you can see in the below image of my desktop icons i.e. circled icons of the WiFi network analyzers that I tried to use."



XP reply:

Dear .......
If your headphone show 32, it is perfect and you don’t need to update again several time your headphone…
If you have tried in a quiet area far from GSM then it is not GSM. however we never find problem with GSM even close to transmitter.
WIFI don’t disturb the DEUS also even if you are close to several transmitter as wifi use different channel at same time, also DEUS change the frequency itself when you turn it on.
You cannot find the problem with your spectrum as you already see and knwo that your DEUS work and transmit the 2.4gHz, so that will bring you nothing more to see the signal on spectrum for my opinion.
We cannot help you by email, as I have already said you it could many thing: crystal quartz, microprocessor or the transmitter chip who is faulty. You cannot replace everything by yourself, you have no other solution than to send it to us now or later and we will repair it under warranty.


Cordialement/Regards

XPLORER Sarl
8 rue du développement - ZI de VIC
F-31320 Castanet Tolosan – France

[WM6]

XP suggest on hardware fault ( crystal quartz, microprocessor or the transmitter chip).
I would not thinking at hardware fault as first in this case.
As you explain couple of times here all can work properly after given (yet unusual) procedure. Did they know this?
From my point of view, this is more likely sign of faulty primary configuration control program (which is not upgraded by new software version).

[Funfinder]

Thx Pishdari for the news and good luck that you are able to use your detector further.

WM6 is right but of course what can happen is that the flash-storage-chip - if its low quality -
loses parts of the information after some years. Those chips contain microscopic tiny transistors
which store the data as on or off states (simple explained, google for compact flash for more info).
This also can happen with old mp3-players - after rewriting the data to them, everything works again.


Seems some configuration info went wrong or was deleted and is no longer overwritable now just by updating.



> Pishdari wrote:
Other manufactures, "of course not metal detectors makers", like cellphone, computer makers, software publishers, they all have lost a huge efforts to support and solve end users problems by releasing small applications or even complicated software applications to help trouble-shooting by end-users, Not simply send back your device to the manufacture

They have not lost support, they have improved alot their software-side and trouble-shooting support because of
the many problems their software made and because of the fast raising demand of the customers.

Of course I know what you wanted to tell us - such special firmware driven detectors needs better software-related user-service.
Absolutly. There just has to go the main power off while upgrading and such a device can be thrown in the trash without useful
recovery support. And you not even can replace anything by yourself because everything happens inside some micro-controllers.


What are that laws where you can't send a piece of electronic for repair?
Does the post-office tells the authorities that you are in contact with a foreign metal detector company?
You may open the XP Deus and just send them the PCB only to a private address of one of the XP guys in France.
Or you better buy or built some new metal-detector - in such countries for shure you can get some good mine-detectors
with a little bit of money and connections! Or you live with the XP problems as long as you still can detect metal with it.
At least you will need some technical knowledge if the coil-lipo-accu goes bad to replace it - but this may take some years.

btw. I don't fully understand what sort of info you are writing to XP:
"spectrum analyzer"

Do you wanna analyze the digital transmission signals and at what frequency they are?
If you write to XP France such stuff for shure they must become curious or even sceptical.
Because for them you also could be just some kind of hacker who just wants to clone the XP.

However all this would be no problem if they just send you the needed eeprom erase-apps
including secure firmware-update stuff so afterwards it will be absolutly clear whats the matter.


As long as no water or extremly heavy force damaged your XP device and especially if those
problems did start directly after a firmware-upgrade its pretty clear that a software issue.
Hope you get this trouble solved soon.

[Qiaozhi]

Pishdari - Clearly it is not a good idea to purchase a complex [foreign] piece of equipment in your country, unless there is some local service and support. The problem certainly appears to be hardware-related, and it looks like your only option is to send it back to the manufacturer.

[Funfinder]

Another question is how healthy is the radiation of the XP Deus if its weared in the shirts breast-pocket
for the nearby heart and other organs. Did they made serious clinical tests or not?!
This depends alot on what frequency it works and how much power it uses.
And digital pulse-modulation as used for the TETRA networks is more dangerous for health than usual FM.