Waterppk

Hello, I have inherited a VI that is running a while loop and a timed loop in parallel. The while loop has no delay/wait until next so it's just cruising along eating CPU time, the timed loop is set for every 2ms but obviously finishes late on every iteration. Is the while loop capable of blocking execution of the timed loop? Thanks! Chris

I searched around the forums/online and I can't seem to find anyone who's used LabVIEW to monitor folders for changes in files/folders. I'm collecting data on a network drive in my building and then hoping to have my data post processor monitor that folder for generated data, when data is generated I then want the post processor to automatically process the data but not touch any old data. Any thoughts?

I have to say there are a few bugs with Veristand, mainly little things once you get beyond getting the software installed and configured, but overall it is simply head and shoulders better than using SIT or any of the previously available systems/solutions. I'd encourage you to give it a try. Regarding specifically getting mixed channels up and running, it's kind of unusual because they aren't using MAX for configuration, it's configured in Veristand by just telling it you want MIO and how many channels of what you need. Magic happens and you suddenly have channels available to map system I/O to physical I/O with analog/digital/counter/etc. CAN implementation is also much easier/more configuration available. The best part is the workspace, once you get beyond that it's not anything like LabVIEW in the sense that they've really integrated the editing and running modes to the point where you don't stop the program to edit the UI, you just do whatever you wanted to and it's done. That said, you can still import anything from LabVIEW if you want/need it, allowing you to build custom whatever VI's and put them into Veristand. Overall, a little buggy getting off the ground but once you've got it figured out it's great!

Yeah, turns out to be quite the mess. Veristand RT install doesn't even show up in the software list unless you've got the newest version of LV Real-Time installed, one of the default packages with LV RT is the Web Server 1.0.0, which ironically conflicts with the 9.0 version of RT at this time, so it won't let itself install. I can't find a newer version of RT web server so I've just not installed it to get RT 9.0 up so I can install the Veristand RT. Moral of the story - if you get a cryptic message about not being able to connect to the FTP server when deploying from Veristand and you've checked your networking it's likely actually that you haven't/weren't able to install the Veristand RT, which doesn't show up if you check the software packages listing if you haven't updated RIO, CAN and RT!

Nobody's touched Veristand? I think I may have figured it out, I'll post confirmation when I'm done downloading LV2009, it's likely that I need to run new drivers on the RT system all around to get support for Veristand on the PXI (CAN, RIO, RT, etc).

Anybody out there playing with Veristand yet? I can't get it to connect to my PXI (in addition to many other fun bugs)

Works great and makes sense, thanks for the VI and the help!

