GETTING STARTED GUIDE

Transcription

1 GETTING STARTED GUIDE 3D SUPERVISION SYSTEMS January 15, 2013

2 Authors PAOLO RASPA RICCARDO DONNINI 3D SUPERVISION SYSTEMS Acknowledgements This product was developed in collaboration with Prof. David Scaradozzi and supported by LabMACS, Laboratory of Modeling, Analysis and Control of Dynamical Systems, Department of Information Engineering, Universita Politecnica delle Marche, Ancona (IT). Legal Informations Any information contained in this publication regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. 3D SuperVision Systems makes no representations or warranties of any kind whether expressed or implied, written or oral, statutory or otherwise, related to the information, including, but not limited to its condition, quality, performance, merchantability or fitness for purpose. 3D SuperVision Systems disclaims all liability arising from this information and its use. Trademarks The Microchip name and logo, the Microchip logo, MPLAB R, PIC R, PIC32 R logos are registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries. MPLAB R Certified logo is trademark of Microchip Technology Incorporated in the U.S.A. and other countries. National Instruments, NI, ni.com, and LabVIEW are trademarks of National Instruments Corporation. Refer to the Terms of Use section on for more information about National Instruments. For patents covering National Instruments products/technology, refer to the National Instruments Patent Notice at All other trademarks mentioned herein are property of their respective companies. ksupport@3d-svs.com mwww.3d-svs.com/support 1

3 Contents 1 Introduction Supported Hardware Software Requirements Product description Dmicro Toolkit Palette Description I/O Palette Timing Palette Analog Digital Converter Pulse Width Modulation Led and Switch Serial communication Ethernet communication String USB External Interrupts Dmicro Compiler Description Create your LabVIEW code Microcontroller initialization Main Program Flow Communication with other devices (Optional) Convert your LabVIEW program to C code Build your program and get a PIC32 compliant firmware Import and run the firmware using MPLAB Preliminaries Import the Firmware in MPLAB Download the code PC - PIC32 Ethernet communication Supported LabVIEW palettes

4 Chapter 1 Introduction The 3Dmicro Toolkit is a NI Labview Add-on to perform the following tasks: Rapid prototyping of embedded software for 32-bit PIC R microcontroller using LabVIEW graphical programming paradigm Developing and building PIC32 R compliant firmware using VIs from 3Dmicro Palette. Interfacing with 32-bit PIC R MCUs using either serial and/or Ethernet communication. Remote monitoring and control of complex systems exploiting the PIC32 R I/O and communication functionalities Interfacing the PIC32 R with external sensors and actuators This document is a guide for the software 3Dmicro Toolkit and contains the followings: Presentation of 3Dmicro Toolkit components and features Step by step guide to develop your LabVIEW code and build it to obtain 32-bit PIC R compliant.hex firmware Step by step guide to download and run.hex firmware using the MPLAB R IDE 1.1 Supported Hardware 3Dmicro Toolkit supports the following Microchip devices: PIC32MX360F512L an High-Performance, General Purpose and USB 32bit Flash Microcontroller. Datasheet is available at ww1.microchip.com/downloads/en/devicedoc/61143g.pdf PIC32MX795F512L an High-Performance, USB, CAN and Ethernet 32bit Flash Microcontroller. Datasheet is available at ww1.microchip.com/downloads/en/devicedoc/61156g.pdf 3Dmicro Toolkit moreover supports the following Microchip Starter Kits, which are equipped with the Microchip On-Board Microcontrollers.as in Table 1.1: The PIC32 R family is listed below, supported devices are marked in red.

5 Introduction Table 1.1: Microchip Demo Boards Microchip Microchip Microchip Starter Kit USB Starter Kit Ethernet Starter Kit Equipped with Equipped with Equipped with PIC32MX360F512L PIC32MX795F512L PIC32MX795F512L 1.2 Software Requirements The following software are supported and must be installed in order to use the 3Dmicro Toolkit software: mwww.3d-svs.com/support 4

