search

Robo3D / Meta-Reader

0 stars 2 forks source link

Capture onboard slicing meta data #3

Open victorevector opened 7 years ago

victorevector commented 7 years ago

Support for capturing onboard slicing meta data

victorevector commented 7 years ago

Update related to QA testing

QA Pass # 15 QA User Victor QA Date 3/22/2017 QA App Version RoboLCD 1.5.0 MetaReader 1.0.7 QA RoboOS Version 1.3.0-r2.1 QA Octoprint Version 1.3.1-robo QA Firmware Version r2-1.1.6

Issue

Inconsistent capture of onboard slicing meta data. Below you will find the stl files i sliced. "Yin_Yang..." is missing layer count. "Razor_Holder" is missing infill, layer height, and layer count.

Razor_holder.STL.zip Yin_Yang_Tea_candle_holder.STL.zip

AllenMcAfee commented 7 years ago

I tested the meta reader on 3 R2s and 1 C2 and found an inconsistency between the meta data displayed on the C2 as compared to the R2s. Each R2 successfully showed the meta data from Simplify3D, while the C2 did not show any meta data.

This was sliced with the same Simplify profile (for C2) that works on both the R2 and the C2. It was also tested with 3 different sliced files, with the C2 failing the meta read.

Meta Reader version: 1.0.7 img_0220

img_0221

victorevector commented 7 years ago

@AllenMcAfee Can you upload some of the gcode files in question? It'll aide with the testing process.

Ximidar commented 7 years ago

Allen, could you list your exact testing process? I'm wondering how long you waited from upload, to viewing the meta data. Did you back out and re look at the meta data? Basically I would like to know how many chances you gave the meta reader to produce results before it qualifies as a failure

On May 18, 2017 6:36 PM, "Victor E F" notifications@github.com wrote:

@AllenMcAfee https://github.com/allenmcafee Can you upload some of the gcode files in question? It'll aide with the testing process.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/Robo3D/Meta-Reader/issues/3#issuecomment-302585474, or mute the thread https://github.com/notifications/unsubscribe-auth/AMIt8AHR5YF87MthVOWL7xUAq9Ffwamcks5r7PIugaJpZM4MS4bT .

AllenMcAfee commented 7 years ago

@Ximidar I am aware of the lag between loading these values, and did check it at least 3 times during a 2 hour print. My test was as follows:

Results All R2s showed the correct Meta data for the 2 separate Simplify-sliced GCODE files. The single C2 that was tested only showed Z offset.

Given the issues with Cura 2.5 we are seeing (missing meta data values in footer of file), I wanted to test the only 3rd party software we are currently using.

Ximidar commented 7 years ago

Could you upload the files you used in a zip and post them here?

Ximidar commented 7 years ago

the build time failed to populate because when there's only one hour in the build time it changed the meta data

;   Build time: 12 hours 10 minutes
;   Build time: 1 hour 24 minutes