Can someone tell me a good way to determine what version of kamikaze is on my BBB? The flashing process is very inconsistant so i can’t tell if it flashed correctly. Im not getting the 4 lights at the end, but ‘sometimes’ it will turn itself off after flashing. I can log into octoprint. But i need to know if the flash really worked.
Secondly, im trying to go through the wifi steps in the wiki and that isn’t working at all. Even tho it wasn’t mentioned i did eventually figuer out i needed to type “connmanctl” first. however the first command after that does nothing. scan wifi does nothing, services does nothing, agent on DOES work. “connect wifi_dc85de828967_38303944616e69656c73_managed_psk” doesn’t work .
here’s a screenshot towards the end showing some of the commands
no its the 2.0.8 or whatever ‘stable’ version. i reflashed yet again, but recorded it with my camera and i got 4 solid lights and it turned itself off. I also ftp’d into it and see files listed for the 10th month of 2016 so it appears the flash worked.
and after editing the file the guide doesn’t say anything else…i rebooted, tried to ping google, didn’t work, so i dunno i have a wiki and a guide that doesn’t work at all
well one of the main reasons i picked this board over all the others was because of wifi/octoprint. I wanted to easily be able to have it setup in a different room without messy cords. I seen the wiki pages and thought ok they have it all figuered out, just follow the steps and it will be a snap…i did my research and tried to find a wifi stick that was easily compatible, and seen links like this http://davenelson.com/beaglebone-black-wifi-adapter-wna1100/
now 2 days straight going through the ‘arch wiki’ and doing stuff like this https://wiki.debian.org/ath9k , and then realizing i have no idea how to install the firmware to the doogle after reading stuff like this https://github.com/qca/open-ath9k-htc-firmware and i don’t even know if im barking up the right or wrong tree…
seriously thinking i should just sell this on ebay at this point, but i bent 4 pin’s on the replicape doing all the reflashes (i know u can flash maybe with the cape on ,but the instructions say to hold the button which means having it off)
anyways this is all very very annoying and i havn’t even gotten to the ‘redeem’ page yet on the wiki…its going to take 4 years to get this thing running
Also issues with USB dongles is why 2.1 RC was pushed forward. We’re working on a way to get a version of kamikaze to be sent from a gcode command but it’s not ready yet
well here’s the terminal where i tried, nothing happened and this is after a fresh flash and apt-get update and upgrade. did i do something wrong trying to load them?
last night after alot of tinkering i did manage to get the ‘scan wifi’ to work, and when i tried to connect it asked for a passphase but it wouldn’t connect with the password. I wasn’t sure what i did to get it working that far so i decided to do the reflash and start from scratch because ill have to do this every time i update kamikaze.
basically what im thinking is the ath9k driver needed to be installed, and that let it work a little bit, but i have to get the ‘firmware’ part installed to really get it working and thats the part i don’t know how to do. Also isn’t there supposed to be a debian GUI? ive tried repeatedly to VNC into this and i keep getting a terminal instead of a GUI. i was going to try installing the wifi via the GUI
maybe i should try the 2.1 version? or can someone walk me through getting the firmware file and putting it in the right folder? i can ftp into it but it wouldn’t let me modify files, maybe i needed ftp in as root.
ok i just tried 2.1RC, 2 mins setting it up and it worked instantly, that is more like it. just hope i don’t run into problems being RC. The reason i didn’t start out with this version is i read a few scary bugs in the comment section
So the bugs are purely fixable and nothing that should stop you from at least printing. And once you have redeem configured just save your http://local.cfg and when the final 2.1.0 comes out you can flash it without having to worry about how long it’ll take to reconfigure everything.
Then take the settings you modified and put them in a http://local.cfg file. You really shouldn’t modify the printer config directly, because it would get overwritten by a redeem update.
That’s why I updated the wiki. If it’s a printer.cfg that you created, it’s fine. But if you’re updating the settings for a pre-existing printer.cfg it will get over-written later. That’s why if you’re using any printer type previously defined in Redeem (core XY, cartesian, i3, mendelmax, etc.) you should only change settings in local.cfg and not in your local version of printer.cfg. The printer.cfg defines a type of printer, the local.cfg is specific to your hardware, if that makes sense?
Jon, I totally agree with you an with the files hierarchy. It works. If you build 3d printer from scratch with one of popular kinematics good practice I think, is to copy one of the printer.cfg and edit or make new with specific parameterers there. In this case you can make you specification changes in printer.cfg and save it on computer before reflash/update. After reflashing you need only to upload you specific printer.cfg. Updating existing printer.cfg you can do by the same - copying and making new specific printer.cfg. Then you don’t need to use local.cfg - some another level in hierachy. With using local.cfg or only copied printer.cfg after update anyway you need to paste or upload your configuration or file. You always have something to upload or paste. Difference for me is that local.cfg can be edited directly in Octoprint without upload what is big advatage when you test your printer configurations. When it’s done you can make approved printer.cfg and use it. This is my opinion when I use Replicape for the custom printer.
ok so is there a reason why im not seeing any printer profiles in octoprint? the stable version had the printer profiles like corexy ect, but i can’t find them in this version.
in settings under cura, there is a button to ‘test’ the cura folder, it says path does not exist. i ftp in and look in this folder and i see nothing named cura…
Also upon logging into octoprint it says there is an update to kamikaze, “Kamikaze: unknown
Installed: Commit a4485840f820ddf8c3a77a0df0eb1906eb322322
Available: Commit a77ee3aa250a304e2dc1a8d5d39169480fcd244e”
i try to install and it says
" Updating, please wait.
dd: failed to open ‘/dev/mmcblk0’: Permission denied
dd: failed to open ‘/dev/mmcblk0’: Permission denied
** Updating Kamikaze **
** install U-boot**
The update did not finish successfully. Please consult the log for details."
So i go back to the wiki page and copy/paste all the commands under “update packages” again. Then i put the commands for "Manual installation of package feed "
i log back in to octoprint, the ‘update’ still doesn’t work. i look in curaengine, and the folder still fails the ‘test’, but now i have 3 printer profiles, kossel_mini_02, prusa_i3_02, thing_02. But no corexy? I do spot a maxcorexy in the redeem part.
But i assume none of those cura profiles will work with corexy. Maybe im wrong but it seems like something is just wrong or installed wrong?
I just relogged into octoprint and go to the curaengine and now the profiles are gone again…redeem profiles are still there, but magically the 3 that were in cura gone…seriously what is going on
