DeterminedOpier

So, @ldiaz, and others who may be interested in this thread. The Orange Pi One experiment is a complete failure. Octoprint installs correctly, connects, prints, all just fine and everything is seamless. But, and this is obviously a huge but, long prints eventually fail, and usually late. So you wake up to a 20 hour print that should still be going, and the print head is frozen at over 80%. So essentially a whole day got taken up, for nothing. This has happened repeatedly, over a dozen times, while I tested and retested to eliminate variables. * Changed brand of SD card. * Moved pis to power source not the same as printer, in case it was a voltage sag. * Using shielded printer cables. * Initially we used an OctoFarm overlay program, so tested with and without. * This happened on both Prusa and several CR-10s. And the most telltale of them all was that yesterday I burned a standard Raspberry Pi Octopi image, fired up one of my 3B plusses, and hooked it to one of the CR-10s. The camera came on (which I never got working on the Opi), and the first large 22 hour print just finished. I think there is some kind of communication jam up going on, because though the problem is repeatable, it happened at different times. Some even failed at 2%, same behavior. I didn't have the serial log enabled, but the standard log showed nothing. If you are interested @ldiaz, I am willing to hang in there and continue to test for you. After a week and a half of failed prints, I personally I am completely abandoning the Opis for now and moving to Rpis. Nobody even answered my webcam question, and I know Igor isn't interested in camera stuff historically, so it just isn't worth it for now. I am subscribed to this thread, so if you want to come back and try to figure it out at some point, just let me know and I'll be happy to lasso a printer and see if it works. Thankyou of course for all of your efforts. I love Armbian and appreciate the work that you all bring to the world of experimental computing. I will do whatever I can to help.

I have made the change on several of these Orange Pi Ones now, and you don't have to do anything in armbian-config. Just that one field in the dtb file is it.

For those who may be finding this thread later, I made some interesting progress today. The Orange Pi One has only one regular USB port, which, using OctoPi, you need for the printer. But it does have also a USB OTG, which you may call Micro USB, and I have never used it for anything. Initially I plugged in the camera to that with an adapter, and got nothing on lsusb at all. After some digging, I found the way to cure this. You have to edit the dtb file in the /boot/ dtb/ directory for your board. All the supported boards are in there. Then you have to convert that binary dtb file into text, with a program called dtc. pi@citrico-opione:/boot/dtb$ sudo dtc -I dtb /boot/dtb/sun8i-h3-orangepi-one.dtb -O dts -o /boot/dtb/sun8i-h3-orangepi-one.dts that gives you the dts file, which you can open in nano. pi@citrico-opione:/boot/dtb$ sudo nano sun8i-h3-orangepi-one.dts Find the code block that has dr_mode in it. On this board it is usb@1c19000. Change the value to host instead of otb. Then control x, y, enter to save the file. Then you have to convert it back to binary. You can make a backup of your original binary file first if you want, then do this: pi@citrico-opione:/boot/dtb$ sudo dtc -I dts /boot/dtb/sun8i-h3-orangepi-one.dts -O dtb -o /boot/dtb/sun8i-h3-orangepi-one.dtb then reboot. The micro usb is now a regular usb, and my gembird camera came up under lsusb. I also had enabled usb0 in the hardware options in armbian-config, but I don't know if I had to do that. I actually just enabled them all before finding this solution. Still stuck on the video though. Snapshots are working.

Another update. I was able to update OctoPi to 1.4.2 and the printer connected. It was on the second try actually, but it did connect, using the two AUTO settings. So @ldiaz it is working fine with no errors updating the base software and the plugins.

And get this. The snapshot works in octoprint, which is listed as this: http://127.0.0.1:8080/?action=snapshot That was after I switched the ffmpeg path to: /home/pi/ffmpeg_cedrus264_H3/ffmpeg

