i get this error. i know very very well that there are a few threads on this however this seems pretty specific. when i print at regular speed (around 60 - 100mms) it kicks out this error anywhere between layers 5 and 9.
however if i slow the speed factor down to 25% it prints fine.
i have changed the wires, rerouted them, reflashed the cb1, changed the mem card and even changed the timer that most frown upon.
it was working just fine when it was connected via usb instead however i came upon a can guide that made sense and thought , i too would like to be cool. now im shafted.
problem number 2:
im uncomfortable to ask this because it sounds stupid but. my usb ports on my manta m5p do not register any peripherals that i plug in there.
when i wanted to flash my ebb i had to go the computer route (stm32cubeprogrammer)because the manta would not read it while plugged into any of the usb ports for flashing (yes i did have the 5v jumper in, ive burned enough of these to know better).
dont know if these two are related but yeah. yar she blows.
thank you in advance.
edit: also i would like to add that its not always the ebb. sometimes it just sais mcu which i assume would be either the manta or the cb1.
i did read your thread on timer too close and tried everything that i could understand with my african brain. that aside i think i found the problem for the timer too close. my txqueuelen is set to 1024. not sure why. problem is i cant access that fille, it sais permission denied. how can i access it or recreate it?
----edit------
managed to change the file. will update.
also for the second problem. its not the ebb that i am whining about. its the fact that the manta does not “see” anything i plug into any of the three usb ports. as if they have been deactivated. it didnt do it before i did the can bridge flash.
What do you expect this board to “see” when plugging something in? These USB ports are for the compute module that you can install on this board, e.g. a CM4 or a CB1 as well.
If you did not flash any of the boards with the wrong firmware parameters or somehow massively messed up the Linux on the CB, then “reflashing everything” has a good chance of NOT solving your issue.