Output pulse every n units for x4 encoder

I found this on the National Instruments website showing how to ouptu a pulse every N input pulses, the issue is that I'm trying to do this on X4 decoding. I have a NI9178, NI9401 and a NI9201, I'm trying to input an X4 encoder to my counter and subsequently output a pulse every N steps on a seperate line to trigger an external piece of hardware. My encoder has 200PPR and runs at about 2000RPM.
Here's the link to the file: http://zone.ni.com/devzone/cda/epd/p/id/3288
Thanks for any assistance you can provide,
Nick

So I have been trying to figure this issue out by using the forums and all I've managed to do is confuse myself.
I'm "simply" trying to output a series of pulses after counting N number of input pulses. Here is the VI I'm working on (adapted from a previous forum post - Encoder VI for NI.vi is the main program). There is one counter input and one counter output, along with some analog inputs (which for now can simply be ignored). I'm trying to count the ticks off of Phase A from the input encoder and subsequently output a pulse every 100 ticks on the output counter task.
Please if anyone has any suggestions I am very open to them.
Nick
Attachments:
Encoder VI For NI.vi ‏54 KB
Analog Graph2.vi ‏21 KB
Get Terminal Name with Device Prefix.vi ‏50 KB

Similar Messages

Need to use quadrature encoder to trigger (RTSI) single point DAQ on 2 channels of E-Series DAQ, using 6602 NI-TIO for counting encoder pulses.

This is for LV6i, W2000, all PCI equipment.
Using a quadrature-measure position-VI, I get 7200 edges/rev from the encoder of my physical system. This equates to 0.05 degrees of angular displacement. This amounts to an angle stamp as opposed to a time stamp.
I need each of these 7200 edges (source: 6602 NI-TIO) to trigger (using RTSI) the acquisition of a single sample from each of 2 channels on an E-Series DAQ board (maybe more channels later). I only need/want one rev (7200 samples per channel) of data for each run of the test. As I write this I think I want pre-triggering and a little more than a rev of data. So the
re is a buffering step. Anyway, you can get the idea.
I need this angle stamp and the DAQ samples to be placed in an array and on the hard drive for graphing and other mathematical treatment, analysis, etc.
I think there must be a way to use the quadrature output of the counter/timer as a scan clock for the DAQ board, but I haven't seen an example to guide me.
It seems like all of the RTSI or other triggering examples I have seen trigger once to start a continuous scan, not a series of discrete samples repeated quickly. I am not sure how to fill an array with this data. Again, examples are for continuous sampling, not a series of discrete readings.
Any hints on any part of this task will greatly appreciated. This is my first LV project.

