I read how the duet and archim use same processor and between my two printers i like the duet reprap firmware way better than my Archim with marlin4due. But i cant find any ware how to convert my firmware on my archim and dont want to spend another cple hundred for another duet board when my archim is basically same thing
reinstalled config file on sd card and works now
i installed new y endstop switch so i used the rrf configeration tool like i have many times before. but this time after installing new settings, i can get connected on web interface control but each time go to setting i get unconnected and this error
Communication Error
An AJAX error has been reported, so the current session has been terminated.
Please check if your printer is still on and try to connect again.
Error reason: SyntaxError: Unexpected token a in JSON at position 512
12:41:17 PMM122
=== Diagnostics ===
Used output buffers: 3 of 32 (10 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19 running on Duet WiFi 1.0
Board ID: 08DDM-9FAM2-LW4SD-6JKFL-3S86L-KJW3X
Static ram used: 21176
Dynamic ram used: 95928
Recycled dynamic ram: 1680
Stack ram used: 1304 current, 5880 maximum
Never used ram: 6408
Last reset 00:24:05 ago, cause: power up
Last software reset reason: User, spinning module GCodes, available RAM 7344 bytes (slot 4)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 31.8, current 40.6, max 40.9
Supply voltage: min 11.9, current 12.1, max 12.3, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: standstill
Driver 3: standstill
Driver 4: standstill
Date/time: 2017-08-27 12:41:16
Slowest main loop (seconds): 0.009727; fastest: 0.000000
=== Move ===
MaxReps: 2, StepErrors: 0, FreeDm: 240, MinFreeDm 238, MaxWait: 1695ms, Underruns: 0, 0
Scheduled moves: 10, completed moves: 10
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heater = 0, chamber heater = -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
Network state is running
WiFi module is connected to access point
WiFi firmware version 1.19
WiFi MAC address 5c:cf:7f:ee:63:0e
WiFi Vcc 3.10, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39152
WiFi IP address 10.0.0.163
WiFi signal strength -55dBm
HTTP sessions: 1 of 8
Socket states: 2 0 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
trying set up duet control features first one is to extrude 5mm filament, is there way to do it with heaters off
; Extrude 5mm filament
T0
G1 E5 F300
k working thank you
; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves
M555 P1 ; Set firmware compatibility to look like RepRapFirmare
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X200 Y200 Z200 S0 ; Set axis maxima
G31 P600 X0 Y0 Z2.26 ; Set Z probe trigger value, offset and trigger height
M557 X15:185 Y15:185 S20 ; Define mesh grid
ya changed the z to 2.26 if that was right place
i thought somthing in hear should state that or be changed to match, or do i get rid of this file also
; homez.g
; called to home the Z axis
G91 ; relative mode
G1 Z4 F200 ; raise head 4mm to ensure it is above the Z probe trigger height
G90 ; back to absolute mode
G1 X100 Y100 F2000 ; put head over the centre of the bed, or wherever you want to probe
G30 ; lower head, stop when probe triggered and set Z to trigger height
did all of that and tested good if mean the paper test and numbers changing 400s to 500s, its working and can calabrate it and works right reading the bed and setting the g31 command.
but any time i have to rehome z it dosnt stop on time even after lights up
have mosly working now exept after reboots wene have to home z the red light is flashing and reading but keeps going into bed to deep.
; Endstops
M574 Y1 S0 ; Define active low and unused microswitches
M574 X2 S1 ; Define active high microswitches
M558 P2 X0 Y0 Z0 H5 F120 T6000 ; Set Z probe type to modulated, the axes for which it is used and the probe + travel speeds
G31 P600 X0 Y0 Z2.26 ; Set Z probe trigger value, offset and trigger height
M557 X15:185 Y15:185 S20 ; Define mesh grid
; homez.g
; called to home the Z axis
G91 ; relative mode
G1 Z4 F200 ; raise head 4mm to ensure it is above the Z probe trigger height
G90 ; back to absolute mode
G1 X100 Y100 F2000 ; put head over the centre of the bed, or wherever you want to probe
G30 ; lower head, stop when probe triggered and set Z to trigger height
; Drives
; Probe deployment routine for Mini Kossel
M564 S0 ; don't apply limits
G1 X25 Y93 Z40 F10000 ; put probe arm next to belt
G1 X-5 F500 ; move probe arm across belt
G1 X12 F1000 ; move probe back
G1 X0 Y0 F10000 ; move to somewhere sensible
M564 S1 ; apply limits again
is it in these settings making it do that,, i want it to use x switch but on highend not low end
do i need that file, i erased this file and now tries homing in middle like directions say should