Other Language


Product Features
  • Alternative M.2 2260 or 2280 B-M key
  • CANbus 2.0B backward compatible with 2.0A
  • Supports baud rate 100/125/250/500(default)/800/1000K
  • Supports CAN message acceptance filter
  • Keeps configuration after hardware reboot
  • Up to 6000 CAN messages per second (receive data)
  • Supports Listen-only mode
  • Additional driver to support Linux SocketCAN
  • Supports SAE J1939 high layer protocol (Optional)
  • Termination resistor enabled/disabled by jumper
  • Complies with EN61000-4-5 2.5kV surge protection
  • Complies with IEC 60950-1:2005 + A1: 2009 + A2:2013 2.5kV HiPOT protection
  • Complies with EN61000-4-2 (ESD) Air-15kV, Contact-8kV
  • 30μ” golden finger, 3-year warranty
  • Supports -40 to +85 degrees
  • Industrial design, manufactured in Innodisk Taiwan
Featured Technologies:
Specs Order Information Related Resource +ADD TO INQUIRY


Module NameEGPC-B201
Module TypeM.2 to Dual Isolated CANbus 2.0B/J1939 Module
Form FactorM.2 2260/2280 B-M
Input I/FPCI Express 2.0 x 1
Output I/FCANbus 2.0B
Output connector2 x DB-9
Power Consumption2.69W (3.3V, 815mA)
Dimensions (W x L x H/mm)22 x 60/80 x 8.05
TemperatureSTD temp: 0°~70°C
Wide temp: -40°~85°C
EnvironmentVibration: 5G @7~2000Hz
Shock: 50G @ 0.5ms
NotesDownload driver and API (the same as EMUC-B202) from MyInnodisk website.
Windows: XP (32bit), 7 (32/64bit), 8/8.1 (32/64bit), 10 (32/64bit)
Linux: Kernel 2.6 and above (Native CDC-ACM driver),
Kernel 2.6.38 and above (SocketCAN Driver), 32/64bit

Order Information:

Model Name Description
EGPC-B201-W1 (2260, CAN2.0B)
EGPC-B201-W2 (2280, CAN2.0B)
M.2 to dual isolated CANbus 2.0B Module
EGPC-B201-W3 (2260, J1939)
EGPC-B201-W4 (2280, J1939)
M.2 to dual isolated CANbus J1939 Module
EGPC-B201-W5 (2260, CANopen)
EGPC-B201-W6 (2280, CANopen)
M.2 to dual isolated CANbus CANopen Module

Related Resources:


Innodisk and Cookies

We use cookies on this website to provide you with the better user experience. By accepting cookies, you agree to our use of cookies. For more information on how we use cookies, please see our Privacy Policy.