Agh got ya
This brings me exactly to the point I try and get across when clients get ********** and blame Profilux. Here is the reason for my point
The drivers are not written or manipulated by GHL in anyway, they are provided by the USB chipset manufacturers. GHL is reliant 100% on their performance and what the PC/laptop they are being installed on.
You case is a perfect proof of this-
Installing a third party driver on a pc GHl have no control over with no profiLux attached in effect taking the ProfiLux 100% out of the loop, the issue of failed install happened with no GHL equipment being part of the failure.
So where is this GHL's fault? well no where really, it just shows the unreliability of USB and why GHL do try and favour RS232, but the issues here is RS232 is dog old technology which no modern PC has access to.
So whats the way forward?
My personal belief is we need to move towards Ethernet uploads and connectivity, we then reove the issue of drivers, but then move onto the instability of a persons personal network.
Will GHL ever win this battle?
Tough one, too many variables are involved, but for sure GHL is working solidly to make LAN very stable when the network it is connected to is stable.
There is a point to remember here also - GHL have far more advancements than any other controller, it is also not just a controller and another point is the continual updates to meet user demand mean you have to perform firmware updates more often so put at risk these errors when doing them. GHL could just not do any releases for 6 months, sit back develop all in house and then release but user demands do not dictate such luxuries.
With us all working together GHL connectivity is getting stronger and stronger, and lets not forget we are not aware of one single functionality bug, just cases of uploading firmware issues, and since the release of 5.0P drop outs also have reduced massively.
I am still happy to say wthout risk that GHL is still "bug free" yes it has firmware update issues due to various connectivity options, but operationally it is rock solid
Hope that makes sense.
Last edited by aqua_digital; 02.04.2010 at 18:27.
The issues that you raise are no different from any number of other software providers. Compatiability is a constant problem and you are correct to say that it is a catch 22 because GHL gets the blame for it when it may very well be an issue dealing with others' drivers. But that is also the same problem that any number of other software providers have.
I hope that I am not sounding critical. I originally installed my firmware "p" with no problems and was nothing but happy. I was asked to install over usb to usb to see if it worked and I was happy to do it although I would liked to have known that I was testing a suspected issue.
I still have nothing but praise for the company (with the exception of the user manual). I would like to write a version just for english speakers that is more user friendly. If I had a free weekend, I would just do it and post it on line for anyone to review and see if it is more helpful, but I am not going to do that.
Finally, I love the controller, the dosing pumps are by far my favorite and I am a loyal customer. I will continue to buy GHL products and I will be happy to help in the future with "pushing buttons" to see what happens for the betterment of this hobby.
I will play around with the driver issue some more now that everyone else in the office is gone and see what happens.
Ken
Last edited by Ken Good; 02.04.2010 at 18:34.
I guess I am glutten for punishment. I reinstalled the driver and it recognized the new driver. So now that I am an expert on using the flasher file, I decided that I would try it all again. But I have to say that I got the same result. Although this time, I was down for at most five minutes and not 2 hours.
Here is what happened. I connected to the controller using the software over the USB to USB connection. I selected the firmware "p" and started the update process just like I have many times before. I tried to monitor what happened. Again, the update stopped in the middle. I believe that it stopped where the controller shuts off all the outlets and the firmware continues. It was at this point that the update stopped.
I am wondering if maybe it is shutting down power to the USB outlet too. Just a thought.
So now that I am an expert on the flasher feature, I will confirm that the P3 has an issue installing and updating firmware "p" over the USB to USB using the profilux software.
Ken
I now make you an official expert can you try it after following the instructions in this link, setting an RS485 delay
http://www.aquariumcomputer.com/Foru...ead.php?t=1937
Last edited by aqua_digital; 02.04.2010 at 19:16.
Okay, I am now just into S/M. I did as you requested. I feel like I just set a record this time. I must have been down for only 2 minutes. But I got the same result. Error took place at the same point. The firmware update stopped at the same place as last time. When the controller shuts down the outlets this is when the firmware update stopped.
Ken
Last edited by Ken Good; 02.04.2010 at 19:34.
I am posting this to see if my new banner works.
Please disregard.
Ken
Hi Ken
many thanks your your hints - I think this was an important discovery
it seems the USB connection is disturbed when the sockets are deactivated during the update, maybe the switching off of the connected devices cause electromagnetic distrubances which are large enough to jam the USB connection.
Could you try an update over USB when the powerbar is disconnected?
Bookmarks