Discrepency in output

Hi All ,
I have a query , in the below code
wa_exceplist_inv-ADC_VARIANCE = wa_exceplist_inv-AVERAGE_DAILY_CONSUMPTION -
                       wa_exceplist_inv-PREVIOUS_ADC.
the values for the fields are
wa_exceplist_inv-AVERAGE_DAILY_CONSUMPTION  = 25.50
wa_exceplist_inv-PREVIOUS_ADC = 0.00
but the output in the field    wa_exceplist_inv-ADC_VARIANCE is 0.00 where in it should be 25.50 ,
the date declaration for the above fields are :
AVERAGE_DAILY_CONSUMPTION type erdz-I_ABRMENGE,
        PREVIOUS_CONSUMPTION TYPE erdz-I_ABRMENGE,
        PREVIOUS_ADC type erdz-I_ABRMENGE,
        ADC_VARIANCE type erdz-I_ABRMENGE,
where   erdz-I_ABRMENGE is of the type DEC .
can anyone please give some suggestions on this .

Hi,
I tried this in my report pgm as below and it is working fine..
data: AVERAGE_DAILY_CONSUMPTION type BBPMENGE value '25.50',
      PREVIOUS_CONSUMPTION TYPE BBPMENGE,
      PREVIOUS_ADC type BBPMENGE value '0.00',
      ADC_VARIANCE type BBPMENGE.
      ADC_VARIANCE = AVERAGE_DAILY_CONSUMPTION - PREVIOUS_ADC.
      write:/ ADC_VARIANCE.
I am getting 25.50 as output.
Keerthi.

