Pfi armv7

Hi.
Is there any way I can make pfi compile code optimized for armv7 instead ov armv6?
Thanks

In LabVIEW 7.0, the DAQmx Connect Terminals.vi is here: All Functions>>NI Measurements>>DAQmx - Data Acquisition>>DAQmx Advanced>>DAQmx Signal Routing palette. If you don't have it there, you probably don't have a recent enough version of NI-DAQmx, which you can download here.
-Alan A.

Similar Messages

New ADT vs PFI

Hi,
I just recompiled my swf with the new air 2.6 adt, and I am very surprised.
First of all, all buttons now take about 5 seconds to respond, vs almost immediate in the pfi.
Next, all the bitmaps i cached are screwed up, virtually nothing is showing. And the rendering speed of these bitmaps is also at least 10x slower than before.
My project is coded in Flash CS5, stage size is set to iphone (480*320) and I have been testing on an Ipad (i used to set the publish setting to iphone and ipad). I'm pretty sure I'm doing something wrong since the new packager is suppose to be faster.
I found this line in its list of improvements:
Improved hardware acceleration on iOS. Hardware acceleration on iOS now works like it does on Android, and generally provides much better performance than with PFI. And speaking of PFI…
Does this mean that I should avoid using cacheAsBitmapMatrix? Even if that's the case, why are my buttons slower? I never cached them.
Also, some vectors render incorrectly (sometimes not showing alpha). I have never seen this problem in the old PFI, the app always looked the same whether it's on the ipad or computer.
Can someone please explain to me what's going on?
PS. Are game center/iAd supported in this version?

