COMPANY   PRODUCTS   APPLICATIONS   NEWS   DOWNLOADS   SUPPORT CONTACT US  

Visual Solutions, Inc.

This Section

 


All images and information
found on this site are
© 2008 by

Visual Solutions,
Incorporated.

Tech Tips
  • MSP430 Compile Error

  • F28xx Flash Burn

  • F2812 eZdsp ADC troubles

  • Adding CAN bus to F2812 and LF2407 eZdsp

  • Install "hangs"

  • Fix error when compiling sample hold blocks

  • Access blocks wedged in inaccessible parts of screen

  • F2812 eZdsp ADC troubles

  • Label the X axis on an XY plot

  • Repair C-Code search path ("Unknown command 'cl.exe'" appears in DOS window when compiling)

  • Speeding up real-time simulation under VisSim


  • MSP430 Compile error: version' must be '2', but module has the value '3'

    You need to download the latest IAR Embedded Workbench "version 4". Unfortunately, IAR has 2 version 4's that are incompatible. This is indicated by "IAR Universal Linker V4.59T/386". VisSim requires IAR linker version V4.60 or better. You may download a free version from here: IAR Free Trial.


    Burning flash on F280x and F281x

    To create a flashable .out file, check the "Target Flash" option in the VisSim Code-Gen dialog box.
    To burn the .out to flash, Start Code Composer. Then, under "Tools" menu, select "F28XX On-Chip Flash Programmer" Put the path to your .out file in the "Please Specify COFF file to
    Program..." You can copy the .out file path from the VisSim Code-Gen/Download dialog. The other Code Composer settings should default to eZdsp values. Then click "Execute Operation"

    To boot from flash, make sure F2808 eZdsp SW1 pos 1,2&3 are ON (to left if you look at board with power on left edge)

    To debug from VisSim and use monitor buffer blocks and JTAG hotlink, you must first exit Code Composer as it won't relinquish the JTAG.


    F2812 Analog inputs give poor  results

    The eZdsp cards sold by Spectrum Digital do not connect analog VRefLo to GND. Because of this, many first time users of F2812 eZdsp's mistakenly connect the input signal to ADCINxx and GND, then wonder why the resulting reading appears as if no connection is present. To fix the problem, you must also connect P9-Pin18 to any of the P9 GND pins 1-19.

    Another source of noise in  F2812 ADC inputs can be due to an inadequate sampling interval. Though the ADC unit can be configured for sampling times below 200ns, it is not recommended. The ACD Config... option in VisSim will let you configure precisely the amount of sample time you need. This is typically between 200-400 ns depending on the input signal impedance.


    F2812 eZdsp need an external circuit to connect to CAN bus

    The eZdsp cards sold by Spectrum Digital do not have a CAN transceiver on the board. To use CAN bus, you must create your own external CAN transceiver circuit and connect to the eZdsp. Click here for TI parts and circuit information.


    Install Hangs after clicking "Next"

    There is a known conflict between the Wise installer and some other tasks. Two such tasks ares the Synaptics touchpad driver "Syntpenh.exe" and Computer Associates "UMCLIWNT.exe" under Windows 2000 and XP. To perform the install, type CTRL-ALT-DEL and click on "Task Manager", select "Processes" and click on the "syntpcnh.exe" or "UMCLIWNT.exe"  task. Click "End task". This task will restart on reboot.

    You may now complete the VisSim installation. VisSim itself has no problem with the Synaptics touchpad driver or UMCLIWNT.exe.


    Fixing C-Code compile error when using sampleHold blocks

    Some versions of VisSim/Embedded Controls Developer v4.5 give a compile error when sampleHold blocks are present in the compiled diagram. This can be easily fixed by downloading the file vsuser.h to \vissim45\vsdk\include.


    Accessing blocks wedged in inaccessible parts of screen.

    Sometimes blocks get wedged into inaccessible parts of the screen, like behind the toolbar or beyond the scrollable regions of the diagram.

    There is an easy remedy when this occurs:

    1. Move to the level of the diagram that contains the inaccessible blocks.
    2. Click the mouse on empty screen background to deselect any selected block.
    3. Hold down the SHIFT key and click the mouse to select all blocks at the current level.
    4. Release the SHIFT key.
    5. Click on any block.

    VisSim repositions all previously inaccessible blocks in the viewable region of the work area.


    Labeling the X axis on an XY plot.

    When displaying two variables in a Time Domain plot, the X axis is labeled with units of time. However, if you change the plot type to XY, there is no label on the X axis. This is because in an XY plot, VisSim automatically labels the X axis with the label for the input signal used for X coordinate generation. For example, if you activate XY Plot and choose 2 under X Axis, VisSim uses the label assigned to input signal 2.

    Thus, to display an X axis label on an XY plot:

    1. Click the right mouse button over the plot.
    2. Click on the Options tab; then choose XY Plot and select the signal to be used for X coordinate generation in the X Axis box.
    3. Click on the Labels tab; then enter a label for the input signal you chose to be used for X coordinate generation. The Trace 1 box corresponds to 1 in the X Axis parameter, the Trace 2 box corresponds to 2 in the X Axis parameter, and so on.

    Repairing your C-Code search path

    If "Unknown command 'cl.exe'" appears in the DOS window when compiling it is likely because your path variable has not been setup to find the Microsoft Visual C (MSVC) compiler file, cl.exe.

    There are two ways to solve this issue. 1) reinstall MSVC and check the box that requests to update shell variables to allow command line compiles. or 2) Edit VisSim batch files used in compiling VisSim diagrams to include a call to the MSVC batch file, vcvars32.bat. This batch file sets shell variables PATH and INCLUDE to the location of MSVC files so the compilation can work automatically.

    Microsoft changes the location of MSVC files with each new release. So depending on the version of MSVC in use, insert the appropriate line (see below) as the first line in each of the following VisSim batch files: Vsmdll32.bat, Vsmcg32.bat, and Simobjcl.bat.

    For MSVC ver. 4.0, insert:

    call C:\Msdev\bin\vcvars32.bat x86

    For MSVC ver. 5.0, insert:

    call "C:\Program Files\DevStudio\VC\bin\vcvars32.bat"

    For MSVC ver. 6.0, insert:

    call "C:\Program Files\Microsoft Visual Studio\VC98\bin\vcvars32.bat"

    If your MSVC application was installed to a different drive or directory, please make the appropriate changes to the inserted line.

     


    Speeding up real-time simulation under VisSim

    Q: I already have a seat of VisSim and I run RealtimePro on my PCI DAS 1602/16 card. Sometimes I need a faster simulation rate. The fastest I can go is around 2.5 to 4 msec, depending on the size of my simulation. I have a standard Gateway 866 with 256 SRAM and Windows 98. Can I go faster? How? If I were to get a new computer, what parameters are important for speed? How would I spec it out?
                                                                                    -Dave Winter, Sequal
     

    A: The PCI DAS 1602 can sample closed loop in VisSim at over 30KHz on a 800 MHz CPU. Thus, the bottle neck is your CPU and the VisSim model execution speed.
    There are several ways to speed up a simulation:

    1)  Buy a new system. (I like the Athlon 64 3.5GHz, but the P4's are good too). Get at least 512 meg RAM, 1044 meg would be optimal. Make sure you get DDR (Double Data Rate) RAM or RAMBUS to get full speed from the CPU. Try to get NT 4.0, Win 2000 or XP.  Avoid Windows 9x/ME, it does not schedule tasks very well.

    2) Use VisSim C-Code with PC target to compile the main portion of your diagram into a DLL. This can speed things up by a factor of 5 or more.

    3) Put portions of the computation that are only used at infrequent times (like sim startup or shutdown) into an enabled compound that is only executed under certain conditions.
     

     VISUAL SOLUTIONS, INCORPORATED - Last Updated: Tuesday April 22, 2008   MODELING THE FUTURE