22 December 2010
Notes from remote Bomgar session w/ Martin Osisoft
1. PI connection manager re-created
2. New local PI trust created. Found local trust was missing.
3. He reminded that Interface will update only 20 tags / 2 min. designed for protection from flooding (which is cool i think).
3. All OPC tags should have Location3 = 1 (enable Advise mode) instead of Polling Mode.
- I now notice from Watch Log "Advise class 1, ...." which was not present last time
- 817 tags per group is too big (so it will be adjusted automatically by having Advise Mode)
- /UR = 5 in the ICU which i havent figure out what it is actually.
- Update Rate settings was deleted in the ICU (which i also have no idea at the moment).
2. New local PI trust created. Found local trust was missing.
3. He reminded that Interface will update only 20 tags / 2 min. designed for protection from flooding (which is cool i think).
3. All OPC tags should have Location3 = 1 (enable Advise mode) instead of Polling Mode.
- I now notice from Watch Log "Advise class 1, ...." which was not present last time
- 817 tags per group is too big (so it will be adjusted automatically by having Advise Mode)
- /UR = 5 in the ICU which i havent figure out what it is actually.
- Update Rate settings was deleted in the ICU (which i also have no idea at the moment).
20 December 2010
Multiple Foxview screens having different time
ok. so u might have more than 1 FoxView screen. in my place, we have 2 and certain AW/WP having 4 FoxView license.
so if u see each-and-every-one screen having different time (lagging by 1 min). The explanation is as below:
- Foxview updates its timestamp (top middle screen) every 1 min
- Its time source is your Windows clock
- So, in order to reset all Foxview screen's time, do as follows:
1. Open the date/time Windows applet where you can see the clock.
2. At 3 secs (this is not fixed - it depends on how fast your Foxview loads) before your Windows clock is about to change to the next minute, CLOSE your FoxView.
3. Depending on how your Foxview is configured, some plant has Foxview to auto-open once closed. If yours is not configured that way, u can always manually open additional Foxview screen by going to File > Additional Foxview.
4. Foxview changes it's clock once a minute based on WHEN IT WAS STARTED. It can be 1 second to 59 seconds off of Microsoft Windows time depending on when it is started.
Cheers Foxlist !!!
so if u see each-and-every-one screen having different time (lagging by 1 min). The explanation is as below:
- Foxview updates its timestamp (top middle screen) every 1 min
- Its time source is your Windows clock
- So, in order to reset all Foxview screen's time, do as follows:
1. Open the date/time Windows applet where you can see the clock.
2. At 3 secs (this is not fixed - it depends on how fast your Foxview loads) before your Windows clock is about to change to the next minute, CLOSE your FoxView.
3. Depending on how your Foxview is configured, some plant has Foxview to auto-open once closed. If yours is not configured that way, u can always manually open additional Foxview screen by going to File > Additional Foxview.
4. Foxview changes it's clock once a minute based on WHEN IT WAS STARTED. It can be 1 second to 59 seconds off of Microsoft Windows time depending on when it is started.
Cheers Foxlist !!!
19 December 2010
using Foxtst program to check FoxAPI version
FoxAPI (Local) comes on the Day0 CD for V4.3, V6.2 and V6.4.
FoxAPI V4.3.2 is the latest, plus there are QFs on top of that to get you to the latest version.
V4.3.x comes on a separate CDROM, I suggest purchasing or replacing your FoxAPI CDROM. Your local sales/service rep. can help you with that.
Use the foxtst utility to determine the installed version of FoxAPI™ software. Type:
cd /opt/fox/ais/bin
foxtst
Enter 1200 for the Sub Menu choice prompt.
Enter 29 for the function selection prompt.
The FoxAPI version information is returned, for example, “FoxAPI_version = 4.2.6.”
As I recall V4.2.8 ( came as a QF) was the best version to use before V4.3.X came into exsistance.
Regards,
Scott L. Landry
Sr. Systems Service Eng. II
IOM Gulf Coast District
FoxAPI V4.3.2 is the latest, plus there are QFs on top of that to get you to the latest version.
V4.3.x comes on a separate CDROM, I suggest purchasing or replacing your FoxAPI CDROM. Your local sales/service rep. can help you with that.
Use the foxtst utility to determine the installed version of FoxAPI™ software. Type:
cd /opt/fox/ais/bin
foxtst
Enter 1200 for the Sub Menu choice prompt.
Enter 29 for the function selection prompt.
The FoxAPI version information is returned, for example, “FoxAPI_version = 4.2.6.”
As I recall V4.2.8 ( came as a QF) was the best version to use before V4.3.X came into exsistance.
Regards,
Scott L. Landry
Sr. Systems Service Eng. II
IOM Gulf Coast District
16 December 2010
Mark V HMI - Timesync Problem
i have a problem with Mark V HMI MTK (Master Time Keeper) in this case my GT1_SVR running Windows NT 4.0 not able to be connected to my GPS Clock Module(in this case Arbiter System 1084B).
http://www.arbiter.com/catalog/product/model-1084a-b-c-gps-satellite-precision-time-clock-(40ns).php
This Mark V HMI has got a special PCI card from Symmetricom BC635PCI installed and at the back of the PCI card, a coaxial RG-58 connecting to my Arbiter 1084B.
U can see shot below, the supplied software from Symmetricom which is BC635CPP cannot connect to the GPS module. Observe the "tracking" in red color.
also see this Mark V TCI (Turbine Controller Interface) settings in Control Panel.
http://www.arbiter.com/catalog/product/model-1084a-b-c-gps-satellite-precision-time-clock-(40ns).php
This Mark V HMI has got a special PCI card from Symmetricom BC635PCI installed and at the back of the PCI card, a coaxial RG-58 connecting to my Arbiter 1084B.
U can see shot below, the supplied software from Symmetricom which is BC635CPP cannot connect to the GPS module. Observe the "tracking" in red color.
also see this Mark V TCI (Turbine Controller Interface) settings in Control Panel.
Meinberg Lantime M600 GPS Timesync Module (Backview)
just fyi..
Meinberg Lantime M600 GPS Timesync Module (Backview)
12 December 2010
Foxboro I/A P92 rebuild log - FAT at Bukit Jelutong
1. configure SysDef using Components Configurator (CC).
2. save your final *.cfg file (SysDef file) for backup.
3. create Commit Disk using CC. U will need Media Distribution Disk which comes along your P92 from USA.
4. install Day 0 cd ie. I/A 8.5. U will need to supply Commit Disk which u've built via step 3.
5. U will also need to supply Revision Level Disk for I/A 8.5 (also comes with your P92).
6. reboot
7. install FoxView (and FoxDraw) via given cd.
8. install System Manager 2.0 (note that I/A 7.X doesn't support this software)
9. assign CP letterbug using Dell PDA.
10. install IACC, Ferret etc etc
Note
d:/opt/fox/iacc/coExistance (setting file location)
2. save your final *.cfg file (SysDef file) for backup.
3. create Commit Disk using CC. U will need Media Distribution Disk which comes along your P92 from USA.
4. install Day 0 cd ie. I/A 8.5. U will need to supply Commit Disk which u've built via step 3.
5. U will also need to supply Revision Level Disk for I/A 8.5 (also comes with your P92).
6. reboot
7. install FoxView (and FoxDraw) via given cd.
8. install System Manager 2.0 (note that I/A 7.X doesn't support this software)
9. assign CP letterbug using Dell PDA.
10. install IACC, Ferret etc etc
Note
d:/opt/fox/iacc/coExistance (setting file location)
07 December 2010
Physical memory limit in Windows
Physical memory limit in Microsoft Windows...
http://msdn.microsoft.com/en-us/library/aa366778(VS.85).aspx
http://msdn.microsoft.com/en-us/library/aa366778(VS.85).aspx
03 December 2010
Subscribe to:
Posts (Atom)