Printable View
available now
New in V1.1.1.8:
Support for newer magnetic stirrer model (V2) for ProfiLux 3 (with included firmware 6.38), ProfiLux 4 (with included firmware 7.16) and GHL Doser 2/2.1/Maxi Slave/Standalone (with included firmware 1.30)
Sockets/switch channel Operating hour meter can be set for ProfiLux 4
Good Morning,
After the upgrade to this version 1.1.1.8 I noticed two issues:
1: My PL-ADIN card has now stopped working in my V2 Expansion Box.
2: my Salinity port has now stopped working in my Expansion box. I even re-calibrated it and it still fails. I went as far as swapping it with my other salinity probe on my P4 to confirm it still a working probe and it works. It just sits at 100ms. I have reset the V2 Expansion Box.
I was able to resolve #1 Issue. After a full reset of the both the P4 and the V2 Expansion Box it now seeing the PL-ADIN Card.
I can still not get my salinity probe off from reading 100ms thou. I do not have any non expired calibration solution, so just ordered some and will try a re-calibration of it when it comes in.
Something did break in the V1.1.1.8 software.
Even after a calibration, the system is still alerting on the salinity probe. I even reseted the Expansion V2 box and the P4.
As you can see even with the Alarm Disabled, it still produced an alarm.
Attachment 11085
What concerning is the Salinity readings should not activate the alarm.
Attachment 11086
The Display shows for the Salinity ***
Attachment 11087Attachment 11088
App Notification
Attachment 11089
Steps I have done:
Re-Calibrated the Probe 3 times using GHL calibration solution.
Replaced the Probe from my other P4 unit and calibrated the probe I took off the V2 Expansion Box when I placed it on the P4 and the probe works, and the one that was on the P4 placed it on the V2 Expansion Box, calibrated it and I still get the error.
Rebooted both the V2 Box, and the P4
I am running the latest Firmware, and software on all devices. This did not happen till the upgrade to V1.1.1.8
Thank you
If you revert back one FW version, does the issue persist?
In the one screen shot the Alarm shows disabled and I still receive the alert in V 1.1.1.8
To revert back, do I a backup of the config as it is today? Or do I restore the config that I had before 1.1.1.7 then go back one Firmware? Or do I go back one firmware then restore my backup files?
Thanks
Which firmware versions are installed on your devices?
The current firmware versions in GCC V1.1.1.8 are:
ProfiLux4: V7.16
ExpansionBox2: V2.04
ProfiLuxTouch: V1.06
Below are my Current Firmware levels:
P4: V7.16 (Wifi is 6816)
Expansion Box 2: V2.04
Both of My Touches show V1.06.
ProfiLux4 most likely detects a sensor error.
This happens if the actual value exceeds the maximum ADC.
What does your ADC show and what are the limits in the sensor settings?
Another possibility could be caused by virtual sensors. Do you use any in combination with Cond.(S)?
ADC?
Attachment 11099
I do not have a virtual probe for the Cond.(s).
I found the ADC :)
Here is my entire probe settings inside GCC Desktop Software.
Attachment 11100
Settings seem fine.
Another approach could be isolating the PAB-system, which signals a communication error when no response came on time.
If there are other PAB-devices on the bus, isolate ProfiLux4 and ExBox2; use another PAB-cable, too, just to be sure and try the second PAB-port on each device.
The Expansion Box is right off the P4, less then 18 inches away. I did replace the cable and it dong the same thing.
I then went about disconnecting everything, only leaving the Expansion Box and the P4 connected and did not make a difference.
This happened right after I did the upgrade it was working ok before the upgrade.
The devices are already seperated, so can you please revert to the previous firmwares (ProfiLux4 and ExBox2) and try again?
want to make sure I do this correctly?
You want me to revert back both on the P4 and the Exbox to the previous versions?
Do You want me to do the Exbox2 First and then the P4? Or do the P4 first then the Exbox2?
I am only asking this because the probe was working with the Exbox2 was at V2.04 and P4 was at V1.1.1.7?
Thank you
Hello Kevin,
revert to the same firmware versions that worked before.
V1.1.1.7 is GHL Control Center's version number and not ProfiLux4, which was in your case propably V7.15.
So, try P4:V715 and ExBox2:2.04 (if these are the versions that definitely worked for you before).
Sorry for the delay,
Reverting the code back and the probe works now so it is related to the upgrade?
Hello Kevin,
just to be sure: you are currently using P4:V715 and ExBox2:2.04 and you have correct reading and no error is shown?
I do not see the relation between the versions (V715 and V716). There have no modifications been made that would explain that.
The ADC2 value is at the upper limit (1023), so the probe may be just bad.
Upgrade again to V7.16, recalibrate the probe and check the readings.
Matthias,
Sorry for the delay, it still did not work, and I ordered another salinity probe and will post the results once it arrives.
Any problems going straight from GHL Control Center 1.1.1.2 and firmware 7.12 to this update ?
No problems.
Just make sure you create a backup copy of your P4 settings and sensor settings.