Poli Log - Revision history

Poli at 13:16, 8 February 2020

2020-02-08T13:16:16Z

← Older revision		Revision as of 13:16, 8 February 2020
Line 26:		Line 26:
	*D3D workshop		*D3D workshop
	*Plastic recycling shredder and extruder - experiment with recycled PET and virgin PETG coextrusion		*Plastic recycling shredder and extruder - experiment with recycled PET and virgin PETG coextrusion

			=2/8/20=
			Had ordered new PNP and NPN induction sensors, but post office didn't deliver them. Had some unhelpful but sympathetic phone calls, so had to re-order. Received sensors.

	=1/4/20=		=1/4/20=

Poli at 20:03, 5 January 2020

2020-01-05T20:03:58Z

← Older revision		Revision as of 20:03, 5 January 2020
Line 26:		Line 26:
	*D3D workshop		*D3D workshop
	*Plastic recycling shredder and extruder - experiment with recycled PET and virgin PETG coextrusion		*Plastic recycling shredder and extruder - experiment with recycled PET and virgin PETG coextrusion

			=1/4/20=
			Was having problems with losing sound when OSE linux went to sleep. Tried messing with Alsa, and reinstalling OSE linux but continued to have problems. Wanted to upgrade to ubuntu 18.04 hoping to fix the issue, but didn't have space in partition for download. Used gparted repartition hard drive and reinstalled OSE linux. When running sudo apt upgrade started getting errors of E: Sub-process /usr/bin/dpkg returned an error code (0) referencing freecaddaily19-python3... and libocct7.3. Reinstalled without updates or internet connect. Removed freecad (https://installlion.com/ubuntu/xenial/universe/f/freecad/uninstall/index.html) and Freecad daily (http://www.pcds.fi/downloads/applications/graphics/cad/freecad/repository/freecad.daily.repository.html). Now I could upgrade the system and update to ubuntu 18.04. Upgrade went fine and sound seems good, GUI is gnome while I had come to like unity, seems a little more sluggish than 16.04. installed freecad 0.18, looks older than freecad 0.16 but didnt test too much. Thinking about installing OSEv0.1 as a third OS but need to add a hard drive first.

	=12/14/19=		=12/14/19=

Poli at 20:00, 14 December 2019

2019-12-14T20:00:33Z

@@ Line 54: / Line 54: @@
 < PID Autotune start
 < PID Autotune failed! timeout
 > M303 E0 S200 C3
 < PID Autotune start
@@ Line 71: / Line 70: @@
 < echo:Steps per unit:
 < echo:  M92 X80.00 Y80.00 Z80.00 E161.30
 < echo:  M203 X300.00 Y300.00 Z10.00 E25.00
 }}

Poli at 19:58, 14 December 2019

2019-12-14T19:58:45Z

← Older revision		Revision as of 19:58, 14 December 2019
Line 71:		Line 71:
	< echo:Steps per unit:		< echo:Steps per unit:
	< echo: M92 X80.00 Y80.00 Z80.00 E161.30		< echo: M92 X80.00 Y80.00 Z80.00 E161.30
	< echo:Maximum feedrates (mm/s):		< echo:Maximum feedrates (mm-s):
	< echo: M203 X300.00 Y300.00 Z10.00 E25.00		< echo: M203 X300.00 Y300.00 Z10.00 E25.00
	< echo:Maximum Acceleration (mm/s2):		< echo:Maximum Acceleration (mm-s2):
	< echo: M201 X3000 Y3000 Z100 E10000		< echo: M201 X3000 Y3000 Z100 E10000
	< echo:Accelerations: P=printing, R=retract and T=travel		< echo:Accelerations: P=printing, R=retract and T=travel
	< echo: M204 P3000.00 R3000.00 T3000.00		< echo: M204 P3000.00 R3000.00 T3000.00
	< echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)		< echo:Advanced variables: S=Min feedrate (mm-s), T=Min travel feedrate (mm-s), B=minimum segment time (ms), X=maximum XY jerk (mm-s), Z=maximum Z jerk (mm-s), E=maximum E jerk (mm-s)
	< echo: M205 S0.00 T0.00 B20000 X20.00 Y20.00 Z20.00 E5.00		< echo: M205 S0.00 T0.00 B20000 X20.00 Y20.00 Z20.00 E5.00
	< echo:Home offset (mm)		< echo:Home offset (mm)

Poli at 19:57, 14 December 2019

2019-12-14T19:57:29Z

@@ Line 54: / Line 54: @@
 < PID Autotune start
 < PID Autotune failed! timeout
 }}

Poli: /* 12/14/19 */

2019-12-14T19:26:08Z

12/14/19

