Rat Rig Community [Unofficial]•2y ago

MCU cannot connect

Have you encountered an M8P error prompt indicating that the MCU cannot connect?

moonraker.log

klippy.log

56 Replies

blacksmithforlife•2y ago

Did you flash the M8P?

xenial-blackOP•2y ago

yeah

blacksmithforlife•2y ago

How did you flash the M8P?

xenial-blackOP•2y ago

With the SD card, I'll try again

blacksmithforlife•2y ago

how did you compile the firmware?

xenial-blackOP•2y ago

I'm trying firmware_ The latest firmware in binaries

blacksmithforlife•2y ago

so you went to http://RatOS.local/configure?step=1 followed the steps? Clicked the "compile firmware" button and then followed all the steps written out below?

xenial-blackOP•2y ago

yes

blacksmithforlife•2y ago

what is the output of ls /dev/*?

xenial-blackOP•2y ago

Yes, firmware failed to flash The strange thing is that after re flashing, the prompt MCU cannot connect is still displayed

blacksmithforlife•2y ago

so it was not renamed to FIRMWARE.CUR?

xenial-blackOP•2y ago

After one successful change, there was no further success.

blacksmithforlife•2y ago

what does ls /dev/serial/by-id/* show?

xenial-blackOP•2y ago

blacksmithforlife•2y ago

what about just /dev/serial?

xenial-blackOP•2y ago

Same question

blacksmithforlife•2y ago

Anything in dmesg? You could also check journelctl as well

xenial-blackOP•2y ago

Refresh succeeded, but an error was reported

xenial-blackOP•2y ago

@blacksmithforlifeIt seems that the cause of the problem has been found, but/btt manta m8p does not appear in the/dev directory

blacksmithforlife•2y ago

That comes from the firmware on the manta. When it connects to the cb1 it tells it what the connection should be. I think you flashed the wrong firmware on the manta What does ls /dev/serial/* output?

xenial-blackOP•2y ago

Can I manually add/dev/serial/by id/?

xenial-blackOP•2y ago

blacksmithforlife•2y ago

You can but you shouldn't cause it will cause problems later with Rat-OS. I would start over with the configurator and have reflash the board. That firmware doesn't look correct

xenial-blackOP•2y ago

Unable to connect to the configurator at this time, unable to find the hotspot for ratos

blacksmithforlife•2y ago

If there's no hotspot it probably is connected to the wifi

xenial-blackOP•2y ago

Yes, it's already connected to WIFI

blacksmithforlife•2y ago

Then just use that URL and add /configure?step=1 192.168.0.121/configure?step=1

xenial-blackOP•2y ago

ok Do you want to recompile the firmware here, and then refresh the SD card again? ok,Resolved

xenial-blackOP•2y ago

I want 4028 to turn off the fan when the speed is 0, but an error will appear.

blacksmithforlife•2y ago

Upload your printer.cfg

xenial-blackOP•2y ago

printer1.cfg

blacksmithforlife•2y ago

@miklschmidt the manta m8p board config doesn't have the aliases for the 4pin fans 4p_controller_board_pin and 4p_controller_board_tach_pin @xxrobot in the meantime, which fan port did you want to use for the 4 pin fan? fan5? if so, remove

[fan]
pin: PB8
tachometer_pin: PC14 
tachometer_poll_interval: 0.0005
cycle_time: 0.01

[fan]
pin: PB8
tachometer_pin: PC14 
tachometer_poll_interval: 0.0005
cycle_time: 0.01

and put

#needed until ratos is updated to include this info in the RatOS/boards/btt-manta-m8p/config.cfg
[board_pins manta_m8p_tmc2209]
aliases:
  4p_controller_board_pin=PB8,
  4p_controller_board_tach_pin=PC14

#needed until ratos is updated to include this info in the RatOS/boards/btt-manta-m8p/config.cfg
[board_pins manta_m8p_tmc2209]
aliases:
  4p_controller_board_pin=PB8,
  4p_controller_board_tach_pin=PC14

on line 150

xenial-blackOP•2y ago

yes,fan5 Pin 'adxl345_cs_pin' is not a valid pin name on mcu 'mcu'

miklschmidt•2y ago

Correct, i forgot this again will fix now

blacksmithforlife•2y ago

you didn't uncomment line 118 I just made a PR

miklschmidt•2y ago

You're making too easy for me

blacksmithforlife•2y ago

gotta give back somehow

miklschmidt•2y ago

Doesn't quite match the 1.0 pinout

miklschmidt•2y ago

part_cooling_pin=PE4 Close though!

blacksmithforlife•2y ago

DOH - typo!

miklschmidt•2y ago

Seems like i can fix it directly in the PR if you want?

blacksmithforlife•2y ago

lol, just pushed

miklschmidt•2y ago

Haha just saw thanks man

blacksmithforlife•2y ago

anytime

miklschmidt•2y ago

Merged!

xenial-blackOP•2y ago

"Yes, it hasn't been canceled, as it has been found that plugging in the ADXL will not power on."

blacksmithforlife•2y ago

you have line 118 #[include RatOS/printers/v-core-3/input-shaper.cfg] it needs to be [include RatOS/printers/v-core-3/input-shaper.cfg] notice I removed the #

xenial-blackOP•2y ago

Octopus Pro is still very convenient to use and has successfully printed a set of structural components

blacksmithforlife•2y ago

@xxrobot now that Mikel merged the change you don't need to add what I said in https://discord.com/channels/582187371529764864/1086663477709508648/1086981773004644354 Just remove the stuff you have in the user overrides section since it isn't needed

xenial-blackOP•2y ago

Ok 👍 Oh, the M6/7/8 pins of M8P1.1 and 1.0 have been changed

blacksmithforlife•2y ago

Yeah, ratos doesn't support 1.1 yet

xenial-blackOP•2y ago

Ok,I overridden the parameter below and it worked fine

Gaming

Programming

MCU cannot connect

Did you find this page helpful?