Sounds like a fairly ambitious first project!
I assume your 7200 edges/rev come from an encoder with 2 channels in quadrature which each provide 1800 cycles/rev. You can clock in analog data at 1800 scans/rev with either of the two encoder channels, but will probably need an external quadrature decoder circuit to produce 7200 scans/rev. Either method can be done with screwdriver and wire or else by using another counter from the 6602 and the RTSI bus. Here are two approaches in detail, but you could mix-and-match as needed.
Note also that if you can be sure that your reference encoder will be uni-directional, you wouldn't need to measure position -- position could be determined by the array index of the analog scan data. This would simplify things greatly.
1800 scans/rev, screwdriver & wire
Wire both encoder channels to your 6602 breakout box and configure your counter for the 4x quadrature option. Send a wire from one of the encoder channel connections at your 6602 breakout box to a PFI pin at your E-series board breakout box. Config the analog acquisition to use an external scan clock and specify the correct PFI pin -- there are built-in examples that will guide you. Now one edge of one encoder channel acts as a scan clock for your analog acquisition. Inside the 6602 breakout box, route the same signal to one of the default gate pins and configure your encoder counter gate to use that pin as its gate signal. Note that there will be a race condition governing whether the encoder value updates from the encoder inputs before or after the value is latched by the gate.
7200 scans/rev, extra counter & RTSI
Make sure you have a RTSI connector between your two acquisition boards inside your PC. Build a quadrature decoder circuit that will convert your two encoder channels into a clock and direction output. (Consider the LSI 7084 decoder chip or similar). Setup your "encoder" counter for buffered position measurement. Use "Counter Set Attribute" to define "up down" as "digital" (don't use it to define "encoder type"). The clock output goes to the counter SOURCE and the direction output goes to the counter UP_DOWN pin.
Use "Adjacent Counters.vi" to identify the counter considered adjacent to your encoder counter. Configure it for "retriggerable pulse generation". Use "Counter Gate (NI-TIO).vi" to specify "other counter source" as the gating signal. Configure the output pulse specs to be short duration (make sure total of delay + pulse width is less than the minimum period of the incoming encoder clock signals). Use "Route Signal.vi" to send this counter's output onto the RTSI bus, say RTSI 0.
Now configure the analog acq. to use RTSI 0 as its external scan clock. Also configure the encoder counter to use RTSI 0 as its gate signal. Voila! Now your quadrature decoder clock output acts as a scan clock for analog acquisition and a "gate" to buffer your encoder measurement. The short delay helps ensure that the clock updates the position measurement before the gate fires to latch the value.
Respond if you need clearer explanation. There's a fair amount of decent info "out there" if you scour the online help and this website. Good luck!

Trigger digital output at every 10 digital pulses

How can i generate an output pulse at every 10 input pulses comming from an encoder?
I need to trigger a sensor at every 10 encoder pulses to get data from the sensor.

Hello jyp777,
What you will need is a counter with an if statement that activates a digital output every 10 ticks. To do this, I would look at a LabVIEW example titled: Counter - Count Edges (Continuous Clock) that can be found under Help >> Find Examples... >> Hardware Input and Output >> DAQmx >> Counter Input in LabVIEW. Using this example VI, it should be a simple step to add a condition that triggers a digital output when the count reaches 10.
You can also use a Digital Output example if you need help in this area. These examples can be found by going to :
Help >> Find Examples... >> Hardware Input and Output >> DAQmx >>Digital Output. I would recommend "Digital - Continuous Output.vi".
Happy LabVIEW coding!
Thanks,
Collin D.
Applications Engineer
National Instruments

Create 4 digital output pulses base on input ttl signal

Hi
I am a beginner in Labview and would appreciate any advice on how to solve the following problem.
I am creating a TTL pulse train, and would like to send that into Labview as input. For every falling edge detected on the input signal, I'd like Labview to generate 4 digital output pulses. For each output pulse, I'd like to be able to specify the delay, and duration. The picture should illustrate it more clearly, with the numbers showing the intended order of magnitude.
System: NI PCI-6733 DAQ card, Labview 8.5
My daq card has 2 24-bit timers, and 8 digital I/O but I don't know what the best approach is for creating between 4-8 output pulses of this precision..should it be handled in hardware, or in software? And how would I go about it
Thanks,
-Sidney
NI Hardware: PXI-7853R, PCI-5122, PCI-6733, PXI-1036, PCI-MIO-16E-4, PCI-6110
Computer Hardware: Xeon Quad Core - 2.33 Ghz, 8 GB RAM
Software: Labview 2009, Labview FPGA 2009, Vista 64-bit, MAX 4.6, DAQmx 9.0, NI-SCOPE 3.5
Solved!
Go to Solution.

Hi Yann,
Wow, thank you so much for this example! I'm trying to take a look at it, but when I run it.. it responds with the following error message
Error -200452 occurred at Property Node DAQmx Trigger (arg 1) in DAQmx Start Trigger (Digital Edge).vi:1->reprise-1.vi
Possible reason(s):
Measurements: Specified property is not supported by the device or is not applicable to the task.
Property: Start.TrigType
Task Name: _unnamedTask<49>
This is strange too, because ive already used the Digital Edge Start trigger for a different application with this card.
-Sidney
NI Hardware: PXI-7853R, PCI-5122, PCI-6733, PXI-1036, PCI-MIO-16E-4, PCI-6110
Computer Hardware: Xeon Quad Core - 2.33 Ghz, 8 GB RAM
Software: Labview 2009, Labview FPGA 2009, Vista 64-bit, MAX 4.6, DAQmx 9.0, NI-SCOPE 3.5

Counte CMOS output pulse

Hello,
I'd like to know whether there are any couters which can count CMOS output pulse.
The rating of CMOS pulse are:
Output pulse: CMOS 5V
Output pulse width: 10 ns
(It is actually output from Hamamatsu C9744 photon counting unit)
I have some PCI cards (6014 and 6110), but their counter logic is TTL, not CMOS.
When the CMOS output is connected to a counter of these cards, the counter number
increased, but this may not be a correct counting.
If you have a good idea to count with NI products, please let me know.
Thank you for your time and kind help.
Hiro
Solved!
Go to Solution.

Hey Hiro,
The bottom line is that a TTL counter will be able to read from CMOS input, but not the other way around. Therefore, you are OK. This is mentioned in the last line of this link: http://digital.ni.com/public.nsf/allkb/5AB6172CAE2BEF3E8625629800597B3F?OpenDocument
An explanation of the voltage thresholds associated with each standard can be found in the graph in this link:http://www.interfacebus.com/voltage_threshold.html
The counters on your devices fall under TTL/CMOS standards, which can count a CMOS pulse input. Some general information about each standard can be found at this link: http://digital.ni.com/public.nsf/allkb/2D038D3AE1C35011862565A8005C5C63?OpenDocument
Regards,
Jeff L.
Applications Engineer | National Instruments

DAQ device for linear encoder & labview 7.0

Ok, I am in a bit of a bind, so the quicker the response the better =). I currently have Labview 7.0, and am needing to read the pulses of a MicroE hi-res encoder. I know I am in need of a DAQ device, so I just want to know which one would be the best (cost-effective & easy to manipulate with Labview). Also, I need three analog inputs as well. Preferably the range of the analog inputs would be 0-10 volts (well, preferably 0-10mv, but that is unikely). I am very unfamiliar with programming Labview, but will learn what I need .
Thank you VERY much!

