A10M Firmware?

[JaredBurton]

Hello,

In my efforts yesterday to figure our what was wrong with my A10M (bed was shorting, has been fixed) I flashed the firmware. It looks like I had a bad copy of the firmware, as now it is not reading the gcode correctly. I found and flashed it with firmware for the A10, and now it reads right, but I do not have functionality of the second filament. Does anyone have a good copy of the A10M firmware?

[aarli]

I compiled it today.
https://github.com/harlyh/Prusa_I3_3Dpr ... 3d%20touch

[JaredBurton]

I compiled it today.
https://github.com/harlyh/Prusa_I3_3Dpr ... 3d%20touch

Thank you!

I have uploaded the new firmware, seems like its alright for now. Except it does not return home how I expect it to. After homing the bed and left/right, it moves to the center and moves up and stops, then up again and stops. I do not have the auto leveling sensor installed, but I see there are now options for it. Would this have anything to do with it?

[aarli]

Oh, I get what you're saying. I haven't compiled the non 3d touch version of it yet. Give me 10 minutes

[JaredBurton]

Oh, I get what you're saying. I haven't compiled the non 3d touch version of it yet. Give me 10 minutes

Fantastic, thank you so much! Which version of Arduino is needed? I have 1.8.5 or 1.8.7. Or would it be best to use Xloader?

[aarli]

Here ya go.
https://github.com/harlyh/Prusa_I3_3Dpr ... 3d%20touch

Please note that this hasn't been properly tested. But the same firmware on my regular A10 printer works fine.
I was actually going to do some more thorough work on this firmware on the weekend. The regular A10 version has many
new and experimental features enabled, which actually work quite fine. Going to open these up in A10M too...

But there are some discrepencies between my previous A10 config and the one Geeetech has provided with 1.1.8, so I need to do some side-by-side comparison to figure out which ones make sense and which ones don't.

I use Arduino 1.8.5 but all my firmware uploads are going through Repetier Server (Running on Raspberry pi) and printers are connected to it.
Kind of remote printing, monitoring and control from another room

chrome_2018-10-11_20-27-27.png (103.69 KiB) Viewed 59570 times

[JaredBurton]

Here ya go.
https://github.com/harlyh/Prusa_I3_3Dpr ... 3d%20touch

Please note that this hasn't been properly tested. But the same firmware on my regular A10 printer works fine.
I was actually going to do some more thorough work on this firmware on the weekend. The regular A10 version has many
new and experimental features enabled, which actually work quite fine. Going to open these up in A10M too...

But there are some discrepencies between my previous A10 config and the one Geeetech has provided with 1.1.8, so I need to do some side-by-side comparison to figure out which ones make sense and which ones don't.

I use Arduino 1.8.5 but all my firmware uploads are going through Repetier Server (Running on Raspberry pi) and printers are connected to it.
Kind of remote printing, monitoring and control from another room

Well, it looks like I'm still having the same issue. Not exactly sure what to do, I made a short video showing what is happening.
https://youtu.be/abErLyEbdXA

Any help or ideas would be appreciated. If nothing else, I'll wait til the new firmware has been all tested and try again next week.

[aarli]

Thanks for feedback. Sorry to see that.

I think I know what's wrong.
I guess I have to re-flash my printer with non-3d-touch firmware to verify it. But don't worry. I guarantee when I'm done you'll be happy
But... You must wait till I get back home.

I promise I'll make fixing this priority #1.

In theory I could even fix it right now (as I have remote access to my home pc where everything is set up) and you could try again.
Otherwise it's gonna take exactly 5 hours before I can test myself (it's 1pm, I have to be in the office till 5:30 + need 20 minutes to ride home)

If its urgent, let me know

EDIT: I'm going to compile Geeetech's own 1.1.8 (no 3d touch) for you, and post the hex file here, so you get a working printer already. I can then later concentrate on 1.1.9

EDIT2: I just made a decision to write some code this weekend, to implement touch sensor's auto-detection (+ menu settings on touch sensor: Auto-Detect, Installed, Not Installed (with AD being the firmware default). It makes absolutely no sense to have 2 different firmware's only because of touch sensor.
So, hopefully my update will get pulled back to Geeetech and Marlin in general.
Come to think about it, it would even be possible to auto-detect sensor needle tip's relative X, Y, Z offset from printing nozzle's tip.

EDIT3: The original non-3d-touch version 1.1.8 hex is here

[JaredBurton]

That did the trick!!! Thank you so much! Now I have a working printer, and I'm running a test print as we speak. Looks like the original firmware will do for now, and I'll be looking forward to seeing what you do with the new firmware, once its been tested and is working.

Thank you again so much for your help!

[_kaktus_]

...

EDIT2: I just made a decision to write some code this weekend, to implement touch sensor's auto-detection (+ menu settings on touch sensor: Auto-Detect, Installed, Not Installed (with AD being the firmware default). It makes absolutely no sense to have 2 different firmware's only because of touch sensor.
So, hopefully my update will get pulled back to Geeetech and Marlin in general.
Come to think about it, it would even be possible to auto-detect sensor needle tip's relative X, Y, Z offset from printing nozzle's tip.

...

Hi


Wouldn't it be better to introduce conditional compilation with one parameter
Depending on its value, part of the code could be omitted for compilation. What still requires a lot of work to adjust the whole code.

Then you have two firmware versions in one source. When making changes, it is very convenient and includes both versions at once.