← Older revision		Revision as of 19:26, 14 December 2019
Line 28:		Line 28:

	=12/14/19=		=12/14/19=
	Designed MoClo vector first vector series (levels 0,1,2). Working on D3D, z-probe when plugged in still reads triggered regardless of sensor being activated or not, hot end is having trouble reaching temperature. Disassembled a bit and tightened heater block, hotend, and heat break, hope heater block isnt too close to the heat sink but is too stuck to loosen. Able to use nozzle fan with M106 but immediately halts heating. Disconnected heatsink fan allows hotend to get too temperature. Used		Designed MoClo vector first vector series (levels 0,1,2). Working on D3D, z-probe when plugged in still reads triggered regardless of sensor being activated or not, hot end is having trouble reaching temperature. Disassembled a bit and tightened heater block, hotend, and heat break, hope heater block isnt too close to the heat sink but is too stuck to loosen. Able to use nozzle fan with M106 but immediately halts heating. Disconnected heatsink fan allows hotend to get too temperature. Used M303 E0 S200 C3 to autotune PID, worked without extruder fan but fails with fan going. Research says fan is always on and not adjustable. Ordered replacement Z-probe parts. Not sure if running without fan will be okay, large thermal mass to absor heat but don't want filament to melt above heat break.

	{{Quote\|		{{Quote\|
Line 55:		Line 55:
	< PID Autotune failed! timeout		< PID Autotune failed! timeout
	}}		}}




	=12/7/19=		=12/7/19=

Poli at 19:23, 14 December 2019

2019-12-14T19:23:30Z

← Older revision		Revision as of 19:23, 14 December 2019
Line 30:		Line 30:
	Designed MoClo vector first vector series (levels 0,1,2). Working on D3D, z-probe when plugged in still reads triggered regardless of sensor being activated or not, hot end is having trouble reaching temperature. Disassembled a bit and tightened heater block, hotend, and heat break, hope heater block isnt too close to the heat sink but is too stuck to loosen. Able to use nozzle fan with M106 but immediately halts heating. Disconnected heatsink fan allows hotend to get too temperature. Used		Designed MoClo vector first vector series (levels 0,1,2). Working on D3D, z-probe when plugged in still reads triggered regardless of sensor being activated or not, hot end is having trouble reaching temperature. Disassembled a bit and tightened heater block, hotend, and heat break, hope heater block isnt too close to the heat sink but is too stuck to loosen. Able to use nozzle fan with M106 but immediately halts heating. Disconnected heatsink fan allows hotend to get too temperature. Used

	{{		{{Quote\|
	< M503< M301 P22.20 I1.08 D114.00		< M503< M301 P22.20 I1.08 D114.00
	< M303 E0 S200 C3		< M303 E0 S200 C3

Poli at 19:22, 14 December 2019

2019-12-14T19:22:49Z

@@ Line 26: / Line 26: @@
 *D3D workshop
 *Plastic recycling shredder and extruder - experiment with recycled PET and virgin PETG coextrusion
 =12/7/19=

Poli: /* 12/7/19 */

2019-12-08T03:44:59Z

12/7/19

← Older revision		Revision as of 03:44, 8 December 2019
Line 33:		Line 33:

	Using M119 command to try to figure out what is going on, see diagram below. Worried it is a hardware problem on the board. Thought using the 6th pin would work to at least make the z-max triggerable and then marlin update could make that input the z-min. Not sure how to further troubleshoot.		Using M119 command to try to figure out what is going on, see diagram below. Worried it is a hardware problem on the board. Thought using the 6th pin would work to at least make the z-max triggerable and then marlin update could make that input the z-min. Not sure how to further troubleshoot.

			Moved Y-end stop from y-max to z-min. Reads triggered z-min when unpressed but open when pressed. Suggests a firmware and possibly new sensor would fix the issue.

	<html><img src="https://docs.google.com/drawings/d/e/2PACX-1vQ4qaPmue7rtSgJPDqphu8Ns8xntdOGUvlmiVVpgqXziq2JYaM685cpLQjDpo-o8_6r_Q1Ef4_xPvBh/pub?w=960&h=720"></html>		<html><img src="https://docs.google.com/drawings/d/e/2PACX-1vQ4qaPmue7rtSgJPDqphu8Ns8xntdOGUvlmiVVpgqXziq2JYaM685cpLQjDpo-o8_6r_Q1Ef4_xPvBh/pub?w=960&h=720"></html>


	=12/1/19=		=12/1/19=

Poli at 23:36, 7 December 2019

2019-12-07T23:36:34Z

← Older revision		Revision as of 23:36, 7 December 2019
Line 42:		Line 42:
	[[File:End stop extension flat.fcstd]]		[[File:End stop extension flat.fcstd]]

	(Wife) crimped the ends of the new and old z-axis sensors, using https://www.amazon.com/gp/product/B07CVYPDGS. New sensor still doesn't work, but old sensor does (though brown wire is loose). Only problem with the old sensor is the thread are too big to fit through holder so it is insecure. Tried testing setup, but z-axis sensor is not causing bed to stop and up/down directions are flipped (!?). Homing is going down. Tried using M562 Z but it doesn't work, even with M500 and a restart. Flipping motor wires on arduino did work to correct direction but sensor still doesn't cause bed to stop raising. M119 says x- is min, y is max and z is ~~max (i think - will need to check again)~~.		(Wife) crimped the ends of the new and old z-axis sensors, using https://www.amazon.com/gp/product/B07CVYPDGS. New sensor still doesn't work, but old sensor does (though brown wire is loose). Only problem with the old sensor is the thread are too big to fit through holder so it is insecure. Tried testing setup, but z-axis sensor is not causing bed to stop and up/down directions are flipped (!?). Homing is going down. Tried using M562 Z but it doesn't work, even with M500 and a restart. Flipping motor wires on arduino did work to correct direction but sensor still doesn't cause bed to stop raising. M119 says x- is min, y is max and z is min.

	=11/27/19=		=11/27/19=