6 Introduction Operating Systems Microsoft Windows XP 32-bit Microsoft Windows 7 32-bit/ 64-bit NI LabVIEW Software LabVIEW bit 1 C Generator Internet Toolkit Microchip Software PIC32 R Starter MPLAB R IDE v8.41 Microchip Application Kit Software v2.0a Libraries v * 1 Only 32-bit versions are compatible with the 3Dmicro Toolkit 2 Required for the 3Dmicro Toolkit to work. If NI LabVIEW C Generator is not included in your LabVIEW installation, an evaluation copy can be downloaded from p/id/3143/lang/en. NI may require the registration of a NI account in order to download this software. 3 Required to establish an Ethernet connection with an Ethernet-enabled 32-bit PIC R microcontroller. If NI LabVIEW Internet Toolkit is not included in your Labview installation, it can be downloaded from NI may require the registration of a NI account in order to download this software. ksupport@3d-svs.com mwww.3d-svs.com/support 5

7 Chapter 2 Product description 3Dmicro Toolkit is a software to create high level microcontroller programs using LabVIEW dataflow programming language and to convert them into compact machine code for storage in the PIC32 microcontroller s memory. The 3Dmicro Toolkit software is made up of three main components: 3Dmicro Palette A LabVIEW palette with 32-bit PIC R microcontrollers specific VIs to create microcontroller programs 3Dmicro Compiler A standalone compiler for 32-bit PIC R microcontrollers, to convert programs into compact machine code for storage in the PIC32 microcontroller s memory. 3Dmicro Toolkit Examples Preconfigured LabVIEW projects to start programming your PIC32 R applications 2.1 3Dmicro Toolkit Palette Description NI LabVIEW Functions palette are collection of Virtual Instrumentation (VIs) and Functions used to build block diagrams. Each VI provides LabVIEW high-level functions to write your LabVIEW program. Functions do not have front panels or block diagrams but do have connector panes. 3Dmicro Toolkit adds a function palette, called 3Dmicro Palette, to the ones shipped with LabVIEW. Built-in VIs within the 3Dmicro Palette provides tools needed to develop embedded projects on PIC32 microcontrollers. Each VI provides a specific function of the microcontroller. VIs from the 3Dmicro palette can be connected to other VIs of the LabVIEW palette in the block diagrams to build an embedded application to be run on the microcontroller. VIs can be opened and modified or used as they are as subvis in your block diagram to reduce the embedded programming development time. Inputs to the VIs can be configured using sliding menus, to avoid configuration errors. Detailed descriptions are available within LabVIEW Context Help, which can be activated using the CTRL+H shortcut. Appendix.1 contains a complete list of Supported and Unsupported LabVIEW VIs. The 3Dmicro Palette can be accessed right-clicking in an empty space of the Block Diagram. Then select 3Dmicro Toolkit PIC32MX. The 3Dmicro Toolkit library is shown here as a LabVIEW palette.

8 Product description I/O Palette The PIC32MX795F512L and the PIC32MX360F512L provides 7 ports, ordered by letters, from A to G, with 8 pins available for each port as generic I/O pins. 3Dmicro Palette provides VIs to VIs are used to initialize, read and set the logic state of common I/O ports or single pins. IOPORT Init provides primitives to configure single I/O pins of a port or an entire port as digital input or output ports. Please remember that each microcontroller pin is shared for different purposes (e.g. could be a A/D pin, a serial TX as well as a generic I/O pin). Setting a pin or an entire port as a generic I/O could prevent the micro from behaving as expected. Therefore be careful during initialization and refer to the MCUs Datasheet linked in Section 1.1 for more information. IOPORT Read VI can be used to read the logic level of an input port. Port must be configured as input port using IOPORT Init VI. ksupport@3d-svs.com mwww.3d-svs.com/support 7

