Intrepid Tools at the Junction Tokyo Hackathon

Add SimpleLink™ Studio to the generated C Code Interface project

First, download the SimpleLink Studio archive from https://github.com/jchung-intrepid/CCIF_SIMPLELINK_BASE.git. Copy the entire ‘simplelink’ folder and paste it into the project directory. You can open the project directory from Visual Studio by right clicking on the project and selecting ‘Open Folder in File Explorer’.

Figure 1: Copy the downloaded simplink directory into the CCIF project directory.

In Visual Studio, right click on the project and use Add -> New Filter to add a ‘simplelink’ directory with three sub directories named ‘include’, ‘common’, and ‘source’. Then, drag and drop all contents of each directory from your project directory.

Figure 2: Add filters using Add -> New Filter.

Figure 3: Add files in include, source, common directories to the project.

In Visual Studio, make the following changes to the project properties:

1. Go to Configuration Properties -> C/C++ -> Additional Include Directories. Add $(SolutionDir)\simplelink\, $(SolutionDir)\simplelink\include, $(SolutionDir)\simplelink\source, and $(SolutionDir)\simplelink\common. Figure 4: Add simplink include paths to the project.
2. Goto Configuration Properties -> Linker -> Input -> Additional Dependencies. Add Add $(SolutionDir)\simplelink\SimpleLinkStudio.lib.Figure 5: Add simplink library path to the project.
3. Goto Configuration Properties -> C/C++ -> Code Generation -> Runtime Library. Set to ‘Multi-threaded DLL (/MD)’.Figure 6: Set Runtime Library to link dynamically during build.
4. Goto Configuration Properties -> C/C++ -> Precompiled Headers. Set to ‘Not using precompiled header’.Figure 7: Change Precompiled Header to ‘Not Using Precompiled Headers’.
5. Include “simplelink.h” in SpyCCode.c. Then, copy and paste the following function stubs in SpyCCode.c. These are asynchronous callback functions used by SimpleLinkStudio™ to notify various network events and need to be defined somewhere in your program.

/*!
\brief This function handles WLAN events
\param[in] pWlanEvent is the event passed to the handler
\return None
\note
\warning
*/

void __cdecl SimpleLinkWlanEventHandler(SlWlanEvent_t *pWlanEvent)
{
}

/*!
\brief This function handles events for IP address acquisition via DHCP
indication
\param[in] pNetAppEvent is the event passed to the handler
\return None
\note
\warning
*/

void __cdecl SimpleLinkNetAppEventHandler(SlNetAppEvent_t *pNetAppEvent)
{
}

/*!
\brief This function handles callback for the HTTP server events
\param[in] pHttpEvent – Contains the relevant event information
\param[in] pHttpResponse – Should be filled by the user with the
relevant response information
\return None
\note
\warning
*/

void __cdecl SimpleLinkHttpServerCallback(SlHttpServerEvent_t *pHttpEvent,
SlHttpServerResponse_t *pHttpResponse)
{
}

/*!
\brief This function handles general error events indication
\param[in] pDevEvent is the event passed to the handler
\return None
*/

void __cdecl SimpleLinkGeneralEventHandler(SlDeviceEvent_t *pDevEvent)
{
}

/*!
\brief This function handles socket events indication
\param[in] pSock is the event passed to the handler
\return None
*/

void __cdecl SimpleLinkSockEventHandler(SlSockEvent_t *pSock)
{
}

Build the C Code Interface project

If you have completed step 2, your C Code Interface project should compile successfully. You are now ready to add your code in SpyCCode.c or add additional source and header files as needed to build your desired application.

Figure 1: Extend SpyCCode.C and create more source files as needed to implement your application.

Run the built C Code Interface DLL with Vehicle Spy

When you build your C Code Interface project in Visual Studio, the result is a DLL that plugs into Vehicle Spy. The DLL exports a set of standard functions, which Vehicle Spy calls to make everything work. When you start Vehicle Spy, it will dynamically load the DLL and execute your C Code Interface project.

To do this, go back to Vehicle Spy where you created your C Code Interface Project. Click on the play button located on the top left corner of the window and Vehicle Spy will start. If you have already completed our hardware setup guide, Vehicle Spy will connect to neoVI FIRE and gain access to the vehicle network that neoVI FIRE is connected to. After Vehicle Spy starts, you will notice that the Output console will start printing ‘Another Second happened’ as defined in the Spy_Main().

Figure 1: Output console window showing Printf message from Spy_Main().

Downloads

SimpleLink™ Studio Archive – Contains changes from Intrepid Control System to build seamlessly in C Code Interface project environment.

Base VS Project for C Code Interface + SimpleLink Studio – This is a clean archive of Visual Studio project containing all the default C Code Interface and SimpleLink™ Studio source and library files. Use this as a base to quickly start developing your application for Vehicle Spy and CC3100. Start coding your application by extending SpyCCode.c.

Application Sequence

This sample C Code Interface application does the following:

