This sample data serves to showcase how you can work with data recorded through a CANmod.router:
https://www.csselectronics.com/products/4x-can-bus-router-fd-converter-gateway-usb

For this purpose, we deploy a CANedge2 (incl. GPS/IMU) to record data as follows:
- CAN 1: A single CAN message with ID 0x200 and a payload of zeros 
- CAN 9: Internal GPS/IMU data
- CAN 2: Muxed data from a CANmod.router 
- The CANmod.router in turn is connected to four separate CAN buses (all simulating J1939 messages)

This results in the below files (which you can open via the asammdf GUI, for example):

1) muxed-raw: This is the file directly recorded by the CANedge 
- CAN 1: This contains the single CAN message with ID 0x200 
- CAN 9: This contains the internal GPS/IMU data
- CAN 2: This contains CAN FD messages that carry the muxed data from the CANmod.router

2) demuxed-raw: The raw file can be demuxed via a CANedge MF4 converter, resulting in a new MF4 file
- CAN 1: Same data as before
- CAN 9: Same data as before
- CAN 2: This is now empty 
- CAN 3: This now contains demuxed J1939 data from the CANmod.router CAN-S1
- CAN 4: This now contains demuxed J1939 data from the CANmod.router CAN-S2
- CAN 5: This now contains demuxed J1939 data from the CANmod.router CAN-S3
- CAN 6: This now contains demuxed J1939 data from the CANmod.router CAN-S4

3) demuxed-dbc-decoded: The demuxed file can now be DBC decoded via any CANedge software/API tool. 
We decode it via the asammdf GUI, resulting in a new MF4 file that contains decoded signals, linked to their source CAN channel