9 Product description IOPORT BIT Read VI can be used to read the logic level of an input pin. Pin must be configured as input pin using IOPORT Init VI. IOPORT BIT Set VI can be used to set the logic level of an output pin or of an entire output port. Pin (port) must be configured as output pin (port) using IOPORT Init VI Timing Palette 3Dmicro Toolkit provides support to timing functions of the microcontroller. TICK and TOCK VIs can be used to count the time period between a TICK and TOCK execution. E.g. VIs can be used to coordinate code execution in programming loops. DelayMS VI can be used to pause the microcontroller for a specific length of time. ksupport@3d-svs.com mwww.3d-svs.com/support 8

10 Product description Analog Digital Converter The microcontrollers of the PIC32 family provides up to 6 analog inputs related to a 10-bit Analog/Digital converter (ADC) The following VIs are used to setup and read analog signals from the ADC. AN Init configure the Analog Digital converter, setting up the Analog Input Mux AN Read is used to read analog input data, from the Analog Digital Converter. The function output is the float value of the voltage read on the analog pin Pulse Width Modulation VIs to set Pulse Width Modulation (PWM) outputs (e.g. drive a servo motor) follow. ksupport@3d-svs.com mwww.3d-svs.com/support 9

11 Product description Led and Switch Microchip Demo Boards provides Leds and switch buttons connected to the PIC32 R I/O ports. The following VIs enable, toggle LEDs and read Switches states. When not used with Microchip Demo Boards, listed in 1.1, leds are initialized as generic outputs and switch buttons are initialized as generic inputs. LED Init initializes one of the leds of the Starter Kit or all the leds, depending on the input parameter ksupport@3d-svs.com mwww.3d-svs.com/support 10

12 Product description Serial communication Serial communication is provided by the following VIs: UART Init.vi initializes a Serial Communication using the UART protocol. Using the input parameters, the serial port, the BAUD rate, parity bit configuration and the number of stop bits can be configured. ksupport@3d-svs.com mwww.3d-svs.com/support 11

13 Product description The UART Receive string.vi receive strings using serial communication. Serial header and terminator character can be manually configured, using the input parameters, in order to parse a message using the protocol of choice UART Send string.vi sends strings using serial communication Ethernet communication These function VIs can be used to setup a Telnet communication with an host device. Ethernet communication is supported only by PIC32MX795F512L, see 1.1. The function VI ETH Init configures the registers of the microcontroller to setup an Ethernet communication using Telnet protocol. This VI needs a static IP address and a subnet mask as inputs. That IP address must be written when required when launching the Ethernet Monitor interface. ksupport@3d-svs.com mwww.3d-svs.com/support 12

14 Product description The function VIs ETH Receive variable and ETH Receive string are used to receive respectively a float number and a string via Telnet. The function VIs ETH Send variable and ETH Send string are used to send respectively a float number and a string via Telnet. A boolean output variable is set to true whenever a new string is received. To get an example on how to use communication function VIs refer to the Ethernet Communication Example and related guide which are stored in the folder C:\USER\Documents\3Dmicro Toolkit\Ethernet Communication Example String String manipulation is provided by the followings VIs. These VIs are a clone of the VIs already present in the LabVIEW string palette, but they already realized in ANSI C-Code to reduce software overhead. The following function VIs provides conversion from string to different numeric format. For other string manipulation VIs refer to LabVIEW string palette within LabVIEW Programming Palette ksupport@3d-svs.com mwww.3d-svs.com/support 13

15 Product description The following function VIs provides conversion from different numeric format to string. mwww.3d-svs.com/support 14

16 Product description USB This function VIs can be used to store data on an external USB drive. They can be used as is on the PIC32 Starter Kits and other versions of the PIC32 Starter Kits boards. The function VI USB Init configure the register of the microcontroller to setup an USB device. The initialization blocks the program until an USB device is plugged in the board. USB File Open can be used to open a file, chosen using the input string with a write, read, append option. The function VI gives back a File RefNum which can be used as an handler for successive manipulations. USB File Close is used to close a file by its File RefNum ksupport@3d-svs.com mwww.3d-svs.com/support 15

