drunken-octopus / drunken-octopus-marlin

An Alternative (Unofficial) Marlin Firmware for AlephObjects Printers
GNU General Public License v3.0
34 stars 13 forks source link

April Release - Taz6 v3 BLTouch - Fails to upload(?) - Patreon Edition #13

Closed keawepoo closed 4 years ago

keawepoo commented 4 years ago

Steps to Reproduce

  1. Start Cura
  2. Update firmware

Expected behavior: To update the firmware...

Actual behavior: It just sits at "updating firmware"... For at least 5mins. After that I canceled the update.

Additional Information

https://imgur.com/a/xvHd3RX

marciot commented 4 years ago

The recommended flashing program for the Archim is BOSSA (https://www.shumatech.com/web/products/bossa).

With it, follow this procedure for flashing:

If you cannot connect to the serial port after this process, try the following:

keawepoo commented 4 years ago

Im sorry, I thought I had listed it as the stock board. Will this still work?

marciot commented 4 years ago

Oh, I'm sorry. No, those procedures are for the Archim board. For a stock (Rambo) board, you could try either one of these tools:

I've used the first tool, but not the second. Anyhow, the fact Cura isn't able to load the FW isn't really anything to do with Drunken Octopus. Have you tried asking for help in the Cura forums?

keawepoo commented 4 years ago

Its all good, It was my own oversight. What board is it listed as? Mega or Uno? Im using the xloader. Well I also tryed lulzbot one too and it failed. That being somewhat old I dont know if it would still be a Cura issue.

marciot commented 4 years ago

Mega.

keawepoo commented 4 years ago

Baub rate 57600 or 250000??

marciot commented 4 years ago

I think either will work, but 250000 preferred.

keawepoo commented 4 years ago

at 250000, it says that upload has failed... at 57600 it just stays at "uploading..."

Edit: Sorry it says "Can't open port" for 250000 and 57600.

marciot commented 4 years ago

Does the printer otherwise turn on? You may have blown fuses on the board or something. Make sure the BLTouch didn't short something out. I recommend disconnecting it, as well as anything else you might have connected to the board.

marciot commented 4 years ago

You could also reach out to Ultimachine for ideas. At this point, it doesn't seem like it's a firmware issue, but a hardware issue of some sort.

keawepoo commented 4 years ago

BLTouch isnt even connected yet... Ive tried to print via octoprint and it works. but ya will do. Thank you.

marciot commented 4 years ago

That's weird. Usually flashing is a fairly straightforward process, easier on the Rambo than the Archim. Not sure why your board is being problematic.

keawepoo commented 4 years ago

Well I do know that theres a EPROM issue... where it doesnt save anything. I think I posted awile back about it.

https://github.com/marciot/drunken-octopus-marlin/issues/10

But latter on I found more issues, when doing M500/1.

keawepoo commented 4 years ago

That's weird. Usually flashing is a fairly straightforward process, easier on the Rambo than the Archim. Not sure why your board is being problematic.

So I just flashed lulzbot firmware on and it worked... So that might be a issue with DO?

marciot commented 4 years ago

Weird. Can you try the regular TAZ 6 build from DO?

On Apr 8, 2020, at 5:10 PM, keawepoo notifications@github.com wrote:

 That's weird. Usually flashing is a fairly straightforward process, easier on the Rambo than the Archim. Not sure why your board is being problematic.

So I just flashed lulzbot firmware on and it worked... So that might be a issue with DO?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

keawepoo commented 4 years ago

I just did. I tryed the R10 standard Tilapia_SingleExtruder, That one failed. Then I tryed R9 standard Tilapia_SingleExtruder and it worked...

So it really looks like theres a issue over all in R10.

marciot commented 4 years ago

Interesting. I’ll see if I can look into it this weekend. Thanks.

keawepoo commented 4 years ago

Fixed with R11.