Alright, so the latest project is to drive a throttle body type valve with Pulse Width Modulation (http://en.wikipedia.org/wiki/Pulse_width_modulation). I have a number of PCI cards to choose from (using PCI-6123 counter 0), and am able to correctly run my valve through MAX. I'm having trouble running a VI and controlling the duty cycle through it. The valve needs to be driven at 128 Hz and varying duty cycle between 5% and 95%, which I've tested through MAX and it works great. The attached VI will run the valve, but it won't update: so I can input a duty cycle, run the VI and it will move to the requested position, but when I change the duty cycle in the front panel control it doesn't change the valve position or the PWM output. I have any test tools available if they're needed, but this looks to be a problem with my understanding of how to control a counter's output duty cycle in a VI. Any ideas? Available hardware devices are (if you have something against using a 6123 for some reason): PCI-6122 PCI-6123 (currently using ctr0 and works fine) PCI-6601 cRIO: 9211 9481 9481 9203 9265 9411 SCXI: (Can't use, too slow) 1102B 1102B 1520 1124 1520 Gen_Dig_Pulse_Train-Continuous-Variable_Freq_LV86.vi

I inherited this piece of code, it's running on a NI cRIO and the objective of the code is to move variables from the RT variables to globals or vice versa. Anybody have a better/cleaner way of doing this?

I spoke with someone from LabView who does the actual RT programming (on the LabView side) at a conference today in Milwaukee. He said that my PC vi (it's running on the correct target) would attempt to redeploy the variables if it didn't think they were deployed, he said the same thing you did, that the easiest thing is to create a build for the RT and run that, then to disconnect from the target and run the local files, otherwise of course I could try tracking down the dependencies and figure out what the actual problem is. Thank you both for all of your help!

Got it back, just set everything in MAX to reinstall and it rewrote the configuration file (I would imagine). The webserver now works properly, I switched the port back to 80 so the browser wouldn't have any issues and it still works fine. Still don't know how to get a 'full' deploy where I can run a VI on my PC and also have VI's on the RT system running concurrently without issues, the ONLY reason I'm wanting to do this is so the VI's properly deploy everything, like my HTML pages (which I can set to be copied over to the www folder with a deployment, but if I just run the VI on the RT it doesn't copy over).

I do have the niwebserver.conf in the root, I suspected having to deploy to get the settings to change so I was doing that, but it's nice to know where the files are ending up so I can check, here's my niwebserver.conf: # Web server configuration file. # Generated by LabVIEW 8.6 # 3/25/2009 1:05:01 PM # # Global Directives # ServerRoot "." LogLevel 2 TypesConfig $SERVER_ROOT/mime.types ThreadLimit 10 LoadModulePath "./modules" "./LVModules" "./.." LoadModule LVAuth lvauthmodule LoadModule LVRFP lvrfpmodule LoadModule dir libdirModule LoadModule copy libcopyModule LoadModule esp libespModule LoadModule LvExec ws_runtime Listen 90 # # Directives that apply to the default server # ServerName UW HIL DocumentRoot "/ni-rt/system/www" Timeout 60 AddHandler LVAuthHandler AddHandler LVRFPHandler AddHandler dirHandler AddHandler espHandler .esp AddHandler LvExec AddHandler copyHandler DirectoryIndex index.htm KeepAlive on KeepAliveTimeout 60 Good news, I figured out the problem - the NI webserver wasn't an installed component! I went into MAX and checked the installed software and I was wanting to install that component. Bad news - the only reason I was in MAX was because I nuked the ni-rt.ini and redeployed without rebooting. This created a new ni-rt.ini file and so then I rebooted the PXI system (having a 'fresh' ni-rt.ini file), now when it boots it says: "System state: No software installed", so I would imagine in their infinite wisdom some NI programmer felt that LabView should write all the configuration data to the ni-rt.ini, so my system isn't aware that it's configured and ready to go. The good news is that it's still recognized in MAX, but I can't FTP to it to fix the ni-rt.ini Any ideas on how to proceed from here? Format the disk and start over or? Thanks

QUOTE (Neville D @ Mar 25 2009, 07:01 PM) Thanks for the quick response, I hadn't seen it when I posted previously I changed the HTTP port to 90 and tried to connect through a browser (192.168.1.200:90) and get nothing, I also tried pinging ports 80 and 90 and again get nothing. I tried connecting to the Remote Panel and get: Remote panel connection refused by specified server: Make sure LabVIEW Web Server is enabled on specified server I verified my settings in properties (by right clicking on my chassis), however when I FTP'd to it and checked the settings they were not as set, it had: WebServer.Enabled= FALSE I manually edited that line to read: WebServer.Enabled=True and recopied it over but it made no difference. My current ni-rt.ini in the root of the PXI is: [LVRT] CDIntervalTicks= 55 EnableCPULoadDisplay= True LABVIEWRTDir= C:\ni-rt\system PATH= C:\ni-rt\system\; RTCPULoadMonitoringEnabled=True RTEnetRcvMode= 2 RTTarget.ApplicationPath= c:\ni-rt\startup\startup.rtexe RTTarget.EnableFileSharing= True RTTarget.TimeZone= CST6CDT RTTarget.VIPath= C:\ni-rt\startup server.tcp.access= "+*" server.tcp.enabled=True server.tcp.serviceName="Main Application Instance/VI Server" SocketRecvBufferSize= 65535 SocketSendBufferSize= 65535 StartupDLLs=c:\ni-rt\system\taggerrt.dll;c:\ni-rt\system\mxsemb.dll;c:\ni-rt\system\NcRpcSrv.dll;c:\ni-rt\system\nidevldp.dll; c:\ni-rt\system\taggerrt.dll;NiRioRpc.dll;NiViSrvr.dll;c:\ni-rt\system\nipxism.dll;niorbp.dll; WebServer.Enabled=True WebServer.TcpAccess="+*" webservices.SecurityAPIKey="PqVr/ifkAQh+lVrdPIykXlFvg12GhhQFR8H9cUhphgg=:pTe9HRlQuMfJxAG6QCGq7UvoUpJzAzWGKy5SbZ+roSU=" webservices.ValidTimestampWindow=15 [NVE] MessageQueueUpperBound=1000000 [sTARTUP] EarlyStartupLibraries= C:\ni-rt\system\lvuste.dll;C:\ni-rt\system\tsengine.dll;C:\ni-rt\system\nisl_emb.dll; MainExe= /ni-rt/system/emblview.exe [sYSTEMSETTINGS] Comment=00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 Comment_Format=512 Host_Name=EcoCAR-Chassis1 Protect_Reboot=FALSE [TCP_STACK_CONFIG] DNS_Address=0.0.0.0 Gateway=192.168.1.1 IP_Address=192.168.1.200 Subnet_Mask=255.255.255.0 Thanks again for your help!

QUOTE (Waterppk @ Mar 25 2009, 06:06 PM) Looks like I can't ping port 80, which would make it hard to handle an http request, any ideas? Chris

Hello, Running LabView 8.6 I'm using a PXI system and trying to create a build that will run on the PC and also deploy my project on the PXI system. I can create a build file for the PXI and have that run, however if I try to run the PC VI that monitors the network shared variables from the PXI system, it will just try to run over the PXI deployment resulting in the PXI VI's stopping and the PC VI starting. Seems like I'm missing something. . . Bonus points if you can tell me why I can't get the webserver up and running. I have the PXI system set up at 192.168.1.200, my PC is also behind the same router at 192.168.1.100, I have enabled the web server on the PXI system and have all of the "filters" set to asteriks, so I shouldn't be blocking myself from accessing the web server. There are the default files (like Index.htm) in the PXI web root (at C:\ni-rt\system\www) and I can ping the PXI system, however when I navigate to 192.168.1.200 in a browser I get nothing, also going directly to 192.168.1.200/Index.htm returns nothing. Thanks much and let me know if you need more information! Chris