Hello heepofajeep,
I would highly recommend you go with an M-Series Mulitfunciton DAQ Device for this application. The two counter channels on these devices have expanded support for two phase relative linear and angular encoders, compared to older E Series devices. In addition, these devices are capable of performing analog input, analog output, and digital I/O operations. They contain a minimum of 16 analog input lines, with a programmable gain amplifier that will allow you to programmatically set the range anywhere as large as +/-10V to +/-0.1V in order to take full advantage of the resolution of the ADC on the device. These devices can be programmed in LabVIEW 7.0 or later with the NI-DAQmx driver, and there is the DAQ Assistant and many great example programs for getting up and running with your application quickly.
I hope this information helps and let us know if you have any further questions.
Regards,
Travis G.
Applications Engineering
National Instruments
www.ni.com/support
Message Edited by Travis G. on 08-18-2006 04:55 PM

Single trigger output pulse each iteration

I want to output a trigger pulse, record two analog inputs, and save the data to a text file. When I do this for one iteration it works fine, but multiple iterations only acquire and save, the output pulse is only generated on the first iteration. I am using a counter pulse output to generate the signal. How can I fix this issue?

Hi there,
What kind of board are you using? Are you saving data to the file on every iteration? Depending on your application, it might be advisable to save all data to a file after you are done with your application. Can you post your code so that we can look at it?
Regards,
Efrain G.
National Instruments
Visit http://www.ni.com/gettingstarted/ for step-by-step help in setting up your system.

ProRes presets for Media Encoder CC now available for download

