Posts made by obokenpally
-
RE: HOMES fine, CRASHES when starting print
@gloomyandy I also noticed the output in putty when connected to dwc, has a bunch of connected establishment codes and a bunch of continueing code that gets generated,basically stating the printer is connected blah blah.
When i have dwc off, and just using putty there are no lines being generated from consol. Its like my printer only has its brains. When dwc is connected, ( could i have screwed up setup that bad? ) or is that normal?
-
RE: HOMES fine, CRASHES when starting print
keeps gettin flagged as spam, i messaged you in discord, and sent a TXT of the output during the g28
-
RE: HOMES fine, CRASHES when starting print
@gloomyandy Debugging enabled for modules: GCodes(3)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) WiFi(14) Display(15) LinuxInterface(16)
USB: M111 P16 S1
Debugging enabled for modules: GCodes(3) LinuxInterface(16)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) WiFi(14) Display(15)
USB: G28( G28 didnt do anything btw )
-
RE: HOMES fine, CRASHES when starting print
@gloomyandy i can use m122 in putty, but g28 does nothing again
-
RE: HOMES fine, CRASHES when starting print
@gloomyandy when i enter g28 in dwc is homes perfectly fine
-
RE: HOMES fine, CRASHES when starting print
@gloomyandy nothing happens it says sending, but no movement. Using pronterface and usb cable
-
RE: HOMES fine, CRASHES when starting print
@gloomyandy m122
=== Diagnostics ===
RepRapFirmware for LPC176x based Boards (biquskr_1.4) version 3.1.1-14 running on LPC176x at 120Mhz
Used output buffers: 1 of 16 (10 max)
=== RTOS ===
Static ram: 4468
Dynamic Memory (RTOS Heap 5): 1704 free, 1680 never used
Exception stack ram used: 408
Never used ram: 276
Tasks: HEAT(blocked,1372) MAIN(running,1840) IDLE(ready,84)
Owned mutexes:
=== Platform ===
Last reset 00:01:53 ago, cause: [power up]
LPC Flash Slot[66]:
Last software reset at 2020-11-15 11:49, reason: User, spinning module LinuxInterface, available RAM 252 bytes (slot 0)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0042a000 BFAR 0xe000ed38 SP 0x10000018 Task MAIN
Stack: 00000004 100010d0 2007e1e0 00000001 000462c7 00000004 10000d40 2007e1e0 2007d1dc 00000004
Stack: 00040205 80000000 00000000 00000000 2009c020 00000001 00040caf 00040d80 41000000 10003f68
Stack: 00000000 00000000 10003048
Error status: 0
Driver 0: standstill, SG min/max 0/388, error r/w 0/0, ifcnt 16, cnt r/w 7389/16, timeout 0, failedOp 0xff
Driver 1: standstill, SG min/max 0/398, error r/w 0/0, ifcnt 16, cnt r/w 7389/16, timeout 0, failedOp 0xff
Driver 2: standstill, SG min/max 0/126, error r/w 0/0, ifcnt 16, cnt r/w 7389/16, timeout 0, failedOp 0xff
Driver 3: standstill, SG min/max 0/118, error r/w 0/0, ifcnt 16, cnt r/w 7389/16, timeout 0, failedOp 0xff
Driver 4: standstill, SG min/max 0/0, error r/w 0/0, ifcnt 14, cnt r/w 7390/14, timeout 0, failedOp 0xff
Date/time: 2020-11-15 11:42:47
Slowest loop: 66.69ms; fastest: 0.30ms
Watchdog timer: 7492301/7500000
Step timer: target 102676553 count 113431450 delta -10754897 late 0
USBSerial connected 0
ADC not ready 0 ADC error threshold 10 ADC Init 1
Ints: 45452; Calls 136268; fast: 2uS; slow 20uS adj 0 bad 0 big delta 0
PWM Channels
state 0 next 55863 on 120000(0) off 120000(0) pin 2.5
state 1 next 55863 on 60000(1) off 60000(1) pin 2.3
state 2 next 55863 on 60000(0) off 60000(0) pin 2.7
state 3 next 55863 on 120000(0) off 120000(0) pin 2.4
Delta 55863 Start 0 End 4
=== Move ===
Hiccups: 0, FreeDm: 100, MinFreeDm: 98, MaxWait: 77441ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 8, completed moves: 8, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0, chamberHeaters = -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is ready with "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon* is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 12ms ago
RX/TX seq numbers: 2933/2934
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.1.1
Code buffer space: 2048
Configured SPI speed: 8000000 Hz
Full transfers per second: 31.02 -
RE: HOMES fine, CRASHES when starting print
@Phaedrux yes i have used the probe for a while, and tested that it is registering within its range in dwc ect as far as im concerned the probe is in 100% working order
-
HOMES fine, CRASHES when starting print
Cr10s pro, skr1.4 turbo, pi b3 , 4mm inductive probe
Homes X Y&Z perfectly while cold, and hot.
But when i start a print it will home X and Y
Sucessfully. Than it will move to center for the Z homing, ( this is where is will just continue to go down.. and not stop )
There are NO offsets in slicer or dwc
Starting gcode only has ( G28 )