Black strip in front panel

Hi,
I'm using LabVIEW 8.6 and I've created a top-level application. On and off I've been working with this for several weeks without problems until now. Before it appeared I was working on replacing the controls and indicator with system types instead of modern.
Now there is a black strip (or rectangle shape) which sits below the menu and tools bar, these are some artefacts I've noticed.
the shape is only visible in edit mode (not runtime)
the shape resizes with the front panel to fit the width of the window
the shape remains beneath the tool bars regardless of where I pan to
I can't select it to do anything
I only see this in this particular VI
when I click save the black strip is replaced with a copy of the menu bar. The previous working menu bar is now non-functional of course.
Restarting LabVIEW and loading onto another machine has no effect - the issue is with the VI not the LabVIEW setup I believe.
I would really like to not have to copy/redo this work into a new VI. Anyone have any suggestions??
Attached are some screen shots which will explain things better.
Cheers.

Update Jan 26, 2015!!!
I put this here as well... We need to smash this bug and help NI Figure out a bug fix...
Same thing happened in LV 2013 SP 1 On Win 7, Saved in LV 11, opened in another machine, STILL has the bug... Can not get rid with resetting or anything.. Is transported with the vi's and LLB's... Seems to STICK with this front panel. Seems to be an "attribute" of the color I added when this happened. I could Ctrl Z "out" of adding the color but the Black Strip stayed there...
Suspect it occured when I tried to change the panel COLOR with the paintbrush...
Here is the BLACK bar... It SWITCHES up and down from the Blue to the Black..
Developers!
KNOW WHAT IS GOING ON??
I put the offending code in the
Service Request #2222205
Go get that bug and let me know when you SMASH it! Will be a fun and rewarding one to find.. Look into the Paintprush interraction with screen extents AND how this interracts with SCROLLBARS... When we paint on a BORDER??? What if panel elements overlap??
What if we SHOW ALL hiddel elements?? I tried that too...

Similar Messages

Audigy 2 Platinum Front Panel

I just built a new custom machine and I want to use my audigy 2 plantium. My new case is black and the front panel is white. Can I just purchase a new front panel that is black? Or can I just change the white face plate? It looks like the white face plate just clips on. There is nothing wrong with the device other than its an eye sore. I looked on creative's website and could not find anything about replacement panels. I really do not want to buy a new X-Fi Platinum and spend $99 bucks on a backup computer, as I already have a X-Fi in my main system.
Thanks for the help.

Actually I'm having the same problem too here.
Did all the troubleshooting I could the only thing left is to test the AD_EXT cable.
Anyone able to give some advise on this?

Front panel controls show up one at a time

When I first open my main vi the controls on the front panel appear one at a time over 20-30 seconds. The problem was compounded when a second front panel was made switching between the two the controls for the second panel pop up one at a time and after they all appear the first panels controls go away one at a time. Any ideas on why this ocurs and how do I fix it so the transition happens quickly?

BenThe code is modeled on a vi that was done under LV5 and was also ported over to new computers and LV8. We had to install the traditional drivers to get that code to run on the new systems. The original vi transitions fairly quickly. The new vi is modeled on the original code with efforts being made to strip it of the overhead bagage. ie.the sequence structures and controls no longer needed..... The new code from the begining has sequentially brought up each control with each new control being added it progressively gets worse. With the addition of the second front panel in the same vi the protracted transition of the controls became a significant issue.
Bob
Attachments:
20060817.zip ‏2692 KB

How to make some part of front panel transparent?

There is a property node to make a front panel completly transparent...but is there anything that only makes some part of the vi transparent like if I define a decorative block in the vi which takes 1 quardant of front panel and I have a control to make it transparent during runtime...
And moreover the frontpanel transparent property makes the whole window transparent, is there any way to retain toolbar of window like stop, run button when front panel is transparent??

Hi,
Have a look at this VI (attached). To make it work you need to create an image mask as a .png (open paint, colour in the areas that you want to become invisible and save it as a .png). The VI diffentiates between white areas and black areas of the mask you create, the black areas will become transparent and the white areas will remain the same- this will be implemented on your front panel. I've included an example of a possible paint image in "mask2.png".
You may also want to play around with the resolution of the mask created in paint, this will effect how the program works (I advise you use a lower resolution than your display- I used 500x300)
NT: If the front panel controls disappear, go into the block diagram window and attach a false constant instead of a control. Let me know if this works
Cheers, Tom
Attachments:
custom window.zip ‏107 KB