17 Product description USB File Read and USB File Write are used to read (write to) a file which handler is a File RefNum created with USB File Open. Different options can chosen as input parameters, as described in the following figures. To get an example on how to use The USB function VIs refer to the USB Example and related guide which are stored in the folder C:\USER\Documents\3Dmicro Toolkit\USB Example External Interrupts An external interrupt event is a digital signal change on an input port which can be detected by the microcontroller to jump from the linear code execution to the execution of another part of the code specified in a different function. The 3Dmicro palette provides an Interrupts palette to initialize PIC32 R microcontroller registers to configure Interrupts events, depending on different signal change events and to handle this events. To get an example on how to use the Interrupt function VIs refer to the Interrupts Example and related guide which are stored in the folder C:\USER\Documents\3Dmicro Toolkit\Interrupts Example The INT Init 795.vi for the PIC32MX795F512L (in case the user would program the PIC32MX360F512L, the initialization function would be INT Init 360.vi) configure external interrupt condition to trigger the interrupt event. This function needs as inputs the number of the external interrupt to configure (from 0 to 4), the interrupt priority (from 0 to 7), the trigger event (rising or falling edge of the digital signal on the input pin) and the enable/disable flag. Please note that only one external interrupt (INT0) is available for the PIC32 Ethernet Starter Kit, because the input pins of other interrupts are used for other functions. ksupport@3d-svs.com mwww.3d-svs.com/support 16

18 Product description INT Clear Flag 795.vi for the PIC32MX795F512L (in case the user would program the PIC32MX360F512L, the clear function would be INT Clear Flag 360.vi) are used to clear external interrupt flag to allow the microcontroller to handle another interrupt event mwww.3d-svs.com/support 17

19 Product description 2.2 3Dmicro Compiler Description The 3Dmicro Compiler is a stand-alone program which can be used to compile 3Dmicro Toolkit projects, developed using the 3Dmicro Palette. The output of the 3Dmicro Compiler is a firmware (HEX file format) ready to be downloaded to the 32-bit PIC R microcontroller The 3Dmicro Compiler can be either summoned within LabVIEW from Tools 3Dmicro Toolkit Compiler Or called as a standalone program from Start menu All Programs 3Dmicro Toolkit 3Dmicro Compiler The first time 3Dmicro Compiler is executed a pop up window request for product activation. Software activation is requested only to use the 3Dmicro Compiler. 3Dmicro Palettes and other components of 3Dmicro Toolkit do not need any activation or registration. ksupport@3d-svs.com mwww.3d-svs.com/support 18

20 Product description Following the instruction enable an Internet connection and click on Free Evaluation to proceed with 3Dmicro Compiler online activation. In case an internet connection is not available at the moment, another pop up window will guide the user through the offline activation. Send an to with subject WebActivation and the reply will enclose a certificate file to use for the activation. The following pop up window will be shown every time the 3Dmico Compiler is launched during the evaluation period. ksupport@3d-svs.com mwww.3d-svs.com/support 19

21 Product description The pop up window is removed after purchase and registration of the product. To proceed to purchase click on Purchase or click on Continue Evaluation to continue to 3Dmicro Compiler till the evaluation period expires. In case an internet connection is not available at the moment, another pop up window will guide the user through the offline registration, to do after purchasing the product online. Send an to with subject WebRegistration and the reply will enclose a certificate file to use for the registration The top sliding menu of the 3Dmicro Compiler interface can be used to select the device. The user can choose among: 1. PIC32 Development Boards (a) PIC32 Starter Kit (b) PIC32 USB Starter Kit II (c) PIC32 Ethernet Starter Kit 2. PIC32 Microcontrollers (a) PIC32MX795F512L (b) PIC32MX360F512L For PIC32 Microcontrollers target some parameters (oscillator frequency) can be chosen via a pop up menu. ksupport@3d-svs.com mwww.3d-svs.com/support 20

