View Full Version : Error 28 and Error 50 after upgrading to Firmware 7.12 (P4) and 6619 (WiFi) - TCP/IP
After updating my P4 to 7.12 and my WiFi to 6619 I randomly get Error 28 or Error 50 when I use TCP/IP connection. I have the same problem both with GCC 1.1.1.3 and GCC 1.1.1.4
Works well with USB cable
Sincerely Lasse
Hello Lasse
establish a connection via USB, and check the WLAN settings under "System". A screenshot of the settings would be helpful
regards Pit
The setting is the same as before the upgrade. it works without any problems with TCP/IP before update. It works even now but after 5 - 10 minutes - error 28 or error 50 shows up. Screenshot below - I have blank my password
10675
Sincerely Lasse
Bstohrer
07.05.2018, 22:39
Following along.
I have been having the same issue with the same errors as Lasse. Although it doesn't seem to matter what version of GCC, or firmware. I'm on P4: 7.12 and my WiFi to 6619 and GCC 1.1.1.4. It has happened with all versions of firmware, WiFi and GCC. It just happens much more often now.
Bob
I keep a copy of GCC 1.1.1.2, only for backup/restore settings because always fail during transfert with newest GCC on P4.
MatthiasF
08.05.2018, 09:17
This will be no problem with firmware and GHL Control Center versions.
It could be due to resyncs to the WiFi network, where a timeout occurs.
Setting the timeout in the 'connection administration' can help here for proper reconnection.
As Matthias wrote: http://forum.aquariumcomputer.com/showthread.php?13406-GHL-Control-Center-1-1-1-3&p=81638#post81638 "some deep changes, some parts of the communication stack had been heavily re-worked".
On GCC 1.1.1.2 with same timeout settings: "3000ms" i can backup settings most of time without problem, but with newest GCC most of time it fail.
:-)
Thank you for answers
I´ll try with 5000 ms and see if it will be better
Sincerely Lasse
houman_hashemi
10.05.2018, 07:20
Hello,
I found something which could help perhaps: I had error code 28 sometimes with GCC 1.1.1.3 and 1.1.1.4. When it happens, there are two solution:
1- reboot my computer,
2- use GCC 1.1.1.2 to connect. So I keep 1.1.1.2 on my computer and use it for that.
I don't think it's a matter of firmaware.
I have Profilux 3 with firmware 6.34.
Hope it can help to fix it.
Houman
Hello,
I found something which could help perhaps: I had error code 28 sometimes with GCC 1.1.1.3 and 1.1.1.4. When it happens, there are two solution:
1- reboot my computer,
2- use GCC 1.1.1.2 to connect. So I keep 1.1.1.2 on my computer and use it for that.
I don't think it's a matter of firmaware.
I have Profilux 3 with firmware 6.34.
Hope it can help to fix it.
Houman
Number 1 works for me - but normally not for a long time. Number 2 - have not tested with 1.1.1.2
I test with 5000 ms - its get better but if my computer is heavy loaded (I try to let GCC save my measurements the same time that I try to surf the net) - I get Error 28.
Sincerely Lasse
It´s getting better with 5000 ms - only get the error once since I change from 3000 to 5000
Sincerely Lasse
Bstohrer
16.05.2018, 20:53
It´s getting better with 5000 ms - only get the error once since I change from 3000 to 5000
Sincerely Lasse
Lasse,
I tried 5000 ms, still many error 28s and 50s per day. Tried 9000 ms and now I can stay connected for a 1-3days at a time.
Bob
Matthias
17.05.2018, 08:01
to
As Matthias wrote: http://forum.aquariumcomputer.com/sh...1638#post81638 (http://forum.aquariumcomputer.com/showthread.php?13406-GHL-Control-Center-1-1-1-3&p=81638#post81638) "some deep changes, some parts of the communication stack had been heavily re-worked".
On GCC 1.1.1.2 with same timeout settings: "3000ms" i can backup settings most of time without problem, but with newest GCC most of time it fail.
and
I found something which could help perhaps: I had error code 28 sometimes with GCC 1.1.1.3 and 1.1.1.4. When it happens, there are two solution:
1- reboot my computer,
2- use GCC 1.1.1.2 to connect. So I keep 1.1.1.2 on my computer and use it for that.
the customers here are talking about ProfiLux, not Doser
I changed only one aspect in regards to communication from 1112 to 1113: the Doser gets a regularly keep alive in order to prevent the TCP socket to close down
-> I highly doubt that there is any difference between 1112 and higher versions for P4 communication
so I see no sense in using the outdated 1112
about the timeout
honestly I think it does not matter if you have 1000ms, 3000ms or even 5000ms
if you need that high timeouts than there is something heavily wrong with your Wifi/LAN network
the normal response time is max. 30ms!
in my network it is between 10ms to 20ms
in GCC is a "communication monitor" - activate it and see the reponse times - if there are may red or even black bars then there is a problem in the communication
-> I highly doubt that there is any difference between 1112 and higher versions for P4 communication
so I see no sense in using the outdated 1112
On GCC 1.1.1.2 with same timeout settings: "3000ms" i can backup settings most of time without problem, but with newest GCC most of time it fail. It's a fact...
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions, Inc. All rights reserved.