LEDs on front panel

Employed my Vista Pavilion for several years without incident until last night when I noticed the top "on/off" button which usually glows a light blue was unlit.   I originally assumed a power glitch, so I just restarted the machine to note the following:
    Fans come on and the power supply seems OK, but the system did not boot.   The screen was just black with no characters or image/background. In fact, the screen's power saving mode soon engaged indicating the video card was not sending a signal. Never get to the BIOS screens.
     Now here is what I think may be significant: the green LED and blue LED in the front console were on continuously.
Sometimes, hardware manufacturers provide diagnostic information by way of the lights (e.g., washing machines).   In other words, turning on LEDs can provide state information. Is this true with HP hardware?
Some more clues which tell you what is not the problem. I happened to have a new power supply handy, so I traded it out with the same results.   In normal operation, the green LED indicates disk activity, so I just removed the disk entirely to see if the green light would go out.   Nope, still on steady.   The blue LED typically implies the WiFi operation but I rather doubt at this pre-boot state the WiFi would be working.
I traced the power button line (two grey wires) to a half-sized board in the rear. No breaks in the wire or bad connections.
Any ideas?

HP Pavilion Elite m9357c Desktop PC
Motherboard Specification, MCP61PM-HM (Nettle3)
http://h20564.www2.hp.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-c01357175
Don't understand this reference to a half-height board.
The Front Panel Header (9-pin, 2x5) on the motherboard is where those front panel LEDs and buttons are terminated.
EXAMINE Pictorial in the Internet link to motherboard (above).
HOWEVER, some HP Desktop models have a front LED to show the user of LAN or Wi-Fi connections.
That wire would connect to the network card or motherboard via a different connector.
Some Media PCs of this era (2008) had Infared connections (option) for remote control of TV tuner option card.
LEDs do not last forever (have a long, but finite life) and can fail due to DC over-voltage or surge conditions (environmental, component failure).
In addition, this Desktop PC is now 7 years old .... a long-life for any desktop.
IF the motherboard has failed (component failure, such as capacitors), then replacement may be best advice.

Print Front Panel/Change Colors?

Unfortunately, the optimal GUI for display on a computer screens does not
work very well for printing. I have a program that has a lot of graphs with
black backgrounds and it really sucks the black ink if it is printed often.
In the past, I solved this issue by having a duplicate screen that I sent my
data to that had white backgrounds. In this case I have a lot of tabs,
controls, and indicators and it would take too long to create all the print
screen scenarios on a separate VI.
Question: Does anyone know of a simple method to invert colors or change
brightness of panel printouts to use less ink?

When using Bill's solution, you can use the "Panel >> Defer Panel Updates" property using Property Nodes. Set it to TRUE, then change colors, print the front panel, reset the color, then set the "Defer Panel Updates" to FALSE.
That way the user will never see the panel color change.
Please see the attached image.
- Philip Courtois, Thinkbot Solutions
Attachments:
PrintWhitePanel.JPG ‏59 KB

Is there anything like a front-panel OPEN or FP.STATE property for an RT (cRIO) VI?

I'm wondering if there is a way for an RT VI to detect when its front-panel is open, both when run interactively from within a project and also when accessed remotely as an embedded window within a browser?
Solved!
Go to Solution.