22 Product description The first time (and each time they change) the 3Dmicro Compiler runs, a pop up menu will prompt the user for the location of Microchip drivers and application libraries. Refer to the Appendix A of the 3Dmicro Toolkit Installation Guide for more information about Microchip drivers and application libraries installation and location. Selecting the path of a 3Dmicro Toolkit Project, the 3Dmicro Compiler can build code to a PIC32 R compliant.hex firmware to be downloaded to the microcontroller, using MPLAB R. Please see Sections 3.1, 3.3 and 3.4 for more details. ksupport@3d-svs.com mwww.3d-svs.com/support 21

23 Chapter 3 This section shows how to use 3Dmicro Toolkit to run an example project. The steps are briefly summarized here: 1. Use a 3Dmicro Toolkit project to create your LabVIEW program 2. Convert your LabVIEW program to C code using LabVIEW C Generator 3. Use 3Dmicro Compiler to build your program to PIC32 R compliant.hex firmware 4. Use MPLAB R to import the.hex firmware to a 32-bit PIC R microcontroller and run it 3.1 Create your LabVIEW code Examples of already developed code are available in each project folder in C:\USER\Documents\3Dmicro Toolkit\ shows a series of example projects you can use to start programming your 32-bit PIC R microcontroller. You can start from one of these examples to start your project. In this section, starting from a simple Example project, you can learn how to modify an example to your need and find some tricks that you should consider when you develop your Labview code to be run to the microcontroller. Each LabVIEW project, which is a file with the name of the project and extension.lvproj must be stored in its own folder, with depending VIs contained in the same folder. The.lvproj LabVIEW project must contain the main LV.vi, which is the main program which will be executed on the microcontroller. Please note that the main LV.vi will form the main loop of the program on the microcontroller and that NO WHILE LOOPS are needed to wrap the code executed in the main LV.vi Other SubVIs you want to use in your main LV.vi must be added to your project

24 Other VIs and files in Ethernet monitor folder of your project cannot be modified, they are used for communication purposes. The main program must be embedded in a time frame. Other time frames can be embedded, along with case and loop structures. Concurrent loop are not allowed, because the PIC R microcontroller cannot support parallel code execution. Remember that the structure of each 3Dmicro Toolkit program is made up of three phases: 1. Microcontroller initialization 2. Main Program Flow 3. Communication with other devices (Optional) Microcontroller initialization The first step is necessarily separated from the two others. The initialization frame can be embedded in its own frame, each initialization follows each another. Initialization VIs, described in Section 2.1, should be used here, each one in its own time slot. As an example we can add Serial initialization in a new time slot Main Program Flow This section must follow the initialization. Here it is allowed to use all the existing LabVIEW code, if it does comprise only supported VIs, according to Section.1 along with VI s from the 3Dmicro Palette described in Section 2.1. As an example here we can use process simple numeric data using the Array and Numeric VIs from the LabVIEW Programming palette. A custom subvi can also be added. ksupport@3d-svs.com mwww.3d-svs.com/support 23

25 Please note that array and strings variable cannot be allocated as LabVIEW local variables. You can also merge some C code, using theinline C nodes, made available by the LabVIEW C Generator Toolkit Communication with other devices (Optional) This optional section can follow or be merged within the main program flow. As an example we can send the sum of two integer numbers to the PC using serial communication. First we need to convert the number to a decimal string using the 3Dmicro Toolkit String palette described in Section 2.1.8, then the UART You can use all the the VIs described in Sections and Refer to the Interrupts Example, USB Example and Ethernet Communication Example stored in C:\USER\Documents\3Dmicro Toolkit folder for more details on a practical implementation of programs to communicate with external local or remote device or PC. Refer to Section 3.5 and LabVIEW documentation for an example on how to connect and interface with the microcontroller. 3.2 Convert your LabVIEW program to C code To build C code strarting from VI, go back to the Project Explorer window, right-click on Build Specification, then left-click on New C Code Generation (*.c, *.h) ksupport@3d-svs.com mwww.3d-svs.com/support 24