Similar Messages

  • PSE 8 monitor-output discrepancy

    I've been using Photoshop Elements 8 successfully for several years. My OS is Windows XP and my printer is an Epson R1900. I consider myself to be a very good printer. But... about two or three months ago my system changed drastically. Where before I usually had near WYSIYG compatibility between monitor image and printed output now I had a very great discrepancy. If I edited an image in PSE 8 and went ahead and made a print from that edit using the settings (ICM) I had always used with no problems, the result was a dark, greenish-cast image that bore little relation to either the monitor image OR the Windows picture an fax viewer. I've reloaded both printer and PSE 8 software. This did no good
    Currently, because of this discrepancy, I'm forced to use the Windows viewer for evaluation. The PSE 8 monitor image that give a correct print looks somewhat washed out and with a slightly reddish cast, one you would never think of printing as is. Some older files, say one with a typical blue sky, show up with the sky having a vivid robin's egg blue cast or have other areas of the image showing off color.
    Any suggestions, ideas, or fix ideas will be appreciated.
    Bob Clemens
    Rochester, NY

    I have two monitors.   The trick to moving something from the #1 Monitor to #2 monitor is to first
    click that button between the X and the - up at the top right of your screen in the blue bar.  Hover over it and it
    says "Restore Down".  This makes whatever you have on the screen less than full screen but
    still visible.
    Then you can grab it and move it over to the other screen.  (Left click, hold, and drag)  For some
    reason, a full screen view won't move, but the smaller screen view does.  Grab it and move it
    horizontally to the other screen.
    After you have it on the second screen in the smaller size, that Restore Down button becomes the
    Maximize button.  Click that and whatever you've moved will be full screen.
    My set-up is a little different because my #1 screen is to my left and is the smaller screen just
    because that's how my office is arranged.  I do my primary work on my #2 screen which is the
    larger screen. Programs open on #1 screen and I have to move them to #2 screen.

  • Discrepancy between HD monitor and output video

    Howdy community,
    I have a weird problem with Final Cut Pro 7. I have an Asus VW266H HD monitor, set at a good viewing angle on my desk. When I was editing some footage, it looked WAY too dark, so I used a color correction filter and brought the blacks up to 95. The resulting image in the FCP viewer window is the one you see on the left in my screen shot. I hope you can imagine just how dark the original footage was. I was reasonably satisfied with how the footage looked, especially since it wasn't looking "milky" like it can if you lighten/whiten too much in post.
    So then I exported the footage, and got the image on the right (in my screen shot). These two images are from the same second of video, on the same monitor. NO changes were made between the exported version in QT on the right and the FCP viewer image on the left.
    Why does my monitor and/or the final cut viewer window show me an image that does not represent my output? If the image in final cut and the exported version in quick time look so different, how can I trust my eye in final cut?
    Obviously, this is a huge problem.
    Please help!!!

    If that is the case, how does the editor control how the image looks to others?
    You can't. This general problem has been around since the advent of moving pictures. Wander over to the video wall at any big box store and look at the displays. There won't be two that appear alike. All you can do is control the image you send out.
    If you are seriously interested in image integrity, get yourself a output device from AJA, BlackMagic, Matrox, etc that can send a qualified signal and a calibrated broadcast TV monitor to to view that signal. Then you'll know what it really looks like.
    To paraphrase the old Yiddish saying, "A man with two clocks can never be sure of the time, but, man with an atomic clock, will know."
    Good luck.
    x

  • Replacement AC Adapter - Output Discrepancy

    I bought a replacement power adapter on ebay, the specifications for the non-apple replacement matched exactly. The one I received though is slightly different: output of 2.65A instead of 1.875A as stated on the original A1036 adapter. The vendor assures me this is acceptable, but I don't want to cook anything. Any thoughts? Thanks!
    Dave

    Hey Dave,
    Well I'm sitting here on a 1.2 14" iBook and just read your post. I looked at my power adapter and it's a 65 Watt adapter outputting 24.5 Volts @ 2.65 Amps model A1021. Didn't realize I had one. I never even look at the Amp rating but the 65W A1021 is considered an upgrade from the A1036 and is usually more expensive. If you had a larger PowerBook it would require this adapter.
    So upshot is I apparently have both ( about 5 all together ) and use both interchangeably. The iBook is not going to care how many Amps the adapter is capable of putting out. It will only use what it needs.
    Richard
    Message was edited by: spudnuty

  • Discrepancy in the table payr, need urgent help

    Dear All,
    i have one table payr in logical database.
    2 fields of it i,e kunnr and vblnr
    When i goto se16 and select the data for say kunnr = '2901350' and vblnr = '20002000'
    Now what happens for this combination i get no data found.
    but say i enter only vblnr = '20002000' i get teh outpur with kunnr '2901350'.
    BUt at the time of selection i enter data i dont get it.
    I also tried entering '0002901350' than to data is not coming.
    when i entered in selection kunnr = '2901350*' then i get the output
    PLease help me output it this is the problem with the conversion exit or not
    how to resolve the problem
    Regards,
    Tanvi

    is the table being updated by any  Z PROGRAM ,,
    if so then in that program check whether the entries on kunnr and vblnr have used conversion alpha routine ..
    if i dont use a routine on value 21220020 then if it is storing in the table as 21220020 then its a discrepancy cause it has to be stored as 0021220020 .
    see if any database entry is like this which u have referred in the post .
    if any one is missing(either on kunnr or vblnr) then its a data discrepancy problem for which u cannot handle with a select.
    regards,
    vijay

  • Get MUTLIPLE output files for SINGLE input file with multiple records

    Hi ,
    I have source xml file  which has multiple records in it and  I want to get multiple seperate  flat files for it.
    this is my source structure
    <root>
    <Header1 fld1=1234 fld2="name1" fld3='SAP1"
    fld4='000" fld5=0 fld6="sdn1"></header>...............no line items here
    <Header2 fld1=123 fld2="name" fld3='SAP"
    fld4='00" fld5=0 fld6="sdn" ><line fld7=value1 fld8=value2 fld9=value3 /line><line fld7=value4 fld8=value5 fld9=value6 /line></header>.....two line items here
    <Header3 fld1=123 fld2="name" fld3='SAP"
    fld4='00" fld5=0 fld6="sdn" ><line fld7=value7 fld8=value8 fld9=value9 /line></header>......one line item here
    Header4 fld1=12345 fld2="name2" fld3='SAP2"
    fld4='0006" fld5=01 fld6="sdn2"</header>.......no line items here
    </root>
    I am trying to get flat files as many time the <b>header</b> values occur that many target files should appear in the target.
    like
    file1:
    1234name1SAP10000~sdn1
    file2:
    123nameSAp000~sdn
    value1value2valu3
    valu4value5value6
    file3:
    123namesap000~sdn
    value7valu8value9
    file4:
    12345name2SAP2000601~SDN2
    here I have 4 headers so i need to get 4 output files ,similarly for 'n' headers I need to get 'n'  output flat files. the above mentioned source xml file is just one file,like that I might get somany sourc xml files which has similar structure in it.
    and also it is important to get the line items,if exists to the header, for the corresponding headers.
    how can I achieve this?do I need to use BPM or any mappings other than Graphical? 
    please suggest me.
    thank you.
    Babu
    sorry,output file structure changed
            Babu

    Babu,
    See the Mapping and the logic.
    Make sure your target message occurrence:http://www.flickr.com/photo_zoom.gne?id=1412748793&size=o
    Check out for source and target structure
    http://www.flickr.com/photo_zoom.gne?id=1412748803&size=o
    http://www.flickr.com/photo_zoom.gne?id=1412748809&size=o
    http://www.flickr.com/photo_zoom.gne?id=1412748815&size=o
    http://www.flickr.com/photo_zoom.gne?id=1412748825&size=o
    Results:http://www.flickr.com/photo_zoom.gne?id=1412748799&size=o
    Note:
    While creating Interface determination choose it as Enhanced/Extended
    The Receiver Content conversion - For field separator and line separator give 'nl' , coz we concatenated all of them using ~ in mapping.
    If you find any discrepancy in the above logic , please let me know.
    raj.

  • Duplexing Discrepancy

    Some of our users have noticed that on some models of HP printers that when they duplex, there is a discrepancy between the margin size intended and what is printed. An example is if you wanted to print both sides borderless, then the duplexed or back side may be slightly shrunk to have a small margin. This issue does not come up often, but I have seen a few threads in the last week which brought it up.
    After extensively researching this and through contacting our engineers I have found an answer for this issue. For those who have experienced this issue, it is part of the printer’s design and will not be subject to change. Essentially, it is due to the mechanics of the duplexer. The first page is held by the output roller, but the second page reduces in size so that the main roller can maintain contact with the page (this affects all inkjets).
    If you need to print with duplex outside of these margin presets, the best method to achieve this is by manually duplexing the pages involved (placing the printed page face up, right side up in the tray). To perform large print jobs which require this feature, simply print off the odd pages first (there should be an option in your program’s print settings for this), then manually duplex all the even pages.
    I hope this information is helpful to anyone who might experience this issue.
    This question was solved.
    View Solution.

    Here is a cute cat for reading this post  

  • [Solved] Parsing findmnt output?... Is it reliable/portable in bash.

    Solution/better suggestion in second post...
    There seems to be little about using anything other than the output of mount or fstab when dealing with filesystems in scripting. Most of what I've read on it uses awk or cut for parsing "mount" but what about findmnt when needing  some of the same info. particularly "findmnt -rn" which prints the same raw information as mount but space separated and without the words like "type" and "on". I'm not entrirely concerned with posix compliance as most of it amount to makings it compatible with much much older systems. Personally I think bash has been around long enough to be portable in and of itself in most circumstances but that's just my opinion. Is "findmnt" as portable as "mount" for scripting? that is really my question.
    An example would be say I wanted only the "target" and "source" information stored with process substitution in bash.
    with mount I could use
    #mount | cut -d ' ' -f 1,3
    to get that info for all mounted filesystems
    OR
    #mount | grep sdb1 | cut -d ' ' -f 3
    to get where a particular partition (/dev/sdb1) is mounted.
    with findmnt it would be just as simple but take the words "on" and "type" out of the parsing.
    #findmnt -rn | cut -d ' ' -f 1,2
    or for the second example using mount...
    #findmnt -rn | grep sdb1 | cut -d ' ' -f 1
    if neither of these are the best for getting simple information then I can accept other suggestions as well.
    Think of the pipe to grep section having a variable with the needed string instead of "sdb1" for instance...
    maybe this is just a minor formatting discrepancy. If so feel free to point it out... I'm kinda on my journey of do's and don't's in shell scripting with only google and the man pages as my resources for learning.
    Last edited by Thme (2012-12-22 19:55:58)

    falconindy wrote:
    Thme wrote:
    with findmnt it would be just as simple but take the words "on" and "type" out of the parsing.
    #findmnt -rn | cut -d ' ' -f 1,2
    or for the second example using mount...
    #findmnt -rn | grep sdb1 | cut -d ' ' -f 1
    This is an entire misuse of findmnt. If you're going to talk about "portable" or "POSIX", then you can't even use mount.
    If you want specific columns from findmnt, then ask for them. Specifically, the -o option is your friend, i.e.
    $ findmnt -runo source,target /dev/sdb1
    /dev/sdb1 /home
    If you're looking for some absurd level of portability where you might encounter systems that don't have findmnt, then you'll need to build a parser for /etc/mtab, and even that isn't portable.
    That's clear enough to me. And no I wasn't too interested in POSIX compliance. It seems like overkill in most circumstances. As for the findmnt options.. I should have read the man page a little more... totally skimmed over it... I'll mark this as solved...

  • REG:SERVLET OUTPUT STREAM

    I am trying to implement upload/view functionality..To view an uploaded txt file or html file,I am just flushing out the file contents into servlet's output stream..The content type has been set appropriately.
    The problem is for some html files ia m able to see the file contents in the browser,and for some html files,the browser displays a open/save dialog box..
    Can any1 explain me why this discrepency?Its the sam e code and same content type..why is it so?

    Thanks for ur reply...
    All i mentioned was in the same browser..PFB the code snippet
         ServletOutputStream pic = null;
         pic = response.getOutputStream();
         ByteArrayOutputStream baos = new ByteArrayOutputStream();
         byte b[] = new byte[5*1024];
         while(true)
              int bytes = in.read(b);
              if(bytes == -1)
                   break;
              baos.write(b, 0, bytes);
         response.setContentLength(b.length);
         b = baos.toByteArray();
         pic.write(b, 0, b.length);
         pic.flush();
         pic.close()

  • Level Meter Plug In -VS- Output 1/2 meter...Inconsistencies...

    I'm mixing an 18 minute long recording for vinyl release. The vinyl pressing company has a minimum dbl on recordings they master and press. If the level is under, they charge hundreds of dollars more to re master and increase the volume via massive compression.
    So to check and double check the overall volume in Logic Express 8, all I can find for a meter is the "Level Meter" in the visualization plug in toolbox. So I have the Level Meter "plugged" into the Output 1/2 track...The problem with the Level Meter is that it is showing levels around 8 dbl lower than the Output 1/2 meter. This could potentially be an expensive discrepancy not to mention may have a negative effect on the end product's sound quality.

    Eriksimon wrote:
    If you used a meter as an insert, it comes, like other effects plugins, before the fader. Sorry, I didn't read attentively the first time.
    Still, the effect is the same as pre-fader metering. The signal passes the meter before it goes to the fader. If you turn pre-fader metering on you'll see that your faders don't affect the channel strip level meters anymore and behave like inserted level meters as well.
    So if you lower the fader on channel 1&2 so you no longer see clipping, how does it work?
    1. Does it lower the output simply telling you that you are not clipping going out from fader 1&2?
    or
    2. Does it lower the input from all contributing channels so that the source coming to fader 1&2 no longer clips?

  • Discrepancy between IM stock and WM Stock

    Hi experts,
    We found there is discrepancy between IM stock and WM Stock.Before configuring WM storage types , IM Stocks are not syched. So WM stocks are showing less then IM stocks,. Now i need to synch up the IM stock and WM stock. what we needs to do. Can you please guide us.
    Thanks & Regards,
    Vamsi

    OR
    have a look at using transaction LX23 (provided you dont use HUM this should help you determine/ analyse and post any differences between IM and WM).
    thanks,
    A
    LX23: Stock Comparison Inventory Management / Warehouse Management
    Description
    Using this report you can generate an inventory comparison between the IM System (Inventory Management) and the WM System (Warehouse Management).
    On the selection screen, you can limit the area for comparison by entering the plant / storage location, plant / warehouse number or only the warehouse number.
    In addition to specifying the area, you can also determine the extent of information to be issued.  Here you have three options:
    1. "With bin inventory"
    In addition to generating the corresponding stock figures, you can also have a list of the corresponding WM bin quantities included.
    2. "All data on material"
    Even if only one difference occurs in one of the listed combinatations of material / batch / special stock indicator / supplier, all material combinations are listed. This can be very helpful when searching for errors.
    3. "Clear differences"
    If you mark this field, the system will generate a batch input session. By starting the batch input session, the differences to be cleared are removed in the IM system.  Negative WM stock figures and stock differences in returns will not be cleared.
    If you want to have a batch input file generated for the purpose of clearing the differences, it is important, for consistency reasons, that the materials in the respective warehouse are blocked in order that postings affecting stock figures can be prevented.
    CAREFUL: If you generate this session, all the material stocks belonging to the respective warehouse number are blocked completely, that is, for the duration of the program, no postings affecting the stock in the warehouse will be possible!
    Prerequisites
    The comparison is also possible for warehosue numbers managed on a decentralized basis.
    Output
    You receive a list with various materials. The list contains the following information, for example:
    The first line contains the plant, storage location, warehouse number, material number, total stock in inventory management, total stock in the warehouse, and the difference between the stocks.
    The following line contains the first combination of batch / special stock indicator / supplier (or sales document and item number for sales order stock) and stock category (Q,R,S, ), the stock figures in Inventory Management, in Warehouse Management, and the difference.
    If a batch input session is to be generated, the list contains a note in the log as to whether or not a session has been generated or behind the pushbutton "non-postable stocks", which materials could not be cleared because of negative stock figures or because they belong to returns stock.
    Edited by: WILSAQ on Aug 11, 2009 12:09 AM

  • Discrepancy message Link Duplex Mismatch

    I got a lot of Discrepancy messages that operation team said that are wrong messages. one of them is below :
    [sc11601.stc.com.sa,FastEthernet7/1],[rc11601.stc.com.sa,FastEthernet12/0/1]
    interface FastEthernet7/1
    description P2P.RC11601.SC11601 -> RC11601 FE12/0/1
    ip vrf forwarding COM/IS
    ip address 172.20.2.62 255.255.255.252
    ip accounting output-packets
    ip ospf network point-to-point
    speed 100
    duplex full
    wrr-queue bandwidth 70 30
    wrr-queue queue-limit 60 20
    wrr-queue cos-map 1 2 0 1
    wrr-queue cos-map 2 2 2 3 6 7
    mls qos trust dscp
    end
    SC11601#sh interfaces FastEthernet7/1
    FastEthernet7/1 is up, line protocol is up (connected)
      Hardware is C6k 100Mb 802.3, address is 00d0.00ec.7400 (bia 00d0.00ec.7400)
      Description: P2P.RC11601.SC11601 -> RC11601 FE12/0/1
      Internet address is 172.20.2.62/30
      MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
         reliability 255/255, txload 1/255, rxload 98/255
      Encapsulation ARPA, loopback not set
      Keepalive set (10 sec)
      Full-duplex, 100Mb/s
      input flow-control is off, output flow-control is unsupported
      ARP type: ARPA, ARP Timeout 04:00:00
      Last input 00:00:00, output 00:00:00, output hang never
      Last clearing of "show interface" counters never
      Input queue: 0/75/0/123 (size/max/drops/flushes); Total output drops: 62970
      Queueing strategy: fifo
      Output queue: 0/40 (size/max)
      5 minute input rate 38682000 bits/sec, 18397 packets/sec
      5 minute output rate 179000 bits/sec, 166 packets/sec
      L2 Switched: ucast: 11975833 pkt, 1479635171 bytes - mcast: 14194902 pkt, 3811719114 bytes
      L3 in Switched: ucast: 429215085703 pkt, 94830171248319 bytes - mcast: 0 pkt, 0 bytes mcast
      L3 out Switched: ucast: 6824514014 pkt, 1288372109867 bytes mcast: 0 pkt, 0 bytes
         430025276460 packets input, 94920777016321 bytes, 0 no buffer
         Received 14799648 broadcasts, 0 runts, 0 giants, 0 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
         0 input packets with dribble condition detected
         7696316854 packets output, 1389443700164 bytes, 0 underruns
         0 output errors, 0 collisions, 2 interface resets
         0 babbles, 0 late collision, 0 deferred
         0 lost carrier, 0 no carrier
         0 output buffer failures, 0 output buffers swapped out
    SC11601#
    other interface:
    interface FastEthernet12/0/1
    description P2P.RC11601.SC11601
    ip vrf forwarding COM/IS
    ip address 172.20.2.61 255.255.255.252
    no ip directed-broadcast
    ip accounting output-packets
    ip route-cache flow
    ip ospf network point-to-point
    load-interval 30
    full-duplex
    service-policy input Set-Experimental-COM/IS
    service-policy output HSBB-Policy
    end
    RC11601#sh interfaces FastEthernet12/0/1
    FastEthernet12/0/1 is up, line protocol is up
      Hardware is cyBus FastEthernet Interface, address is 0010.0d59.0981 (bia 0010.0d59.0981)
      Description: P2P.RC11601.SC11601
      Internet address is 172.20.2.61/30
      MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 85/255
      Encapsulation ARPA, loopback not set
      Keepalive set (10 sec)
      Full-duplex, 100Mb/s, 100BaseTX/FX
      ARP type: ARPA, ARP Timeout 04:00:00
      Last input 00:00:00, output 00:00:00, output hang never
      Last clearing of "show interface" counters 2w6d
      Input queue: 0/75/6/0 (size/max/drops/flushes); Total output drops: 238552
      Queueing strategy: VIP-based fair queuing
      30 second input rate 167000 bits/sec, 148 packets/sec
      30 second output rate 33621000 bits/sec, 17158 packets/sec
         266182338 packets input, 34247141843 bytes, 0 no buffer
         Received 693431 broadcasts, 0 runts, 0 giants, 1 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
         0 watchdog, 0 multicast
         0 input packets with dribble condition detected
         27319889810 packets output, 6807897544306 bytes, 0 underruns
         0 output errors, 0 collisions, 0 interface resets
         0 babbles, 0 late collision, 0 deferred
         0 lost carrier, 0 no carrier
         0 output buffer failures, 0 output buffers swapped out

    momsrv02:/ # snmpwalk rc11601 1.3.6.1.2.1.2.2.1.2
    interfaces.ifTable.ifEntry.ifDescr.1 : DISPLAY STRING- (ascii):  GigabitEthernet1/0/0
    interfaces.ifTable.ifEntry.ifDescr.2 : DISPLAY STRING- (ascii):  Serial2/0
    interfaces.ifTable.ifEntry.ifDescr.3 : DISPLAY STRING- (ascii):  Serial2/1
    interfaces.ifTable.ifEntry.ifDescr.4 : DISPLAY STRING- (ascii):  Serial2/2
    interfaces.ifTable.ifEntry.ifDescr.5 : DISPLAY STRING- (ascii):  Serial2/3
    interfaces.ifTable.ifEntry.ifDescr.6 : DISPLAY STRING- (ascii):  Serial2/4
    interfaces.ifTable.ifEntry.ifDescr.7 : DISPLAY STRING- (ascii):  Serial2/5
    interfaces.ifTable.ifEntry.ifDescr.8 : DISPLAY STRING- (ascii):  Serial2/6
    interfaces.ifTable.ifEntry.ifDescr.9 : DISPLAY STRING- (ascii):  Serial2/7
    interfaces.ifTable.ifEntry.ifDescr.10 : DISPLAY STRING- (ascii):  Serial3/0
    interfaces.ifTable.ifEntry.ifDescr.11 : DISPLAY STRING- (ascii):  Serial3/1
    interfaces.ifTable.ifEntry.ifDescr.12 : DISPLAY STRING- (ascii):  Serial3/2
    interfaces.ifTable.ifEntry.ifDescr.13 : DISPLAY STRING- (ascii):  Serial3/3
    interfaces.ifTable.ifEntry.ifDescr.14 : DISPLAY STRING- (ascii):  Serial3/4
    interfaces.ifTable.ifEntry.ifDescr.15 : DISPLAY STRING- (ascii):  Serial3/5
    interfaces.ifTable.ifEntry.ifDescr.16 : DISPLAY STRING- (ascii):  Serial3/6
    interfaces.ifTable.ifEntry.ifDescr.17 : DISPLAY STRING- (ascii):  Serial3/7
    interfaces.ifTable.ifEntry.ifDescr.18 : DISPLAY STRING- (ascii):  Serial4/0
    interfaces.ifTable.ifEntry.ifDescr.19 : DISPLAY STRING- (ascii):  Serial4/1
    interfaces.ifTable.ifEntry.ifDescr.20 : DISPLAY STRING- (ascii):  Serial4/2
    interfaces.ifTable.ifEntry.ifDescr.21 : DISPLAY STRING- (ascii):  Serial4/3
    interfaces.ifTable.ifEntry.ifDescr.22 : DISPLAY STRING- (ascii):  Serial4/4
    interfaces.ifTable.ifEntry.ifDescr.23 : DISPLAY STRING- (ascii):  Serial4/5
    interfaces.ifTable.ifEntry.ifDescr.24 : DISPLAY STRING- (ascii):  Serial4/6
    interfaces.ifTable.ifEntry.ifDescr.25 : DISPLAY STRING- (ascii):  Serial4/7
    interfaces.ifTable.ifEntry.ifDescr.26 : DISPLAY STRING- (ascii):  Serial5/0
    interfaces.ifTable.ifEntry.ifDescr.27 : DISPLAY STRING- (ascii):  Serial5/1
    interfaces.ifTable.ifEntry.ifDescr.28 : DISPLAY STRING- (ascii):  Serial5/2
    interfaces.ifTable.ifEntry.ifDescr.29 : DISPLAY STRING- (ascii):  Serial5/3
    interfaces.ifTable.ifEntry.ifDescr.30 : DISPLAY STRING- (ascii):  Serial5/4
    interfaces.ifTable.ifEntry.ifDescr.31 : DISPLAY STRING- (ascii):  Serial5/5
    interfaces.ifTable.ifEntry.ifDescr.32 : DISPLAY STRING- (ascii):  Serial5/6
    interfaces.ifTable.ifEntry.ifDescr.33 : DISPLAY STRING- (ascii):  Serial5/7
    interfaces.ifTable.ifEntry.ifDescr.34 : DISPLAY STRING- (ascii):  FastEthernet8/0/0
    interfaces.ifTable.ifEntry.ifDescr.35 : DISPLAY STRING- (ascii):  FastEthernet8/0/1
    interfaces.ifTable.ifEntry.ifDescr.36 : DISPLAY STRING- (ascii):  E1 8/1/0
    interfaces.ifTable.ifEntry.ifDescr.37 : DISPLAY STRING- (ascii):  E1 8/1/1
    interfaces.ifTable.ifEntry.ifDescr.38 : DISPLAY STRING- (ascii):  E1 8/1/2
    interfaces.ifTable.ifEntry.ifDescr.39 : DISPLAY STRING- (ascii):  E1 8/1/3
    interfaces.ifTable.ifEntry.ifDescr.40 : DISPLAY STRING- (ascii):  E1 8/1/4
    interfaces.ifTable.ifEntry.ifDescr.41 : DISPLAY STRING- (ascii):  E1 8/1/5
    interfaces.ifTable.ifEntry.ifDescr.42 : DISPLAY STRING- (ascii):  E1 8/1/6
    interfaces.ifTable.ifEntry.ifDescr.43 : DISPLAY STRING- (ascii):  E1 8/1/7
    interfaces.ifTable.ifEntry.ifDescr.44 : DISPLAY STRING- (ascii):  FastEthernet9/0/0
    interfaces.ifTable.ifEntry.ifDescr.45 : DISPLAY STRING- (ascii):  FastEthernet9/0/1
    interfaces.ifTable.ifEntry.ifDescr.46 : DISPLAY STRING- (ascii):  POS9/1/0
    interfaces.ifTable.ifEntry.ifDescr.47 : DISPLAY STRING- (ascii):  E1 10/0/0
    interfaces.ifTable.ifEntry.ifDescr.48 : DISPLAY STRING- (ascii):  E1 10/0/1
    interfaces.ifTable.ifEntry.ifDescr.49 : DISPLAY STRING- (ascii):  E1 10/0/2
    interfaces.ifTable.ifEntry.ifDescr.50 : DISPLAY STRING- (ascii):  E1 10/0/3
    interfaces.ifTable.ifEntry.ifDescr.51 : DISPLAY STRING- (ascii):  E1 10/0/4
    interfaces.ifTable.ifEntry.ifDescr.52 : DISPLAY STRING- (ascii):  E1 10/0/5
    interfaces.ifTable.ifEntry.ifDescr.53 : DISPLAY STRING- (ascii):  E1 10/0/6
    interfaces.ifTable.ifEntry.ifDescr.54 : DISPLAY STRING- (ascii):  E1 10/0/7
    interfaces.ifTable.ifEntry.ifDescr.55 : DISPLAY STRING- (ascii):  POS10/1/0
    interfaces.ifTable.ifEntry.ifDescr.56 : DISPLAY STRING- (ascii):  E1 11/1/0
    interfaces.ifTable.ifEntry.ifDescr.57 : DISPLAY STRING- (ascii):  E1 11/1/1
    interfaces.ifTable.ifEntry.ifDescr.58 : DISPLAY STRING- (ascii):  E1 11/1/2
    interfaces.ifTable.ifEntry.ifDescr.59 : DISPLAY STRING- (ascii):  E1 11/1/3
    interfaces.ifTable.ifEntry.ifDescr.60 : DISPLAY STRING- (ascii):  E1 11/1/4
    interfaces.ifTable.ifEntry.ifDescr.61 : DISPLAY STRING- (ascii):  E1 11/1/5
    interfaces.ifTable.ifEntry.ifDescr.62 : DISPLAY STRING- (ascii):  E1 11/1/6
    interfaces.ifTable.ifEntry.ifDescr.63 : DISPLAY STRING- (ascii):  E1 11/1/7
    interfaces.ifTable.ifEntry.ifDescr.64 : DISPLAY STRING- (ascii):  FastEthernet12/0/0
    interfaces.ifTable.ifEntry.ifDescr.65 : DISPLAY STRING- (ascii):  FastEthernet12/0/1
    interfaces.ifTable.ifEntry.ifDescr.66 : DISPLAY STRING- (ascii):  POS12/1/0
    interfaces.ifTable.ifEntry.ifDescr.67 : DISPLAY STRING- (ascii):  Null0
    interfaces.ifTable.ifEntry.ifDescr.68 : DISPLAY STRING- (ascii):  Loopback1
    interfaces.ifTable.ifEntry.ifDescr.69 : DISPLAY STRING- (ascii):  Serial8/1/0:0
    interfaces.ifTable.ifEntry.ifDescr.70 : DISPLAY STRING- (ascii):  Serial8/1/1:0
    interfaces.ifTable.ifEntry.ifDescr.71 : DISPLAY STRING- (ascii):  Serial8/1/2:0
    interfaces.ifTable.ifEntry.ifDescr.72 : DISPLAY STRING- (ascii):  Serial8/1/3:0
    interfaces.ifTable.ifEntry.ifDescr.73 : DISPLAY STRING- (ascii):  Serial8/1/4:0
    interfaces.ifTable.ifEntry.ifDescr.74 : DISPLAY STRING- (ascii):  Serial8/1/5:0
    interfaces.ifTable.ifEntry.ifDescr.75 : DISPLAY STRING- (ascii):  Serial8/1/6:0
    interfaces.ifTable.ifEntry.ifDescr.76 : DISPLAY STRING- (ascii):  Serial8/1/7:0
    interfaces.ifTable.ifEntry.ifDescr.77 : DISPLAY STRING- (ascii):  Serial10/0/0:0
    interfaces.ifTable.ifEntry.ifDescr.78 : DISPLAY STRING- (ascii):  Serial10/0/1:0
    interfaces.ifTable.ifEntry.ifDescr.79 : DISPLAY STRING- (ascii):  Serial10/0/2:0
    interfaces.ifTable.ifEntry.ifDescr.80 : DISPLAY STRING- (ascii):  Serial10/0/3:0
    interfaces.ifTable.ifEntry.ifDescr.81 : DISPLAY STRING- (ascii):  Serial10/0/4:0
    interfaces.ifTable.ifEntry.ifDescr.82 : DISPLAY STRING- (ascii):  Serial10/0/5:0
    interfaces.ifTable.ifEntry.ifDescr.83 : DISPLAY STRING- (ascii):  Serial10/0/6:0
    interfaces.ifTable.ifEntry.ifDescr.84 : DISPLAY STRING- (ascii):  Serial10/0/7:0
    interfaces.ifTable.ifEntry.ifDescr.85 : DISPLAY STRING- (ascii):  Serial11/1/0:0
    interfaces.ifTable.ifEntry.ifDescr.86 : DISPLAY STRING- (ascii):  Serial11/1/1:0
    interfaces.ifTable.ifEntry.ifDescr.87 : DISPLAY STRING- (ascii):  Serial11/1/2:0
    interfaces.ifTable.ifEntry.ifDescr.88 : DISPLAY STRING- (ascii):  Serial11/1/3:0
    interfaces.ifTable.ifEntry.ifDescr.89 : DISPLAY STRING- (ascii):  Serial11/1/4:0
    interfaces.ifTable.ifEntry.ifDescr.90 : DISPLAY STRING- (ascii):  Serial11/1/5:0
    interfaces.ifTable.ifEntry.ifDescr.91 : DISPLAY STRING- (ascii):  Serial11/1/6:0
    interfaces.ifTable.ifEntry.ifDescr.92 : DISPLAY STRING- (ascii):  Serial11/1/7:0
    interfaces.ifTable.ifEntry.ifDescr.93 : DISPLAY STRING- (ascii):  Loopback0
    interfaces.ifTable.ifEntry.ifDescr.94 : DISPLAY STRING- (ascii):  GigabitEthernet1/0/0-mpls layer
    interfaces.ifTable.ifEntry.ifDescr.95 : DISPLAY STRING- (ascii):  POS9/1/0-mpls layer
    momsrv02:/ #

  • Pxi4461 latency from starttrigger signal to actual output

    i use a pxi4461 to output an analog signal. i've connected this analog output from the pxi4461 to one of the input channels on a pxi4472 card. on the same chassis, i'm having a pxi7831R card timestamp the 'Dev0/AO/StartTrigger' signal on the pxi4461 card. i'm also timestamping the pxi4472's 'AI Convert' signal using the same clock.
    whenever an analog output is spit out from the pxi4461, i get two timestamps, 1) the time when 'StartTrigger' signal on pxi4461 produces an impulse, and 2) the time of an impulse from the pxi4472's 'AI Convert' signal whose corresponding sample point records the start of the analog output fed to it. somehow, i always see a latency of about 1msec between these two timestamps. i'm
    anxious to find out the source of this discrepancy and would appreciate it if anyone has any specs on the following:
    1) for the pxi4461, the latency between when 'startTrigger' produces an impulse and when the analog output is actually outputed?
    2) for the pxi4472, the latency between when a signal reaches the input channel and when it is A/D sampled (so that an 'AI Convert' signal produces a pulse)?
    thanks!

    graduate student,
    The behavior that you describe with your PXI-4461 and PXI-4472 is probably not due to latency, instead it is related to the onboard filtering that is part of the DSA boards. This behavior is described in the manuals for the devices:
    PXI-4461 (p.2-8 - p.2-21)
    http://www.ni.com/pdf/manuals/373088a.pdf
    PXI-4472 (p.3-4 - p.3-10)
    http://www.ni.com/pdf/manuals/322940c.pdf
    While you will not be able to remove the delays that these filters cause, the delays are deterministic and you should be able to easily compensate for them.
    Best of luck with your application.
    Regards,
    Jed R.
    Applications Engineer
    National Instruments

  • PCI-7352 DAC Output

    I'm using the PCI-7352 to drive a Physik Instrument C809 amplifier and M230.25 linear acuator.
    I've run into some issues with the speed and following error.  I've finally been able to track down that the DAC seems to be operating around 5V as it's 0 velocity point (based on the output from 1-D interactive in NI-MAX and also in the Read DAC.vi during motions).  Basically, if the voltage is >5 then the actuator extends and likewise if <5V it retracts.  Since the DAC can output +/-10V the motor can retract faster than it can extend (extension speed is much less than the rated velocity; 0.4 mm/sec versus 1.5 mm/sec).  This is very odd as the actuator is rated to go the same speed in both directions, and in fact it does on a completely different controller (Newport ESP300).
    So, I have been in contact with Physik Instrument as I don't understand the issue.  Their response at this point is:
    "At the input of the C-809 it expects 0V for stand still, +10 V for
    maximum positive velocity and -10 V for maximum negative speed. The
    customer has to achieve this at the output of his DAC. If the customer
    doesn't achieve this voltage levels he has a problem inside of his
    software and not a problem of our hardware."
    Based on the output from 1-D interactive and the Read DAC.vi there is clearly a discrepancy.  Is it possible that the PCI-7352 is really operating around 0 as the zero velocity point, when 1-D and Read DAC seem to indicate otherwise?
    At this point it appears as though I'm going to have to manually see what the DAC is outputting, but without a breakout box I'm afraid I'm going to have to purchase a cable as a donor to slice and dice.
    Thanks for any help.
    -Derek

    Derek,
    that's strange behavior. In a closed loop system the controller's output value is defined by the characteristics of the plant. The Read DAC vi returns only the value that is sent to the DAC, but it doesn't measure the real voltage output. One chance is that there is something wrong with the DAC. E. g. I could think of an extremely high offset of -5 V or something like that. Here is an idea how to get a better understanding what's going on:
    Disconnect the C809 from the 7352.
    Configure the board for open loop stepper operation. This will unmap the DAC from the axis.
    Use Load DAC.vi to write a value directly to the DAC.
    Measure the voltage at the analog output. Depending on the cable that you are using, this might be a little bit tricky. If you can't do the measurement directly at the cable, you could ask your local NI branch if they could loan you an UMI-7764 and an SH68-C68-S cable.
    Please let me know how things are going. As the drive and the motor work fine with another controller, I don't think that the C809 has a problem. Stil I have good contacts to PI, so I could talk to them if required. 
    Another question: Have you tried the second axis on the 7352? Do you see the same issue with this axis?
    Thanks and kind regards,
    Jochen Klier
    National Instruments 

  • Display Color Management Simulated Rec709 differs from ProRes Output

    Okay. I've read the Adobe white paper on proper Color Management workflow about a dozen times now, and I'm still getting some inconsistencies in my render outputs.
    DPX footage assigned a Kodak 5218/7218 Profile
    Project Settings: ProPhoto RGB
    Linearized Working Space
    Match Legacy AE QT Gamma Adjustments
    Output Profile: HDTV (Rec. 709)
    I'm outputting to a ProRes 4444 file.
    My problem arises from using the Simulate Output>Rec709 option in AE. I cannot get the output to look like this simulated color. Isn't that supposed to work?
    I can match the output to AE when I turn off Color Management and apply a Color Profile Converter effect, but there is a shift in color when viewing Simulated Color vs. using the Color Converter Effect. Even in AE the Converter Effect looks different than Simulated Color.
    I was under the impression that the point of the Simulated Output and Display Color Management options were to avoid having to do this. Should I change my workflow and just use the Converter Effect on all my comps? Or do I have a setting wrong somewhere? Has anyone else come across a discrepancy like this?

    Interesting. I thought it might have something to do with ProRes, but my bit depth is at 32, and the shifts I'm seeing are more subdued than the pictures in that post. It looks darker (like a gamma shift) and slightly more saturated.
    I'm more interested to know why there is a difference in the simulated output vs the color profile converter. I can see the difference within AE, before exporting anything. What is simulated output doing that my profile converter isn't?

Maybe you are looking for