Accidentally flashed with can pa0/pa1 instead up usb pa11/12 with canboot firmware and can't enter dfu to reflash.

Trying to find pins for st-link.
Or alternative.

Trying to connect to hermit crab hardware/klipper/octopus v1.1

Command never seems to return uuid. So I am guessing it's not booting properly. My functioning usb-c hermit crab also does not return a uuid. So not sure what's going on there.

Anyone using the DFH.fm BTT 3m CAN bus cable ?

Looking to CAN my M8P v1.2 with cb1 and a EBB36

Could you please document the pinout of the motor connector for EBB36 / 42. The pinout diagrams and manual do not provide this information.

Hello,

There is no information about USB wiring in the manual for the sb2240.
Neither that we need to use a jumper on the "5v usb" to power it by usb.

Thanks to add information about it !

I use EBBSB 2209 ，how to solve it
Transition to shutdown state: TMC 'extruder' reports error: GSTAT: 00000001 reset=1(Reset)

I connected an OLED 0,96" display to the I2C connector - EBB 42 CAN V1.2 connected via USB.
This display is functional when connected to the I2C bus on the printer's motherboard.

klipper configuration:

[display oled_1]
display_group: _toolhead_0
lcd_type: ssd1306
i2c_mcu: EBBCan_0   # mcu EBBCan_0
i2c_bus: i2c1             # u'BUS_PINS_i2c1': u'PB6,PB7'
i2c_address: 60         # 0x3C
contrast: 230            # range from 0 to 256

Unfortunately, I still get a timeout error on the i2C.
I tried SDA/SCL both PB3,PB4 and PB6,PB7.

Datasheet STM...

I2C1

I2C2

The USB-C port does not have 5.1K pull down resistors on the USB-C CC lines. This results the board not getting powered/recognized when connected to a properly implemented USB-C port on the host computer.

Where is the prefered spot to hook up power for the 2209 toolhead? Directions are lacking. I originally hooked it up by habit to the toolhead power, but then realized that doesn't get power 24/7.

Hey,
I've got a question, is it possible to use EBB36 with can hub supplied with Hermit Crab? I wanted to test it but something in my brain tells me that i will fry the board. The question is, is it possible to supply 24V and can comunication via USB C like in hermit crab?

The SB2240 Build manual specifies GH1.25 connectors for many of the board side connectors, like the TH0 thermocouple connector, etc.

GH1.25 connectors do NOT mate.

