Quantcast
Channel: All LabVIEW posts
Viewing all 203034 articles
Browse latest View live
↧

Can you manually set a "dirty dot" (file changed indicator) in an executable window title?

October 8, 2024, 9:06 am
$
0
0

I'm probably using the wrong terminology here, which is why I can't find it in Google, so apologies if this is dumb.

 

I have an application where a user can load in a test file, do some stuff, then save it if they want to.

 

I'd like to add "asterisk appears in the window title when the file is unsaved" functionality to my program.

 

Obviously, I can just read the current window title and append an asterisk, but I wondered if this might be an OS-level thing where I can tell the OS that this window should have the "dirty dot".

 

For example, I don't use Macs or Linux much, but I could imagine they may have a different style to indicate a changed document than Windows. I could also imagine other languages might have a different dirty dot scheme.

 

So, I wouldn't be surprised to learn that there's a "set dirty dot" function that calls OS stuff to set this, and I'd rather use that if it already exists.

↧
Search

Re: Using the LabVIEW Shared Variable

October 8, 2024, 9:08 am
$
0
0

Shared variable is installed with the LabVIEW runtime engine.  the only other thing you might need might be the Datalogging and Supervisory Control module.

↧
↧

Re: Strange memory issue

October 8, 2024, 9:15 am
$
0
0
I would agree that this looks like an environment issue. I would suspect that the compiler optimization setting might have something changed.

Two things I would check first:
A) run VIA after setting the cyclic complexity threshold excessively low. (try to get lots of FAILURES)
B) tweak the ini option for compiler optimization all the way to 10(Rarely Limit)
Failing all else- see if you CAN find a LabVIEW.ini from the developer that checked the older files into SCC. Worst case here is that a NEWLY APPLIED optimization caused the leak. You really can't "UNAPPLY" an optimization - you would need to go back to the original working code and recompile with the original setting.
↧

Re: Strange memory issue

October 8, 2024, 9:15 am
$
0
0

After further investigation it definitely looks like something with the LabVIEW environment. I ran the executable of the previous version and it is exhibiting the same issue. This is the same application that is currently running in production. I also tried running from source code using LV 2023 and that ran without issues. Now the hard part is how to I fix my environment so everything will be normal again. It should be noted that this application is pure software. No DAQ or hardware device drivers are being used. The devices the system communicates with use either Modbus or REST APIs. In my testing I am not using the REST based devices as I don't have simulators for those yet. It does use a few .Net calls but there aren't many. A few to get the memory usage. I will have to dig around the environment to see if I can identify any changes. In the meantime I will try building on a different computer.

↧

Re: Can you manually set a "dirty dot" (file changed indicator) in an executable window title?

October 8, 2024, 9:25 am
$
0
0

Just go ahead and set the Windows Title property.  There won't be an easier way and, the property node will give you a great place to attach the BD comment explaining what you did.

 

That "Wheel" is round enough, no need to reinvent a new one. 

 

You might consider also setting a file unsaved flag to throw a user prompt for save in the "application Close?" Event.

↧
↧

Re: Can you manually set a "dirty dot" (file changed indicator) in an executable window title?

October 8, 2024, 9:34 am
$
0
0

Fair enough. I already have the user save warning popup, I just wanted to spruce up the UI a bit. I figured if the OS could handle appending the dot and removing it, it would save me the bit of time to make a function to do it. Plus if Windows comes up with some kind of "stick a red dot on the window icon to indicate file changed" in the future, then this would be forward-compatible 🙂

 

I'm using MGI's Panel Actor library so I'll probably just make a message to set or clear the dot.

↧

Re: Working toward Certified LabVIEW Developer Certification

October 8, 2024, 9:57 am
↧

Re: Darren's Occasional Nugget 06/12/2023

October 8, 2024, 10:03 am
↧
Search

Real-Time Convergence Feasibility question

October 8, 2024, 10:07 am
$
0
0

Hi,

 

I have a conceptual question about whether or not its possible to have a labview program  iteratively change the input values, in this case voltage and drive, during a looping operation to converge on a desired forward power.

 

