Utilizziamo i cookie per rendere migliore la tua esperienza di navigazione. Per rispettare la nuova direttiva sulla privacy, è necessario chiedere il tuo consenso per impostare i cookie. Per saperne di più.
PLUG & PLAY
Log data out-the-box. Standalone. Link your CAN bus to your server in <2 mins
PRO SPECS
Extractable 8-32 GB SD. 2xCAN/LIN. CAN FD. Zero data loss. 50 µs RTC. Error frames. MF4
COMPACT
Only 8 x 5 x 2 CM. 100G. Aluminium enclosure. 6 LEDs. Configurable 5V power out (CH2)
SECURE 3G/4G
Push data via 3G/4G to your own server. Update over-the-air. SIM slot. E2E security
GNSS + 3D IMU
Built-in GNSS/IMU. 3x accuracy via sensor fusion. Position, speed, acceleration & more
INTEROPERABLE
Free & open source software/API. MF4 to ASC/CSV. DBC support. Python. Dashboards
Pro specs CAN logger - at half the cost
The CANedge3 combines innovative design, cutting-edge components - and incredibly low costs:
- 2 x CAN (incl. CAN FD) + 2 x LIN channels
- Extractable 8-32 GB industrial SD card (= months of data)
- Popular binary MDF4 log file format
- Advanced message filtering & transmit functionality
- Start/stop logging triggers based on CAN ID & databytes
- Silent mode, bit rate auto-detection, cyclic logging
- Data compression & encryption (e.g. for GDPR, CCPA)
- Support for CAN/LIN error frame logging
- Fast boot time. Safely disconnect during use (power safe)
The device includes an extractable 8-32 GB industrial SD card for optimal endurance and rapid offline data transfer. It also includes an optional global SIM card.
The CANedge enables logging of raw CAN/LIN data incl. CAN FD, J1939, CANopen, OBD2, UDS, ISOBUS, NMEA2000 - across any CAN/LIN application.
The device is designed to be extremely compact (75 x 47 x 20 mm). Despite the robust aluminium enclosure, it weighs only 100G.
The 2nd port (CH2) provides a configurable 5V power out, letting you easily power e.g. CANmod sensor-to-CAN modules (temperature, analog/digital/pulse, ...)
The 2x high speed CAN channels enable time-synced recording of data from two CAN buses - ideal for e.g. many heavy duty vehicle applications
The CANedge3 comes with flanges to enable easy installation at scale. The 'mounting kit' includes screws and optional vibration dampeners.
You can use your own micro SIM card with the device - or activate the global Super SIM that is included with the device.
USE CASES
The CANedge2 is a powerful, standalone CAN logger for ad hoc analysis, diagnostics and development.
However, the device truly shines in e.g. fleet telematics and IoT machinery setups:
Underground mining & construction
Want to implement vehicle telematics - but your vehicles are underground?
Mining fleets often require automated monitoring, performance monitoring and diagnostics. However, vehicles often only re-surface briefly from mines - making it vital to have an offline 'buffer' if no underground WiFi network is available. Here, the CANedge2 logs data to the SD card and auto-uploads it when the vehicles re-surface and come within range of the WiFi. Further, the GNSS/IMU functionality enables easy tracking of assets - and provides vital signals like position, trip distance, speed and accelerations. Learn more in our mining telematics intro.
Warehouse fleet management
Need to monitor a fleet of AGVs/forklifts in a warehouse?
For site managers/OEMs, the device can collect data from AGV/forklift fleets - e.g. for optimizing battery management. By connecting to the warheouse WiFi, the devices can continuously upload data to your own local/cloud server. This also enables practical predictive maintenace as showcased in this case study of 250+ AGVs.
Vehicle telematics
Need to monitor & optimize a vehicle fleet in near real-time?
For wireless 'on-road' upload of data, the device can connect via a 3G/4G hotspot - or you can use a CANedge3 with internal SIM card for 3G/4G transfer. Alternatively, the CANedge2 can upload data when the vehicle periodically returns to e.g. a terminal WiFi. Ideal for e.g. OBD2 logging, truck fleet management, predictive maintenance and more.
Tip: For 3G/4G use cases, we strongly recommend using the CANedge3.
Remote machine monitoring
Need to remotely monitor & troubleshoot industrial machinery?
Production machinery OEMs often need to deal with diagnostics, maintenance and field breakdowns. Local troubleshooting can be costly and slow. Here, the CANedge2 can be installed to diagnose issues remotely - and/or set up wireless predictive maintenance. Further, with configuration over-the-air, you can e.g. reset the machine via remote controlled transmit messages. Learn more in our CANopen data logger intro.
White label partnerships (OEMs/integrators)
Need a data logger in your product - or as a telematics platform?
The CANedge2 CAN bus logger is easy to integrate in existing systems, making it ideal as a hardware platform for CAN bus telematics solutions. Configuration files, server interfaces, log files etc. all utilize open file formats, with open source API tools available. Further, all software is 100% open source and customizable - for example the CANcloud telematics platform, or the customizable Grafana dashboards.
Reinventing telematics
Today, fleet telematics is vital across vehicles and machines.
However, end users face challenges: Expensive subscriptions. No data ownership. Security concerns. Vendor lock-in.
The CANedge3 provides a modern alternative:
- Log data to the SD and auto-upload via global 3G/4G
- Use your own server (self-hosted or cloud)
- Use your own SIM (or 90% discounted Super SIM)
- Simply add your SIM/server details to the config
- Configure file split size/period to control upload frequency
- 100% secure: HTTPS, credential encryption and more
- Manage via over-the-air updates (firmware & configuration)
- Power e.g. sensor-to-CAN modules via the 2nd port
- Zero fees. Zero lock-in. Interoperable. Open source tools
GPS & 3D IMU - enrich your data
The CANedge3 comes with cutting-edge GNSS/IMU functionality - perfect for use cases like vehicle telematics.
- Add 40+ GNSS/IMU signals to your 2 x CAN/LIN data
- Full GNSS support (GPS, Galileo, BeiDou, GLONASS)
- Built-in gyroscope (roll, pitch, yaw) and accelerometer (X, Y, Z)
- High precision via sensor fusion - even in GNSS hostile areas
- Signals encoded as 'internal' CAN frames (separate channel)
- Configurable message inclusion/frequency (up to 5 Hz)
- DBC file included for easy decoding to human-readable form
- Optionally sync the CANedge RTC via precise GNSS time
- Flexible deployment via external GNSS or LTE/GNSS antenna
Position + sensor fusion
Add time-synced GPS positioning to your CAN/LIN data - with sensor fusion (UDR) for 3x higher accuracy.
Speed
Speed data is useful in e.g. fleet telematics to identify speeding, idle time, asset utilization rates and more.
Altitude
Altitude is key in e.g. analysis of fuel/battery consumption - or e.g. in aerospace applications like drones, planes etc.
Attitude
The GNSS/IMU enables attitude data, giving a 3D view of the asset orientation at any time [automotives].
Trip distance
Trip odometer data enables easy tracking of the trip distance travelled by the asset (since last module power cycle).
Angular rates [pending FW update]
3D IMU angular rates can be used in e.g. the analysis of driving and vehicle dynamics (tire/suspension, drifting, ...).
Acceleration rates
3D IMU acceleration rates can be used in e.g. analysis of driving quality and predictive maintenance.
Geofences
Configurable circular geofences are useful for e.g. theft prevention, safety, automation and more
Timestamp
The high precision epoch timestamp is useful e.g. in syncing the CANedge real-time clock.
Open source software/API - naturally
The CANedge3 uses open formats (MDF4 data, JSON config, S3 server) - and all software/APIs are 100% free and open source.
The software toolbox includes:
- Editors: Easily modify your device config (online/offline)
- CANcloud: Manage connected CANedge3 devices & data
- S3 drive: Mount your S3 server as a 'local drive'
- Converters: Convert data to Vector ASC, PEAK TRC, CSV, ...
- asammdf GUI: DBC decode, plot and export your data
- Python API: Automate your data processing & integrations
- Dashboards: Visualize data in custom browser dashboards
| GENERAL | |
|---|---|
| Functionality | Standalone CAN bus data logger with SD card, 2xCAN/LIN channels, 3G/4G LTE and GNSS/IMU |
| Firmware | Supports free firmware updates for adding features |
| Configuration | Configuration files based on the popular open source JSON schema concept |
| Software | Free open source editor tool for easy device configuration (offline/online version available) |
| Free open source CANcloud telematics platform for managing devices & data via your browser | |
| Multiple tools for mounting your S3 server as a local drive for easy access | |
| Free open source asammdf software & API for editing, DBC converting & plotting MF4 data | |
| Free open source MF4 converters - drag & drop log files to convert into e.g. CSV, ASC, TRC | |
| Free open source Python API - e.g. for automated data processing, reporting or integrations | |
| Free open source telematics dashboards for visualizing your DBC decoded data in your browser | |
| Safety | CE, FCC, IC, RoHS (see Docs) |
| Tested for voltage transients (emissions/immunity), ISO 7637-2:2011, by TUV SUD (see the manual) | |
| Warranty | 1-year warranty |
| Support | Free, fast & high quality support |
| Origin | Denmark |
| CAN BUS | |
| Channels | 2 x CAN channels (incl. CAN FD support) |
| Standard | ISO 11898: Compliant with CAN (up to 1 Mbit/s) and ISO & Bosch CAN FD (up to 5 Mbit/s payload rate) |
| Protocols | Log raw data from CAN based protocols (J1939/FMS, CANopen, NMEA 2000, OBD2, CAN FD, UDS, ...) |
| Identifiers | Compliant with CAN specifications 2.0A (11-Bit ID) and 2.0B (29-Bit ID) |
| Bit-Rate Auto-Detect | Bit rate can be auto-detected or set manually |
| Retransmission | Configurable retransmission of frames that have lost arbitration or been disturbed by errors |
| Transceiver Protection | ±16 kV HBM ESD, ±15 kV IEC ESD, ±70 V bus fault, short circuit |
| Common mode input voltage: ±30 V | |
| TXD dominant timeout (prevents network blocking in the event of a failure) | |
| LIN BUS | |
| Channels | 2 x LIN channels |
| Publisher/Subscriber | Each LIN channel can be configured as a LIN subscriber/publisher with support for LIN data transmission |
| Custom length | Support for custom frame lengths |
| Standard | Compliant with LIN 2.0 up to 20 Kbit/s (support for Classic & Enhanced checksum format) |
| Transceiver Protection | ±8 kV HBM ESD, ±1.5 kV CDM, ±58 V bus fault |
| TXD dominant timeout (prevents network blocking in the event of a failure) | |
| DATA LOGGING | |
| SD Card | 8 GB extractable Class 10 industrial micro SD (SDHC) included (optional 32GB) - read at 80 MB/s i The device uses a class 10 industrial micro SD card with strong specs:
|
| Parallel CAN/LIN | Record data from up to 2 x CAN channels + 2 x LIN channels, simultaneously |
| Real-Time Clock | Yes - CAN frames are date & timestamped with 50 microsecond resolution (battery backup) |
| The RTC can be configured to match local time zones (default: UTC) | |
| The RTC can be auto-synced via 3G/4G LTE or a CAN message (e.g. from the internal GNSS timestamp) | |
| Log File Format | Log data in industry standard binary MF4 (easily convert to e.g. CSV, ASC, pandas, MATLAB, ...) |
| Data Compression | Configurable embedded log file compression (~50-80% size reduction) |
| Silent Mode | Configurable silent mode: Restricted (acknowledge only) or monitoring (zero transmission) |
| Filters | 128/64 regular/extended ID filters per channel (range, mask, acceptance, rejection) |
| Prescaling | Prescale CAN frames to record e.g. by time (per X ms) or by data (e.g. if byte X or Y changes) |
| Transmit | Transmit lists of CAN frames per channel (single-shot/periodic) - e.g. for OBD2 requests |
| CAN Error Frames | Support for logging CAN error frames (bit-stuffing, form, CRC, bit, acknowledgement) |
| LIN Error Frames | Support for logging LIN error frames (checksum, receive, synchronization, transmission) |
| Remote Frames (RTR) | Support for logging/transmission of remote CAN frames (RTR) |
| Cyclic Logging | Optional cyclic logging mode (oldest log file is deleted when SD card is full) |
| Advanced Triggers | Control signal lets you start/stop logging based on custom CAN IDs & data thresholds |
| CAN Heartbeat | Optionally transmit heartbeat CAN frame with device status, storage used & RTC time |
| File Split | Configurable log file split size (by size: 1-512 MB and/or by time period: 0-86400s) |
| Power Safe | 100% power safe data logging - no file corruption when disconnected |
| Unique Device ID | Each device has a globally unique ID ensuring unique log file naming |
| Data Encryption | Log files can be encrypted at rest on the SD card for security/GDPR/CCPA (incl. integrity check) |
| 3G/4G LTE | |
| SIM Slot | SIM card slot for external micro SIM cards (mid size) |
| SIM Card | Use your own SIM card or activate the 'Super SIM' that ships with the device (with 90% discounted rates) |
| Note: Verizon SIM cards are not supported | |
| 3G/4G LTE Module | Professional-grade u-blox LARA-R6001D LTE Cat1 |
| Coverage | Global |
| Frequency (Bands) | 4G LTE FDD bands: 1, 2, 3, 4, 5, 7, 8, 12, 13, 18, 19, 20, 26, 28 |
| 4G LTE TDD bands: 38, 39, 40, 41 | |
| 3G bands: 1, 2, 5, 8 | |
| Frequency (MHz) | 4G LTE FDD: 700, 800, 850, 900, 1700, 1800, 1900, 2100, 2600 |
| 4G LTE TDD: 1900, 2300, 2600 | |
| 3G: 850, 900, 1900, 2100 | |
| Certifications | LARA R6001D: PTCRB, GCF, FCC/ISED, RED, NCC, RCM, Giteki, AT&T |
| Protocol | HTTP/HTTPS: Stable and secure transfers - ideal for big data telematics |
| Over-The-Air (OTA) | Configuration & firmware over-the-air (COTA/FOTA). Configurable sync rate. Optionally disable |
| Heartbeat | If enabled, the CANedge3 periodically "checks-in" by uploading a small device status file |
| Data Upload State | Optionally disable/enable upload of log files (e.g. via over-the-air configuration) |
| Antenna | External (SMA). Can be extended or replaced by e.g. a 2-in-1 antenna (3G/4G LTE + GNSS) |
| Server Interface | Popular S3 REST interface - plug & play with MinIO (open source), AWS, Google Cloud, ... |
| 3G/4G LTE SECURITY | |
| HTTPS | Data & over-the-air updates can be sent via HTTPS (TLS 1.2) for secure transfer |
| Credential Encryption | S3 server credentials can be encrypted in the config on the device SD card |
| Signed Firmware | Firmware updates are digitally signed to verify that they are from a trusted source |
| User Policies | Fully customize access rights across CANedge devices and end users through S3 policies |
| GNSS & 3D IMU | |
| Module | Professional-grade u-blox NEO-M9V sensor module (92-channel) with built-in gyroscope and accelerometer |
| GNSS | Supports combinations of GPS (USA), Galileo (Europe), BeiDou (China), GLONASS (Russia) |
| Sensor Fusion (UDR) | Enhanced position precision via sensor fusion (UDR) of GNSS and 3D IMU [automotives only] |
| Up to 3x better accuracy vs. GNSS-only receivers | |
| Extended and improved GNSS fix in GNSS hostile areas (e.g. urban environments, tunnels, ...) | |
| Accuracy | Position: 2.0 m CEP (Circular Error Probable) |
| Heading: 0.3 deg | Pitch: 0.4 deg | Roll: 0.6 deg (68% at 30 m/s) | |
| Velocity: 0.08 m/s | |
| Sensitivity | Tracking/Navigation: 160 dBm | Cold starts: 148 dBm |
| Acquisition | Cold start: ~30-120 seconds from device boot |
| GNSS Antenna | Required for GNSS-based data (not for IMU) |
| DATA PARAMETERS | |
| CAN encoding | The GNSS/IMU data is encoded as 'CAN messages' within the CANedge log files (on a separate channel) |
| Configuration | GNSS/IMU messages can be filtered/prescaled to enable custom message inclusion and frequency |
| Optionally record GNSS/IMU messages only if valid | |
| Signals | The module adds several GNSS/IMU signals (for a full list, see the Docs or DBC file) |
| GNSS position: Longitude and latitude information [5 Hz] | |
| GNSS time: Precise GNSS based epoch timestamp [5 Hz] | |
| GNSS status: Fix type (NO/UDR/2D/3D/GNSS+UDR) and satellite count [5 Hz] | |
| GNSS speed: Travel speed in m/s and km/h [5 Hz] | |
| GNSS altitude: Altitude in meters [5 Hz] | |
| Attitude/orientation: Roll, pitch, heading [automotives only] [5 Hz] | |
| GNSS odometer: Distance traveled (since power on) [5 Hz] | |
| 3D IMU: Accelerometer-based acceleration (X, Y, Z) [5 Hz] | |
| Geofences: Status of the configured geofences [5 Hz] | |
| ELECTRICAL | |
| Input Supply | +7V to +32V DC via the Channel 1 DB9 (e.g. from the vehicle/machine power supply) |
| Power Consumption | Very low (~1 W in normal operation, ~2.5 W during 3G/4G transfer) - no risk of battery drainage |
| Protection | Reverse voltage protection on CAN-bus supply |
| Transient voltage event protection on supply lines | |
| MECHANICAL | |
| Enclosure & Weight | Compact aluminium enclosure: 75 x 47 x 20 mm (W x L x H excl. flanges & antenna connector). 100 grams |
| Antennas | 3G/4G LTE antenna and GPS antenna included |
| Flanges | Flanges with 4 x M3 screw holes (head diameter < 6 mm) - see also the CANedge 'mounting kit' |
| Connector | 2 x Standard D-sub 9 (DB9) connectors (optional OBD2/J1939/... adapters) |
| Pin-Out | See the product manual for the DB9 connector pin-outs |
| Configurable Power Out | Channel 2 can be configured to supply 5V to external modules (e.g. the CANmod sensor-to-CAN modules) |
| LEDs | Logger status via 6 external LEDs: Power, CH1, CH2, Memory, LTE, GNSS |
| Temperature | Operating temperature (parts): -25degC to +70degC |
| IP Rating | IP Rating 40 |
Comparison table
| CL1000 | CL2000 | CANedge1 | CANedge2 | CANedge3 | |
|---|---|---|---|---|---|
| CAN & LIN | CL1000 | CL2000 | CANedge1 | CANedge2 | CANedge3 |
| # of CAN channels | 1 | 1 | 2 | 2 | 2 |
| # of LIN channels | 2 | 2 | 2 | ||
| CAN FD | Yes | Yes | Yes | ||
| RTC with battery backup (resolution) i All loggers except the CL1000 have a real-time clock for timestamping each data frame with the absolute date & time. The CANedge timestamp resolution is 20x higher than the CLX000, which is relevant as the CANedge is able to log a far higher number of frames per second. | Yes (1 ms) | Yes (0.05 ms) | Yes (0.05 ms) | Yes (0.05 ms) | |
| #frames/second i The CLX000 is able to log up to around 800-1000 frames without message-loss. The CANedge is designed for lossless logging at any busload and has been used in various use cases to record 3000+ frames/second (1500+ per channel). In practice, most CAN bus applications broadcast between 500-1500 frames/second. | ~800-1000 | ~800-1000 | 3000+ | 3000+ | 3000+ |
| DATA LOGGING | CL1000 | CL2000 | CANedge1 | CANedge2 | CANedge3 |
| SD card logging i All loggers have an 8 GB SD card as the default card (optional 32 GB SD card upgrade) | Yes | Yes | Yes | Yes | Yes |
| Industrial & extractable SD i The CLX000 enables log file transfer via USB (~0.5 MB/s), while the CANedge enables log file transfer via the extractable industrial micro SD card (~80 MB/s) | Yes | Yes | Yes | ||
| Log file format i The CLX000 logs in a simple CSV-style TXT format. The CANedge logs in the MDF4 (.MF4) log file format is a standardized and popular binary format for logging e.g. CAN bus and LIN bus data. It is supported by various existing software and API tools. The MF4 format is ~50% more compact than the CLX000 format (~80% with compression enabled) | .TXT | .TXT | MDF4 (.MF4) | MDF4 (.MF4) | MDF4 (.MF4) |
| Cyclic logging i Cyclic logging lets the device overwrite the oldest file once the SD card is full | Yes | Yes | Yes | Yes | Yes |
| Silent mode | Yes | Yes | Yes | Yes | Yes |
| Bit-rate auto detection i The device can auto-detect the bit rate for most applications. It is also possible to select a manual bit-rate from a list of standard bit-rates. Further, the CANedge supports advanced bit-rate customization | Yes | Yes | Yes | Yes | Yes |
| Filters & prescaling i The CLX000 supports up to 8 | Basic | Basic | Advanced | Advanced | Advanced |
| Transmit lists i The CLX000 supports up to 20 custom transmit frames, while the CANedge supports up to 64 custom transmit frames per channel | Basic | Basic | Advanced | Advanced | Advanced |
| Control signal (trigger) i The CLX000 supports start/stop of logging based on the presence of a specific CAN ID. The CANedge extends this to be able to trigger logging/transmitting on specific signal values as well (e.g. if EngineSpeed exceeds a specific threshold) | Basic | Basic | Advanced | Advanced | Advanced |
| Data compression & encryption i The CANedge enables optional compression of data to reduce file size by 50-80% vs. uncompressed data (and vs. the CLX000 log files). Further, the CANedge can encrypt data so that it can only be read via a password - e.g. to ensure GDPR/CCPA compliance as well as ensure that the data has not been tampered with | Yes | Yes | Yes | ||
| CAN/LIN error frame logging i The CANedge supports logging of CAN/LIN error frames | Yes | Yes | Yes | ||
| STREAMING | CL1000 | CL2000 | CANedge1 | CANedge2 | CANedge3 |
| USB streaming to PC i The CLX000 has a USB connector to allow streaming of data in real-time via USB to a PC. The streamed data can be displayed in SavvyCAN and e.g. analyzed for reverse engineering | Yes | Yes | |||
| GNSS/IMU | CL1000 | CL2000 | CANedge1 | CANedge2 | CANedge3 |
| GNSS/IMU support i The CANedge supports a built-in GNSS/IMU module. This enables you to connect an external GNSS antenna (or a 2-in-1 antenna) to add 40+ signals like position, speed, distance, attitude and more. | Optional | Optional | Yes | ||
| WIFI/LTE | CL1000 | CL2000 | CANedge1 | CANedge2 | CANedge3 |
| Secure WiFi/LTE data transfer i The CANedge2 can auto-push log files to your own S3 server (e.g. an AWS S3 cloud or MinIO S3 server). Data can be uploaded via HTTP or secure HTTPS. The connectivity also allows the devices to auto-sync the RTC to ensure that large fleets of devices are in time sync. | WiFi | 3G/4G LTE | |||
| Over-the-air config/firmware | Yes | Yes | |||
| SOFTWARE | CL1000 | CL2000 | CANedge1 | CANedge2 | CANedge3 |
| Configuration editor i The CLX000 INI config can be modified via a text editor. The CANedge JSON config can be modified via a text editor or the free online/offline editor tools. For the CANedge2, we also provide a simple batch manager tool for updating multiple devices over-the-air | Yes | Yes | Yes | Yes | Yes |
| DBC conversion support i The CLX000 log files can be DBC converted via the free SavvyCAN software. The CANedge log files can be DBC converted via e.g. the free open source asammdf software or Python API | Yes | Yes | Yes | Yes | Yes |
| Convert data to e.g. ASC, TRC i The CLX000 and CANedge log files can be converted via simple drag & drop converters, which can also be used in scripts or via the command line. The CANedge converters support multiple formats including Vector ASC, PEAK TRC, CSV. | Yes | Yes | Yes | Yes | Yes |
| Graphical plot support i The asammdf GUI enables easy graphical plots of DBC converted data | Yes | Yes | Yes | ||
| Data processing API i The CANedge log files can be processed via Python APIs for e.g. automatic analysis of large amounts of data. Further, S3 APIs can be used for easily managing uploaded data & device files on your server - enabling fully automated systems e.g. for BI integration or data dashboards | Yes | Yes | Yes | ||
| Dashboard integration i The CANedge data can be easily visualized via free, open source and customizable browser dashboards (e.g. via Grafana). This is particularly useful in combination with the automatic data collection of the CANedge2 | Yes | Yes | Yes | ||
| Telematics "cockpit" i CANcloud is a free optional browser tool for the CANedge2. It lets you log in to your server via the browser and manage your connected devices & data. For example you can monitor devices in the field via the status dashboard and perform easy over-the-air updates | Yes | Yes | |||
| MECHANICAL | CL1000 | CL2000 | CANedge1 | CANedge2 | CANedge3 |
| L x W x H (mm) i Note that CANedge antennnas/flanges are excluded in the measurements | 67 x 43 x 24 mm | 67 x 43 x 24 mm | 75 x 47 x 20 mm | 75 x 47 x 20 mm | 75 x 47 x 20 mm |
| Volume (cm3) | 70 cm3 | 70 cm3 | 70 cm3 | 70 cm3 | 70 cm3 |
| Weight (g) | 50 | 50 | 100 | 100 | 100 |
| Enclosure | ABS Plastic | ABS Plastic | Aluminium | Aluminium | Aluminium |
Tecnologix offre supporto gestito direttamente dal Team di sviluppo.
Non esitare a metterti in contatto con i nostri esperti.
Basta chiedere qui
Non esitare a metterti in contatto con i nostri esperti.
Basta chiedere qui