A few more details: pi@citrico-opione:~/ffmpeg_cedrus264_H3$ v4l2-ctl --list-devices cedrus (platform:cedrus): /dev/video2 USB2.0 PC CAMERA: USB2.0 PC CAM (usb-1c1b000.usb-1): /dev/video0 /dev/video1 pi@citrico-opione:~/ffmpeg_cedrus264_H3$ cd pi@citrico-opione:~$ v4l2-ctl --list-devices cedrus (platform:cedrus): /dev/ pi@citrico-opione:~$ v4l2-ctl -d /dev/video2 --list-formats --list-ctrls Codec Controls mpeg_2_slice_parameters 0x009909fa (unknown): type=103 flags=has-payload mpeg_2_quantization_matrices 0x009909fb (unknown): type=104 flags=has-payload h264_sequence_parameter_set 0x00990ce8 (unknown): type=110 flags=has-payload h264_picture_parameter_set 0x00990ce9 (unknown): type=111 flags=has-payload h264_scaling_matrix 0x00990cea (unknown): type=112 flags=has-payload h264_slice_parameters 0x00990ceb (unknown): type=113 flags=has-payload h264_decode_parameters 0x00990cec (unknown): type=114 flags=has-payload h264_decode_mode 0x00990ced (menu) : min=0 max=0 default=0 value=0 h264_start_code 0x00990cee (menu) : min=0 max=0 default=0 value=0 hevc_sequence_parameter_set 0x00990cf0 (unknown): type=120 flags=has-payload hevc_picture_parameter_set 0x00990cf1 (unknown): type=121 flags=has-payload hevc_slice_parameters 0x00990cf2 (unknown): type=122 flags=has-payload hevc_scaling_matrix 0x00990cf3 (unknown): type=123 flags=has-payload hevc_decode_mode 0x00990cf7 (menu) : min=0 max=0 default=0 value=0 hevc_start_code 0x00990cf8 (menu) : min=0 max=0 default=0 value=0 ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'ST12' (Sunxi Tiled NV12 Format, compressed) [1]: 'NV12' (Y/CbCr 4:2:0) USB2.0 PC CAMERA: USB2.0 PC CAM (usb-1c1b000.usb-1): /dev/video0 /dev/video1 I'm still working on it. These commands I got from @ldiaz working on my rpi cameras that didn't work. It seems like the gembird is a common camera though, and it seems like it should be working, but so far it isn't.

Hi guys. I've just spent yet another two hours trying to find an answer to my webcam problem and there does not seem to be an answer from what I can discern. Still working to try to get a camera to work with Octopi from what I have around. Strange thing I discovered that the USB OTG port on the Opi One does not seem to work, but when plugged into my single regular USB, I get this for the camera: pi@citrico-opione:~/ffmpeg_cedrus264_H3$ lsusb Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 1908:2310 GEMBIRD Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub It is one of the known working with mjpeg-streamer https://community.octoprint.org/t/usb-webcams-known-to-work-with-mjpg-streamer/21149 but the notes don't seem to be current. pi@citrico-opione:~/ffmpeg_cedrus264_H3$ ls /dev/video* /dev/video0 /dev/video1 /dev/video2 I have tried some of the old gits out there. My only ray of hope was when I did modprobe hid-gembird it did not error, just seemed to say ok. But still no webcam, just a different message, of/dev/video0: Device or resource busy instead of it not being a video capture device. So I"m out of ideas. Any help would be appreciated. Trying to find an inexpensive webcam solution for octopi using my Opi Ones.

FYI for anyone following this thread in the future, if you are trying to get the old standard orange pi camera (that Steven sells on Ali) to work with Armbian, as of right now it is not supported in the mainline kernel, and the legacy 3.4 kernel is deprecated because the repositories are no longer supported. So for now, they don't work. We'll have to put them away until they are cool and retro like vinyl records.

Thankyou.

Hi team. I am having a difficult time getting the standard Opi CSI camera to work on the newest mainline Armbian. I don't have the ability to use a legacy version because it is coupled with a preconfigured Octopi, thanks to @ldiaz. He says that Octopi will work with the camera once the system works with the camera, and I have not been able to get it to work. There are at least a dozen threads here about that camera, but most are dated. And the ones that aren't seem to talk more about performance, and they assume that your camera is working. I also saw one about overlays, which I have no idea how to deal with, or even what they are. Something tells me it just isn't this hard and that there must be some kind of way to deal with this easily, or it just isn't supported right now in this version and that's that. Either is fine. I'm old, and my brain hurts. Thanks in advance.

I caught one thing I hadn't tried from all the threads out there about the gc2035 (orange pi branded) camera. This is what it says. pi@citrico-opione:~/v4l2loopback$ v4l2-ctl -d /dev/video0 -D Driver Info: Driver name : cedrus Card type : cedrus Bus info : platform:cedrus Driver version : 5.4.45 Capabilities : 0x84208000 Video Memory-to-Memory Streaming Extended Pix Format Device Capabilities Device Caps : 0x04208000 Video Memory-to-Memory Streaming Extended Pix Format Media Driver Info: Driver name : cedrus Model : cedrus Serial : Bus info : platform:cedrus Media version : 5.4.45 Hardware revision: 0x00000000 (0) Driver version : 5.4.45 Interface Info: ID : 0x0300000c Type : V4L Video Entity Info: ID : 0x00000001 (1) Name : cedrus-source Function : V4L2 I/O Pad 0x01000002 : 0: Source Link 0x02000008: to remote pad 0x1000004 of entity 'cedrus-proc': Data, Enabled, Immutable

Ok thanks I'm going to keep digging with it. I don't see a guide by @@lex, just that thread that got hijacked, and I don't understand overlays at all at present, but I'll try to figure it out. To me right now the important thing was getting octopi going and being able to install the plugin for the raise cloud. It works fantastic, and I am over the top grateful for the help. The camera is a nice thing, but not a big deal with what I am trying to do with them right now. Eventually I'll get it.

