zobert
-
Posts
8 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Gallery
Posts posted by zobert
-
-
I have alway set these in my INI file:
appFont="0" 13
dialogFont="2" 13
systemFont="1" 13
HideRootWindow=True
blinkBG=000000FF
thanks for the font info. I guess I will need to find a way to detect the OS and go from there.
So far Microsoft has kept Arial in all the OS versions and this is the reason I have decided to use this as my standard font for all functions. I even make these my defaults in the labview.ini file for the IDE.
-
Since Win2K I have been adding following to application ini files to "fix" my fonts. These match what I have set development environment to use for fonts.
MyApplication.ini
[MyApplication]
FPFont="Arial 14"
appFont="Arial 14"
dialogFont="Arial 14"
systemFont="Arial 14"
BDFont="Arial 14"
Default Windows System Font.
NT4 - MS Sans Serif
2K/XP - Tahoma
Vista/7 - Segoe UI
- 2
-
Are you using PBMS to simulate Profibus Network? Need to make sure check simulate box in configuration tool for each slave. Also need to set slot number when configuring Analog modules.
Been using (via OPC) to simulate slaves for my PFB master cards and LabVIEW. Have developed DLL wrapper VI's (will locate and ZIP) for "GetRXData" from PFB cards which would be similar for "Set" and PBMS card. Easiest thou is via OPC.
Also, card name needs to match (CASE SENSITIVE) what is in device manager. i.e. "Card" does not equal "CARD"
-
I am interested in finding out how many of my fellow LAVA lovers have had success interfacing LabVIEW with PCS 7 and what method was used to communicate - i.e. Profibus, OPC, etc
Have used the SST series Profibus cards to make "soft" PLC with LabVIEW for 10+ years. Had to make DLL wrappers but works well. If card software comes with DLL and .h files can have LabVIEW generate DLL wrapper VI's. Also have used OPC via Profibus ethernet CP to communitcate with PLC's.
-
Microsoft releases new Windows Updates (unless serious security risk) Second Tuesday of the month.
Also a reason to save work before leaving at the end of the day.
Worked out with our IT staff to have a seperate GP for our development and production machines to notify that updates are available so we can ensure systems are in a safe condition when updates are applied.
Just remember other programs can do the same, seen with many AV products as well as with most other apps that default to check for updates.
-
QUOTE (Michael Aivaliotis @ Feb 3 2009, 09:03 PM)
I installed Windows Vista on my PC. Now when I open old code which was written on Windows XP, all the fonts on the Vi diagrams seem to be slightly bigger. I notice this because text and string constants are now touching other objects when they weren't before. This also applies to bundle\unbundle nodes, properties etc. Anyone know how to fix this? I'm using LabVIEW 8.6. This even happens to newly created VI'sIs this just the new standard?
Same issue when 2000 was released.
NT4 MS Sans Serif
2000/XP Tahoma
Vista Segoe UI
I have been using the BDFont=, appFont=, etc... in all ini files since Win2K release since still supporting apps on NT4 and all new apps have alignment issues when installed on NT4.
-
Check out Symmetricom. They have LabVIEW drivers for a few of their IRIG-B cards.
http://www.symmetricom.com/products/gps-so...ware-downloads/
QUOTE (spsuamin @ Jan 12 2009, 12:47 PM)
Hi Everybodyhttp://www.irigb.com/IRIGB_standard.html
Usually the decoding of the signal takes place using hardware, however the customer has only provided the raw signal and has left the interpretation responsbility to my company.
P.S. I know there is a FPGA example at ni.com but I don't have FPGA software and so it made it difficult for me to figure out what was going on in the code.
Any information would be great. Thanks in advance
LabVIEW Development System Has Stopped Working
in LabVIEW General
Posted
http://windows.microsoft.com/en-US/windows7/install-and-use-windows-xp-mode-in-windows-7
With Win7 Pro you can use Microsoft's VM.