1. Initializes the CC3100 board to a default state and connect to a WiFi AP of your choice. The application will retry every 1 second until connection is made.
2. Attempts to open a TCP connection to a TCP server listening at port 5001. The application will retry every 1 second until connection is made.
3. Data from the server will be received by the BsdTcpClientReceiveProcess function. For the sake of demonstration, the function will simply echo the received data back to the server.
4. Anytime Vehicle Spy receives a CAN message that matches one of the four messages defined in the Receive Table of the Messages Editor, CCIF_SimpleLink_TCP.vs3 will invoke the matching Event Handler callback function defined in the C Code Interface DLL. When Vehicle Spy invokes the callback function, it will pass the pointer to the CAN Message object to the DLL. Figure 1: Messages Editor window showing the four CAN Receive Messages. Figure 2: C Code Interface ‘Edit’ window showing Event Handlers for the four Receive Messages
5. The Event Handler callback receives the CAN Message from Vehicle Spy and sends the 8 byte content of the message to the connected server via socket. Figure 3: Receive Message Event Handlers defined in the C Code Interface project.

Running the Sample Application

Before you proceed, please make sure that you have all the hardware, software, and download contents from the step 1.

1. Open the C Code Interface DLL project in Visual Studio and set the WiFi AP connect credentials and TCP Server IP address.Figure 1: Define parameters needed to connect to an AP such as SSID and Passkey in sl_common.h.
2. Double click the downloaded ‘CCIF_Simple_TCP.vs3’ file to start Vehicle Spy. Press the ‘Edit’ button from C Code Interface window and set the project path to the Visual Studio project file located in the downloaded CCIF_SimpleLink_TCP archive.Figure 2: CCodeInterface ‘Edit’ window – change project path to the directory in your PC where .vcxproj is located.
3. CAN messages originate from physical CAN networks in your vehicle. Hence, we must first connect a CAN network adaptor to the vehicle’s CAN bus. Do this by taking the 25pin – OBDII cable and connecting your neoVI FIRE to the 25pin connector of the cable and the OBDII connector to your car’s OBDII port. For those who do not have access to an actual vehicle, Intrepid is providing a CAN bus simulator which generates fixed set of CAN messages to mimic a CAN bus. This simulator, called neoECU Simulator has an OBDII port which conveniently plugs into the OBDII connector on the 25pin – OBDII cable. Finally, supply power to the neoECU Simulator by connecting the provided power pack to the 12V barrel jack connector. This will power both neoECU Simulator and neoVI FIRE.Figure 3: neoVI FIRE and neoECU Simulator connected via 25pin – OBDII cable.
4. Now that we have a CAN adaptor (neoVI FIRE) connected to your vehicle or the neoECU Simulator, we need to connect the neoVI FIRE to the PC so that it can forward all received CAN messages to the Vehicle Spy software. Do this by simply connecting the USB cable between neoVI FIRE and your PC.
5. At this point all Intrepid hardware and software should have been configured. Finally, connect the CC3100 Boosterpack + Advanced Emulation boosterpack board to your PC using the provided micro USB cable. Figure 4: Connecting CC3100 from http://processors.wiki.ti.com/index.php/CC31xx_Quick_Start_Guide.
6. Make sure CC3100 board is properly connected to your PC. Open Vehicle Spy. When you start Vehicle Spy, it should have full read & write access to the connected CAN bus via the neoVI FIRE adaptor. Start Vehicle Spy by pressing the play button on the top left corner of the window. You should see a real-time trace of all CAN messages generated by your vehicle or the neoECU Simulator from Vehicle Spy’s Messages view.Figure 5: Messages window showing real-time CAN traffic and CCodeInterface window showing output from DLL.
7. Identify the four CAN messages that contain data that represents the first four knobs on the neoECU Simulator. Vehicle Spy will send those messages to the C Code Interface DLL, which will then forward them to a remote TCP server via connected socket.Figure 6: Messages window showing the four CAN Messages mapped to neoECU Simulator Knobs.
8. Verify that Vehicle Spy has successfully loaded the C Code Interface DLL by observing the ‘Output’ tab of the C Code Interface window.Figure 7: CCodeInterface Output console showing CC3100 connection status.
9. Setup a remote TCP Server on your Smartphone, MAC, or PC with proper IP address and port number. If you are using an Android phone, convenient way to do this is to download the TCP/UDP TEST TOOL app by animod from Google Play and use the app to setup a TCP Server.Figure 8: A sample TCP Server application used for testing.
10. Click button from Graphical Panel to instruct C Code Interface DLL to start forwarding CAN data to the connected TCP Server. Data sent by the TCP Server can be viewed in Vehicle Spy by observing the ‘Output’ tab of the C Code Interface window.Figure 9: Click the ‘Send CAN Data to TCP Server’ button from Graphical Panel window to instruct CCodeInterface to send data to the connected TCP Server. There is also a Red/Green LED indicating the socket connection status.

Figure 10: Android app showing CAN data sent by CCodeInterface using socket connection made by CC3100.

Downloads

CCIF_SimpleLink_TCP.vs3 – A Vehicle Spy 3 save file that loads and executes the user code in CCIF DLL. It contains decoding information of four CAN messages, which are handled by the four Rx Message Event Handlers. When Vehicle Spy receives any one of those messages, it will forward them to CCIF by invoking the matching Event Handler callback.

Base VS Project for C Code Interface + SimpleLink Studio – This is a complete archive that contains all the C Code Interface source files for this sample application. Use CCIF_SimpleLink_TCP.vs3 to load and execute this DLL project.