Page 2 of 2

Re: 4038 appears dead. All keys lit up.

Posted: 16 Jul 2013 08:47
by omitix
I have the same issue. how did you solve it?

Re: 4038 appears dead. All keys lit up.

Posted: 17 Jul 2013 02:57
by dmorris
I was not able to find a solution. The phones are still dead.

Re: 4038 appears dead. All keys lit up.

Posted: 17 Jul 2013 03:01
by Eliott
Eliott wrote:In the original described situation you can't do anything than exchange the set.
I think it is described detailed enough how to fix it.

Re: 4038 appears dead. All keys lit up.

Posted: 17 Jul 2013 03:12
by dmorris
Thanks for the idea mgsox however this has not worked.

I do not have a power adapter as power is supplied via POE.

As soon as I plug in the cat6 cable (holding i 1 2 3) the lights are lit up immediately. There is no pause at all between plugging in the cable and the lights coming up.

Do I need to be using a power adapter rather than POE for your suggestion? If so I could possilby buy one form an electronics store to give it a go.
mgsox wrote:i do not know if you have resolve the issue but you can try this (i found it in this forum)


1)So, on your side you have at first to configure your PC with address "
192.168.1.6"
2)Then start your IpTouch in industrial mode:
- IP Touch starts in industrial mode thanks to key (i 1 2 3)
+ Disconnect power of the set
+ push key i
+ reconnect power (hold always key "i" pressed)
+ push at the same time "1" "2" "3" (and "i" of course)
+ when the leds go on, you can release the key
+ now, the set is in "industrial mode"
3)Use a crossed cable to connect your Set to the PC, or a HUB
4)Now you make a telnet on the set
5) Erase Thales Security
thalsec reset
6) Restart the set


good luck

Re: 4038 appears dead. All keys lit up.

Posted: 17 Jul 2013 03:53
by vad
From my point of view - can be 2 problem:
- some keys pressed (push/release all keys, shake set).
- internal fault - processor in set not working.

Re: 4038 appears dead. All keys lit up.

Posted: 17 Jul 2013 12:48
by Eliott
Again. The Memory Chip is faulty. No chance to fix it.

PS: If keys are blocked you will have stuck_keys in display followed by Key-ID