NI-FGEN Problems in TestStand using IVI Calls

Hello:
I have a problem. When using a 5411 under TesStand, making IVI calls the 5411 O/P is distorted when I configure it to O/P a simple Waveform ( 1.544 MHz, 5Vp-p 0V DC Offset). The same setup using either a CVI application utilizing the function panel or the soft front panel yields a fantastic O/P. If I can not make IVI calls from TestStand then what is the use?
Help.... Very fruntrared and on a deadline
cheers...

Hello Craig -
I've quickly looked over the CVI IVIclass demos including the quick bit of Fgen code, if you run this project and monitor the output in MAX you are seeing good results? If so, yes I'd check the settings in your IVI steps in TestStand. (If you haven't seen it yet try \CVI\samples\iviclass\fgen.prj)
CVI also ships with function-by-function class help files which on my machine are located at C:\vxipnp\winnt\niivi\Help, I point this out since the demo sequence for IVI in TestStand makes a direct DLL call to set up the soft front panel as a non-interactive window... there are a few other cases where features of the driver are not accessible just by editing the step properties, but that is across the board, so again if it worked in CVI it should work here.
I'm going to attach a quick little TestStand sequence (written for TS 2.0.1f1 the current release) to this project as a way of you just loosely troubleshooting, all it will do is launch the soft front panel and use the controls to try and set up your waveform... Try it once with the simulated instrument, or just go straight to altering the FileGlobal variable to point to your logical name and tell me if you get better or worse response?
To alter the internals of the call to hardware right-click on the second step and choose 'edit Fgen'... you may want to examine your clock, the channel settings and extensions to make sure anything you configured in your code is configured here... The only thing I am still unsure of is whether you were using the default sine waves or if you were definining something arbritrary, the 5411 does have the ability to set sample counts/ waveform size /sampling rate. You may want to try setting your Arb SampleRate higher, or fall back on a quick DLL call to set some attributes manually if you can't access them any other way.
You can use the IVI operation "get Information" on a particular logical name to aquire the current/default settings of your instrument.
Below is some text I extracted from a LabVIEW example (I don't know how useful the actual code will be, but perhaps this is the cause of your undersampled data?) Jitter can also be a symptom of undersampling. I will try and check with the hardware team for you and post if I have any other ideas...
-Regards
Elaine R.
National Instruments
http://www.ni.com/ask
--Extracted from an example "Generating Segments of Larger Waveforms with the NI 5411" --
>>To set up sample counts, pass the array of sample counts you want to use to create a new arbitrary sequence. The array must have at least as many elements as the value you specify in the Sequence Length parameter. Each Sample Counts array element corresponds to a Waveform Handles array element and indicates how many samples of the given waveform to generate. Each element of the Sample Count array must be larger then the minimum waveform size and a multiple of the waveform quantum. You can obtain these values by calling niFgenQueryArbWfmCapabilities.
For the NI 5411, you can use a minimum of 256 Sample Counts, with a quantum of 8, which is the same as creating a waveform for the NI 5411. The other restriction is that you cannot use a number greater than the number of samples in the waveform.
In terms of use, the NI 5411 only generates the number of samples that are indicated by the Sample Count number regardless of how many actual samples are in the waveform array downloaded to the NI 5411.
Attachments:
fgen.seq ‏50 KB

Similar Messages

  • I want to call the DMM- SFP from Teststand using IVI

    Hi I have a Teststand 3.0 system with a NI-PXI 4070, and I want to call the DMM-SFP from Teststand using the IVI driver architecture. Unfortunatley I cannot figure out how to link the DMM-SFP to the Logical name.

    ADL,
    If you are using the TestStand IVI step types, after you have added the logical name in MAX, you can insert an IVI DMM step type. Then right-click on the step and choose "Edit IVI Dmm". You should be able to choose from the Logical Name Ring Control the logical name you created in MAX.
    If you haven't added the logical name into MAX, depending on what version of MAX you have, you can refer to Using Measurement & Automation Explorer 2.x to Configure Your IVI System or look in the IVI help that comes built into MAX 3.0.
    If you checked there already or have another question, please let us know!
    Regards,
    Shannon R.
    Applications Engineer
    Nati
    onal Instruments

  • 5112 in Teststand using IVI step

    I am trying to configure with options and set the 5112 to average but get an error. I also can not validate any of my niscope settings. The step seems to work when I execute it, and I only find out what is not supported when it fails.
    Error executing substep 'Post'.
    An exception occurred calling 'RunStep' in 'ISubstep' of 'TestStand Ivi Step Types 1.0 Type Library'
    An error occurred while executing the step.
    Component Works IVI Control Error: The IVI Configure operation failed for logical name 'niScope'.
    Details: Extension capability not supported by instrument driver. (AverageAcquisition)
    Source: TSIviStepTypes
    Please help.

    If you are running TestStand 2.0, you will need to upgrade to 2.0.1. You can get information about this at www.ni.com/upgrade. If you are currently using 2.0.1 then I need to know what version of NI-Scope and what version of the IVI engine.
    Michael

  • Know steps names of called sequence file using sequence call step type in TestStand

    Hi,
        I have a problem in accessing step names in called sequence file using "Sequence call"step type in TestStand 4.0.
    I would list out all step names of called sequence file. Is it possible to do through C#.NET? If, yes, Please explain to me in detail with possible example.
    Thank you,
    regards
    RKK

    Hey RKK,
    I want to first set your expectations for the forums.  This is not a place for people to review and rewrite your code for you; this is a place for specific and general questions.  I am not saying your question in this thread is inappropriate, because it is a good questions.  We should just not post code and ask others to fix it here.  If you are looking for this type of service we have alliance members that can help you write your TestStand Operator Interface (www.ni.com/alliance).
    As for you question about getting the sequence names for a sequence file that is not the currently running sequence file, you will need to open a reference to that sequence files and then use the API calls that I mentioned in my previous posts.  You can use the Enigine.GetSequenceFileEx function to open a reference to sequence file, and you will need to close the reference with the Engine.ReleaseSequenceFile function when you are done using it.  After you have a reference to this external Sequence File, you can use the example dll and sequence I previously sent you.  I also attach a new sequence file (SeqFile2.seq) plus an updated GetNames.seq to illustrate how to use the above mentioned functions.  I hope this helps.  Have a great day!
    Best Regards,
    Software Engineer
    Jett R
    Attachments:
    GetNamesOfSequencesInFile.zip ‏52 KB

  • Intermittent problem with TestStand calling CVI DLL calling MSCV DLL

    Sorry about cross post, but I am not sure which group is best to address
    this issue.
    Setup:
    Windows 2000 SP1
    TestStand 2.01f
    CVI 6.0
    MSVC++ 6.0 SP5
    Problem:
    I have a CVI Test Library DLL that contains test functions called by
    TestStand using the C/CVI adapter. The CVI Test Library DLL in turn makes
    several calls to another DLL written in MSVC++. I am experiencing an
    intermittent problem with one of the MSVC functions. The problem ~appears~
    to be stack related, but I am not sure. Among other things, this MSVC
    function accepts a const char * argument that is a TestStand lookup string.
    The function uses this string to access the TestStand API.
    What happens is this: Everything works fine. I then recompile the CVI DLL
    after making some mod, then run. The MSVC++ DLL asserts that the const char
    * arg passed by the CVI DLL is NULL. However, this is not the case if I
    single step through the CVI code. It has happened both with passing
    variables as the const char * argument and as hardcoded strings literals, so
    its not that I am actually passing NULL. The other argument to this
    function is the TestStand sequence context dispatch pointer (LPDISPATCH
    pobjSequenceContextDisp) and it always ~appears~ to be passed correctly.
    The problem is frustrating and hard to debug because I can not
    deterministically reproduce it. The problem ~never~ appears when I debug my
    MSVC++ DLL in Visual Studio. And it only occasionally appears otherwise.
    The problem, when it appears, always appears on the first run after
    recompiling the CVI DLL, though the problem does not happen after ~every~
    recompilation. I'd say it happens 1 in 6 times after a recompile.
    Recompiling the exact same code does not always make the problem disappear.
    If I change the CVI code (code that has nothing to do with the argument
    itself though) and recompile the problem almost always goes away. Selecting
    'Mark all for compilation' and rebuilding does not make the problem go away.
    Only tweaking the CVI code and recompiling does (usually).
    Whats more, the problem appears:
    * With the CVI DLL built as Debug or Release mode.
    * With the CVI default calling convention set to __stdcall or __cdecl.
    * With the C/CVI TestStand adapter set to run in-process or external
    instance of CVI.
    The problem appears to be some sort of stack or argument passing problem
    between CVI and MSVC, though thats just a guess based on the symptoms. I
    have quadruple checked the calling conventions of all declared functions.
    The CVI DLL functions all use TX_TEST (which resolves to __cdecl). The MSVC
    DLL functions all explicitly use __stdcall. Is there a problem with calling
    __stdcall MSVC functions from a __cdecl CVI function?
    I can find no other memory leaks or indications of memory corruption
    elsewhere in either the CVI or MSVC DLLs. Its only this one function that
    exhibits this strange 'null const char *' problem.
    Can anyone offer any ideas about what may be causing this problem? Anything
    else I should check/verify?
    Regards,
    Joe

    Silvius,
    > Although I'm not sure if any of the following are the real cause of
    > your problem, I have the following suggestions:
    Thanks for the reply. At this point any and all suggestions are welcome...
    > 1. There could be a problem with calling
    > __stdcall MSVC functions from a __cdecl CVI function. As a workaround
    > wrap the _cdecl call inside a _stdcall call that is exposed or
    > exported to TestStand or vice-versa. This can be a problem because if
    > _cdecl is used, the calling function is responsible for cleaning up
    > the stack and if _stdcall is used, the called function is responsible
    > for cleaning up the stack.
    I was under the impression that as long as everything was explicitly and
    consistently declared, you could safely mix cdecl and stdcall f
    unction
    calls. Is it bad to do this? Is this a known issue with the CVI compiler?
    I've never seen a problem with doing this under MSVC++.
    I'll try wrapping them in cdecl calls for CVI - though we have a
    depressingly large number of stdcall functions in the MSVC DLL ;-). They
    need to remain stdcall in the DLL because we also call them from Visual
    Basic.
    > 2.Don't mix Debug version of one DLL with the Release version of the
    > other DLL. I had some bad experiences doing this and both DLLs where
    > developed in MSVC. Allways use either Debug either Release versions of
    > DLLs.
    I verified that the MSVC DLLs were either ALL Debug or Release. I too have
    seen nasty problems when MSVC Debug and Release is mixed.
    One thing I had not thought of until your reply: What about mixing CVI Debug
    DLLs with MSVC Release DLLs? Have you ever seen issues with doing this?
    Thanks!
    Joe

  • Iam using Iphone4,my problem is while imake a call or when ia attend a incoming call,the screen doesnt lock,while i kept in my ear  to attend a call it automatically gets inside keypad or it on hold tab this makes me uncomfortable pls give a solution

    Iam using Iphone4,my problem is while imake a call or when ia attend a incoming call,the screen doesnt lock,while i kept in my ear  to attend a call it automatically gets inside keypad or it on hold tab this makes me uncomfortable pls give a solution

    This sometimes happens if you have a case or screen protector on the phone.  IF you have one of these remove it and see if it makes any difference

  • Who can help me using IVI powersupply in Teststand!

    Hi there,
    I'm newly in working with Teststand and IVI drivers and
    have a little simple question.
    I have a step to configure the powersupply.
    The logical name is "SamplePowerSupply", the operation
    is "configure". If I change to the "Validate IVI Configuration" form, uncheck the simulate checkbox
    and press the button "Init" I get the following errormessage:
    ....returned an error: -1073807343 ... Insufficient location information or the requested device or resource is not present in the system (-31619).
    But in MAX I see my powersupply and it seems to work correct.
    Thanks for any answer !!
    Mr.Pe

    Some IVI drivers are designed to work in simulation mode, that is, the virtual instrument can be defined in MAX but no physical instrument is necessary to use the "instrument". If you turn off the simulate checkbox on the validate dialog box, TestStand will create the instrument session without simulation and the driver will attempt to talk to a physical instrument. If no physical instrument definition is available or if the address defined for that virtual instrument is incorrect, the above error can occur.
    Scott Richardson (NI)
    Scott Richardson
    National Instruments

  • Agilent 34980A simulation using IVI-drivers in Teststand?

    Hello! I am unable to simulate 34980A in TestStand and here are some results based on testing:
    Agilent 34980A is linked to logical name SampleDmm. Simulate With: Specific Driver.
    IviStepTypes.seq used with only DMM and Switch steps.
    Using IviDMM IVI-C causes runtime-error in Ivi DMM Configure Single Point: Component Works IVI Control Error: The IVI Configure operation failed for logical name 'SampleDmm'. Details: Extension capability not supported by instrument driver.  (Base)
    Using IviDMM IVI-COM causes runtime-error in Ivi DMM Read Single Point: Component Works IVI Control Error: The IVI Read operation failed for logical name 'SampleDmm'. Details: Attribute ID not recognized. [IVI Error Code:  BFFA000C] Source: TSIviStepTypes
    Skipping Ivi DMM SFP -step removes that error but next one waits in Ivi DMM Configure Multi Point: Component Works IVI Control Error: The IVI Configure operation failed for logical name 'SampleDmm'. Details: Attribute or property not supported. [IVI Error Code:  BFFA0012] Source: TSIviStepTypes
    Skipping multi point steps helps until Ivi Switch Connect where another error hits: Component Works IVI Control Error: The Connect operation failed for logical name 'SampleDmm'. Details: No path was found between the two channels. [IVI Error Code:  BFFA2011] Source: TSIviStepTypes
    I find some similarities in forum post that involves HP 34401A and IVI .
    According to IVI-C Class Driver Support for IVI-COM Specific Drivers the fault might be in 64 bit system (the note in the end). Is this the case? I can't use IVI-COM-drivers in 64bit system?
    Example's default DMM Hewlett-Packard 34401A Digital Multimeter simulation works perfectly in unmodified example(it has IVI-C). It even shows simulated numbers in the SFP which is zero all the time with Agilent.
    Has anyone succeeded to simulate 34980A properly in TestStand? Any knowledge about how to solve this thing? Any help is welcome. Thank you.
    Setup:
    -Teststand 5.1
    -Windows 7 64bit
    -IVI shared components 2.2.1
    -Visa shared components 1.5 64bit
    -Agilent IO libraries suite 16.3 Update 1
    -Agilent 34980A IVI Driver 1.5.3
    -MAX/Agilent 34980A published APIs:
        -IviDmm 4.1 IVI-COM (IVI-C tried with less success)
        -IviSwtch 4.0 IVI-C & IVI-COM

    Some IVI drivers are designed to work in simulation mode, that is, the virtual instrument can be defined in MAX but no physical instrument is necessary to use the "instrument". If you turn off the simulate checkbox on the validate dialog box, TestStand will create the instrument session without simulation and the driver will attempt to talk to a physical instrument. If no physical instrument definition is available or if the address defined for that virtual instrument is incorrect, the above error can occur.
    Scott Richardson (NI)
    Scott Richardson
    National Instruments

  • 1. The procedure called by CUSTOM.pll causes the problem when we use f60gen

    When CUSTOM.pll contains a call to a package that in turn calls a remote package, the CUSTOM.pll compile hangs forever.
    1. The procedure called by CUSTOM.pll causes the problem when we use f60gen. Though same procedure compiles successfully using "alter procedure compile" command.
    2. We have observed the problem happens due to synonym present on the remote database(db link).
    It doesn’t work if you are calling SYNONYM on remote database. It works, for calls to tables or procedures or packages in remote database if that object is OWNED DIRECTLY by the account to which dblink is connecting to.
    select object_name, object_type from user_objects@NH_SCM_ICE.DB.ATT.COM ;
    OBJECT_NAME OBJECT_TYPE
    FA_LOCATIONS SYNONYM
    FND_FLEX_VALUES SYNONYM

    The database link is created under the APPS user in the local database but connects to a different user (SWCS_ICE_SUPCHAIN) in the remote database.
    The user in the remote database does not own any objects. It only has synonyms to objects owned by apps and others.
    Incidentally, the hang also happens when trying to describe the remote package from the application tier (8.0.6.3 sqlplus) but the describe works fine from the DB tier (10gR2 sqlplus).

  • Problems in using Ivi driver ke230y in "IviDCPwr Measure [MSR].vi"

    Hello all,
            I have a problem in using IVI driver (ke230y) to control keithley2303 powersupply with LABVIEW 2013.
     After I initialize and config ke2303 well and run to  "IviDCPwr Measure [MSR].vi", it ocurrs errors. While lasting about 15 seconds and then reports errors as attached:
    The code (attached) when I test with other powersupplies such as agilent66309d and keithley2306(with ivi driver ke230x), it runs well.
    So I've no idear about this problem with keithley2303 powersupply, can you guys ever meet this problem and may reply for me to fix it.
    thank you for your reading and help!
    best wishes,
    Phil
    Solved!
    Go to Solution.
    Attachments:
    error.jpg ‏36 KB
    code.jpg ‏43 KB

    I don't have the any driver's source code (such as ividcpwr.dll source code), how can I modify the specific driver through labwindows.
    Follow your advice I use I/O trace to get trace as follows:
    1 IviDCPwr_InitWithOptions ("ke2303", VI_FALSE, VI_TRUE, "", 0x0C913064) VI_SUCCESS 14:45:10.675
    2 IviDCPwr_ConfigureVoltageLevel (ke2303, "CHANNEL1", 3.8) VI_SUCCESS 14:45:11.405
    3 IviDCPwr_ConfigureCurrentLimit (ke2303, "CHANNEL1", 0, 3) VI_SUCCESS 14:45:12.104
    4 IviDCPwr_ConfigureOutputEnabled (ke2303, "CHANNEL1", VI_TRUE) VI_SUCCESS 14:45:12.824
    5 IviDCPwr_Measure (ke2303, "CHANNEL1", 1, 0) VI_ERROR_TMO 14:45:16.207
    6 IviDCPwr_GetError (ke2303, -1073807339, 0, "") 0x00000037 14:45:32.991
    7 IviDCPwr_GetError (ke2303, -1073807339, 55, "Primary Error: ..................") VI_SUCCESS 14:45:32.991
    8 IviDCPwr_close (ke2303) VI_SUCCESS 14:45:33.847
    I cannot see any GPIB command in the trace but some IviDCPwr functions.
    Besides, if I know any bug (eg. some wrong GPIB command) in ividcpwr.dll, how can I modify it before I get it's source code.
    Pls teach me anytime in your conveneince.
    thanks!

  • Dear Apple,  I have a problem when I use "iTunes Gift Card" to shop in a game which is called "Puzzle

    Dear Apple,
    I have a problem when I use "iTunes Gift Card" to shop in a game which is called "Puzzle & Dragons"(パズル&ドラゴンズ). I cannot buy anything in the game and the system shows the following message: "please contact itunes support to complete this transaction".
    Could you help me to solve the problem? Thank you very much!
    Best Regards,
    tat

    Click here and request assistance.
    (79862)

  • IVI FGEN problems with HP 33120A

    Hi,
    I'm trying to control a HP 33120A using IVI through CVI. The basics work
    well, but when I try to do arbitrary waveforms of amplitude modulation if
    get errors.
    I have include the code snipets with error handling removed for brevity.
    Unfortunately I can not find a sample with either of these two cases, and
    the error codes do not shed any lights. I have looked at the IVI.h file and
    documentation to try and get more insight but I'm hitting a brick wall.
    I would appreciate any examples/solution even partial.
    Cheers
    Peter
    // Snipet of code for ARG gen.
    iError = IviFgen_AbortGeneration (instHndARBGen);
    iError = IviFgen_ConfigureOutputMode(instHndARBGen, IVIFGEN_VAL_OUTPUT_ARB);
    iError = IviFgen_ClearArbWaveform (ins
    tHndARBGen,
    IVIFGEN_VAL_ALL_WAVEFORMS);
    // returns an error of 0xBFFA2006
    iError = IviFgen_CreateArbWaveform (instHndARBGen, NPoints, Values,
    &hWaveForm);
    iError = IviFgen_ConfigureArbWaveform(instHndARBGen, "1", hWaveForm,
    Amplitude, 0.0);
    iError = IviFgen_InitiateGeneration(instHndARBGen);
    iError = IviFgen_EnableOutput(instHndARBGen, "1");
    // Snipet of code for Aplitude Modulation
    iError = IviFgen_AbortGeneration (instHndARBGen);
    iError = IviFgen_ConfigureOutputMode (instHndARBGen,
    IVIFGEN_VAL_OUTPUT_FUNC);
    // returns an error of 0xBFFA0010
    iError = IviFgen_EnableAM (instHndARBGen, "1", IVIFGEN_VAL_INTERNAL);
    iError = IviFgen_ConfigureAMInternal (instHndARBGen, Depth,
    IVIFGEN_VAL_WFM_SQUARE, FrequencyModulation);
    iError = IviFgen_InitiateGeneration (instHndARBGen);
    iError = IviFgen_EnableOutput (instHndARBGen, "1");

    Hi,
    I guess the two instruments have a similar command set. I am also guessing that you are using the standard VISA type instrument driver for the 33120A and not the IVI.
    You will have to switch of the Query because the query string returned will have 33120A related text. This should get you passed the Initialisation.
    Have you not tried Agilent web site for a HP1441A driver?
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • Why do I get error -17500 when calling a batch file using the call executable step type?

    I am calling a batch file using the call executable step type. If the path to the batch file contains a space I get error -17500 and a message stating there was an error in "Post". For example the path to the batch file is "c:\TestWin\Test Files\...\Program.bat" When I run this I get the above mentioned error, however if I change my directory structure so the path is now "c:\TestWin\TestFiles\...\Program.bat" it runs fine. I use the browse feature to find my batch file so it is not me typing in a path incorrectly. I have removed the batch file and I get a different error stating that it couldn't find the file so it appears that for my error it can find the file but can't run it. I am
    sure that this has something to do with the fact that batch files are written in DOS but really don't want to resort to changing my directory structure on all my test stations. Is there any way to fix this problem so I can leave a space in my path?

    It appears I have figured it out. This was on another computer so I was unaware of how they used their computer. I like you got it to work in the temp directory and in fact got the program.bat file to work as long as I put it under the temp directory, but when I switched out to my TestWin directory it wouldn't work, so I removed everything from the directory except the batch file it self and it work. What I found out after adding files in one at a time is that the person had a file called "Test" with no file extension in there "c:\TestWin\" directory. Removing this file made it work. Putting the file back broke it. So it appeares that when teststand was running it followed the path saw a space and attempted to grab the "Test" file instead of bro
    wsing into the "Test Files" directory. If you create a file in your temp directory called "temp" with no file extension you will see the same problem. Thank you for your help.

  • FGen sweep function TestStand

    I have a NI PXI 5402 and wish to use its 'sweep' function in TestStand. I can open the NI FGEN Soft Panel on its own and can use the sweep function manually. However when opening the ivi FGen function in TestStand it has some functions in it but does not have the sweep function. How can I utilise the sweep function from TestStand?

    Hi Steve,
    It should be in the latest IVI Compliance Package
    Just use this link:
    http://joule.ni.com/nidu/cds/view/p/id/1313/lang/de (german)
    http://joule.ni.com/nidu/cds/view/p/id/1313
    Juergen
    =s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=

  • I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build.  The same call works fine when running on the device

    I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device (iPhone) using debug build. When running with a release build, the result handler is never called (nor is the fault handler called). Viewing the BlazeDS logs in debug mode, the call is received and send back with data. I've narrowed it down to what seems to be a data size issue.
    I have targeted one specific data call that returns in the String value a string length of 44kb, which fails in the release build (result or fault handler never called), but the result handler is called as expected in debug build. When I do not populate the String value (in server side Java code) on the object (just set it empty string), the result handler is then called, and the object is returned (release build).
    The custom object being returned in the call is a very a simple object, with getters/setters for simple types boolean, int, String, and one org.23c.dom.Document type. This same object type is used on other other RemoteObject calls (different data) and works fine (release and debug builds). I originally was returning as a Document, but, just to make sure this wasn't the problem, changed the value to be returned to a String, just to rule out XML/Dom issues in serialization.
    I don't understand 1) why the release build vs. debug build behavior is different for a RemoteObject call, 2) why the calls work in debug build when sending over a somewhat large (but, not unreasonable) amount of data in a String object, but not in release build.
    I have't tried to find out exactly where the failure point in size is, but, not sure that's even relevant, since 44kb isn't an unreasonable size to expect.
    By turning on the Debug mode in BlazeDS, I can see the object and it's attributes being serialized and everything looks good there. The calls are received and processed appropriately in BlazeDS for both debug and release build testing.
    Anyone have an idea on other things to try to debug/resolve this?
    Platform testing is BlazeDS 4, Flashbuilder 4.7, Websphere 8 server, iPhone (iOS 7.1.2). Tried using multiple Flex SDK's 4.12 to the latest 4.13, with no change in behavior.
    Thanks!

    After a week's worth of debugging, I found the issue.
    The Java type returned from the call was defined as ArrayList.  Changing it to List resolved the problem.
    I'm not sure why ArrayList isn't a valid return type, I've been looking at the Adobe docs, and still can't see why this isn't valid.  And, why it works in Debug mode and not in Release build is even stranger.  Maybe someone can shed some light on the logic here to me.

Maybe you are looking for