#issue with EBB36

79 messages · Page 1 of 1 (latest)

frosty sparrow
#

Hi guys, recently installed this with the help of some of the guys in this discord, did some first layer test print then suddenly I got this error
and now, even after restart, doesn't seems like ebb is reachable anymore.
😭

#

completely powered off everything, turned it back up and it seems to be responding again

#

but...not sure what the timer too close supposed to point to

sly silo
#

This sounds like a Pi/Pi Alternative issue. What are you using for a host?

frosty sparrow
#

CB1 with M8P

sly silo
#

@frosty sparrow Are you using a single config for your Manta and EBB or are they two separate configs?

frosty sparrow
sly silo
#

And you added the proper UUIDs to both and took out the serial calls?

frosty sparrow
#

I put the correct UUIDs to each of the config, yes

#

but what is serial calls?

sly silo
#

If you’re using the BTT sample configs they have lines that list the serial number for the boards. That’s used to address them, like the UUID does, but you need to remove it when you add canbus.

#

Do you have the host listed also

#

And do you have the include for the ebb? I’m on mobile, so I can’t look at your config yet.

frosty sparrow
#

ah no I don't

#

on printer.cfg, I only declared mcu canbus uuid

#

on ebb.cfg i only declared ebb uuid there

#

what I'm not clear about is, if I need to declare all of the uuid in printer.cfg or ebb.cfg

#

and you said to take out any serial which I never had in the first place

sly silo
#

Did you use the BTT example configs?

#

@frosty sparrow

frosty sparrow
#

BTT example configs for m8p or ebb?

sly silo
#

Yes.

frosty sparrow
#

i have both, do you mean both or just one of them?

sly silo
#

Both. Did you use them for your current configs and then modify them or start from scratch?

frosty sparrow
#

i originally used BTT example config which I tweaked it for stock ender 5 pro, then continued on from there to merc 1.1, then now with ebb

sly silo
#

Ok hang on.

#

try adding this:

[mcu CB1]
serial: /tmp/klipper_host_mcu

to the top of your printer.cfg. The rest looks good. So if that doesnt help, you have another issue with the CB1

frosty sparrow
#

something has gone awry, when I check canbus query, it came up with no UUIDS found

#

was working okay last night......

sly silo
#

Yes, thats correct. Klipper will only report can devices not in use. Since yours are in use, none are found.

frosty sparrow
#

do you make canbus cable yourself? i used 18AWG for power and rj45 for the signals as they're twisted

#

so the fact that it found none means it's working okay? cuz I'm getting this

sly silo
#

No, I used the premade LDO and crimped it. The RJ45 is solid core?

frosty sparrow
#

this is what I see in klippy.log

#
Traceback (most recent call last):
  File "/home/biqu/klipper/klippy/serialhdl.py", line 68, in _get_identify_data
    params = self.send_with_response(msg, 'identify_response')
  File "/home/biqu/klipper/klippy/serialhdl.py", line 261, in send_with_response
    return src.get_response([cmd], self.default_cmd_queue)
  File "/home/biqu/klipper/klippy/serialhdl.py", line 318, in get_response
    self.serial.raw_send_wait_ack(cmds[-1], minclock, reqclock,
  File "/home/biqu/klipper/klippy/serialhdl.py", line 253, in raw_send_wait_ack
    self._error("Serial connection closed")
  File "/home/biqu/klipper/klippy/serialhdl.py", line 61, in _error
    raise error(self.warn_prefix + (msg % params))
serialhdl.error: mcu 'mcu': Serial connection closed
mcu 'mcu': Timeout on connect
Created a socket
mcu 'mcu': Wait for identify_response
Traceback (most recent call last):
  File "/home/biqu/klipper/klippy/serialhdl.py", line 68, in _get_identify_data
    params = self.send_with_response(msg, 'identify_response')
  File "/home/biqu/klipper/klippy/serialhdl.py", line 261, in send_with_response
    return src.get_response([cmd], self.default_cmd_queue)
  File "/home/biqu/klipper/klippy/serialhdl.py", line 318, in get_response
    self.serial.raw_send_wait_ack(cmds[-1], minclock, reqclock,
  File "/home/biqu/klipper/klippy/serialhdl.py", line 253, in raw_send_wait_ack
    self._error("Serial connection closed")
  File "/home/biqu/klipper/klippy/serialhdl.py", line 61, in _error
    raise error(self.warn_prefix + (msg % params))
serialhdl.error: mcu 'mcu': Serial connection closed```
#

yeah RJ45 is solid core

sly silo
#

Thats a lot of movement for solid core wire

#

Do you have a multimeter?

frosty sparrow
#

yeah

#

check for wire continuity?

sly silo
#

You can check the can connection

#

no resistance

#

Klipper reporting back 0 devices doesnt check comm cables

#

it only knows there is nothing new

#

you want to check the can cable at one end, either the ebb OR the manta

frosty sparrow
#

so signal cable continuity is definitely ok

sly silo
#

no resistance

#

at one end for the can side with everything connected

#

powered off

frosty sparrow
#

when you meant no resistance, is the same as continuity right?

#

it's like when I wanna check if a cable is okay?

sly silo
#

Sorry, check resistance

frosty sparrow
#

i just fixed the crimp and i think it was it

#

the shaking from input shaper potentially caused it came loose

#

everything is talking again now

#

by the way, this crimp came with ebb

#

I have some crimp kit but none of them fit

#

or is the right size

#

do you know what the size is?

#

so that I can get more

#

i only have like 4 left as i had trouble crimping rj45

sly silo
#

microfit 3.0 i believe

#

the rj is super small for that. i would consider moving to a stranded core at 20-22 AWG

frosty sparrow
#

ok, so power can stay at 18AWG stranded core

#

and for signal your recommendation is 20-22AWG? stranded?

sly silo
#

Yeah. The cable I have is smaller than both of those and I wish they were a slight larger. Would have been an easier crimp.

frosty sparrow
#

wouldn't thicker cable introduce more resistance?

sly silo
#

If it’s in good shape for a fairly short run, no. Negligible at most.

frosty sparrow
#

thanks again for your help!

#

I'll keep this open for now just in case 😅

sly silo
#

I would marked it as solved since the issue was addressed and anyone else needs the info. You can always open another.

frosty sparrow
#

ok

#

by the way, what's your first layer and first layer infill speed?

#

just out of curiosity 😅

#

for PLA

#

oh and how do I set this to solved? can't find the tag for solved

sly silo
#

I run my first layers slow a good base is crucial, no reason to make it faster than need be