Discord notes that they are Molex Picoblade compatible connectors (preterminated wire and connector kits can be found on amazon US with an 'MX' designator')

Please update manual accordingly

What is the pitch of the Pin Header Jumper Cap for the EBB36 and EBB42 boards?
My box spilled and I lost all the jumper caps. I need to order a replacement jumper caps but the jumper caps for the EBB36 are not 2.54mm pitch. What is the pitch for these jumper caps?

It's supper convenient to run less wires. But I'm a bit concern about how it'll work with a heated chamber with 80-90C temperature.

I am running a Voron 2.4 with Octopus Pro 1.0, BTT U2C 1.1 and EBB42 1.1 STM32G0B1

All are with the latest firmware.

I am running the EBB42 with 4 wires from the U2C, using can bus communication.

I am also running a can bus communication, using a usb cable, from U2C to Octopus pro 1.0

I have set the can bus everywhere to 250000.

The error is repeatable over and over again, and always at the same point of the print. It actually starts after printing few layers, if my print is only few layers height , it doesn't appear.

So its not an overload . the raspberry pi 4 2gb I am using has 30% used CPU and 12% memory load... its not here the problem I think.

Can it be something in EBB42 from BigTreetech ?

and now after printing fine for few minutes, I am getting this error :

16:45:19
MCU 'EBBCan' shutdown: Timer too close

16:45:19

MCU 'EBBCan' shutdown: Timer too close
This often indicates the host computer is overloaded. Check
for other processes consuming excessive CPU time, high swap
usage, disk errors, overheating, unstable voltage, or
similar system problems on the host computer.
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown

https://github.com/Klipper3d/klipper/issues/5595

not seeing any instructions on connecting via USB. Specifically the Manta M8P
Any help would be appreciated.

Max31865 Overvoltage or undervoltage fault
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown

When i was printting,It suddenly appeared!!!!!
I don't konw why????????????
the wire connected solid! And no indication towards Leakage!It just suddenly happen!!!!!!!!

This happened to me 2/2 times.

First attempt. I flashed CanBus Bootloader as with Communication interface (CAN bus (on PB0/PB1)) not paying attention thinking it was can-USB. Plugged in EBB42 to BTT Hermit Crab CAN-Distribution Board with USB-C cable and no jumper on VBUS, no other cables connected. Turned on printer and could not find EBB42 with "python3 flash_can.py -q" in putty. From this point on Board lights up but will not enter DFU and connect to STM32CubeProgremmer. Multiple attempts to connect with canbus have also failed.

Second attempt. I immediately connected new EBB42 to BTT Hermit Crab CAN-Distribution Board with USB-C cable and no jumper on VBUS, no other cables connected. I did not flash board with any firmware. Turned on printer and heard a tiny pop before BL-touch from Hermit Crab extruder began to cycle. Two USB boards connected to outputs on BTT Hermit Crab CAN-Distribution Board. Port 1 had complete working BTT Hermit Crab extruder/hotend/bltouch/fans, Port 2 had EBB42 v1.2 board with no jumpers. After pop it appears that Component D6 is burned as well as some traces that connect to C31 look wet (probably heat damage?).

I understand that the setup directions have not been followed but why did this happen? It should not be so easy to destroy these boards.

Is this because the wrong firmware is installed?
Is this because I did not connect VBUS jumper?
Is this because I did not use the correct port on BTT Hermit Crab CAN-Distribution Board or the CAN terminate 120R jumper?
Is this because of the hardware from Hermit Crab is incompatible?

My Setup.
Klipper on Raspberry Pi connected to and powered by J26 on BTT Octopus 1.1
BTT Octopus 1.1 runs X,Y,Z0,Z1 and bed heater
Raspberry Pi has BTT RPT-CAN HAT from Hermit Crab CAN
Hermit Crab BTT RPT-CAN HAT connects to Hermit Crab CAN-Distribution Board
Hermit Crab CAN-Distribution Board connects to power supply and Hermit Crab CAN-extruder with extruder/hotend/bltouch/fans connected

keep getting this shit error. Tried 250k, 500k and 1mbit can speeds. Using the octopus 1.1 in can bridge mode. tried different sd cards, power suplies. Unplugged camera. done updates and firmware updates. PLEASE HELP


Uploading klippy (5).log…

Hi all,
Here is my scenario. Manta M8P with CB1 + U2C + EBB 42 V1.2 .
Manta +CB1 with Klipper installed. U2C configured, and I tried to follow the BTT Video to install the firmware on the EBB 42 V1.2. Once the board was in DFU mode and connected to STM32 Cube Programmer, I clicked Download and got an error

`15:06:27 : STM32CubeProgrammer API v2.13.0 | Windows-64Bits

15:07:04 : Read File: \Mac\Home\Desktop\klipper.bin

15:07:04 : Number of segments: 1

15:07:04 : segment[0]: address= 0x0, size= 0x67CC

15:09:29 : UR connection mode is defined with the HWrst reset mode

15:09:29 : USB speed : Full Speed (12MBit/s)

15:09:29 : Manuf. ID : STMicroelectronics

15:09:29 : Product ID : DFU in FS Mode

15:09:29 : SN : 204D39545542

15:09:29 : DFU protocol: 1.1

15:09:29 : Board : --

15:09:29 : Device ID : 0x0467

15:09:29 : UPLOADING OPTION BYTES DATA ...

15:09:29 : Bank : 0x00

15:09:29 : Address : 0x1fff7800

15:09:29 : Size : 68 Bytes

15:09:29 : Bank : 0x01

15:09:29 : Address : 0x1fff7870

15:09:29 : Size : 4 Bytes

15:09:29 : UPLOADING ...

15:09:29 : Size : 1024 Bytes

15:09:29 : Address : 0x8000000

15:09:29 : Read progress:

15:09:29 : Data read successfully

15:09:29 : Time elapsed during the read operation is: 00:00:00.025

15:09:31 : Memory Programming ...

15:09:31 : Opening and parsing file: klipper.bin

15:09:31 : File : klipper.bin

15:09:31 : Size : 25.95 KB

15:09:31 : Address : 0x08000000

15:09:31 : Erasing memory corresponding to segment 0:

15:09:31 : Not flash Memory : No erase done

15:09:31 : File segment @0x08000000 is not 255-bytes aligned. It will be aligned to @0x07FFFFF8

15:09:31 : Download in Progress:

15:09:31 : Error: failed to download Segment[0]

15:09:31 : Error: failed to download the File`

Now the board has the green and blue light (fainted) and I can't connect to it anymore. The cube programmer or the Manta M8P with CB1 don't see it anymore.
I don't know what to do...
Any help would be appreciated.
Thank you!

@bigtreetech consider updating manual, pinout and/or schematic diagrams to describe connector type and pitch details.

For example, am unable to figure out which crimp inserts to use for the EBB36 power/CANBus connector?

The EBB36 4 pin CANBus connector seems to be 3mm pitch based on my cheap calipers, and a dimension inspection of the .step model loaded into Fusion 360. Ideally, the manual/pinout in this repo would have these details.

CONN-TH_4P-P3.00_30002-04WA-T1P seems to be also known as Molex Micro Fit 3.0 for anyone else looking.

Multiple people have burned time on this very question, see https://www.reddit.com/r/BIGTREETECH/comments/12vhc55/4_pin_connector_on_ebb36/

Something like this could be helpful ...

After moving from tap mechanical switch to Voron OptoTap PCB v2.4.1 5-24V, an electrical burning smell was evident.
opto tap indication red/blue was ok. i didn't select 5 or 24v pad at the back of the pcb !
After returning to mechanical switch no more smell (already burnt!), no evidence of heat damage onto opto tap or EBB, the only symptom rgb leds remains off! nil time so far to carry out a trouble shoot, might be front face was not in line with the connector ?

Hello,

The usbC connector doesn't fit the space in the CW2 Cable Bridge :
the space is 3.4mm width. the usbC connector too. But the lower part of the physical usbC is almost 4mm large

Can you correct it ?

Best regards.

Both the step and STL file for the: Printed Part for USB-C Cable. are not working right. It looks that the step and STL files are labeled backwards and you cannot download either one of them.

Hi,
I see two options for improvement:

unconnected pins PA, PB, PC of the STM32GB01 chip

• to create the option of expansion using a shield like the Arduino UNO or Raspberry Pi
  For example, for users who have multiple Hotends on one toolhead.

Cheers.

Hi, I print this cable bridge

[](url)
it has only one hole for the heat threaded insert but my cable chain has 2 holes, where can i find this part with 2 holes I mean something like this but with 2 holes
[](url)

I can't find the pin names (like PA1, PB1, etc) for version 1.1. Version 1.0 does have this file/picture.
For v1.1 I can only find a pin file with the names (litteral names like "fan" and "rgb" etc) for each port.

Is it possible to share this file/picture? I would like to add the x_endstop but it can't find the pin name and it's not in the sample cfg file neither.

It would be great if the use of 3 (or even 4) pin PWM + Tachometer fans could be documented.

For example - is it "safe" to use the PA0 (FAN0/1 header) for +/- and a single pin from the I2C header, say PB4 for the sense/pulse yellow wire? Are there any risks?

Personally I've noticed when wiring a 3 pin fan up like this the fan never stops spinning at idle, there must be some sort of current / loop occurring when adding the PB4 to the sense/pulse connection.

For context - It's generally a good idea to use a fan with a tach for your hotend cooling to avoid potential disasters should it fail or become blocked during a print - for example: https://ellis3dp.com/Print-Tuning-Guide/articles/useful_macros/hotend_fan_monitoring.html

The build guide shows a steel wire is used to support the umbilical cable, and gives great details on how to bend it, but fails to say what size or type of steel wire to use.

Communication timeout during homing probe

I keep getting a "communication timeout during x homing" when i try to home x with the x motor connected to a skr pico and the x endstop connected to my EBB36 (connected to pi via U2C). It works fine with the endstop connected to the pico but i want it to work with the EBB so i can keep the umbilical limited to 4 wires.

Can someone please provide the exact steps for flashing the EBB42 CAN V1.2 board? There is a mix of information for all the board versions, and it is not clear exactly what is applicable to this board.

Using the middle two pins and the jumpers set correctly.
Thanks,

Diagrams should not have light yellow text. Heard about someone frying their EBB board because they misread the diagram.

I mostly love the diagrams the team creates, they've been really helpful. This is a nit pick. Cheers!

For example, the yellow text here is hard to read, easy to screw up...

Hello,

While correctly plugged in like in the manual, i had to invert the 2 fan pin in https://github.com/bigtreetech/EBB/blame/master/EBB%20SB2240_2209%20CAN/sample-bigtreetech-ebb-sb-canbus-v1.0.cfg .
Now i've :

[fan]
pin: EBBCan: PA1

[heater_fan hotend_fan]
pin: EBBCan: PA0
heater: extruder
heater_temp: 50.0

有没有人知道？？

I am on page 27 of manual. When I click download I get Error: failed to download the file

Replaced an EBB36 with the SB2209 and getting this error when I try to extrude.

"Unable to read tmc uart 'extruder' register IFCNT"

Extruder config (I changed the MCU name from EBBCan to can0)

EXTRUDER

[extruder]
step_pin: can0: PD0
dir_pin: !can0: PD1
enable_pin: !can0: PD2

Update value below when you perform extruder calibration

If you ask for 100mm of filament, but in reality it is 98mm:

rotation_distance = <previous_rotation_distance> * <actual_extrude_distance> / 100

22.6789511 is a good starting point

rotation_distance: 22.68486
gear_ratio: 50:10 #for CW2
microsteps: 16
full_steps_per_rotation: 200 #1.8deg Motor
max_extrude_only_distance: 200.0
max_extrude_cross_section: 50.0
max_extrude_only_velocity: 75.0
max_extrude_only_accel: 1500
nozzle_diameter: 0.400
filament_diameter: 1.750
heater_pin: can0:PB13
sensor_pin: can0:PA3
sensor_type: ATC Semitec 104NT-4-R025H42G
#pullup_resistor: 2200 # this is the default for the Revo heater
#control: pid
#pid_Kp: 22.2
#pid_Ki: 1.08
#pid_Kd: 114
min_temp: 0
max_temp: 327
min_extrude_temp: 170
pressure_advance: .035

EXTRUDER MOTOR

[tmc2209 extruder]
uart_pin: can0: PA15
stealthchop_threshold: 999999
run_current: 0.650

with SB2240 after 20/30 minutes of printing I get the error 'tmc "extruder" reports error : GSTAT: 00000004 uv_cp=1 (undervoltage!)

(Ldo nema 14 pancake run_current: 0.65)

both motor and board are new

Sometimes, not always, when restarting the firmware it is shown on Fluidd and Mainsail thermal temperatures chart, a spike in temperature on the hotend of a huge random value.

• Using a PT100 with 2 wires.

hi there...i need some help. yesterday arrived the ebb36 v1.2 and i'm trying to connect it to manta e3ez over can. manta flashed with klipper and selected "usb to can bus bridge (usb on PA11/PA12 and canbus on PB8/PB9)" and here begins the problem... when flashed this way, CB1 doesn't recognize manta anymore over "usb serial" connection. can0 network appears, but just the manta, not the ebb36. to mention that when i try to flash the ebb36 with stmcube i get an error "download failed" like in issue #32 or something like this but when i flash it with canboot, flashes ok (at least no error on download). in the manta manual i didn't found nothing about can bus. after first attempt to flash the ebb, it remains with one led full lit and the other one barely visible.

as written in the build guide i press and hold the Boot button, and then I click
the Reset button to enter the DFU mode but it does not run, there are some jumpers to insert?

My heater cartidge dosent want to heat after an update of system files on mainsail, when activated it only output 1.5V ? it should be 24V for the heater ? i dont know where to look , to a i need to reflash the toolhead to ''update'' it ?

On the page for the SB2209/2240 board there's a picture of an LCD screen somehow attached to the CAN port on the board; what screen is this and how does one attach it?

Build manual(page 8) referring to use special little mount between SB2240 and CW2 extruder.
Could you please add it to the repository or add details to the manual where to download it.

Thanks.

Lost communication with MCU 'EBBCan'
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown

when I started print, It had hannpend for a moment.

HI,
If I want to define an [extruder_stepper] or [manual_stepper] section instead of the [extruder] section ... an error occurs that the microsteps parameter must be defined (of course it is defined)

trying to flash the ebb but all I get is no dfu detected. when plunging in to usb and holding the boot button and taping the rst button windows 11 sees dfu in fs mode but cube programmer will not find

the new SB EBB can board with 2240 TMC driver has some issues I get Section 'tmc2240 extruder' is not a valid config section on start

Hi, I wanted to know what connector is used for thermistor/endstop on the ebb2209.

I see it is a 1.25mm pitch, but no info for finding a compatible crimping tool or more connectors...

Thanks for the info

Randomly shutdown with message:
MCU 'EBBCan' shutdown: Missed scheduling of next digital out event

Canbus:
EBB36 CAN V1.2

U2C:
U2C 2.1

Klipper Version:
v0.10.0-613-gebc3b0de

Both Canbus and u2c is the latest one with STM32G0B1 chipset
Canbus firmware based on manual config using 250k bitrate
U2C firmware using the V2 firmware from github
https://github.com/bigtreetech/U2C/blob/master/firmware/U2C_V2_STM32G0B1.bin

/etc/network/interfaces.d/can0

allow-hotplug can0
iface can0 can static
 bitrate 250000
 up ifconfig $IFACE txqueuelen 1024

Klipper.log

Stats 2394.8: gcodein=0  mcu: mcu_awake=0.007 mcu_task_avg=0.000010 mcu_task_stddev=0.000009 bytes_write=1688503 bytes_read=1079206 bytes_retransmit=9 bytes_invalid=0 send_seq=54108 receive_seq=54108 retransmit_seq=2 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=51 stalled_bytes=0 freq=180001025 EBBCan: mcu_awake=0.015 mcu_task_avg=0.000018 mcu_task_stddev=0.000028 bytes_write=500821 bytes_read=285546 bytes_retransmit=782 bytes_invalid=0 send_seq=13336 receive_seq=13336 retransmit_seq=13310 srtt=0.005 rttvar=0.003 rto=0.025 ready_bytes=45 stalled_bytes=0 freq=63999174 adj=63998877 rpi: mcu_awake=0.000 mcu_task_avg=0.000008 mcu_task_stddev=0.000012 bytes_write=15258 bytes_read=48941 bytes_retransmit=0 bytes_invalid=0 send_seq=2519 receive_seq=2519 retransmit_seq=0 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 stalled_bytes=0 freq=50000064 adj=49999756 sd_pos=584197 heater_bed: target=100 temp=99.7 pwm=0.305 raspberry_pi: temp=45.1 mcu_temp: temp=40.8 sysload=0.24 cputime=197.063 memavail=669104 print_time=2399.725 buffer_time=2.124 print_stall=0 extruder: target=245 temp=245.0 pwm=0.735
Stats 2395.8: gcodein=0  mcu: mcu_awake=0.010 mcu_task_avg=0.000011 mcu_task_stddev=0.000009 bytes_write=1690654 bytes_read=1079756 bytes_retransmit=9 bytes_invalid=0 send_seq=54152 receive_seq=54152 retransmit_seq=2 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=0 stalled_bytes=0 freq=180001017 EBBCan: mcu_awake=0.015 mcu_task_avg=0.000018 mcu_task_stddev=0.000028 bytes_write=502130 bytes_read=285756 bytes_retransmit=782 bytes_invalid=0 send_seq=13359 receive_seq=13359 retransmit_seq=13310 srtt=0.006 rttvar=0.003 rto=0.025 ready_bytes=0 stalled_bytes=0 freq=63999167 adj=63998927 rpi: mcu_awake=0.000 mcu_task_avg=0.000008 mcu_task_stddev=0.000012 bytes_write=15264 bytes_read=48957 bytes_retransmit=0 bytes_invalid=0 send_seq=2520 receive_seq=2520 retransmit_seq=0 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 stalled_bytes=0 freq=50000063 adj=49999770 sd_pos=584804 heater_bed: target=100 temp=99.7 pwm=0.305 raspberry_pi: temp=44.0 mcu_temp: temp=40.8 sysload=0.22 cputime=197.161 memavail=669224 print_time=2400.726 buffer_time=2.125 print_stall=0 extruder: target=245 temp=245.1 pwm=0.735
Stats 2396.8: gcodein=0  mcu: mcu_awake=0.010 mcu_task_avg=0.000011 mcu_task_stddev=0.000009 bytes_write=1694367 bytes_read=1080435 bytes_retransmit=9 bytes_invalid=0 send_seq=54222 receive_seq=54222 retransmit_seq=2 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=39 stalled_bytes=0 freq=180001010 EBBCan: mcu_awake=0.015 mcu_task_avg=0.000018 mcu_task_stddev=0.000028 bytes_write=504023 bytes_read=286017 bytes_retransmit=1313 bytes_invalid=0 send_seq=13392 receive_seq=13389 retransmit_seq=13392 srtt=0.007 rttvar=0.003 rto=0.200 ready_bytes=244 stalled_bytes=11 freq=63999159 adj=63998858 rpi: mcu_awake=0.000 mcu_task_avg=0.000008 mcu_task_stddev=0.000012 bytes_write=15270 bytes_read=48973 bytes_retransmit=0 bytes_invalid=0 send_seq=2521 receive_seq=2521 retransmit_seq=0 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 stalled_bytes=0 freq=50000063 adj=49999792 sd_pos=586083 heater_bed: target=100 temp=99.7 pwm=0.305 raspberry_pi: temp=44.0 mcu_temp: temp=40.8 sysload=0.22 cputime=197.286 memavail=669000 print_time=2401.909 buffer_time=2.306 print_stall=0 extruder: target=245 temp=245.2 pwm=0.682
toolhead: max_velocity: 300.000000
max_accel: 3000.000000
max_accel_to_decel: 1500.000000
square_corner_velocity: 5.000000
toolhead: max_velocity: 300.000000
max_accel: 1000.000000
max_accel_to_decel: 500.000000
square_corner_velocity: 5.000000
Stats 2397.8: gcodein=0  mcu: mcu_awake=0.010 mcu_task_avg=0.000011 mcu_task_stddev=0.000009 bytes_write=1697281 bytes_read=1081048 bytes_retransmit=9 bytes_invalid=0 send_seq=54279 receive_seq=54279 retransmit_seq=2 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=28 stalled_bytes=0 freq=180001004 EBBCan: mcu_awake=0.015 mcu_task_avg=0.000018 mcu_task_stddev=0.000028 bytes_write=504023 bytes_read=286065 bytes_retransmit=1667 bytes_invalid=0 send_seq=13392 receive_seq=13389 retransmit_seq=13392 srtt=0.007 rttvar=0.003 rto=0.800 ready_bytes=244 stalled_bytes=810 freq=63999159 adj=63998777 rpi: mcu_awake=0.000 mcu_task_avg=0.000008 mcu_task_stddev=0.000012 bytes_write=15276 bytes_read=48989 bytes_retransmit=0 bytes_invalid=0 send_seq=2522 receive_seq=2522 retransmit_seq=0 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 stalled_bytes=0 freq=50000063 adj=49999801 sd_pos=586791 heater_bed: target=100 temp=99.8 pwm=0.245 raspberry_pi: temp=44.5 mcu_temp: temp=40.7 sysload=0.22 cputime=197.369 memavail=670132 print_time=2402.613 buffer_time=2.009 print_stall=0 extruder: target=245 temp=245.2 pwm=0.682
MCU 'EBBCan' shutdown: Missed scheduling of next digital out event

Receive: 93 2396.416949 2396.393688 16: seq: 11, thermocouple_result oid=7 next_clock=3275030975 value=29314 fault=0
Receive: 94 2396.716818 0.000000 16: seq: 1d, thermocouple_result oid=7 next_clock=3294230975 value=29316 fault=0
Receive: 95 2397.017185 0.000000 16: seq: 1d, thermocouple_result oid=7 next_clock=3313430975 value=29318 fault=0
Receive: 96 2397.317321 0.000000 16: seq: 1d, thermocouple_result oid=7 next_clock=3332630975 value=29318 fault=0
Receive: 97 2397.617566 0.000000 16: seq: 1d, thermocouple_result oid=7 next_clock=3351830975 value=29318 fault=0
Receive: 98 2397.916577 0.000000 16: seq: 1d, thermocouple_result oid=7 next_clock=3371030975 value=29318 fault=0
Receive: 99 2398.116943 0.000000 12: seq: 1d, shutdown clock=3364630800 static_string_id=Missed scheduling of next digital out event
Transition to shutdown state: MCU 'EBBCan' shutdown: Missed scheduling of next digital out event
This is generally indicative of an intermittent
communication failure between micro-controller and host.

It seems shutdown during thermocouple

Please state what are thex, y, and z directions of the adxl to the front of the pcb.
I did mount my EBB42 that way: