09-15-2018 01:19 PM
@altenbach wrote:
Is there an explanation on exactly what the "issue" is/was? Just telling us what "to do | not to do" is not a solution, especially since all types of installers are still available.
So you had problems with a platform bundle? How about the "web based" installer?
99% of all users here need more than just "plain vanilla LabVIEW and nothing else", so this is not a solution.
@altenbach Sorry, the NI support group said their R&D team was looking into the issue. I was able to find a solution to my problem so I'm assuming they won't tell me what the problem was, but if they do then I will be sure to post it here 🙂
YES, my problems came from the platform bundle installations. I'm not sure about the web based installer.
And YES, this IS a solution! It is a solution to MY problem which is why I made the post in the first place.
Something from the NI bundle installation was causing my network adapters to crash. I assumed it was LabVIEW, since being part of the 1%, that's all I was concerned with.
So I guess this post is only for the 1% that is interested in the "plain vanilla LabVIEW and nothing else".
But as I mentioned, I'll be more than happy to pass along any new information I receive from the NI support group and perhaps it will help the 99%.
09-15-2018 02:07 PM
@altenbach wrote:
@kylemanIs there an explanation on exactly what the "issue" is/was? Just telling us what "to do | not to do" is not a solution, especially since all types of installers are still available.
I would bet the issue is with one or more of the hardware drivers that get installed with a full platform bundle. Whether it is DAQmx, or something else would be interesting to know, possible it is even in one of the low level platform drivers that is used by most NI hardware drivers.
08-05-2019 03:29 PM
Hello the same issue on my laptop,
To eliminate any doubts and suspicions about a specific computer, I did following:
- I took exactly the same model of DELL Latitude E6230 as my laptop which has the issue with WiFi after wake-up. WiFi module in DELL is Broadcom 802.11n
- I put a brand new SSD into the laptop
- I installed Win10, 64bit, build from April 2019
- I installed DELL driver for WiFi
- I installed Office 2019
- I downloaded a few Win updates until they detected that there is nothing to download
- I made the image of SSD
- I tried at least 30x sleep mode, and woke up the laptop, I tried to restart /switch OFF / ON and several times, WiFi always worked without any problems, (no Win10 WiFi issue as NI support claims)
- I installed LabView 2019, LabView NXG3.1 and everything the installer itself recommended (among others it installed DAQmx)
-wake WiFi immediately stopped working after rebooting, disabling and re-enabling the WiFi adapter does not help, either Win FastStartUp enable/disable does not help
- I refreshed the SSD by image with fresh Win10 + Office2019
- then I installed only LV 2019, LV NXG3.1
- WiFi works smoothly after waking up, no Win10 WiFi issue.
-then I installed DAQmx
-WiFi stopped working after waking up, disabling and re-enabling the wifi adapter does not help
I see a very obvious causal link between installing NIDAQmx and the difficulty of waking up WiFi.
I very much welcome advice on how to install NIDAQ into a usable state after installing NIDAQ (hibernation is out of the question, because closing the display at least 10 times a day is both time consuming and will destroy the SSD soon)
Having absolute no issues with Win10 64bit, LabVIEW 2016 and NIDAQmx from 2016 till now when I reinstalled to NI SW from 2019.
Hope somebody help me
Petr
08-07-2019 02:55 PM - edited 08-07-2019 03:00 PM
Fresh Win10 64bit, installed strictly NI DAQmx, nothing else even suggested. The same issue with not working WiFi after wake-up from sleep mode.
Solution:
go to Win services and disable all NI services, Turn off Windows, start your laptop and you can enjoy fully functional WiFi after wake-up from sleep mode.
Stupid, but no better solution yet.
Petr
08-08-2019 02:43 AM
Really solved? I do not thing so.
Have a look here:
https://forums.ni.com/t5/LabVIEW/Labview2017-will-disable-my-wifi-connection/m-p/3957537#M1126419
Petr
08-08-2019 05:44 AM
It is not up to you to decide if a particular message is the solution for the Original Poster's problem. For him, his problem IS solved.
I'm sorry that his solution isn't working for you.
08-08-2019 06:36 AM - edited 08-08-2019 06:37 AM
Also spamming every possible thread that has been created about this issue won't really help. You may feel angry about this issue but if it was as simple as you believe it is it would have been resolved long ago, and if it was as common as you believe there would be MANY more posts about it.
For one I use a computer with Intel chipset too (most computers nowadays do that) and don't have that problem, so there is definitely more to it than just a simple fix in some NI low level platform driver. Most likely it is a combination of specific chipsets, BIOS and various drivers for chipset, network card and what else that causes a situation where one of the NI services causes problems. The problem could be just as much in one of those components but makes itself only appear in the presence of one of the low level DAQ drivers which do go pretty deep into the OS kernel.
The way to resolve this is not by writing responses to many threads but by creating a support request and working constructively with the support people to provide as much information to them as possible. That will mean investment of time and sweat from your side but will be in the end much more productive than multiple rants on the forums.
08-08-2019 07:09 AM - edited 08-08-2019 07:53 AM
I am so sorry gentlemen I wrote to two threads and I wrote "not solved". My fault, yes it is solved for HIM.
Anyway believe me I spent many days on this issue already instead doing my regular job wihout working solution yet. I fully understand there are tons of combinations of HW, BIOS, etc., but from the other hand Dell Latitude laptop with latest BIOS and latest Windows does not sound too exotic to me (yes, still room for combinations I know). The reason I wrote this information in discussion forum is not to spend even more time and "spam every possible thread that has been created about this issue" as you wrote, but to inform others who are suffering what I did already and how to avoid this issue (unfortunatelly this is not solution if DAQmx is needed).
In case I will investigate something new I will write in this thread only (if allowed):
Again I am so sorry.
Petr