08-24-2016 02:59 AM
software : LV 2016(RT, FPGA), LV 2015(RT, FPGA), NI-RIO 16.0, DAQmx 16.0
hardware : cRIO-9033, cDAQ-9134 RT
OS : Windows 7 x64
Hello, This is Seyong.
I installed LV2016 Korean (RT,FPGA,RIO 16.0) and update firmware of cRIO-9033 from 3.5 to 4.0.0f0.
The firmware version of cDAQ-9134 RT is 3.0.0.
Embedded UI is fine under LV 2015 but is not working under LV 2016.
Under LV 2016, my monitor says "no signal" and go into sleep mode.
I can see the logo of National Instruments, GRUB and boot messages.(refer to attached bootcapture.png please.)
I tried 'disk format' several times cRIO and cDAQ.
Regards,
08-24-2016 03:27 AM
cRIO-9033(firmware 4.0)
LV 15.0.0 + RIO 15.0 is fine.
LV 15.0.1 + RIO 16.0 is not working
LV 16.0.0 + RIO 16.0 is not working
cDAQ-9134(firmware 3.0)
LV 15.0.0 + DAQmx 15.0 is fine.
LV 16.0.0 + DAQmx 16.0 is not working
08-24-2016 10:01 AM
Hmm, that's not something that I've seen, what monitor are you using? Can you still contact the controller through MAX? If so, can you enable ssh, boot the target normally (such that it exhibits the issue), and copy the Xorg logs from the controller? It will be located at /var/log/Xorg.0.log
08-24-2016 09:15 PM
In addition to the log file BradM mentioned it would be helpful if you can also capture the output from the 'dmesg' command. At the shell command prompt (serial or ssh) redirect the output from dmesg into a file and attach:
# dmesg > dmesg.log
Some other helpful information in debugging this would be:
08-24-2016 09:54 PM
Hi, BradM, gratian.crisan
This is rapid response for you.
I will post again about log file.
I can run LabVIEW project VI and SSH by Putty.
And,
mini DP to VAG is APL-A1307(B) designed by Apple in CAlifornia.
monitors are,
LG 23MA53. ON-LAP 1002
These monitors and VGA adapter are fine during last 1 year with cRIO-903x
I tried under two OS system. Results are exactly same.
(1) Windows 7 Enterprise K sp1, 64bit with 16GB RAM.(office laptop)
- LabVIEW 2015, 2016
(2) Windows 10 Home 64bit, with 4GB RAM(personal labtop)
-LabVIEW 2015, LabVIEW 2016
Regards,
=========================
Please refer to attached log file.
08-25-2016 02:46 PM
Once we have the output from dmesg we might be able to tell more about what's going on but from the logs posted so far it looks like the Intel video driver is not reading the EDID (i.e. adapter/monitor information) correctly for this adapter and monitor combination.
You can see how that's supposed to look in the 2015_Xorg.0.log:
[3212386.673] (II) intel(0): EDID vendor "MTC", prod id 49
[3212386.673] (II) intel(0): Printing DDC gathered Modelines:
[3212386.673] (II) intel(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz eP)
This is likely a regression in the video driver (kernel or Xorg driver). We are tracking down the miniDP->VGA adapter model you describe in order to reproduce the issue.
08-28-2016 08:27 PM
Hi, gratian.crisan
APL-A1307(B) is same MB572FE/A.
Sorry, it's korean certification name.
Actually, this one maybe....(I bought it at apple shop)
I tried same adapter to a 'LG L1960TR, 19")
It's fail.
So, I tried another adapter NEXTLINK-MDPD02(mini DP to DVI, active, 4k).
It's fine.
I think it's adapter problem.
Regards,
09-08-2016 07:59 AM
I am also using the apple branded active mini-display to VGA adapter and am seeing issues. I have a cDAQ 9132, LabVIEW 2016 32 bit, host is Windows 7 x64 SP1. If the controller is booted into safe mode I see the display working, and during the bios I also see the display working. But with LabVIEW 2016 installed, no console output is seen, or embedded UI (when either is enabled and restarted). I'm pretty new to this hardware in and Linux in general. Is there anything I can do to help debug the display? Do I need to find a different display adapter?
Firmware version 3.0.0f0
Operating System NI Linux Real-Time x64 4.1.15-rt17-4.0.0f0
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
09-08-2016 08:23 AM
Found these articles from Apple Support. The flickering and not waking from sleep issue could be what you're seeing.