CANvas: Configure Your Wireless CAN Analyzer CL3000


Do you want to get cracking asap with your new WiFi CAN analyzer, CL3000?

Then this guide is for you!

Here we explain how you'll easily configure your wireless CAN bus logger in either Access Point (AP) mode or Station (STA) mode.

Before starting, make sure you’ve got the latest version of our free CANvas software!  

Also, if you haven’t yet read our CL3000 intro, check it out here - it gives a light overview of both AP and STA mode. 


Before going through each mode, it's important to understand how the CL3000 web server interface works.

Essentially, every time a log file is "closed", it will appear in the list and be available for download. 

This has one important implication:

If you do not fully turn off your application (e.g. car) and you've set the log file size limit to be large, you may experience that the log files do not appear in the web server interface. This is simply because the log file is not yet closed and no size limit has been hit.

In many applications, there will be a natural "closure" to the log file as you e.g. turn off your car. But if this is not the case, it can be helpful to set the MB file size limit in CANvas to something low (e.g. a few MB) to break up your logging into chunks. This way you will always be able to get the vast majority of your data regardless of whether your application fully shuts down before accessing the files.

The MB file size limit is easily changed under General/Log File settings.


By default, your WiFi CAN logger will arrive in AP mode.  

What does AP mode mean? 

It means that you will see the CL3000 pop up as a “hotspot” in your WiFi hotspot list on e.g. a phone, tablet or PC. The CAN logger will appear as soon as it’s powered via either the CAN bus or USB and you’re in range. 

AP mode is great for e.g. accessing log files from a hard-to-reach CAN logger in the field. You do not have to disconnect the logger, but instead simply enter the “Hostname” (or website name) in a browser on your wireless device. 

By default, you can enter the hostname “id0001” followed by a “/” to get access to the web interface (cf. below picture).




In CANvas, it’s easy to customize the key features of AP mode.

When you open CANvas, simply choose “CONFIGURE LOGGER”, set your “CAN logger model number” to 3000 and go to the WiFi tab - you will see a screen similar to below:


As evident, there are two main settings: WiFi Settings and Web Server Settings.

Below we detail each field in brief:

  • WiFi mode: This lets you switch between AP and STA mode (more below)
  • SSID name: This is the name that will appear in your WiFi hotspot list - we recommend leaving this equal to the logger ID
  • WiFi password: This has to be entered when connecting to the logger
  • Hostname: This name acts as the logger “URL” - once connected to the logger, simply enter “[Hostname]/” in your browser
  • Authentication user name / password: You can set up a user and password that will be required to enter the web server

That’s it!

Once you’re done editing, just hit the export button to load the new CONFIG.INI file onto your USB-connected CL3000.



AP mode is perfect for ad hoc, single logger use cases.

However, it’s far less convenient if you e.g. need to pull data from 20 loggers by connecting 1-by-1 to each of them.

In this case, we instead recommend using Station mode.

How does this help?

In STA mode, each logger can connect to a WiFi hotspot - e.g. from a phone, router, PC or mobile truck / bus hotspot.

This makes the logger web interfaces available on the local network of that WiFi hotspot - allowing you to easily grab files from each of the unique URLs (e.g. “truck12A/”, “truck25B”, …).

You can even set up basic scripts to loop through each URL and pull the raw CAN bus data to a folder, cloud server or similar for post processing!

Vehicle Fleet Wireless Scale Station Mode CAN Bus

EXAMPLE: You may have a CL3000 in a fleet of 20 trucks. The loggers could then be set up to connect to the garage router so that files become available when the trucks return to the garage.

Or, you could set up each logger to connect individually to the respective mobile truck WiFi hotspot to make the loggers accessible on-the-go.

Want to access the data online via the internet?

Typically, you will be able to access the loggers within the same VPN business network - or alternatively you may be able to set up port forwarding to bring the loggers online so they can be accessed remotely.

Below we explain how to easily set STA mode up in practice.


As before, cf. below a picture of the CANvas settings for STA mode.

Note that the fields are identical to AP mode, but some now have different meanings.


Below we briefly go through the relevant fields:

  • SSID name: In STA mode, the name should equal the name of the WiFi hotspot that the logger is to connect to - e.g. “Router12A”
  • WiFi password: This should then simply be the password of that WiFi hotspot, e.g. “Router12ASecretPassword”

Want all your loggers to connect to the same WiFi hotspot?

Then simply enter the same SSID name and WiFi password. 

Want to connect each logger to a separate WiFi hotspot?

In this case, you have to specify these hotspot names and passwords accordingly for each logger. In other words, keep track of which loggers fit which hotspots if you're e.g. connecting each logger to a unique hotspot in a truck or bus.

As for the Web Server Settings, these work similarly to the AP mode - with one key comment:

If you connect multiple loggers to the same network it is key to use unique hostnames

Otherwise you will not be able to use the hostnames for accessing the web server of each logger on the network. As such, we recommend always using unique logger IDs and setting the hostname equal to these.

Identify Individual WiFi CAN Logger 3000 Devices via IP Address

Specifically, you can try adding the unique local IP addresses of each logger in your browser. To find these IPs, you can e.g. go to your router settings and look at the connected client devices.

By entering each IP, you will be able to identify the loggers by their individual CONFIG.INI files that are available on the web server (assuming you’ve used unique LoggerIDs so that you can distinguish the loggers).



Want to avoid the manual task of downloading the log files one-by-one?

One of the cool things about the CL3000 web server interface is that it is extremely easy to manipulate via simple scripts done in e.g. Ruby or MATLAB.

In particular, this is great for looping through multiple wireless CAN loggers and pulling all the log files. You can even set up the code to only take log files that satisfy certain criteria (e.g. in regards to name, date & time stamp etc.)

How does this work?

Setting up scripts is easy due to the inclusion of a JSON file list.

This provides you with a stable method for navigating through log files.

To get you started, we’ve added below a simple Ruby script (change the extension from .txt to .rb).

It consists of two parts: A ‘ClHttpPull’ script (for basic functionality) and a ‘pullLogFiles’ script for customization.

ClHttpPull script: Provides the basic functionality

Script not loaded correctly

pullLogFiles script: Used for customization to your specific use case

Script not loaded correctly

The ‘pullLogFiles’ script references the IP address of a CL3000 device (local IP or port forwarded), sets a file destination folder and downloads all log files with an index above the specified value (250 in the example). This code can naturally be augmented with a loop across several loggers.

The scripts are outside the scope of our free support, but if you have a bit of coding experience it should be easy to work with!

Feel free to share with us any cool use case scripts you’ve done!


FTP Push works elegantly with STA mode, allowing a CL3000 to continuously “push” the latest files to an FTP server whenever it’s in range of the WiFi hotspot.

This is in particular useful when e.g. using on-the-go hotspots (truck mobile hotspots, driver smartphones etc.). The logger will push a new file and delete it once it’s transferred.


In other words: With the FTP push mode, you can collect all the raw CAN data across hundreds of loggers on a continuous basis - without lifting a finger!

With the files gathered in one folder, you can then use CANvas to convert the data into human-readable format using e.g. *.DBC files.

Further, with the “file merge” and “downsampling” features of CANvas it’s easy to compile all of your raw data into right-sized practical files ready for analysis.

For an intro to FTP Push and setting it up, click here!

In case you do not yet have a CL3000, head over to our product page to buy one for just 399 EUR!

If you’ve got questions, feedback or ideas for new features we’d love to hear from you!


We use cookies to improve our site (see our privacy policy)