We are using a transmitter to perform microsecond pulses that is being fed input values from a waveform generator that is being controlled by labview.  Apparently, in its present condition, if the control dials on the transmitter are manipulated manually, the drive can be changed to incrementally to move towards the desired forward power but doesn't do fine adjustments well and will end up overshooting and then have to be dialed down in the other direction.  What I am trying to accomplish is some sort of iterative process so that while the program is running, the program can take the inputs and the recorded output(forward power) and adjust the inputs accordingly so that they converge on some combination of values that achieve the desired forward power.

 

Is this something that labview can perform?  I know that if a control is placed into the program it is initialized that way for the duration and has to be manually changed by the operator in general.

 

A general flow would be something like:

 

Initialized values program start --- pulse --- forward power read --- adjustments made to initialized values --- pulse --- forward power read ---adjustments made or no change because it has converged --- pulse --- adjustments made or no change because it has converged.

↧
↧

Re: LabVIEW subscription model for 2022

October 8, 2024, 10:13 am
$
0
0

Hi Ahmed,

 

 

I hope all is well, I appreciatie that you try to repair mistakes previous made. I also understand turning to a other direction can be chaotic. 

 

Trying to sell the idea of a subscription license to my managers is impossible. Rise of prices at the same time did not make things better, "what if they rise prices again and we did invest another year in writing code in Labview?", "I need to write reports for 2 months make a wiring diagram, then I don't need a Labview License". I can write a lot of reasons the subscription was a bad idea, this forum one of the longest I have seen so far so I will not add more reasons.  A lot of my colleagues are turning towards  C# or Matlab solutions. This means they are also turning away from NI hardware. This also means the time I did invest in education, like evenings learning Labview writing code is in the danger zone. I am not talking about a few evenings here...

 

So I thought well lets give it a try see what happens. I did ask for a quote a few weeks ago at this site:

Perpetual Development Software Licenses for LabVIEW - NI

 

I did not receive any reply. I did give it another try today. On the site I get a message telling me:

 

"Your information was successfully received"

 

I do not get an automatic generated mail as conformation. Nothing there. I also got into contact with the company representing NI and Labview in the country I live. Although they should be informed about the situation the sales person told me to pay 4 x the subscription license cost, the first year support would be included the next year I needed to pay extra for support. Those prices are not restoring confidence.  I don't know if there is a conflict in intrest here, you can get that when you outsource the sales. Anyway I did not get any discount offer. 

 

Can you please make me an quote?

 

A friendly advise I did already mention about outsourcing and conflict of intrest, If I am willig to pay 10k for a measurement system, I need proper technical support when deciding what to buy and how to integrate the system before I buy. Some sales guys simply have not got the technical background to sell these products, NI will never get proper feedback why sales drop and NI will lose market share. Not because the products are bad, they are really high class but because of information loss in the sales proces I rather would have direct contact with NI if needed. Or at least give me a way of sending feedback about the sales company to NI.

 

I hope you give an answer soon. If you need some feedback I am willing to use some time in the evening to reply (my employer is not that happy if I reply during the day about this matter), however please try to find a way to restore the trust so the people working with and invest time in NI products

find their time well spend.

 

↧

how to transmit and receive an image with two USRP 2901 and Labview

October 8, 2024, 10:22 am
$
0
0

Hello, I need to carry out a practice that consists of transmitting an image by means of a USR 2901 and BPSK modulation to receive it in another USRP 2901. I can't find a block diagram that allows me to do this yet. I wanted to know if anyone here has any examples of how to do that. ...

↧

Re: Application builder - Invalid characters in filename

October 8, 2024, 10:35 am
$
0
0
@billko wrote:
@Bob_Schor wrote:

The App Builder crashes when you ask it to build something.  The Error Message is clear, and makes great sense -- your Build seems to specify a file whose name has the characters *IDN?.vi , which are clearly not "legal" filenames, and must reside somewhere in your code.  If you can't find these characters by yourself, post (all of) your code and we'll help you look for this misplaced string (looks like a VISA command/response).

 

Did the code work in an earlier version of LabVIEW?  Have you tried going back to the "earlier version that worked" and seeing what has changed?

 

Bob Schor

Yeah, the OP posted that it used to work in an earlier version.  This sounds like a legacy driver.  LabVIEW must be handling files within an LLB differently these days.  (Although really I am surprised it ever worked.)

Serendipity.  I just reminded another poster that LabVIEW.ini has an old token to allow browsing inside LLBs.  The default value is FALSE.  This could be a legit way for the App Builder to have worked in a previous version with the same token value = TRUE. 