That's like a smart people thread. I'm not one of those guys. They kind of hijacked the thread and the guy never tried the advice buried in there somewhere. Mine is that same orange pi camera though I think.

@ldiaz have you ever tried to get an rpi CSI camera to work with the camera interface? I have tried all of the stuff I could find on the forums sudo apt-get install v4l-utils and what I could understand from this thread: but still nothing, even from just sudo mplayer tv:// Going to try a USB camera now. I just happen to have a pile of those rpi cameras. #edit couldn't get USB camera to work either, but mplayer gave me a different error, and now I have /dev/video 0 1 and 2. #edit2 later found the service in the config script, enabled it, and it got a could not remove klipper service message, but the star was there when I went to check, so it apparently worked. but camera does not

I don't think he did. Octoprint came up but then wouldn't connect on the com port. I'm sure it could be monkey'd, but I didn't try. Today it took me two hours to navigate a plugin for raise cloud, but eventually got it by googling around for the error messages.

To others who may be following this thread or who will hit it later, the Orange Pi One image works right out of the box, but don't upgrade octoprint. We did it and it would no longer connect to the printer.

Well that was easy. Thanks a ton @ldiaz. My twin 17 year olds will now have a lot to work on next. Fun stuff.

Wow exciting @ldiaz I'm on it and will let you know. Thankyou.

So should I just assume this is maybe a future thing @ldiaz ? I saw @Igor took a look at it and liked it but did not comment. Maybe it'll make it into armbian-config at some point down the road. I have a few rpis that I can get started with so it isn't a huge deal. I just love to use Armbian and opis when I can for some reason. It's like my personal discovery or something.

That would be awesome @ldiaz. Thanks. It's funny I am friends with @Igor on FB and asked him if he knew you lol. You are not one of the usual suspects around the FB sbc groups. Again, thanks. Have a great weekend.

Yea you are probably young though. I'm 54, and wrote one of the first books on remote web publishing (in perl) back in 1996, and never had a computer course in my life. Those days are gone for me. My brain just doesn't want learn entire new things anymore. I had to ask my sysadmin the other day to remind me how to use nmap so I could find my pi on the network. At this point I'm just hoping that Mr. @ldiaz can make this thing work. I have a pile of Opi Ones from a failed project a couple years ago and I want to build a print farm for my twins. This would be a real gift for my lazy old brain.

I um don't know how to do a pull request. I am logged into github, but I don't understand any of the lingo it's asking me for. I'm a root 1234 yay it works kind of guy. Anything that breaks is just agony.

Thanks for answering @ldiaz. Yes for sure I would share it if I can get it to work. I made several images for Nacho at NextCloudPi before the Armbian guys made it part of armbian-config. I don't know how to share it on git, but I'll figure it out. I didn't alter the extra.sh at all. # Board Release BOARD=orangepione BRANCH=current RELEASE=buster # General configuration. KERNEL_ONLY="no" KERNEL_CONFIGURE="no" PROGRESS_DISPLAY="plain" BUILD_MINIMAL="no" BUILD_DESKTOP="no" INSTALL_HEADERS="no" # This setting for clean build CLEAN_LEVEL="make,debs,cache,sources" #CLEAN_LEVEL="make,debs,cache" # This setting for rebuilds #CLEAN_LEVEL="debs,extras" #CLEAN_LEVEL="" # Lang DEST_LANG="en_US.UTF-8" # output SEVENZIP="yes" COMPRESS_OUTPUTIMAGE="sha,7z"

I fixed it sorry.

Hi everyone. I tried to use this to build an image for an Opi One. It looked like it was going to work, but now it has thrown this error a couple times: Processing triggers for resolvconf (1.79) ... Errors were encountered while processing: selinux-policy-default E: Sub-process /usr/bin/dpkg returned an error code (1) [ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:239 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ o.k. ] Unmounting [ /home/vagrant/armbian/.tmp/rootfs-current-orangepione-buster-no-no/ ] [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:66 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated Connection to 127.0.0.1 closed. I can't find it now, but the last time I ran it, I searched for some of the error message and Igor had closed a case that was based on some environment quirk. But it didn't explain what that was, and it was closed. I tried to run the script as sudo and got a message that I wasn't the correct Vagrant user, so that didn't work. Just to let you know how thick skulled I am, I just tried to use armbianmonitor, and I'm on an x86 running Ubuntu 20.4. So yeah. Thanks for checking this out if you are reading this. I was blown away that this tool existed, and it's pretty new. Would be awesome if it worked for all the Armbian boards. I attached a zip file of the entire output. Here is the bottom in a pastebin: https://pastebin.com/Cud3EtRG octocitrico.zip