26 In My C Code Generation Properties window you can configure the building process. Check the Build specification name and the Destination directory N.B. DON T CHANGE THE DEFAULT BUILD SPECIFICATION NAME My C Code Generation Click on Source Files, then on main LV.vi and on the to export the VI ksupport@3d-svs.com mwww.3d-svs.com/support 25

27 In the following window just click on the OK button. Then click on Build to make the LabVIEW C Generator create C code Click on Done when the building procedure ends. ksupport@3d-svs.com mwww.3d-svs.com/support 26

28 3.3 Build your program and get a PIC32 compliant firmware This part of the document will guide you through the steps to compile the generated C code to PIC32 R compliant firmware using the 3Dmicro Compiler application. In order to build the generated C code you have to go back to the Project Explorer window, click on Tools in the menubar, then 3Dmicro Toolkit Compiler... Remember that a 3Dmicro Compiler launcher is also available at Start Menu Programs 3Dmicro Toolkit 3Dmicro Compiler The PIC32 R 3Dmicro Compiler interface prompts you 2 questions: ksupport@3d-svs.com mwww.3d-svs.com/support 27

29 1. Select the target device, among the list of supported devices in Section 1.1 and Select the path of the 3Dmicro Toolkit project to convert (e.g. C:\User\[User Name] \Documents\3Dmicro Toolkit example project ) Only the first time or whenever this addresses change you are prompted this other 2 questions: 1. Select the Microchip Starter Kit installation folder. 2. Select the Microchip Solution folder. N.B. Microchip Solutions path insertion is optional in case PIC32MX360F512L (Starter Kit) is being used. ksupport@3d-svs.com mwww.3d-svs.com/support 28

30 The program checks the paths you selected. When the all the paths are correct click on the Compile button to proceed with the compilation. Compilation times decrease considerably after first compilation. In case of some errors about the project folder location or missing dependencies an error message is prompted to the user. mwww.3d-svs.com/support 29

31 You can stop the compilation any time clicking on STOP COMPILATION. In case of errors in the main LV program built, a compilation log is shown in the text box, that you can copy and paste on a text editor and use it for debugging. If you correctly followed this guide, the example should compile without any error, therefore a new Microchip PIC32 R compliant firmware is created as an.hex file. The next tab shows the firmware filename, containing the timestamp, and the folder where the firmware can be found. ksupport@3d-svs.com mwww.3d-svs.com/support 30

32 A small selection box asks whether you want to open a new istance of the MPLAB R IDE or not. Left it unselected if you have already opened the IDE. Then click on FINISH to close this program and continue. 3.4 Import and run the firmware using MPLAB When MPLAB R IDE is opened you must ensure PIC R microcontroller is not connected to the PC. To do that click on Debugger Select Tool None Preliminaries Check the device targeted by MPLAB R. E.g. In the figure below PIC32MX360F512L is marked. If the device identifier is not the one, which is being used, change it clicking on Configure Select Device... ksupport@3d-svs.com mwww.3d-svs.com/support 31

33 Then select the right device from the list. mwww.3d-svs.com/support 32

34 The target device changes consequently. Now the MPLAB R environment is ready to import the firmware Import the Firmware in MPLAB Click on File Import... ksupport@3d-svs.com mwww.3d-svs.com/support 33

35 Then select the.hex firmware file and click on Open. To verify that the firmware has been correctly loaded, please check the Output window. mwww.3d-svs.com/support 34