I know about the "Remote Panel:Connections to Clients" property and I'm already using that to tell whether a remote connection is active (as opposed to running the VI within the development environment). It cannot however tell if the front panel is open within the development environment.
As for the property-node returning an error, that does not appear to work here (perhaps I have selected the wrong property, I'm using the get-reference-to-front-panel property). I suspect that since the VI is setup to work with a remote front panel, the VI thinks that a front panel does exist even when a remote connection does not. I suspect this error check would work if the VI had not been setup for use with a remote connection because then the front panel would be stripped out as the VI was built or perhaps deployed to the RT system.

VI Method "Front Panel:Get Image Scaled" Memory Error 17

Hi all, I've got two almost identical sub vi front panels that I'm dumping to a jpg image for reporting purposes. One was copied and slightly modified from the other to show a different data set and plot. The original works just fine, but the second sub vi, when using the "Front Panel:Get Image Scaled" method to pass the image to write the jpg, always returns the following error:
"Error 17 occurred at Invoke Node in Myprogram
Possible reason(s):
LabVIEW: Not enough memory to manipulate image.
=============================
NI-488: Unrecognized command.
Method Name: Front Panel:Get Image Scaled
[Continue] [Stop] "
I've stripped the problem section into a simple tiny new that only opens the report and tries to get the image with the same working/non-working result above. Using the Execution Trace Highlighter, it error is definitely occuring when the Method executes.
Any ideas? Thanks.

Hey cjgpr,
I haven't been able to dig up much info on this error message. There's one other discussion forum post that talked about it some, and a KnowledgeBase article on it. It seems that whatever changes you made to the front panel have caused it to exceed your computer's memory when creating an image. Try removing items until it works, then see what actually breaks the functionality.
Brian B
Field Sales Engineer
Tennessee/Southern Kentucky
National Instruments

Why does the Font color change on my front panel?

I'm using the Font Dialogue to change the color of highlighted text on my front panel. After I save and reopen my app some of the Text will revert back to their original color (Black). Is this a bug in or am I missing something?

I assume that you want all control labels with white text. If I change the black ones to white and save the VI, the white text color is retained.
LabVIEW Champion . Do more with less code and in less time .
Attachments:
Control Console.vi ‏90 KB

Need new I/O Front panel Cable

Hey all, I was sleeving my I/O Front Panel cable and when managed to mess it up. So bassically what I need is a new cable. Do you guys no any way I can go about getting me a new one? I believe the cable is called AD_Link cable.

http://www.computercablesource.com/round-ide-cable-24-inch--dri've-ultra-ata-33-black-347.html that is advertised to work with it.

Asus Xonar DGX no rear sound / mic. Front panel sound/mic ok. [SOLVED]

Hi guys,
I have a ASUS Xonar DGX PCI-E GX2.5 sound card since my onboard audio crapped out on my motherboard. I just did a first time install on my desktop and the rear portion of my card refuses to work. If I connect up my speakers to my analog output in the back I don't have any options in my sound manager for the analog output to just be a 2.0 system. I get 4.0, 4.1, 5.0, 5.1. All of which do not work obviously. Also my microphone doesn't work plugged into the actual card. If I plug them into the front panel audio, both the microphone and headphone out work. I did some searching, and it seems like a likely cause has something to do with amixer being multichannel. I tried several commands but wasn't successful in getting the audio to work through the back. Any help would be useful, I'm still trying to learn a lot about Arch while doing all this. Thanks in advance!
Solution. Using Alsamixer in terminal and selecting the analog out as stereo headphones, instead of stereo headphones (fp).
Last edited by 15goudreau (2014-08-04 21:56:36)

Search for vid and pid combination, ergo 13f6:8788 in your case. This should be one of the search terms, vid and pid could be also separated, other search terms could include oxygen, sonar, dgx and so on. Simple google search should turn something up.
Edit: The point is to locate a thread/post where the support for this card was implemented/talked about. It could provide some further insight.
The simplest approach would be to download linux-rt sources from aur with yaourt, modify PKGBUILD, compile and then install.
yaourt -G linux-rt
cd linux-rt
Copy this into PKGBUILD replacing the original:
# Maintainer: Joakim Hernberg <[email protected]>
# Contributor: Ray Rashif <[email protected]>
# Contributor: timbosa <[email protected]>
# Contributor: Tobias Powalowski <[email protected]>
# Contributor: Thomas Baechler <[email protected]>
pkgbase=linux-rt
pkgname=('linux-rt' 'linux-rt-headers' 'linux-rt-docs') # Build realtime patched -rt kernel
#pkgname=linux-custom # Build kernel with a different name
_kernelname=${pkgname#linux}
_basekernel=3.14
_releasever=12
_rtpatchver=rt9
pkgrel=1
_pkgver=${_basekernel}.${_releasever}
pkgver=${_basekernel}.${_releasever}_${_rtpatchver}
arch=('i686' 'x86_64')
url="http://rt.wiki.kernel.org/"
license=('GPL2')
makedepends=('xmlto' 'docbook-xsl' 'kmod' 'inetutils' 'bc')
options=('!strip')
source=("https://www.kernel.org/pub/linux/kernel/v3.x/linux-${_basekernel}.tar.xz"
"https://www.kernel.org/pub/linux/kernel/v3.x/patch-${_pkgver}.xz"
"https://www.kernel.org/pub/linux/kernel/projects/rt/${_basekernel}/patch-${_pkgver}-${_rtpatchver}.patch.xz"
# the main kernel config files
'config' 'config.x86_64'
# standard config files for mkinitcpio ramdisk
"${pkgname}.preset"
'change-default-console-loglevel.patch'
'0001-Bluetooth-allocate-static-minor-for-vhci.patch'
'0002-module-allow-multiple-calls-to-MODULE_DEVICE_TABLE-p.patch'
'0003-module-remove-MODULE_GENERIC_TABLE.patch'
'0006-genksyms-fix-typeof-handling.patch'
'0007-asus-xonar-dgx.patch')
md5sums=('b621207b3f6ecbb67db18b13258f8ea8'
'89a5af1f3609d0c27e63fea298dd80ed'
'2aa3614e488efa939007a1c428406c30'
'a8126ad28c0a902a575397cacd099db2'
'843119a441c942efc5ec4b73c3c6ced5'
'eb14dcfd80c00852ef81ded6e826826a'
'6623d69fdc936d707990ca060dabd2ce'
'6839ddec74a5300beff1709a81b0e4f3'
'706549e8a05f33f7fc697f28c0ca71d2'
'd23fc66be93ebce698bd7da844789de1'
'16a161979f846b049e90daea907c35dd'
'SKIP')
prepare() {
cd "${srcdir}/linux-${_basekernel}"
# add upstream patch
msg "apply patch-${_pkgver}"
patch -p1 -i "${srcdir}/patch-${_pkgver}"
# add realtime patch
msg "applying patch-${_pkgver}-${_rtpatchver}.patch"
patch -p1 -i "${srcdir}/patch-${_pkgver}-${_rtpatchver}.patch"
# add latest fixes from stable queue, if needed
# http://git.kernel.org/?p=linux/kernel/git/stable/stable-queue.git
# set DEFAULT_CONSOLE_LOGLEVEL to 4 (same value as the 'quiet' kernel param)
# remove this when a Kconfig knob is made available by upstream
# (relevant patch sent upstream: https://lkml.org/lkml/2011/7/26/227)
msg "change-default-console-loglevel.patch"
patch -p1 -i "${srcdir}/change-default-console-loglevel.patch"
# Fix vhci warning in kmod (to restore every kernel maintainer's sanity)
msg "0001-Bluetooth-allocate-static-minor-for-vhci.patch"
patch -p1 -i "${srcdir}/0001-Bluetooth-allocate-static-minor-for-vhci.patch"
# Fix atkbd aliases
msg "0002-module-allow-multiple-calls-to-MODULE_DEVICE_TABLE-p.patch"
patch -p1 -i "${srcdir}/0002-module-allow-multiple-calls-to-MODULE_DEVICE_TABLE-p.patch"
msg "0003-module-remove-MODULE_GENERIC_TABLE.patch"
patch -p1 -i "${srcdir}/0003-module-remove-MODULE_GENERIC_TABLE.patch"
# Fix generation of symbol CRCs
# http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=dc53324060f324e8af6867f57bf4891c13c6ef18
msg "0006-genksyms-fix-typeof-handling.patch"
patch -p1 -i "${srcdir}/0006-genksyms-fix-typeof-handling.patch"
msg "0007-asus-xonar-dgx.patch"
patch -p1 -i "${srcdir}/0007-asus-xonar-dgx.patch"
msg "All patches have successfully been applied"
if [ "${CARCH}" = "x86_64" ]; then
cat "${srcdir}/config.x86_64" > ./.config
else
cat "${srcdir}/config" > ./.config
fi
# if [ "${_kernelname}" != "" ]; then
# sed -i "s|CONFIG_LOCALVERSION=.*|CONFIG_LOCALVERSION=\"${_kernelname}\"|g" ./.config
# sed -i "s|CONFIG_LOCALVERSION_AUTO=.*|CONFIG_LOCALVERSION_AUTO=n|" ./.config
# fi
# set extraversion to pkgrel
#sed -ri "s|^(EXTRAVERSION =).*|\1 -${pkgrel}|" Makefile
# set localversion to pkgrel-rt
sed -i "s|CONFIG_LOCALVERSION=.*|CONFIG_LOCALVERSION=\"-${pkgrel}${_kernelname}\"|g" ./.config
# don't run depmod on 'make install'. We'll do this ourselves in packaging
sed -i '2iexit 0' scripts/depmod.sh
# get kernel version
make prepare
# load configuration
# Configure the kernel. Replace the line below with one of your choice.
#make menuconfig # CLI menu for configuration
#make nconfig # new CLI menu for configuration
#make xconfig # X-based configuration
#make oldconfig # using old config from previous kernel version
# ... or manually edit .config
# rewrite configuration
yes "" | make config >/dev/null
# stop here
# this is useful to configure the kernel
#msg "Stopping build"; return 1
build() {
cd "${srcdir}/linux-${_basekernel}"
make ${MAKEFLAGS} LOCALVERSION= bzImage modules
package_linux-rt() {
pkgdesc="The Linux Kernel and modules (with realtime preemption)."
#groups=('base')
depends=('coreutils' 'linux-firmware' 'kmod' 'mkinitcpio>=0.7')
optdepends=('crda: to set the correct wireless channels of your country')
# provides=("kernel26${_kernelname}=${pkgver}")
# conflicts=("kernel26${_kernelname}")
# replaces=("kernel26${_kernelname}")
backup=("etc/mkinitcpio.d/${pkgname}.preset")
install=${pkgname}.install
cd "${srcdir}/linux-${_basekernel}"
KARCH=x86
# get kernel version
_kernver="$(make LOCALVERSION= kernelrelease)"
# _basekernel=${_kernver%%-*}
# _basekernel=${_basekernel%.*}
mkdir -p "${pkgdir}"/{lib/modules,lib/firmware,boot}
make LOCALVERSION= INSTALL_MOD_PATH="${pkgdir}" modules_install
cp arch/$KARCH/boot/bzImage "${pkgdir}/boot/vmlinuz-${pkgname}"
# add vmlinux
install -D -m644 vmlinux "${pkgdir}/usr/src/linux-${_kernver}/vmlinux"
# set correct depmod command for install
cp -f "${startdir}/${install}" "${startdir}/${install}.pkg"
true && install=${install}.pkg
sed \
-e "s/KERNEL_NAME=.*/KERNEL_NAME=${_kernelname}/" \
-e "s/KERNEL_VERSION=.*/KERNEL_VERSION=${_kernver}/" \
-i "${startdir}/${install}"
# install mkinitcpio preset file for kernel
install -D -m644 "${srcdir}/${pkgname}.preset" "${pkgdir}/etc/mkinitcpio.d/${pkgname}.preset"
sed \
-e "1s|'linux.*'|'${pkgname}'|" \
-e "s|ALL_kver=.*|ALL_kver=\"/boot/vmlinuz-${pkgname}\"|" \
-e "s|default_image=.*|default_image=\"/boot/initramfs-${pkgname}.img\"|" \
-e "s|fallback_image=.*|fallback_image=\"/boot/initramfs-${pkgname}-fallback.img\"|" \
-i "${pkgdir}/etc/mkinitcpio.d/${pkgname}.preset"
# remove build and source links
rm -f "${pkgdir}"/lib/modules/${_kernver}/{source,build}
# remove the firmware
rm -rf "${pkgdir}/lib/firmware"
# gzip -9 all modules to save 100MB of space
find "${pkgdir}" -name '*.ko' -exec gzip -9 {} \;
# make room for external modules
ln -s "../extramodules-${_basekernel}${_kernelname:--rt}" "${pkgdir}/lib/modules/${_kernver}/extramodules"
# add real version for building modules and running depmod from post_install/upgrade
mkdir -p "${pkgdir}/lib/modules/extramodules-${_basekernel}${_kernelname:--rt}"
echo "${_kernver}" > "${pkgdir}/lib/modules/extramodules-${_basekernel}${_kernelname:--rt}/version"
# Now we call depmod...
depmod -b "$pkgdir" -F System.map "$_kernver"
# move module tree /lib -> /usr/lib
mv "$pkgdir/lib" "$pkgdir/usr"
package_linux-rt-headers() {
pkgdesc="Header files and scripts for building modules for linux kernel (with realtime preemption)."
# provides=("kernel26${_kernelname}-headers=${pkgver}")
# conflicts=("kernel26${_kernelname}-headers")
# replaces=("kernel26${_kernelname}-headers")
install -dm755 "${pkgdir}/usr/lib/modules/${_kernver}"
cd "${pkgdir}/usr/lib/modules/${_kernver}"
ln -sf ../../../src/linux-${_kernver} build
cd "${srcdir}/linux-${_basekernel}"
install -D -m644 Makefile \
"${pkgdir}/usr/src/linux-${_kernver}/Makefile"
install -D -m644 kernel/Makefile \
"${pkgdir}/usr/src/linux-${_kernver}/kernel/Makefile"
install -D -m644 .config \
"${pkgdir}/usr/src/linux-${_kernver}/.config"
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/include"
for i in acpi asm-generic config crypto drm generated keys linux math-emu \
media net pcmcia scsi sound trace uapi video xen; do
cp -a include/${i} "${pkgdir}/usr/src/linux-${_kernver}/include/"
done
# copy arch includes for external modules
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/arch/x86"
cp -a arch/x86/include "${pkgdir}/usr/src/linux-${_kernver}/arch/x86/"
# copy files necessary for later builds, like nvidia and vmware
cp Module.symvers "${pkgdir}/usr/src/linux-${_kernver}"
cp -a scripts "${pkgdir}/usr/src/linux-${_kernver}"
# fix permissions on scripts dir
chmod og-w -R "${pkgdir}/usr/src/linux-${_kernver}/scripts"
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/.tmp_versions"
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/arch/${KARCH}/kernel"
cp arch/${KARCH}/Makefile "${pkgdir}/usr/src/linux-${_kernver}/arch/${KARCH}/"
if [ "${CARCH}" = "i686" ]; then
cp arch/${KARCH}/Makefile_32.cpu "${pkgdir}/usr/src/linux-${_kernver}/arch/${KARCH}/"
fi
cp arch/${KARCH}/kernel/asm-offsets.s "${pkgdir}/usr/src/linux-${_kernver}/arch/${KARCH}/kernel/"
# add docbook makefile
install -D -m644 Documentation/DocBook/Makefile \
"${pkgdir}/usr/src/linux-${_kernver}/Documentation/DocBook/Makefile"
# add dm headers
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/drivers/md"
cp drivers/md/*.h "${pkgdir}/usr/src/linux-${_kernver}/drivers/md"
# add inotify.h
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/include/linux"
cp include/linux/inotify.h "${pkgdir}/usr/src/linux-${_kernver}/include/linux/"
# add wireless headers
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/net/mac80211/"
cp net/mac80211/*.h "${pkgdir}/usr/src/linux-${_kernver}/net/mac80211/"
# add dvb headers for external modules
# in reference to:
# http://bugs.archlinux.org/task/9912
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb-core"
cp drivers/media/dvb-core/*.h "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb-core/"
# and...
# http://bugs.archlinux.org/task/11194
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/include/config/dvb/"
cp include/config/dvb/*.h "${pkgdir}/usr/src/linux-${_kernver}/include/config/dvb/"
# add dvb headers for http://mcentral.de/hg/~mrec/em28xx-new
# in reference to:
# http://bugs.archlinux.org/task/13146
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb-frontends/"
cp drivers/media/dvb-frontends/lgdt330x.h "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb-frontends/"
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/i2c/"
cp drivers/media/i2c/msp3400-driver.h "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/i2c/"
# add dvb headers
# in reference to:
# http://bugs.archlinux.org/task/20402
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/usb/dvb-usb"
cp drivers/media/usb/dvb-usb/*.h "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/usb/dvb-usb/"
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb-frontends"
cp drivers/media/dvb-frontends/*.h "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb-frontends/"
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/tuners"
cp drivers/media/tuners/*.h "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/tuners/"
# add xfs and shmem for aufs building
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/fs/xfs"
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/mm"
cp fs/xfs/xfs_sb.h "${pkgdir}/usr/src/linux-${_kernver}/fs/xfs/xfs_sb.h"
# copy in Kconfig files
for i in `find . -name "Kconfig*"`; do
mkdir -p "${pkgdir}"/usr/src/linux-${_kernver}/`echo ${i} | sed 's|/Kconfig.*||'`
cp ${i} "${pkgdir}/usr/src/linux-${_kernver}/${i}"
done
chown -R root.root "${pkgdir}/usr/src/linux-${_kernver}"
find "${pkgdir}/usr/src/linux-${_kernver}" -type d -exec chmod 755 {} \;
# strip scripts directory
find "${pkgdir}/usr/src/linux-${_kernver}/scripts" -type f -perm -u+w 2>/dev/null | while read binary ; do
case "$(file -bi "${binary}")" in
*application/x-sharedlib*) # Libraries (.so)
/usr/bin/strip ${STRIP_SHARED} "${binary}";;
*application/x-archive*) # Libraries (.a)
/usr/bin/strip ${STRIP_STATIC} "${binary}";;
*application/x-executable*) # Binaries
/usr/bin/strip ${STRIP_BINARIES} "${binary}";;
esac
done
# remove unneeded architectures
rm -rf "${pkgdir}"/usr/src/linux-${_kernver}/arch/{alpha,arc,arm,arm26,arm64,avr32,blackfin,c6x,cris,frv,h8300,hexagon,ia64,m32r,m68k,m68knommu,metag,mips,microblaze,mn10300,openrisc,parisc,powerpc,ppc,s390,score,sh,sh64,sparc,sparc64,tile,unicore32,um,v850,xtensa}
package_linux-rt-docs() {
pkgdesc="Kernel hackers manual - HTML documentation that comes with the Linux kernel (with realtime preemption)."
# provides=("kernel26${_kernelname}-docs=${pkgver}")
# conflicts=("kernel26${_kernelname}-docs")
# replaces=("kernel26${_kernelname}-docs")
cd "${srcdir}/linux-${_basekernel}"
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}"
cp -al Documentation "${pkgdir}/usr/src/linux-${_kernver}"
find "${pkgdir}" -type f -exec chmod 444 {} \;
find "${pkgdir}" -type d -exec chmod 755 {} \;
# remove a file already in linux package
rm -f "${pkgdir}/usr/src/linux-${_kernver}/Documentation/DocBook/Makefile"
# vim:set ts=8 sts=2 sw=2 et:
Then create the file '0007-asus-xonar-dgx.patch' with the following content:
--- a/sound/pci/oxygen/oxygen.c 2014-08-01 20:45:20.299191180 +0200
+++ b/sound/pci/oxygen/oxygen.c 2014-08-01 20:46:11.179947117 +0200
@@ -105,7 +105,7 @@
{ OXYGEN_PCI_SUBID(0x10b0, 0x0219), .driver_data = MODEL_CMEDIA_REF },
{ OXYGEN_PCI_SUBID(0x13f6, 0x0001), .driver_data = MODEL_CMEDIA_REF },
{ OXYGEN_PCI_SUBID(0x13f6, 0x0010), .driver_data = MODEL_CMEDIA_REF },
- { OXYGEN_PCI_SUBID(0x13f6, 0x8788), .driver_data = MODEL_CMEDIA_REF },
+ { OXYGEN_PCI_SUBID(0x13f6, 0x8788), .driver_data = MODEL_XONAR_DGX },
{ OXYGEN_PCI_SUBID(0x147a, 0xa017), .driver_data = MODEL_CMEDIA_REF },
{ OXYGEN_PCI_SUBID(0x1a58, 0x0910), .driver_data = MODEL_CMEDIA_REF },
/* Asus Xonar DG */
Finally run makepkg, should there be errors try removing the src dir first 'yes|rm -r src', then run makepkg again. Should there still be an error post here.
As for the patch, should there be no real difference there is also MODEL_XONAR_DG, might be worth trying out.
Last edited by emeres (2014-08-01 22:34:05)

LV8.0 Auto-print front panel doesn't work

On the front panel in VI Properties/Print Options the 'Automatically print front panel every time VI completes execution' is cleared when you exit the VI Properties dialog and return to it. Consequently, you can't get the front panel to print by checking this option.
Brent

Bshu,
You're absolutely right. That functionality is faulty. A work around may be to use the operate>>print at completion function. FYI: if you enable this property, the VI Properties/Print Options the 'Automatically print front panel every time VI completes execution' turns black. R&D is aware of both of these problems. Thank you for you're very valuable feedback and post to let us know if there's anything else we can help out with.
Best Regards,
Chris C
Applications Engineering
National Instruments
Chris Cilino
National Instruments
LabVIEW Product Marketing Manager
Certified LabVIEW Architect

"The VI's front panel may have been removed."

I was running my program in the development environment and had a sudden exit from labview (w/o a microsoft crash dialog).
So I start labview, file recovery comes up so I recover all and then save all (don't remember if it involved the file in question).
Now a subVI is throwing this error every time I try to open it:
Everything seems to be working and no broken run arrows, etc., but I can't get it open and I need to. Anyone know how to recover from this?
-B
bah! I meant to post this in LabVIEW. Can someone move it?
Message Edited by blawson on 10-22-2009 01:00 PM
-Barrett
CLD

Cross-posting a similar problem: Unable to display the Front Panel of a VI
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

How can I save front panel images each time a loop iterates

So I've been working on some optical codes in LabVIEW for a while, I've read a lot of these similar questions but I can't seem to apply them directly to my situation in all cases.
I essentially have a code that shows an intensity graph that is continually modified in a for loop, I want to save a picture of that intensity graph each loop without having to manually label them. Is there something similar to the get image node that can do this. I've looked through the image acquisition in the vision VIs but only see references to hardware like cameras.
Attached is a simplified version of a changing intensity graph. With the get image I have to establish the names of 10 images and the path there before it will run and save like I want it to.
A million thanks to anyone who can help
Solved!
Go to Solution.
Attachments:
Sample image save.vi ‏19 KB

That worked wonderfully and is exactly what I need for the phase diagrams Im working with. I have a new and similar issue, I do have a camera showing us our laser source in a CCD image within my code. I was hoping to get a picture of that each iteration and hoped the solution you provided would work for both but the CCD jpgs are just black. I'm assuming I may have to use a different acquiring technique with that but dont know the best way to go.
Any help there? I cant really post a VI since the camera stuff wouldnt work but heres a screen shot of the front panel and the CCD image that id like to capture.
Attachments:
2.JPG ‏400 KB

Can't find the pin to connect the front panel of IPMMB-FM motherboard

Hi,
So i have a HPE h8-1240t. My motherboard is:
Manufacturer: IPMMB-FM
HP: Formosa
Here is the picture of my motherboard:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c03132942&cc=us&dlc=en&lc=en
I just bought a new case (Thermaltake Commander MS-I Black). I was trying to swap the system from the old case to the new case. Also, this is my first time doing this. I just keep everything except the case. No luck, i could not connect the front panel such as power switch button, reset button, HDD LED...etc which came with the new case. Any idea how to connect those buttons? THanks very much.
This question was solved.
View Solution.

Yes. The leads in the picture I took from the case manual go on the appropriate pins on the F_Panel block in the lower right near the SATA ports. The pinout should be marked next to the jack in terms very similar to the wire designations.
{---------- Please click the "Thumbs Up" to say thanks for helping.
Please click "Accept As Solution" if my help has solved your problem. ----------}
This is a user supported forum. I am a volunteer and I do not work for HP.

Black strip in front panel

Similar Messages

Maybe you are looking for