hey there guys, there is a good discussion over at the Mobile AIR forum that shares some discoveries about performance with 2.6. i struggled for days then realized any caching (cacheAsBitmap and cacheAsBitmapMatrix) will seriously hinder performance, at least in my app it did. i set my app screen quality to low (i'm using PNGs for a majority of the app anyway) unless i need high quality vector rendering. i am getting 60FPS and am continuing to tune things.
http://forums.adobe.com/community/air/development/android
hope this helps

How do I set a PFI to High on a 6602 Board with DAQ Traditional

Dear All,
I am using LabVIEW 8.5 on 32-bit Windows XP with an NI 6602 DAQ board. In the past I've used DAQmx but for compatability with older software I need to do a few simple things using Traditional DAQ, which I have never used. Specifically I would like to make a simple VI that sets PFI 5 to high when the user presses a button and then low when they press the button a second time. How do I set PFI 5 for output and then write true to it?
Thanks,
Ed
Solved!
Go to Solution.

Dear All,
Apparently its as simple as using the Write to Digital Line VI. However, the non obvious thing is the port width of the 6602 board is 32 not the default 8. Buried in the LabVIEW help files is a list of physical port widths that one must stumble upon. Like the bat cave. In the attached image of the super simple VI I've made the 16 refers to PFI 16. Good to know.
Best,
Ed
Attachments:
write_low.JPG ‏5 KB

How Do I Configure the PFI Lines as input in PXI 6713 module

Hi,
I have PXI 6713 module in my PXI 1044 chassis. I have configured PXI 6713 module to geneate certain analogue signals to my board.
Board inturn process this analogue signal and responds back the status signals through a status register on the board. In my application,the status bits in status register of the board are mapped to the PFI 0:3 bits on PXI 6713 module ( pins 11,10 , 42 and 43).
My query is how do i configue the PFI lines as input in PXI 6713 module to read these status bits ??
May be below explanation could give you little bit more information w.r.to my query.
When i use NI USB - 6008 module to read the same bits , since this device has 12 digital I/O lines, i could able to read the status bits in to the last 4 digital lines by configuring the those digital lines as input.
In PXI 6713 module i have only 8 digital lines. These 8 digital lines i have used to send the digital signals to the board. I am left with no digital I/O lines. Hence i couldn't use these digital lines. I am left with only one option to use. Theya re PFI lines. Moreover the status bits in the pin out of board are mapped such that the bits can be read through the PFI lines.
I am wondering do we have any example code to use inorder to read these status bits on the board using the PFI lines.
Please let me know if you need additional information to help me out.
Thanks.
Solved!
Go to Solution.

Hello There,
When using the PFI pin as an input, you can individually configure each PFI for edge or level detection and for polarity selection. This PFI information can be referenced in the DAQ Analog Output Series Manual on page 6-1 (http://www.ni.com/pdf/manuals/370735e.pdf). Unfortunately, the PXI-6713 PFI lines are only capable of timing input and output signal for AI, AO, or counter/timer functions. The option of creating static DI from the PFI lines is not available for the PXI-6713. However, some cards have this capability. Newer National Instruments products with PFI lines have the option of setting PFI lines as:
Static Digital Input
Static Digital Output
Timing Input Signal for AI, AO, DI, DO, or counter/timer functions
Timing Output Signal from AI, AO, DI, DO, or counter/timer functions
(http://digital.ni.com/public.nsf/allkb/14F20D79C649F8CD86256FBE005C2BC4)
When set as static DIO, the PFI lines are assigned to a different port (eg. PFI0-7 is Port1). More details about this can be referenced at:
http://digital.ni.com/public.nsf/allkb/DA2D3CD0B8E8EE2A8625752F007596E1
http://digital.ni.com/public.nsf/allkb/862567530005F09E8625677800577C27
Regards,
Roman Sandoval | National Instruments | RF Systems Engineer

Can you do Digital In or Out on the same port (byte) as PFI timing?

I'm using an M series board with three digital ports. Port 0 is only for DIO, ports 1 and 2 can be used for DIO or PFI (e.g. clocking, triggering). My question is: can I do both DIO and PFI functions on any one port. For example, on Port 1, I would like to use bits 0 to 6 as Digital Inputs and have an external clock signal go into bit 7 as a clock for Analog Out. Can the port be mixed like this?
Thanks,
Dave
David Thomson Original Code Consulting
www.originalcode.com
National Instruments Alliance Program Member
Certified LabVIEW Architect
There are 10 kinds of people: those who understand binary, and those who don't.

Dave,
The DIO lines on any DAQ device that uses the DAQ-STC ASIC can be configured on a per line basis, so using PFI and DIO lines on the same port will work just fine.
You can run a quick test on this using the "Gen Dig Pulse.vi" example (found in the NI Example Finder under Browse -> Hardware Input and Output -> DAQmx -> Generate Digital Pulses). You should be able to generate a pulse on one of the PFI lines on the board, then read that pulse back in on one of the DIO lines of that port using an external connection.
-Justin

How do I install Adobe Flash Player on Ubuntu 32bit ARMv7 Little Endian machine?

How do I install Adobe Flash Player on Ubuntu (12.04) 32bit ARMv7 Little Endian machine? The .tar.gz and .deb files contains shared libraries for i386 target.

Hello,
There is a procedure of Manual Installation of Adobe Flash Player on Ubuntu, follow these steps :
Open http://get.adobe.com/flashplayer/otherversions/
Choose Linux 32-bit on Step 1
Choose Flash Player 11.2 (tar.gz) on Step 2, download the file
Once download is complete, right click on the flie (tar.gz) and click on "Extract here"
Launch Terminal (Keyboard Shortcut : Ctrl+Alt+T)
Go to that location where you extracted the file
Run this command : sudo mv libflashplayer.so \/usr/lib/firefox-addons/plugins
Launch Mozilla Firefox and check do you have Adobe Flash Player
Thanks,
Vikram

How can I modify this makefile to create proper ARMV7 dylibs?

I need to modify this makefile in order to create proper dylibs for inclusion in my IOS projects. If I just using the dylibs generated without changing this file, I get this error trying to use the dylibs:
ld: warning: ld: warning: ignoring file Undefined symbols for architecture armv7s:
"_mongo_connect", referenced from:
      -[ViewController viewDidLoad] in ViewController.o
libbson.dylib, file was built for unsupported file format
( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (armv7s):
Undefined symbols for architecture armv7s:
"_mongo_connect", referenced from:
      -[ViewController viewDidLoad] in ViewController.o
libbson.dylibignoring file
Undefined symbols for architecture armv7s:
"_mongo_connect", referenced from:
      -[ViewController viewDidLoad] in ViewController.o
libmongoc.dylib, file was built for unsupported file format
( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (armv7s):
Undefined symbols for architecture armv7s:
"_mongo_connect", referenced from:
      -[ViewController viewDidLoad] in ViewController.o
libmongoc.dylib
Undefined symbols for architecture armv7s:
"_mongo_connect", referenced from:
      -[ViewController viewDidLoad] in ViewController.o
The makefile:
# MongoDB C Driver Makefile
# Copyright 2009, 2010 10gen Inc.
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
# http://www.apache.org/licenses/LICENSE-2.0
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# Version
MONGO_MAJOR=0
MONGO_MINOR=6
MONGO_PATCH=0
BSON_MAJOR=$(MONGO_MAJOR)
BSON_MINOR=$(MONGO_MINOR)
BSON_PATCH=$(MONGO_PATCH)
# Library names
MONGO_LIBNAME=libmongoc
BSON_LIBNAME=libbson
# Standard or posix env.
ENV?=posix
# TODO: add replica set test, cpp test, platform tests, json_test
TESTS=test_auth test_bcon test_bson test_bson_subobject test_count_delete \
test_cursors test_endian_swap test_errors test_examples \
test_functions test_gridfs test_helpers \
test_oid test_resize test_simple test_sizes test_update \
test_validate test_write_concern test_commands
MONGO_OBJECTS=src/bcon.o src/bson.o src/encoding.o src/gridfs.o src/md5.o src/mongo.o \
src/numbers.o
BSON_OBJECTS=src/bcon.o src/bson.o src/numbers.o src/encoding.o
ifeq ($(ENV),posix)
    TESTS+=test_env_posix test_unix_socket
    MONGO_OBJECTS+=src/env_posix.o
else
    MONGO_OBJECTS+=src/env_standard.o
endif
DYN_MONGO_OBJECTS=$(foreach i,$(MONGO_OBJECTS),$(patsubst %.o,%.os,$(i)))
DYN_BSON_OBJECTS=$(foreach i,$(BSON_OBJECTS),$(patsubst %.o,%.os,$(i)))
# Compile flags
ALL_DEFINES=$(DEFINES)
ALL_DEFINES+=-D_POSIX_SOURCE
CC:=$(shell sh -c 'type $(CC) >/dev/null 2>/dev/null && echo $(CC) || echo gcc')
DYN_FLAGS:=-fPIC -DMONGO_DLL_BUILD
# Endianness check
endian := $(shell sh -c 'echo "ab" | od -x | grep "6261" >/dev/null && echo little || echo big')
ifeq ($(endian),big)
    ALL_DEFINES+=-DMONGO_BIG_ENDIAN
endif
# Int64 type check
int64:=$(shell ./check_int64.sh $(CC) stdint.h && echo stdint)
ifeq ($(int64),stdint)
    ALL_DEFINES+=-DMONGO_HAVE_STDINT
else
    int64:=$(shell ./check_int64.sh $(CC) unistd.h && echo unistd)
    ifeq ($(int64),unistd)
        ALL_DEFINES+=-DMONGO_HAVE_UNISTD
    endif
endif
$(shell rm header_check.tmp tmp.c)
TEST_DEFINES=$(ALL_DEFINES)
TEST_DEFINES+=-DTEST_SERVER="\"127.0.0.1\""
OPTIMIZATION?=-O3
WARNINGS?=-Wall
DEBUG?=-ggdb
STD?=c99
PEDANTIC?=-pedantic
ALL_CFLAGS=-std=$(STD) $(PEDANTIC) $(CFLAGS) $(OPTIMIZATION) $(WARNINGS) $(DEBUG) $(ALL_DEFINES)
ALL_LDFLAGS=$(LDFLAGS)
# Shared libraries
DYLIBSUFFIX=so
STLIBSUFFIX=a
MONGO_DYLIBNAME=$(MONGO_LIBNAME).$(DYLIBSUFFIX)
MONGO_DYLIB_MAJOR_NAME=$(MONGO_DYLIBNAME).$(MONGO_MAJOR)
MONGO_DYLIB_MINOR_NAME=$(MONGO_DYLIB_MAJOR_NAME).$(MONGO_MINOR)
MONGO_DYLIB_PATCH_NAME=$(MONGO_DYLIB_MINOR_NAME).$(MONGO_PATCH)
MONGO_DYLIB_MAKE_CMD=$(CC) -shared -Wl,-soname,$(MONGO_DYLIB_MINOR_NAME) -o $(MONGO_DYLIBNAME) $(ALL_LDFLAGS) $(DYN_MONGO_OBJECTS)
BSON_DYLIBNAME=$(BSON_LIBNAME).$(DYLIBSUFFIX)
BSON_DYLIB_MAJOR_NAME=$(BSON_DYLIBNAME).$(BSON_MAJOR)
BSON_DYLIB_MINOR_NAME=$(BSON_DYLIB_MAJOR_NAME).$(BSON_MINOR)
BSON_DYLIB_PATCH_NAME=$(BSON_DYLIB_MINOR_NAME).$(BSON_PATCH)
BSON_DYLIB_MAKE_CMD=$(CC) -shared -Wl,-soname,$(BSON_DYLIB_MINOR_NAME) -o $(BSON_DYLIBNAME) $(ALL_LDFLAGS) $(DYN_BSON_OBJECTS)
# Static libraries
MONGO_STLIBNAME=$(MONGO_LIBNAME).$(STLIBSUFFIX)
BSON_STLIBNAME=$(BSON_LIBNAME).$(STLIBSUFFIX)
# Overrides
kernel_name := $(shell sh -c 'uname -s 2>/dev/null || echo not')
ifeq ($(kernel_name),SunOS)
    ALL_LDFLAGS+=-ldl -lnsl -lsocket
    INSTALL_CMD=cp -r
    MONGO_DYLIB_MAKE_CMD=$(CC) -G -o $(MONGO_DYLIBNAME) -h $(MONGO_DYLIB_MINOR_NAME) $(ALL_LDFLAGS)
    BSON_DYLIB_MAKE_CMD=$(CC) -G -o $(BSON_DYLIBNAME) -h $(BSON_DYLIB_MINOR_NAME) $(ALL_LDFLAGS)
endif
ifeq ($(kernel_name),Darwin)
    ALL_CFLAGS+=-std=$(STD) $(CFLAGS) $(OPTIMIZATION) $(WARNINGS) $(DEBUG) $(ALL_DEFINES)
    DYLIBSUFFIX=dylib
    MONGO_DYLIB_MINOR_NAME=$(MONGO_LIBNAME).$(DYLIBSUFFIX).$(MONGO_MAJOR).$(MONGO_M INOR)
    MONGO_DYLIB_MAJOR_NAME=$(MONGO_LIBNAME).$(DYLIBSUFFIX).$(MONGO_MAJOR)
    MONGO_DYLIB_MAKE_CMD=$(CC) -shared -Wl,-install_name,$(MONGO_DYLIB_MINOR_NAME) -o $(MONGO_DYLIBNAME) $(ALL_LDFLAGS) $(DYN_MONGO_OBJECTS)
    BSON_DYLIB_MINOR_NAME=$(BSON_LIBNAME).$(DYLIBSUFFIX).$(BSON_MAJOR).$(BSON_MINOR )
    BSON_DYLIB_MAJOR_NAME=$(BSON_LIBNAME).$(DYLIBSUFFIX).$(BSON_MAJOR)
    BSON_DYLIB_MAKE_CMD=$(CC) -shared -Wl,-install_name,$(BSON_DYLIB_MINOR_NAME) -o $(BSON_DYLIBNAME) $(ALL_LDFLAGS) $(DYN_BSON_OBJECTS)
endif
# Installation
ifeq ($(kernel_name),SunOS)
    INSTALL?=cp -r
endif
INSTALL?= cp -a
INSTALL_INCLUDE_PATH?=/usr/local/include
INSTALL_LIBRARY_PATH?=/usr/local/lib
# TARGETS
all: $(MONGO_DYLIBNAME) $(BSON_DYLIBNAME) $(MONGO_STLIBNAME) $(BSON_STLIBNAME)
# Dependency targets. Run 'make deps' to generate these.
bcon.o: src/bcon.c src/bcon.h src/bson.h
bson.o: src/bson.c src/bson.h src/encoding.h
encoding.o: src/encoding.c src/bson.h src/encoding.h
env_standard.o: src/env_standard.c src/env.h src/mongo.h src/bson.h
env_posix.o: src/env_posix.c src/env.h src/mongo.h src/bson.h
gridfs.o: src/gridfs.c src/gridfs.h src/mongo.h src/bson.h
md5.o: src/md5.c src/md5.h
mongo.o: src/mongo.c src/mongo.h src/bson.h src/md5.h src/env.h
numbers.o: src/numbers.c
$(MONGO_DYLIBNAME): $(DYN_MONGO_OBJECTS)
    $(MONGO_DYLIB_MAKE_CMD)
$(MONGO_STLIBNAME): $(MONGO_OBJECTS)
    $(AR) -rs $@ $(MONGO_OBJECTS)
$(BSON_DYLIBNAME): $(DYN_BSON_OBJECTS)
    $(BSON_DYLIB_MAKE_CMD)
$(BSON_STLIBNAME): $(BSON_OBJECTS)
    $(AR) -rs $@ $(BSON_OBJECTS)
install:
    mkdir -p $(INSTALL_INCLUDE_PATH) $(INSTALL_LIBRARY_PATH)
    $(INSTALL) src/mongo.h src/bson.h $(INSTALL_INCLUDE_PATH)
    $(INSTALL) $(MONGO_DYLIBNAME) $(INSTALL_LIBRARY_PATH)/$(MONGO_DYLIB_PATCH_NAME)
    $(INSTALL) $(BSON_DYLIBNAME) $(INSTALL_LIBRARY_PATH)/$(BSON_DYLIB_PATCH_NAME)
    cd $(INSTALL_LIBRARY_PATH) && ln -sf $(MONGO_DYLIB_PATCH_NAME) $(MONGO_DYLIB_MINOR_NAME)
    cd $(INSTALL_LIBRARY_PATH) && ln -sf $(BSON_DYLIB_PATCH_NAME) $(BSON_DYLIB_MINOR_NAME)
    cd $(INSTALL_LIBRARY_PATH) && ln -sf $(MONGO_DYLIB_MINOR_NAME) $(MONGO_DYLIBNAME)
    cd $(INSTALL_LIBRARY_PATH) && ln -sf $(BSON_DYLIB_MINOR_NAME) $(BSON_DYLIBNAME)
    $(INSTALL) $(MONGO_STLIBNAME) $(INSTALL_LIBRARY_PATH)
    $(INSTALL) $(BSON_STLIBNAME) $(INSTALL_LIBRARY_PATH)
scan-build: clean
    scan-build -V -v make
test: $(TESTS)
    sh runtests.sh
valgrind: $(TESTS)
    sh runtests.sh -v
docs:
    python docs/buildscripts/docs.py
clean:
    rm -rf src/*.o src/*.os test/*.o test/*.os test_* .scon* config.log
clobber: clean
    rm -rf $(MONGO_DYLIBNAME) $(MONGO_STLIBNAME) $(BSON_DYLIBNAME) $(BSON_STLIBNAME) docs/html docs/source/doxygen
deps:
    $(CC) -MM -DMONGO_HAVE_STDINT src/*.c
32bit:
    $(MAKE) CFLAGS="-m32" LDFLAGS="-pg"
test_%: test/%_test.c test/test.h $(MONGO_STLIBNAME)
    $(CC) -o $@ -L. -Isrc $(TEST_DEFINES) $(ALL_LDFLAGS) $< $(MONGO_STLIBNAME)
%.o: %.c
    $(CC) -o $@ -c $(ALL_CFLAGS) $<
%.os: %.c
    $(CC) -o $@ -c $(ALL_CFLAGS) $(DYN_FLAGS) $<
.PHONY: 32bit all clean clobber deps docs install test valgrind

Hi Petar,
Thanks for your answer. No doubt that we could solve the issue using on of the way you suggested.
However, even though I had the evdre issue right after applying time dimension modifications, it occurs that the evdre issue was not due to time dimension modifications. I tested it better and I can tell that using "total" as a level works.
Best regards,
Ludovic

How to output sample and convert clocks to PFI lines of E-Series DAQ (DAQPad-6015)

Hi,
Can someone tell me how to output sample and convert clocks to PFI lines of E-Series DAQ (DAQPad-6015)?
Thank you very much.
Jack

John --
Windows is not an option for me. I like your idea of using a counter output -- it may be helpful as I am getting ramped up, but my application will eventually require both timer outputs.
I have a legacy C application written for Macintosh, and I am in the process of moving it onto OS X. So my options are to use DAQmx Base, or write an in-kernel driver. I actually have already done the latter for 6024/6025 E-series boards (for another company); for this client I was hoping to use the DAQmx Base to allow an easy transition to M-series boards, without the cost of writing and supporting a low-level driver.
The specific task I am doing is relatively straightforward. I record 2 channels of AI for a short period (usually about 250 ms.) and during this time I drive 2 external digital signals. Right now, I use the 2 timer outputs, which allows precise synchronization with the output and AI sampling.
I appreciate your comments, and thanks in advance for any additional suggestions you can lob my way.
--spg
Scott Gillespie
Applied Brain, Inc.
scott gillespie
applied brain, inc.

I need to measure the frequency of a signal on Pin 39 (PFI 15) of a PXIe-6361 module.

I need to measure the frequency of a signal on pin 39 (PFI 15) of a PXIe-6361 module. All of the digital I/O pins are already assigned and in use. The signal frequency range is 50KHz to 500KHz. I have tried all of the sample programs for DAQmx Counter/Timer frequency measurement. If I modify them to use my hardware, I get run-time errors with conflicts with resources already assigned.

Hi Julia,
Thanks for the response. As I stated before, I have tried all of the examples available that apply. There are only three and one of those uses two counters. The two I have tried are:
Examples/Hardware Input and Output/Counter Measurements/Digital Frequency/
DigFreq-Buff-Cont-ExtClk-ArmStart.prj and
DigFreq-LowFreq1Ctr.prj
These examples default to using what appears to be traditional DAQ hardware (Dev1/ctr0 and /Dev1/PFI0). I changed the counter to mine (/PXI1Slot3/ctr3) and directed my signal source (PFI15 on pin 39) to the counter. No matter what I tried would not run. They would always compile but gave run-time errors ranging from resources already in use to “external trigger required”. I have no external trigger source and, if I did, there is no indication of how to assign it to the counter. NI has a very good X Series Users Manual that tells all of the great things you can do with the hardware, but there is NO CLUE how to do any of those things!!!! I know that some NI DAQmx functions use hardware resources that they never tell you about. I discovered that when trying to produce a single output pulse from a timer using counter #0. (Which, by the way, no one at NI could tell me how to do it.)
Measuring frequency should be very simple. The unknown signal is routed through a precise gate to a counter, and then the counter is read. NI DAQmx uses the opposite approach of using my signal as the gate and counting their internal source. However, the examples would not let me use the internal reference sources.
To answer your other questions, I am not performing any other measurements at the same time and the counter is not being used for anything else, period.
Any help would be greatly appreciated. Thanks again.
Wayne K.

How do you map a PFI to a clock to measure frequency?

I am running LabVIEW 8.2 and I am trying to measure the frequency of a voltage on a PFI pin. I have heard that I can map that pin to a counter input to measure the voltage but i cannot figure out how to do it. Are there any VI's already set up to do this? How can I map the PFI to a counter?

Hi Flowserve1,
What hardware are you using to make your measurement? What driver are you working with? You will be able to make measurements with your counter on a digital signal. If you look at the device pinouts for your device in Measurement and Automation Explorer you will see the counter terminals.
Steve B

Instant Client for ARMv7 and ARMv8?

I don't see Instant Client binaries being available for any of ARM architectures (arm-linux). Considering that ARMv7 is already available on server market and ARMv8 is coming soon enough, will there be any binaries compiled for such architectures (soft and hard fp versions)?
I would prefer not to use any kind of gateway (x64-84 machine) to access the database.

I noticed your reply to this topic and I am
having the same problem with OLE DB or ODBC.
I posted the following on another message and
nobody has answered. There are also no examples
in the Oracle web site on how to connect to a
remote client using ADO. Any help will be
appreciated, Tony.
I am trying to create an installation package
from Visual Basic (version 6.0) that will let
me connect to a remote Oracle database. Does
anyone know what needs to be installed on the
client machine? I created a standard package
and it does not work on the client.
My connection string is as follows:
Dim adoCn As New ADODB.Connection
adoCn.Provider = "OraOLEDB.Oracle"
adoCn.ConnectionString = "Data Source=PSYTEST" _
& ";User ID=SYSTEM" _
& ";Password=Ciao" _
& ";PLSQLRSet=1;" _
& ";Remote Server=xxx.xxx.xxx.xxx"
adoCn.Open
The xxx.xxx.xxx.xxx is the IP address of the
server. The program works when I use it on
the local machine, but it does not work when
I create an installation package and I install
it on a remote client machine.

Ld: file was built for unsupported file format...for architecture armv7

hi:
I recently developed a project with custom ANE and I get this error msg when compile ipa since I upgraded the sdk from 3.5 to 3.8.
ANE compile CMD:
adt -package -storetype pkcs12 -keystore ane.p12 -storepass 1234 -target ane yund.ane extension.xml -swc yunding.swc -platform iPhone-ARM -platformoptions platform.xml IDS.framework library.swf libIslandIDSANE.a
platform.xml:
<platform xmlns="http://ns.adobe.com/air/extension/3.5">
     <sdkVersion>6.1</sdkVersion>
     <linkerOptions>
                    <option>-w</option>
        <option>-ios_version_min 4.2</option>
                    <option>-framework Foundation</option>
                    <option>-framework StoreKit</option>
                    <option>-framework AdSupport</option>
                    <option>-framework QuartzCore</option>
                    <option>-framework UIKit</option>
                    <option>-framework CoreGraphics</option>
                    <option>-framework SystemConfiguration</option>
                    <option>-framework Foundation</option>
                    <option>-lz</option>
     </linkerOptions>
             <packagedDependencies>
                    <packagedDependency>IDS.framework</packagedDependency>
          </packagedDependencies>
</platform>
msg:
ld: file was built for unsupported file format ( 0x56 0x65 0x72 0x73 0x69 0x6f 0x6e 0x73 0x2f 0x43 0x75 0x72 0x72 0x65 0x6e 0x74 ) which is not the architecture being linked (armv7): C:\Users\timoo\AppData\Local\Temp\139d9782-79fd-422a-8c15-da1da2da8c53/IDS.framework/IDS for architecture armv7
Compilation failed while executing : ld64
help me
thx

Have you Found the way to solve this problem yet?
I have got the same problem. Here is the error log when building the IPA:
ld: warning: ignoring file /var/folders/c0/m8m1_z5915qblkj9d_7jhmcw0000gn/T/3cb383e9-0092-4b1c-909f-5c219b2fbcd4/Par tytrack.framework/Partytrack, file was built for unsupported file format ( 0x56 0x65 0x72 0x73 0x69 0x6f 0x6e 0x73 0x2f 0x43 0x75 0x72 0x72 0x65 0x6e 0x74 ) which is not the architecture being linked (armv7): /var/folders/c0/m8m1_z5915qblkj9d_7jhmcw0000gn/T/3cb383e9-0092-4b1c-909f-5c219b2fbcd4/Par tytrack.framework/Partytrack
ld: warning: CPU_SUBTYPE_ARM_ALL subtype is deprecated: /Users/apple/Documents/flexsdk/flex3.9/lib/aot/lib/libDebugger1.arm-air.a(avmplusDebugger .cpp.o)
Undefined symbols for architecture armv7:
"_OBJC_CLASS_$_Partytrack", referenced from:
      objc-class-ref in libcom.haibin.extension.PromotionAPI.a(partyTrackAPI.o)
ld: symbol(s) not found for architecture armv7
Compilation failed while executing : ld64
My platformoption.xml content is：
<platform xmlns="http://ns.adobe.com/air/extension/3.8">
    <sdkVersion>7.0</sdkVersion>
    <linkerOptions>
        <option>-ios_version_min 4.3</option>
        <option>-framework CoreData</option>
        <option>-framework UIKit</option>
        <option>-framework Foundation</option>
        <option>-framework Security</option>
        <option>-weak_framework AdSupport</option>
    </linkerOptions>
    <packagedDependencies>
        <packagedDependency>Partytrack.framework</packagedDependency>
    </packagedDependencies>
</platform>
And my build command are:
<target name="package" description="Create the extension package">
<exec executable="${FLEX_HOME}/bin/adt" failonerror="true" dir="${basedir}">
<env key="AIR_SDK_HOME" value="${FLEX_HOME}"/>
<arg value="-package"/>
<arg line="-storetype pkcs12"/>
<arg line="-keystore testkey.p12"/>
<arg line="-storepass 123456"/>
<arg line="-target ane"/>
<arg value="../${ANE_NAME}.ane"/>
<arg value="extension.xml"/>
<arg line="-swc ../swc/${ANE_NAME}.swc"/>
<arg line="-platform iPhone-ARM -platformoptions platform.xml -C ../iPhone-ARM/ . "/>
<arg line="-platform Android-ARM -C ../Android-ARM/ ."/>
<arg line="-platform default -C ../default/ ."/>
</exec>
</target>
File "Partytrack.framework " is in the directory "iPhone-ARM"

PFI for AIR 2.5

Any idea when a new Packager For iPhone will be available that supports AIR 2.5.1 rather than 2.0.1?
StudioCloud (http://studiocloud.com) just released an Android app (http://blog.studiocloud.com/2010/11/new-android-app.html) that works with their existing AIR and Flex applications and we are really excited to have an iPhone app. However, the current PFI does not work with 2.5.1 that I am aware of.
Any news on this or even a prerelease for the new PFI would be great.

I'd like fast app testing, like is in GameSalad, but in the meantime I work with Flash in a way that's reasonably quick, at least if you're a Mac user:
1. I publish the ipa file, and I have ipa set to open in StuffitExpander.
2. Double click on the ipa, and you get a Payload folder with the app inside.
3. Drag the app straight to any of your connected devices in the Organizer window of Xcode. No need to even delete the previous build.
Between Test Movie and the ability to quickly get things onto the devices, without the documented iTunes sync approach, I often go through dozens of test builds a day.

Driving DO lines with external clock wired to PFI lines

Hi all,
I have few issues understanding how to use hardware timing resources in M series USB6229, with particular focus on DO. I have read last couple of day all google offered on the subject but I am still straggling with some basic tasks. To cut the story short, the 1e6 dollar question: can I set up 7 independent DO lines where (different tasks or virtual channels) where lines use same hardware timing source (eg, freqout or CO0 set to ~10kHz sampling time routed to PFI0).
Note: the reason I need 7 independent lines and not a port output (which would be obvious solution) is because I need to have (vastly) different number of samples and for each line.
Follow up question regarding timing: As I understood, any of PFI ports could be used and a input to the external clock which could be used to drive DO line(s) samples. I have tried to generate one DO, eg. P0\line4 by using CO0 to generate 10kHz sample rate. The signal on the line4 is pulse with frequency of few Hz which I routed to PF6 (with actual wire) in hope to use this signal as a clock for line5. I tried this but I am receiving errors about "resources in use"
Possible reason(s):
Specified route cannot be satisfied, because it requires resources that are currently in use by another route.
Property: SampClk.Src
Property: SampClk.ActiveEdge
Source Device: USB-6229
Source Terminal: PFI6
Required Resources in Use by
Task Name: _unnamedTask<7B>
Source Device: USB-6229
Source Terminal: PFI4
Destination Device: USB-6229
Destination Terminal: do/SampleClock
Task Name: _unnamedTask<79>
Apparently, many of internal clocks are routed internally to different PFI lines which mean the lines are occupied resource, and I do not know how to solve this.
I wanted to ask you does this principle sound as something that should work and if you know about some examples that would be excellent.
Any help would be greatly appreciated.
Cheers, Nenad

> To cut the story short, the 1e6 dollar question: can I set up 7 independent DO lines where (different tasks or virtual channels) where lines use same hardware timing source (eg, freqout or CO0 set to ~10kHz sampling time routed to PFI0).
No, you can't. The USB-6229 has a single digital output FIFO which can only be used by one task at a time.
> Note: the reason I need 7 independent lines and not a port output (which would be obvious solution) is because I need to have (vastly) different number of samples and for each line.
It should be possible to generate all seven signals with a single task by generating a waveform that includes all seven signals. If the signals repeat at different rates or you need to start/stop them independently, you will have to disable regeneration and continuously generate new waveform segments on the fly. Continuous Write Digital Port - External Clock - Non Regeneration should be a good starting point for the DAQmx programming, but actually generating the data is likely to be the challenging part.
Brad
Brad Keryan
NI R&D

Digital inputs. PFI trigger inpurs

Hi,
I want to be able to to start the data acquistion by the use of digital tigger, say on the rising edge. Do i use the PFI inputs and if so how. Or can use one of the digital input channels. Any help would be grateful. Note that I am using NI PCI 6259 and labview 7.
Regards,
Tadhg

Using one of the PFI lines is actually a great idea.
For analog input, you could try the LabVIEW example VI, "Acq&Graph Voltage-Int Clk-Dig Start" you'll be able to get up and running quickly. You may select which line to trigger from using the controls under "Trigger Parameters".
If you are performing analog output, the "Gen Mult Updates-Int Clk-Dig Start" works in a similar way.

Pfi armv7

Similar Messages

Maybe you are looking for