36 3.4.3 Download the code Connect the microcontroller to the PC. Now select the appropriate method below depending on the debugger you are using. PIC32 R Starter Kit Select PIC32 R Starter Kit from the Debugger Select tool menu entry. PICkit 3 Select PICkit 3 from the Debugger Select tool menu entry. To check the connection, please look at the Output window. Finally you can download the firmware to the MCU clicking on the Program All Memories icon in the MPLAB R IDE toolbar ksupport@3d-svs.com mwww.3d-svs.com/support 35

37 The first time you download the firmware, MPLAB R IDE prompts an alert. Give authorization to continue the download procedure.then check the Output window for errors: To run the program on the microcontroller either select Debugger - Select Tool - None MPLAB R IDE shows a warning, because it does not recognize updates from an imported firmware. Just select No to ignore this warning. Note that the program will now run independently when powered on. From now on, every time a new.hex firmware has to be downloaded, restart this procedure from Section 3.4 skipping the step ksupport@3d-svs.com mwww.3d-svs.com/support 36

38 3.5 PC - PIC32 Ethernet communication This section explains how to connect an Ethernet Starter Kit Demo Board or a PIC32MX795F512L to the PC, starting from the example stored in C:\USER\Documents\3Dmicro Toolkit\Ethernet Communication Example. The PDF guide, Ethernet Communication Example is stored also in in that folder. From that you can write your own Ethernet communication program to be downloaded on the MCU. N.B. PIC32MX360F512L does not support Ethernet connections. This Section of this guide cannot be used for establishing Ethernet connections with this device. In order to interface a 32-bit PIC R microcontroller and test your program, plug the Ethernet cable in and connect the Ethernet Starter Kit to the same network, where the PC running LabVIEW is connected to. Then open the Project Explorer window for your program. The Ethernet Monitor folder contains three VIs: Global 1.vi contains global variables, used to store values and strings which are going to be sent and received by the MCU. This VI must not be edited. 3Dmicro Toolkit Ethernet Communication.vi establishes the Ethernet connection and updates global variable values. Variable names are referred to the MCU. 3Dmicro Toolkit Ethernet Monitor.vi reads and writes global variable values. This VI can be edited to develop a custom interface. The Block Diagram shows the current communication setup. ksupport@3d-svs.com mwww.3d-svs.com/support 37

39 Open 3Dmicro Toolkit Ethernet Communication.vi Click the Run icon mwww.3d-svs.com/support 38

40 Check that the 3Dmicro Toolkit Ethernet Monitor.vi is closed, before continuing. It does automatically open when a connection has been established. Insert the IP address set in Section 3.1 and click on Connect The led indicator turns green, if a connection is established. In case of errors, the display suggests you to check the network or the IP address. Contact your network administrator in case of repeated connection failures, because the IP address assigned to the MCU could be busy. The 3Dmicro Toolkit Ethernet Monitor.vi Front Panel shows sent and received variable and strings. ksupport@3d-svs.com mwww.3d-svs.com/support 39

41 Variable names are referred to the MCU. Referring to Example described in Section 3.1, receive eth variable 01 and receive eth string 01 values can be set and sent to the microcontroller, which replies sending send eth string 01 back. We can see an example using the PIC32 Ethernet Starter Kit Demo Board. When a Switch button is pressed on the Starter Kit, the send eth variable 01 is sent back to the PC and LEDS are turned ON Click on (CLOSE) and the STOP buttons to terminate the communication. ksupport@3d-svs.com mwww.3d-svs.com/support 40

42 .1 Supported LabVIEW palettes The 3Dmicro Toolkit support most of the standard LabVIEW palettes and VIs in the Programming section. A complete list of supported and unsupported VIs within their respective sections follows. Other LabVIEW palettes are not suitable for being used in embedded applications, therefore are not supported by this Toolkit. These VIs are from the Programming palette ksupport@3d-svs.com mwww.3d-svs.com/support 41

