ls: cannot access '/dev/serial/by-id': No such file or directory

[7milesup]

Hi guys and gals.  Yes, it's me again 

Due to some extruder issues, I was working on the print head of my Voron.  Since I had some wonderful LED chamber lights installed, I had the power on (stupid).   While putting the print head back together I dropped a screw into the HartK PCB and it landed in a way that could not be repeatable in at least 20 million attempts.  The result... magic smoke wafting through the room.   Dangit.  From what I could tell, it fried the Octopus board, the Hartk PCB on the toolhead, and my Orange Pi.  I ordered a new Octopus V1.1 board and Hartk PCB.  I had a Raspberry Pi 4 sitting here so I figured this would be easy(ier) to configure that my Orange Pi.

I have installed the software, mostly using KIAUH and the Voron documentation.   I have installed the firmware on the Octo board as per the documentation.  It seems that everything all went well with no errors on any of the install.  However, I get "ls: cannot access '/dev/serial/by-id': No such file or directory" when I run the dev/by/serial command.  The Octo board does show up in with the lsusb command, so I know the Rpi can see it, but why the error?  Obviously Mainsail shows an error as follows...

Printer is not ready
The klippy host software is attempting to connect. 

So, what am I missing?  I have reformatted and re-installed all of the software a few times now with no luck.

 

TL:DR  ls: cannot access '/dev/serial/by-id': No such file or directory when utilizing the '/dev/serial/by-id command.  WTF.

 

[mvdveer]

Could it be because of this? Try the fix describe in this thread and see if that solves the problem.

[7milesup]

1 hour ago, mvdveer said:

Could it be because of this? Try the fix describe in this thread and see if that solves the problem.

Ok, that solved some of the issues.  Thank you.  The printer is communicating with the Rpi but now, when I send a command such as homing the X-axis I get an error that the "Homing failed due to printer shutdown" message.  What is interesting is that when I try to home any of the axis, the hot end fan starts up even though the heater has not seen an M104 command.  Hmmmm...

 

 

[7milesup]

Some of the communication issues have been solved but there are still problems.  For some reason the z-3 is reversed, which baffles me because I am using the same printer.cfg file as before. 

I will look into this closer tomorrow.

[7milesup]

Question (asking for a friend    If they were to accidentally leave the jumpers on one of the stepper drivers as it came from the factory and powered it on, would that be a problem? 

[mvdveer]

I don't think it will damage the board if that is the question - it may damage the stepper driver though.

Leaving the jumpers in the position they came with the board will put the drivers in SPI mode and should not cause any damage.

Hope this clarifies it.

[7milesup]

Interesting gremlins I have running around here.  When I first built my printer, it seemed that the Motor 5 "port" was possibly malfunctioning.  I moved that Z3 motor to motor 7, and all was fine.  After I fried that board and installed my new Octopus board, I had some odd functions taking place, such as the Z3 motor seemingly wanting to run backward.  I say seemingly because that did not seem like the whole story watching it operate and hitting the Emergency Stop a few times.  My config file was unchanged, so it should have been plug-and-play. 

I just moved my Z3 from motor 7 to motor 5 on my new board and all is fine with the world now.  Could it be possible that I received two different boards that had issues with two different motor positions?  It seems highly improbable, but it sure seems to be the case. 

Anyhow @mvdveer, again, thank you for your help.  One of these days I will have to fly to the land down under and buy you a case of beer.  As a side note, I did see John Butler a couple of weeks ago in St. Paul MN.  I am a fan of him, and it was nice to have some Australia come to me. 

[7milesup]

I thought that I would post an additional data point on this issue.   It does appear that leaving the motor driver jumpers on the board that it has damaged that particular port.  I simply moved the Z3 to a different port and it now operates correctly.

Also, when I dropped that bolt into/onto the Hartk board on the toolhead, it did take out my Orange Pi also.  I tried a few different scenarios last night trying to get my Orange Pi resurrected, but it is dead in the water.  I found it interesting that that one bolt pretty much wiped out all of my electronics.

The printer is up and running again with no issues.  Just some money up in smoke and a learning lesson for me. 

[ken226]

4 hours ago, 7milesup said:

I thought that I would post an additional data point on this issue.   It does appear that leaving the motor driver jumpers on the board that it has damaged that particular port.  I simply moved the Z3 to a different port and it now operates correctly.

Also, when I dropped that bolt into/onto the Hartk board on the toolhead, it did take out my Orange Pi also.  I tried a few different scenarios last night trying to get my Orange Pi resurrected, but it is dead in the water.  I found it interesting that that one bolt pretty much wiped out all of my electronics.

The printer is up and running again with no issues.  Just some money up in smoke and a learning lesson for me. 

 

Look at the bright side.  Now you can get a DSI display like the Pi-TFT43 and run klipperscreen.   Both the BTT and Waveshare versions of the DSI screens are plug and play with the Pi4B.

[claudermilk]

I guess there's a reason they are called "angry pixies" and you really ticked them off throwing a bolt at them.