cjbassman2

That's great thanks. I thought this was the case but wanted to check. Thanks also for the useful lockPort() function advice - could be useful 🙂

I've created a user function as a stand alone sequence that I'm successfully calling from my main sequence. Can this function be called simultaneously from two separate main sequences or do I need to create one for each calling sequence?

I tried 5000 but no change. Same as you this used to work fine but something has changed, I don't remember doing anything that I think could affect it. When the external is the primary/only monitor it works fine. Leaving DAQ open on the external screen, I change it back to extend it moves DAQ to the laptop screen. When I then drag it to the extended screen it remains laptop screen size and won't expand further. I tried compatibility to Windows 8 - no change. I tried changing 'High DPI settings' to System (Enhanced) - no change. I'm running Windows 10 BTW. Life's weird sometimes!

Thanks for your prompt and educational response. I think I've done that change but still have the problem. Have I done it correctly?

Hi, Have a laptop with a higher resolution external monitor. When I run DAQ on the external monitor it refuses to fill the screen when maximised. This is in development mode. All other Windows application adjust ok between laptop and external monitor ok, but DAQ remains fixed at a maximum size equal to the laptop screen. This used to work ok but something has changed. All suggestions welcomed.

Thanks. I'll look at changing our batch file.

Hi, Yes didn't include any license codes for obvious reasons but felt this was a generic issue. I think your point about 'firing up DAQ' using a .ctl is the problem. We have a batch file that does just that so we'll try running it with no file and re-installing the code. Thanks

Hi, I've got DAQ running on a PC with a runtime license and it suffered a power cut. When the PC boots back up I get an error of "License error occurred - Please contact technical support" We tried uninstalling DAQ, deleting the DAQ folder and re-installing DAQ. We then tried re-entering the license by using the on-line and manual options but we get "Key not found" error. We're managing to run it as a 25 day trial at the moment but can anyone suggest what the problem is and how we can get it working back under the runtime license again? Thanks

It would be great to be able to change the way items in the watch window are displayed. To be able to choose Hex, Binary, ASCII or the default Decimal would often help debugging. TIA

Thanks for your quick response. This has generally been running as a runtime without problem on another PC in the factory. I'm now adding some more stuff. My development computer died and I've replaced it but I can't see how that is related. I'll email you the file and try out some of the samples. TBH it seems so random. It's been working OK for a couple of hours now but keeled over in a matter of minutes a few times before that. What's the best email address?

I'm working on a DAQ application with a pro dongle license. The problem I'm having is that DAQ just closes every few minutes or maybe up to half an hour or so. There are no messages, or prompts to save work (which is annoying as I keep losing work). I've tried moving the dongle to different USB ports to no avail. Would you have any suggestions what it might be/what I should look for. I've seen some posts mention memory leaks but I've watched the memory in task manager and everything looks stable. I've attached my application for your reference. ESG4.rar

Thanks for your advice. I'll have a play around with those points.

I've developed an application to work on a touchscreen. It works fine and when using a mouse the buttons depress up/down when they are 'clicked' ok. However when the operation is performed with a finger on the touchscreen the buttons don't generally go up/down. I've seen them move occassionally but generally they don't move. The button functions perfectly but it would be nice for the operators to get then response from the buttons. Any ideas?

Thanks. The two workarounds have now solved my problem.

Do the problems you describe explain why whenever DAQFactory starts up on this PC it thinks there are two versions of it running (although there isn't)? It also seems to always start up in development mode despite me entering the runtime license info. As this is now on the shop floor I only want it to start up in runtime. Is there no work round? I'm happy to run version 17.1 but as I developed the app in 18.1 it won't run in 17.1. Could I install 17.1 on my development PC along with 18.1 and copy and paste everything over to make a 17.1 operable version of my app?