Hi everyone,
We have new ProRes output presets available for Media Encoder CC. You can download the presets here
While the new presets do not add new functionality to Media Encoder, they do provide added convenience. By definition, these presets are for use on Mac OS. If you are on Mac OS X 10.8, or 10.9, the ProRes codecs come installed with your operating system. If you are using Mac OS X 10.7, you will need to install one of the Apple Pro apps (Final Cut Pro, Motion, Compressor, etc.) for the presets to function correctly.
Here’s what’s new with the Media Encoder CC ProRes presets:
Preset names have been updated to say "SD" (instead of “DV")
The Field Order of PAL SD presets changed from "Lower" to "Upper"
Frame Size of NTSC SD presets changed from 720x480 to 720x486. This is based on Apple's ProRes specifications. If 720x480 versions are needed you can create your own User presets with these settings.
Enhanced support for multi-track audio sources. New "Audio Track Layout" and "Channel Layout" sections let you specify the number of exported tracks, track types (single track, dual mono, or stereo pairs), and channel mapping for 5.1 audio
Please note: the ProRes presets should only be installed on AME CC (7.x). They may not work correctly in AME CS6 or earlier versions.
If you have any questions, please let us know.
Eric

Hi Eric,
Much appreciated, but I was wondering when we might expect a framerate and resolution independent way of transcoding media?
Sometimes (as in most of the time) I don't really care about changing resolutions or retiming anything, I usually just have a pile of media that I would like to conform to a single codec, independent of framerate or resolution, like at this very moment.
Right now I need to transcode 100+ clips in various flavors of h.264, mp4, and animation codec in order to get this media into Resolve. I don't want to have to specify different framerates and resolutions, I just want them transcoded to ProRes.
The presets are nice, but the ability to do what I'm needing would greatly reduce the need for presets like these.
Thoughts?
Thanks!
Message was edited by: Graham Hutchins, added a line.

[SOLVED] systemd user unit for lsyncd

After following the the systemd/User - Basic setup wiki article I have successfully setup user services for systemd. I've also setup a systemd user "unit" to run lsyncd. The user unit appears to start successfully based on the unit status shown below. Only problem is lsyncd isn't running and I'm not seeing any relevant errors or info with journalctl. If I run the script defined in ExecStart on the command line lsyncd starts as expected. Any ideas or pointers?
OUTPUT from "systemctl --user lsyncd.service":
lsyncd.service - lsyncd
Loaded: loaded (/home/maseone/.config/systemd/user/lsyncd.service; enabled)
Active: inactive (dead) since Thu 2014-08-28 18:14:50 PDT; 21min ago
Process: 630 ExecStart=/home/maseone/.lsyncd/start_lsyncd_simple.sh (code=exited, status=0/SUCCESS)
Main PID: 630 (code=exited, status=0/SUCCESS)
Aug 28 18:14:50 archie230x systemd[610]: Starting lsyncd...
Aug 28 18:14:50 archie230x systemd[610]: Started lsyncd.
UNIT for lsyncd:
[Unit]
Description=lsyncd
[Service]
ExecStart=/home/maseone/.lsyncd/start_lsyncd_simple.sh
[Install]
WantedBy=default.target
SCRIPT defined in ExecStart:
#! /bin/sh
/bin/lsyncd -log all /home/maseone/.lsyncd/lsyncd.lua
Last edited by maseone (2014-08-29 04:07:58)

firecat53 wrote:
Try changing the service type to forking instead of simple. Or look for an lsycd option that keeps it running in the foreground.
Scott
Thanks for the pointer, it worked! After reading in detail the different types available "forking" does seem the most appropriate type for a daemon written as lsyncd. I believe using an lsyncd option named "detach" would have worked with the "simple" type but forking seemd more appropriate in my case.
Also as an update to my original post I have completely removed the use of the shell script and am now calling lsyncd directly in my defined systemd unit. Also using the %h variable for the home directory now.
REVISED unit file:
[Unit]
Description=lsyncd
[Service]
Type=forking
ExecStart=/bin/lsyncd -log scarce %h/.lsyncd/lsyncd.lua
[Install]
WantedBy=default.target

VBAI: Fire a pulse every N msec based on inspection status

The VBAI Delay function seems to have the functionality I am looking for, but it is too coarse in that the time lapse is 1 second minimum.
I have a Smart Camera (1772). I am doing an OCR inspection that could take a somewhat varying amount of time. I would like to fire a rejector if the inspection fails. The rejector must fire at a fixed amount of time after the camera is triggered. If I cannot reliably do that, then I need another controller in the system which I should not need because the Smart Camera shoulkd be more than adequate. I know it can be done in RT, but I would like to keep things in VBAI for ease of Customer training.
Sequence of operations:
1. Parts travel under 1772 on a conveyor
2. Sensor triggers 1772 when a part is present
3. Image is acquired and processed. OCR inspection performed
4. If OCR inspection fails, fire output pulse exactly 100 (for example) milliseconds after the trigger from step 2
5. Repeat from step 2
Any idea how to achieve that in VBAI?
Thanks,
Dan
Solved!
Go to Solution.

You could have a Generate Pulse step before your acquisition where the pulse is configured to generate a pulse based on a trigger (so configure a continuous pulse and wire you acquisition trigger to an ISO Input line as well that will trigger the output). Now this is the important part...you need to make sure your processing is done before the 100ms or whatever delay you specify or the pulse will begin. If you determine that you don't need to pulse based on your processing, transition to a state where you stop pulse generation on that line to stop it before it happens. In either case, transition to the End state and then the inspection can start again with the state that has the Generate Pulse/Acquire/Process and so the pulse will be reconfigured again for the next part.
If this doesn't work for you, then you could try a SW timed approach. You could have a Run LabVIEW step that gets an accurate timer value when the acquisition step completes, and another VI call that will wait for a user specified amount of time (millisecond resolution) before it continues.
I would recommend the first option since it will be hardware timed (but requires some extra wiring), and if that doesn't work, I can help you with a VI that will do the SW timed behavior you want.
Hope that help,
Brad

Digital stimulus-frequency response: Need to drive with digital output trigger. Using counters for response.

I need to drive stimulus-response with a software driven digital trigger and NI-TIO counter based response. No analog I/O is really relevant, although I have a PCI-6035E multi-function DAQ as part of my gear. I intend to use the analog, but its timing is non-critical and can be software timed.
The real trick is that I want to set the basic timing of the system (in the range of 1 - 50Hz) from the timer0 on the 6035E. This signal needs to be replicated to drive a trigger pulse and to route through RTSI (or a PFI) to trigger frequency counts using the four possible groups of counter/timers on the 6602.
What I need is:
while( enabled )
Repeat at (
software controllable rate = 1-50Hz)
Trigger Sets a PFI line for 10-20us
same trigger sets an RTSI line
- Software Set Delay (usually zero)- stable is more important than the delay time!
Count for software set time on 4 counters
analog samples
Post-process
I want to do this in LabView. I have checked out the Advanced sychronization demos online, but the examples all use analog triggering and buffered digital I/O. This doesn't really address what I need to do.
I have made some failed attempts which relied on software to sync up the trigger and the response frequency acquisition. This is definately flawed. I need to start the counting right after setting the digital output trigger, and stop the count after a fixed interval for frequency calculation.
I am having trouble working through the signal routing to get the timing to trigger off the digital stimulus output pulse.
Any help would be appreciated
Thanks,
Joe

Joe
What are you using the trigger from the 6035E for? I do not know what you mean by, "to trigger frequency countes."
If you are having problems just routing the signal to the 6602, here is a vi that shows you how to route a signal through the RTSI cable to use as the source of a counter.
Brian
Attachments:
Route_RTSI_to_Source.vi ‏67 KB

Error in asfn(rs[[i]]) : need explicit units for numeric conversion

Hi
I am using the sqldf package in R to do some joins of my data table as follows:
p1<-sqldf("SELECT t3.* FROM p as t3 JOIN (SELECT userid, MAX(type) as LastActivityType FROM p GROUP BY userid) t4 ON t3.userid = t4.userid AND t3.type = t4.LastActivityType")
However , I am getting the error mentioned in the subject line
The error doesn't appear when I change the column names from t3.* and limit it to a subset of column names ( t3.userid, t3.LastActivity....).
Surprisingly though, I have another similar sql script in the same code block which runs just fine.
My code runs fine in RStudio, so I guess there's some incompatibility with the Azure environment somewhere. For reference, the sqldf package and its dependencies (imported separately as a zip) is compatible with R 3.1.2
Can someone help me solve this?
Thanks in advance!!

Hi AK
Thanks for the quick response
So I checked the following:
1) Downloaded the dataset from AML from the step just previous to where my sql script appears, fed it into RStudio with stringsAsFactors=FALSE and thereupon ran the sql script. It works without any issues. It works fine if I dont set stringsAsFactors
as false as well
2) Checked the CRAN documentation on the sqldf package, it mentions that the package is valid for versions>=R3.1.0
3)All 4 dependencies were included. Only one was preinstalled. The output log says:
warning: package 'proto' is in use and will not be installedso I removed the package 'proto' just in case it was causing trouble.Nothing Works :/I am pasting the output log, could you have a look and see if I am missing anything obvious?Thanks a ton!UpasanaOutput Log:Record Starts at UTC 11/27/2014 07:38:27:
Run the job:"/dll "ExecuteRScript, Version=5.1.0.0, Culture=neutral, PublicKeyToken=69c3241e6f0468ca;Microsoft.MetaAnalytics.RDataSupport.ExecuteRScript;Run" /Output0 "..\..\Result Dataset\Result Dataset.dataset" /Output1 "..\..\R Device\R Device.dataset" /dataset1 "..\..\Dataset1\Dataset1.csv" /bundlePath "..\..\Script Bundle\Script Bundle.zip" /rStreamReader "script.R" "
Starting process 'C:\Resources\directory\275cc759e61f4dbf889cde5e5cba0835.SingleNodeRuntimeCompute.Packages\AFx\5.1\DllModuleHost.exe' with arguments ' /dll "ExecuteRScript, Version=5.1.0.0, Culture=neutral, PublicKeyToken=69c3241e6f0468ca;Microsoft.MetaAnalytics.RDataSupport.ExecuteRScript;Run" /Output0 "..\..\Result Dataset\Result Dataset.dataset" /Output1 "..\..\R Device\R Device.dataset" /dataset1 "..\..\Dataset1\Dataset1.csv" /bundlePath "..\..\Script Bundle\Script Bundle.zip" /rStreamReader "script.R" '
[ModuleOutput] DllModuleHost Start: 1 : Program::Main
[ModuleOutput] DllModuleHost Start: 1 : DataLabModuleDescriptionParser::ParseModuleDescriptionString
[ModuleOutput] DllModuleHost Stop: 1 : DataLabModuleDescriptionParser::ParseModuleDescriptionString. Duration: 00:00:00.0050545
[ModuleOutput] DllModuleHost Start: 1 : DllModuleMethod::DllModuleMethod
[ModuleOutput] DllModuleHost Stop: 1 : DllModuleMethod::DllModuleMethod. Duration: 00:00:00.0000572
[ModuleOutput] DllModuleHost Start: 1 : DllModuleMethod::Execute
[ModuleOutput] DllModuleHost Start: 1 : DataLabModuleBinder::BindModuleMethod
[ModuleOutput] DllModuleHost Verbose: 1 : moduleMethodDescription ExecuteRScript, Version=5.1.0.0, Culture=neutral, PublicKeyToken=69c3241e6f0468ca;Microsoft.MetaAnalytics.RDataSupport.ExecuteRScript;Run
[ModuleOutput] DllModuleHost Verbose: 1 : assemblyFullName ExecuteRScript, Version=5.1.0.0, Culture=neutral, PublicKeyToken=69c3241e6f0468ca
[ModuleOutput] DllModuleHost Start: 1 : DataLabModuleBinder::LoadModuleAssembly
[ModuleOutput] DllModuleHost Verbose: 1 : Trying to resolve assembly : ExecuteRScript, Version=5.1.0.0, Culture=neutral, PublicKeyToken=69c3241e6f0468ca
[ModuleOutput] DllModuleHost Verbose: 1 : Loaded moduleAssembly ExecuteRScript, Version=5.1.0.0, Culture=neutral, PublicKeyToken=69c3241e6f0468ca
[ModuleOutput] DllModuleHost Stop: 1 : DataLabModuleBinder::LoadModuleAssembly. Duration: 00:00:00.0067974
[ModuleOutput] DllModuleHost Verbose: 1 : moduleTypeName Microsoft.MetaAnalytics.RDataSupport.ExecuteRScript
[ModuleOutput] DllModuleHost Verbose: 1 : moduleMethodName Run
[ModuleOutput] DllModuleHost Information: 1 : Module FriendlyName : Execute R Script
[ModuleOutput] DllModuleHost Information: 1 : Module Release Status : Release
[ModuleOutput] DllModuleHost Stop: 1 : DataLabModuleBinder::BindModuleMethod. Duration: 00:00:00.0106972
[ModuleOutput] DllModuleHost Start: 1 : ParameterArgumentBinder::InitializeParameterValues
[ModuleOutput] DllModuleHost Verbose: 1 : parameterInfos count = 5
[ModuleOutput] DllModuleHost Verbose: 1 : parameterInfos[0] name = dataset1 , type = Microsoft.Numerics.Data.Local.DataTable
[ModuleOutput] DllModuleHost Start: 1 : DataTableCsvHandler::HandleArgumentString
[ModuleOutput] DllModuleHost Stop: 1 : DataTableCsvHandler::HandleArgumentString. Duration: 00:00:13.1522942
[ModuleOutput] DllModuleHost Verbose: 1 : parameterInfos[1] name = dataset2 , type = Microsoft.Numerics.Data.Local.DataTable
[ModuleOutput] DllModuleHost Verbose: 1 : Set optional parameter dataset2 value to NULL
[ModuleOutput] DllModuleHost Verbose: 1 : parameterInfos[2] name = bundlePath , type = System.String
[ModuleOutput] DllModuleHost Verbose: 1 : parameterInfos[3] name = rStreamReader , type = System.IO.StreamReader
[ModuleOutput] DllModuleHost Verbose: 1 : parameterInfos[4] name = seed , type = System.Nullable`1[System.Int32]
[ModuleOutput] DllModuleHost Verbose: 1 : Set optional parameter seed value to NULL
[ModuleOutput] DllModuleHost Stop: 1 : ParameterArgumentBinder::InitializeParameterValues. Duration: 00:00:13.1845731
[ModuleOutput] DllModuleHost Verbose: 1 : Begin invoking method Run ...
[ModuleOutput] Microsoft Drawbridge Console Host [Version 1.0.2108.0]
[ModuleOutput] [1] 56000
[ModuleOutput]
[ModuleOutput] The following files have been unzipped for sourcing in path=["src"]:
[ModuleOutput]
[ModuleOutput] Name Length Date
[ModuleOutput]
[ModuleOutput] 1 sqldf_0.4-10.zip 71667 2014-11-21 11:38:00
[ModuleOutput]
[ModuleOutput] 2 chron_2.3-45.zip 107752 2014-11-21 11:38:00
[ModuleOutput]
[ModuleOutput] 3 DBI_0.3.1.zip 153831 2014-11-21 11:38:00
[ModuleOutput]
[ModuleOutput] 4 gsubfn_0.6-6.zip 348505 2014-11-21 11:38:00
[ModuleOutput]
[ModuleOutput] 5 proto_0.3-10.zip 458519 2014-11-21 11:38:00
[ModuleOutput]
[ModuleOutput] 6 RSQLite_1.0.0.zip 1211130 2014-11-21 11:38:00
[ModuleOutput]
[ModuleOutput] Loading objects:
[ModuleOutput]
[ModuleOutput] port1
[ModuleOutput]
[ModuleOutput] [1] "Loading variable port1..."
[ModuleOutput]
[ModuleOutput] package 'gsubfn' successfully unpacked and MD5 sums checked
[ModuleOutput]
[ModuleOutput] Loading required package: proto
[ModuleOutput]
[ModuleOutput] [1] TRUE
[ModuleOutput]
[ModuleOutput] package 'DBI' successfully unpacked and MD5 sums checked
[ModuleOutput]
[ModuleOutput] [1] TRUE
[ModuleOutput]
[ModuleOutput] package 'RSQLite' successfully unpacked and MD5 sums checked
[ModuleOutput]
[ModuleOutput] [1] TRUE
[ModuleOutput]
[ModuleOutput] package 'sqldf' successfully unpacked and MD5 sums checked
[ModuleOutput]
[ModuleOutput] [1] TRUE
[ModuleOutput]
[ModuleOutput] Loading required package: tcltk
[ModuleOutput]
[ModuleOutput] Error in asfn(rs[[i]]) : need explicit units for numeric conversion
[ModuleOutput]
[ModuleOutput] In addition: Warning messages:
[ModuleOutput]
[ModuleOutput] 1: In strptime(x, format, tz = tz) :
[ModuleOutput]
[ModuleOutput] unable to identify current timezone 'C':
[ModuleOutput]
[ModuleOutput] please set environment variable 'TZ'
[ModuleOutput]
[ModuleOutput] 2: In strptime(x, format, tz = tz) : unknown timezone 'localtime'
[ModuleOutput]
[ModuleOutput] 3: package 'gsubfn' was built under R version 3.1.2
[ModuleOutput]
[ModuleOutput] 4: package 'DBI' was built under R version 3.1.2
[ModuleOutput]
[ModuleOutput] 5: package 'RSQLite' was built under R version 3.1.2
[ModuleOutput]
[ModuleOutput] 6: package 'sqldf' was built under R version 3.1.2
[ModuleOutput]
[ModuleOutput] 7: In strptime(xx, f <- "%Y-%m-%d %H:%M:%OS", tz = tz) :
[ModuleOutput]
[ModuleOutput] unknown timezone 'localtime'
[ModuleOutput]
[ModuleOutput] DllModuleHost Stop: 1 : DllModuleMethod::Execute. Duration: 00:02:41.0341394
[ModuleOutput] DllModuleHost Error: 1 : Program::Main encountered fatal exception: Microsoft.Analytics.Exceptions.ErrorMapping+ModuleException: Error 0063: The following error occurred during evaluation of R script:
[ModuleOutput] ---------- Start of error message from R ----------
[ModuleOutput] R script execution failed. Please click on "View Output Log" in the properties pane for full details.
[ModuleOutput] ----------- End of error message from R -----------
Module finished after a runtime of 00:02:41.1766291 with exit code -2
Module failed due to negative exit code of -2
Record Ends at UTC 11/27/2014 07:41:12.

Best display calibration unit for mac pro under $100?

I have come to the conclusion that calibration by eye is a suckers bet. So looking at calibration units, for example spyder 3 express.
Wondering what units work best with mac pro (2008 8 core).
Thanks for replies.

My experience is that it comes down to multiple factors. The monitor, the application you're using, along with the color profiles you're using.
I use a 30" Dell display hooked to a 5770 graphics card and I make sure the color profiles are consistant over the applications I use.
At one stage I bought a Huey Color Correction device. I eventually put it on the shelf and forgot about it.
My conclusion is, after years of consistently good color printing results, is that if you've got the components right like a good monitor and working with consistant color and press profiles then the "Expert Mode" is Apple's Color Calibration in System Preferences is completely adequate.
I spend every day color correcting in our graphic design business and we get terrific, predictable results.

Need help with control system that reduces a flat output signal every time a certain input exceeds given value

I'm having difficulty setting up a closed loop control system that reduces one of my voltage outputs (connected to a high voltage system) by 30% every time a measured voltage exceeds a certain threshold value. I'm using a USB 6229 DAQ. I've been trying to create a waveform that looks like a DC signal, but the only waveforms that I can seem to manipulate while my VI is running are the stock waveform types. Also, I've tried to use a formula node or conditional structure to update the output value every time the measured voltage exceeds a given value, but everything I do reinitializes the output value every time it runs or won't store the previous signal value. I'm using LabVIEW 8.6 and don't have the PID or similar express VI's. I've attached the mess I've got working right now. Can anyone help? I'm really stuck!
Thanks!
Attachments:
HiV step down.vi ‏40 KB
output control.vi ‏100 KB

I'm sorry it's such a mess; I'm still pretty new at this. These are both little driver programs for a larger overall control program.
Output control is meant to send a flat signal to the DAQ whose value can be manipulated while the VI is running. I have the second activated segment merely to check the values being output. I didn't realize I attached a version with a meaningless control...I had a control where the user would put in the stating voltage (the high voltage source has a 1V-100V setting for external control). I've attached this slightly different but equally dysfunctional version. Ideally, I would have liked something like the analog signal generator vi to come with an input wiring for offset on the DC signal. Most of the code was diabled because it is copied from an example; it is largely rubbish. I initially used the DAQ Assistant, but when things weren't working out I switched to putting in each step manually to try to troubleshoot.
As far as HiV step down is concerned, I've tried something different with a nested case structure (if that's the right terminology?), and I've attached that file. I think this problem has been solved, but you never know!
Attachments:
output control slightly different.vi ‏100 KB
HiV step down w case structures.vi ‏44 KB

"not enough disk space for asset encoding" error message

I'm using DVD SP 4.2.1 and trying to burn a DL DVD. Every time I try to build the TS folders somewhere, I get the "not enough disk space for asset encoding" message. I have PLENTY of space (over 100GB) where I'm assigning it to create the TS folders. I don't understand why I'm getting the message. Your help is appreciated.

Max,
I think you're onto something here. I noticed that the original disk (an old Iomega Peerless 20GB removable hard drive) was nearly full. I also saved the DVD Studio Pro file for the project to the same drive. I think that, somehow, the application looked to that drive to do something and got a "disk full" message from that disk and gave me the error.
The workaround was to transfer all the assets AND the project file to another hard disk with plenty of space (over 100 GB). The settings for the DVD Studio Pro encoding process remained the same…my computer's internal hard disk with its 30 GB of free space. I re-linked the assets and the disk building and encoding process went smoothly and I'm now the proud owner of a finished DVD.
There's probably something lurking in the background here, but this worked for me.
Thanks for making the suggestion to look deeper! My problem is solved!
Kevin

Output pulse every n units for x4 encoder

Similar Messages

Maybe you are looking for