Page 1 of 1

Process Bug in 3.1

Posted: Tue Jun 07, 2016 5:33 pm
by greybeard
My DaVinci 1.0A is hacked and has Repeter 0.92 firmware.
In previous versions of s3d, printing directly from s3d or from exported gcode did not require any tweaking of process. Now, it requires fussing, as follows:
When printing, a message appears informing that DaVinci requires .3w file format, and won't print.
So, I see a file format input field in the Scripts tab of the process panel. I select gcode, then update the process and can print and/or export gcode - that part works. I also exported the process and factory file.
The BUG, is after exiting s3d, that file format field changes back to .3w. So, every time I want to print after exiting, I have to repeat this...

Re: Process Bug in 3.1

Posted: Wed Jun 08, 2016 6:49 am
by CompoundCarl
I've used repetier on mine as well. Just remove all of the post-processing commands since you don't need them with repetier. Then you can choose gcode for the file format and it will stay that way.

Re: Process Bug in 3.1

Posted: Wed Jun 08, 2016 11:03 am
by greybeard
Thanks.
There is/was only one post-script: {PREPEND "; total_filament = [total_filament_used]\n"} .
After deleting it, it worked as you indicated.

However, it brings up another BUG: The filament length is not correctly reported - it appears to add the length to previous remaining amount (not subtract it) until rebooting the printer, then the correct remaining length is shown in printers LCD.

Been using s3d for 18 months and for $150, I'm not impressed with their Quality Control - especially when it's sooo long between update releases.

And, what happens when clicking the toolbar and un-selecting the check-mark? As expected, the toolbar goes away but, only way to get toolbar back it to Quit and Restart s3d.

Re: Process Bug in 3.1

Posted: Wed Jun 08, 2016 2:40 pm
by CompoundCarl
It sounds like you're doing something wrong, because I have the correct filament length in all my files and haven't seen any of these problems on my da vinci running Repetier. So if you're seeing an issue, it's likely you have something setup differently.

Might help if you describe exactly what steps your taking and provide some sample files

Re: Process Bug in 3.1

Posted: Wed Jun 08, 2016 4:17 pm
by greybeard
Build stats indicate job will use 0.23m

Before printing: LCD displays current amount of FF printed = 56.0m (attached)

After print completed, LCD displays amount printed = 56.4m (attached)

After printer re-boot, LCD displays amount printed = 56.2m (attached)

Limit of three file attachment so, if you do want the process fff, I'll add it to follow-up post. But, these images pretty well explain it...

Re: Process Bug in 3.1

Posted: Thu Jun 09, 2016 8:21 am
by CompoundCarl
You're using the repetier firmware, so you might need to look and verify what exactly it uses to determine the filament usage for each file. Is it calculated from the actual printing moves in the gcode or are they using something else? Perhaps they are actually using the filament tag (which seems silly since the firmware is already tracking the extruder movements internally and would already know exactly how much was used)

Re: Process Bug in 3.1

Posted: Thu Jun 09, 2016 11:22 pm
by Anthrobones
Graybeard,
I have a setup exactly like yours, and I saw the same error message as you.. however, after upgrade, I cannot connect to my printer any longer (see pic).. I've tried the checkbox for 'accept M101 commands' under g-code, but still the same thing.. I have tried to go back to 3.02, but the same thing again. Never had this problem before... any ideas?

and I agree, $150 for this software, and after update, I can't use it any longer :/ NOT cool.
Error When Connect.JPG

Re: Process Bug in 3.1

Posted: Fri Jun 10, 2016 4:30 am
by CompoundCarl
There's nothing that would be different if you go back to version 3.0.2 unless you changed your profile. So if you want to use 3.0.2, you might also want to go back to Help > Configuration Assistant, and make sure you download a new fresh profile for the 1.0.

Something that also helped me was going to Tools > Firmware Configuration, clicking on the Communication tab, and enabling hardware flow control. After you do this, you may need to click Export at the top to save a new configuration (more info about why that is needed here: https://www.youtube.com/watch?v=NYPUAqT4UyI)

Re: Process Bug in 3.1

Posted: Fri Jun 10, 2016 11:15 am
by greybeard
I had dropout problems in version 2.x but resolved it by changing the control flow, cache, timeout...
The settings in attached are those that have continued to work for me...