43 Structures Supported VIs Not Supported VIs For Loop Event Structure While Loop Shared Variable Case Structure Global Variable Flat Sequence Feedback Node In Place Element Structure Stacked Sequence Structure Diagram Disable Structure Conditional Disable Structure Formula Node Local Variable Array Supported VIs Not Supported VIs Array Size Sort 1D Array Index Array Replace Array Subset Insert Into Array Delete From Array Initialize Array Build Array Array Subset Array Max & Min Reshape Array Search 1D Array Split 1D Array Reverse 1D Array Rotate 1D Array Interpolate 1D Array Threshold 1D Array Interleave 1D Arrays Decimate 1D Array Transpose 2D Array Array Constant Array To Cluster Cluster To Array Matrix (All sub-palettes) Cluster, Class & Variant Supported VIs Not Supported VIs Unbundle By Name Build Cluster Array Bundle By Name Index & Bundle Cluster Array Unbundle Cluster To Array Bundle Array To Cluster Class VIs mwww.3d-svs.com/support 42

44 Numeric Supported VIs Not Supported VIs Add Fixed Point (All sub-palettes) Subtract Multiply Divide Quotient & Remainder Increment Decrement Add Array Elements Multiply Array Elements & Min Compound Arithmetic Absolute Value Round To Nearest Round Toward -Infinity Round Toward +Infinity Scale By Power Of 2 Square Root Square Negate Sign Numeric Constant Enum Constant Ring Constant Random Number (0-1) Expression Node Random Number (0-1) DBL Numeric Constant +Inf -Inf Machine Epsilon Math & Scientific Constants (All sub-palettes) Numeric Conversion Supported VIs Not Supported VIs To Extended Precision Float To Extended Precision Complex To Double Precision Float To Double Precision Complex To Single Precision Float To Single Precision Complex To Fixed-Point Number To Boolean Array To Quad Integer & Remainder Boolean Array To Number To Unsigned Long Integer To Time Stamp To Word Integer Convert Unit To Byte Integer Color to RGB To Unsigned Quad Integer RGB to Color To Unsigned Long Integer To Unsigned Word Integer To Unsigned Byte Integer Boolean To (0,1) Cast Unit Bases String To Byte Array Byte Array To String ksupport@3d-svs.com mwww.3d-svs.com/support 43

45 Numeric Scaling Supported VIs Not Supported VIs Radiants to Degrees Convert RTD Reading Degrees to Radiants Convert Strain Gauge Reading RPM to Radiants Convert Thermistor Reading Radiants per Seconds RPM Convert Thermocouple Reading Boolean Supported VIs Not Supported VIs And Number To Boolean Array Or Boolean Array To Number Exclusive Or Not Compound Arithmetic Not And Not Or Not Exclusive Or And Array Elements Or Array Elements Boolean To (0,1) True Constant False Constant String Supported VIs Not Supported VIs String Length Match Regular Expression Concatenate Strings Format Date/Time String String Subset Scan From String Replace Substring Format Into String Search and Replace String Spreadsheet String To Array Match Pattern Array To Spreadsheet String Trim Whitespace Build Text To Upper Case To Lower Case Space Constant String Constant Empty String Constant Line Feed Constant End of Line Constant Tab Constant mwww.3d-svs.com/support 44

46 String/Number Conversion Number To Decimal String* Number To Hexadecimal String* Number To Octal String* Number To Fractional String* Number To Exponential String* Number To Engineering String Format Value Decimal String To Number Hexadecimal String To Number Octal String To Number Fract/Exp String To Number Scan Value Additional String Functions Search/Split String Scan String For Tokens Pick Line Match First String Match True/False String String/Array/Path Conversion String To Byte Array Byte Array To String Path to Array of Strings Array of Strings to Path Path To String String To Path Additional String Functions Search/Split String Scan String For Tokens Pick Line Match First String Match True/False String Search and Replace Pattern Index String Array Append True/False String Rotate String Reverse String * These VIs are seamlessly replaced by the 3Dmicro Toolkit String Palette VIs in Section ksupport@3d-svs.com mwww.3d-svs.com/support 45