↧

Re: BUG: LV crashes when autocreating controls/indicators of free wire

October 8, 2024, 10:50 am
$
0
0
@billko wrote:
@Yamaeda wrote:

A cowworker clicks a lot while thinking often creating wires. These are most often not connected to anything and the new autocreate controls (which is a neat idea) don't know what to create and spins crazy and crashes LV.

Can it be turned off?

A coworker of mine has a more annoying habit of moving things around while thinking, then putting them back and SAVING it.  That used to work back in the days before versioning software (although even then this was not considered good practices), and of course when I review changes, I have to ask about the VI that changed but wasn't captured in the change log.  Not to mention the space wasted by committing a file that didn't need to be committed. 

 

Unfortunately,  annoying coworkers (goatworkers and sheepworkers) cannot be turned off automatically.   I HAVE found that they can be TEMPORARILY disabled with a cast-iron skillet 🍳 applied directly to the mouse-hand or cranium (depending upon the severity of the annoyance)

 

Note: I am no longer bothered by coworker behaviors.

↧
↧

Shared Variable dialog not visible in trial version of Community Labview

October 8, 2024, 11:43 am
$
0
0

I'm new to Labview and am trying to learn how to use shared variables between two main.vi files.

 

I could not see the Shared Variable dialog under the project folder (My Computer/New/..).

 

Is this feature not available for the trail version?  I attached a screen-shot of what I can see with regard to menus.

 

Thank you for any help and apologies in advance.

 

Thank you.

↧

Re: Shared Variable dialog not visible in trial version of Community Labview

October 8, 2024, 11:40 am
$
0
0

Shared Variables have to be under a library. Create a library and then you can right-click on the library to create a Shared Variable.

↧
Search

Re: Shared Variable dialog not visible in trial version of Community Labview

October 8, 2024, 12:09 pm
$
0
0

Hi.  And, thank you for replying.

 

REVISED: My OS is a Mac (Big Sur).  Is this an admin issue?

 

I added a library and obtained a build error: Error 8 occurred at Create Folder.  The verbose reply message is below. Any help gratefully appreciated.

 

Click the link below to visit the Application Builder support page. Use the following information as a reference:

Error 8 occurred at Create Folder in Create Directory Recursive.vi->AB_Destination.lvclass:Create_Destination.vi->AB_Build.lvclass:Create_Destinations.vi->AB_Application.lvclass:Create_Destinations.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_DLL.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_Frmwk_Build.lvclass:Build.vi->Build Wrapper.vi->Build Wrapper.vi.ACBRProxyCaller.6D20003B

Possible reason(s):

LabVIEW: (Hex 0x8) File permission error. You do not have the correct permissions for the file.

/Applications/National Instruments/builds

↧

Re: Shared Variable dialog not visible in trial version of Community Labview

October 8, 2024, 1:14 pm
$
0
0

Revised again.  I read somewhere that Xcode for MacOS was required for building the shared library, so I installed Xcode.  Still no luck on the error message.  Hope for some help from the community.  Thank you

↧
↧

Re: Shared Variable dialog not visible in trial version of Community Labview

October 8, 2024, 2:15 pm
$
0
0
@hornPlayer wrote:

Revised again.  I read somewhere that Xcode for MacOS was required for building the shared library, so I installed Xcode.  Still no luck on the error message.  Hope for some help from the community.  Thank you

I can only confirm, that this option is missing on Mac (Sonoma and xcode is installed), here is side by side comparizon with Windows:

Screenshot 2024-10-08 23.12.34.png

↧

Re: Converting DAQmx Scaled values to Unscaled in I32 resolution

October 8, 2024, 2:25 pm
$
0
0

When using DAQmx Compute Reverse Polynomial Coefficients VI, you don't have to input the number of points to be the same as the number of possible unique ADC codes*. Try attached VI.

*You may want to validate the scaling at all possible ADC codes (and then the unscaling) just to make sure the fit that DAQmx computes is good at every value you care about.

↧

Re: Real-Time Convergence Feasibility question

October 8, 2024, 2:36 pm
$
0
0

Try this example:
examples\control\PID\General PID Simulator.vi

There are several controls examples that can be found using the NI Example Finder.

↧
Viewing all 203034 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>