Hi:
I was working with FTView 5.0 and Historian 2.0, server/client application, and the continuous bugs an errors makes me sick. Here is a list of some of them:
- When you drag a pop-up display (On Top display), the background screen flashes.
- The alarms (FTAE) sometimes disconnect from Server, with no reason.
-The alarm banner can’t show the alarms sorted by event (time and date of the trigger), for example to show the last alarm ocurred, like RSView32.
-Sometimes in the activity bar appears the message “Server is running in grace mode”, although the licenses are installed correctly in server (Server and RSLinx Enterprise).
-The TrendX control doesn’t works correctly reading data from FT Historian. It hangs when tou try to navigate in the X axis (time). Also, the ActiveX doesn’t show the real time data value (in the legend in bottom). Also it hangs when you try to read more than 15 or 24 hours from a datalog.
- Another error from TrendX (don’t care where is reading data from). When the display is opened, the last lapse of time shows wrong in the pens, it seems like the data in that period of time doesn’t exist and the graphic try to interpolate that space. If you open again the display, the previous error lapse shows correct, but the new last lapse shows with error, and so on. The error only occurs in the last lapse of time, from the end of X axis to 1 or 2 minutes backward, depending of the scale used.
-Sometimes, when you execute the display command, the display doesn’t appears, although in the activity bar the command shows executed. With this, the client application state in a grey background without a display and you have to apply the classic Ctrl.+alt-supr to exit to Windows and then restart the client.
-Sometimes, the animation color of a object (red for 0 and green for 1) is not reflected in the client display, although the bit in ControlLogix has toggled. You have to close and open the display to see the change. This happens random and is very problematic because you don’t know the real state of the tag. For example you start a motor and the motor graphic continues in red, but in real the motor is running and the running bit in Clgx is in 1.
- The tooltip text in the objects that references global objects sometimes works and sometimes no. They looks flashing and you can’t read the text.
- When you copy and paste and element (for example a button) from one display to another, an error appears. You have to make with drag&drop, although sometimes this action makes the program crash and appears the Windows errors report.
- When you right click “add component to application” to add a display from another application, with the same language even, then all the texts of the added display appears with ?
I don’t remember more bugs for the moment, but I have to say that any of this errors was corrected with the patches from Rockwell.
I hope that FTView 5.1 version and FTHistorian 2.1 might be released soon. I'm can't downgrade to RSView Supervisory 4.0, because I understand that the displays are not compatible.
If anyone knows how to correct some of this bugs, I would be very grateful.
Thanks
I was working with FTView 5.0 and Historian 2.0, server/client application, and the continuous bugs an errors makes me sick. Here is a list of some of them:
- When you drag a pop-up display (On Top display), the background screen flashes.
- The alarms (FTAE) sometimes disconnect from Server, with no reason.
-The alarm banner can’t show the alarms sorted by event (time and date of the trigger), for example to show the last alarm ocurred, like RSView32.
-Sometimes in the activity bar appears the message “Server is running in grace mode”, although the licenses are installed correctly in server (Server and RSLinx Enterprise).
-The TrendX control doesn’t works correctly reading data from FT Historian. It hangs when tou try to navigate in the X axis (time). Also, the ActiveX doesn’t show the real time data value (in the legend in bottom). Also it hangs when you try to read more than 15 or 24 hours from a datalog.
- Another error from TrendX (don’t care where is reading data from). When the display is opened, the last lapse of time shows wrong in the pens, it seems like the data in that period of time doesn’t exist and the graphic try to interpolate that space. If you open again the display, the previous error lapse shows correct, but the new last lapse shows with error, and so on. The error only occurs in the last lapse of time, from the end of X axis to 1 or 2 minutes backward, depending of the scale used.
-Sometimes, when you execute the display command, the display doesn’t appears, although in the activity bar the command shows executed. With this, the client application state in a grey background without a display and you have to apply the classic Ctrl.+alt-supr to exit to Windows and then restart the client.
-Sometimes, the animation color of a object (red for 0 and green for 1) is not reflected in the client display, although the bit in ControlLogix has toggled. You have to close and open the display to see the change. This happens random and is very problematic because you don’t know the real state of the tag. For example you start a motor and the motor graphic continues in red, but in real the motor is running and the running bit in Clgx is in 1.
- The tooltip text in the objects that references global objects sometimes works and sometimes no. They looks flashing and you can’t read the text.
- When you copy and paste and element (for example a button) from one display to another, an error appears. You have to make with drag&drop, although sometimes this action makes the program crash and appears the Windows errors report.
- When you right click “add component to application” to add a display from another application, with the same language even, then all the texts of the added display appears with ?
I don’t remember more bugs for the moment, but I have to say that any of this errors was corrected with the patches from Rockwell.
I hope that FTView 5.1 version and FTHistorian 2.1 might be released soon. I'm can't downgrade to RSView Supervisory 4.0, because I understand that the displays are not compatible.
If anyone knows how to correct some of this bugs, I would be very grateful.
Thanks