Early in Setup: No console response to M115 via SBC
-
I've got a Duet3 HW v1.1
I have a 1Hz red flashing Diag LED on the Duet3I'm running the 3.1.1 Release firmware
I have an RPI4 as the SBC
I can connect to the DWC
No more updates/upgrades are available from sudo-apt-update/sudo-apt-upgradeWhen I run an M-command the console the first command gives no response. The second command yields the spinning donut of death and never returns a response. I am getting status from the Duet3 (MCU Temp) so I believe SPI communication is working -- in some form.
How do I diagnose the difficulty with getting console commands to run?
I don't have a meaningful config.g file yet, as I'm building a CNC and I'm just trying to get the control box up and running. I don't have any motors connected yet and the mechanical parts for my CNC won't be coming for a week. So I'm happy to use any config.g that is useful for making progress on the electronics build. My next actual goal is hooking up the ps_on pin to a relay that will turn on the 24v power supply so I can test all my power rails. That said, here is my current config.g
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.8 on Mon Nov 23 2020 08:08:52 GMT-0800 (Pacific Standard Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"avid_cnc" ; set printer name M669 K1 ; select CoreXY mode ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M584 X0 Y1 Z2 ; set drive mapping M350 X16 Y16 Z16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00 ; set accelerations (mm/s^2) M906 X1200 Y1200 Z1200 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X600 Y900 Z175 S0 ; set axis maxima ; Endstops M574 X1 S3 ; configure sensorless endstop for low end on X M574 Y1 S3 ; configure sensorless endstop for low end on Y M574 Z1 S3 ; configure sensorless endstop for low end on Z ; Z-Probe M558 P0 H100 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed M557 X15:215 Y15:195 S20 ; define mesh grid ; Heaters M140 H-1 ; disable heated bed (overrides default heater mapping) ; Fans M950 F0 C"out4" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off ; Tools M563 P0 D0 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings are not defined ; Miscellaneous T0 ; select first tool
-
Ah! I needed to pull the SD card out of the Duet. I found this in a forum, but I didn't see it in the instructions.
-
@N7JTI said in Early in Setup: No console response to M115 via SBC:
I have a 1Hz red flashing Diag LED on the Duet3
That's the normal status of the diag light. Think of it like a heartbeat.
@N7JTI said in Early in Setup: No console response to M115 via SBC:
but I didn't see it in the instructions.
I've added some notes about not having an SD card in the Duet here: https://duet3d.dozuki.com/Wiki/SBC_Setup_for_Duet_3