Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. MikeGeppert
    3. Posts
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 28
    • Best 0
    • Controversial 0
    • Groups 0

    Posts made by MikeGeppert

    • Firmware development and debugging setup help?

      How do you setup for Debugging the firmware on a Duet3 6HC?
      Using Eclipse I can build the Duet3_Debug target but did not find any clean way to get Eclipse to connect to a MPLAB ICD ICE.
      Can a GDB connection be used?

      My intent is to find out why some commands can use global variables just fine and other commands can not.
      Example: (First M557 is commented out is the one I would like to use)
      ; M557 X{(sensors.probes[0].offsets[0]+5)}:{(move.axes[0].max-sensors.probes[0].offsets[0]-5)} Y{(sensors.probes[0].offsets[1]+5)}:{(move.axes[1].max-sensors.probes[0].offsets[1]-5)} P5:5
      M557 X5:295 Y5:295 P5:5

      I also noted that simple "M557 X{5}:{295} Y{5}:{295} P5:5" did not work either.

      I was thinking to just lift the parser code out and run in a Linux processor with some BOOST test code but the thread of stuff to pull in became pretty big. I also saw that FreeRTOS has a port for running under Linux, that looked like fun, but we would need to stub the real time stuff. In this case I really dont care about sensors and motors so all that can just do nothing.

      Thanks,

      posted in Firmware developers
      MikeGeppertundefined
      MikeGeppert
    • RE: Error building RepRapFirmware 3.3-dev

      @dc42 said in Error building RepRapFirmware 3.3-dev:

      I suggest you install this https://xpack.github.io/windows-build-tools/ if you haven't already, then adjust your PATH so that the version of make.exe from that installation is picked up before any other. You can type "where make" at the Windows command prompt to find out where make is being fetched from.

      Yah... I tried several combinations (starting with the ones in the instructions) and finally gave up on Windows.

      I installed a Virtual Box with a Ubuntu distribution and got it all working. Just avoided the whole make/rm command line length issue all together.
      Thanks

      posted in Firmware developers
      MikeGeppertundefined
      MikeGeppert
    • RE: Error building RepRapFirmware 3.3-dev

      @dc42 said in Error building RepRapFirmware 3.3-dev:

      I suspect you are using a version of Make that doesn't handle long lines. There are some notes in the Build Instructions on this.

      For the "Instructions for Windows", step 3, Download and install GNU Arm Eclipse, the link is deprecated. There is a link that says "As of 2018-03-19 this project can be found here".

      Going to that link "GNU MCU Eclipse (formerly GNU ARM Eclipse)" claims it is also deprecated "DEPRECATED: as of 2020, the project was migrated to the Eclipse Foundation (https://github.com/eclipse-embed-cdt)"

      I then went to the Eclipse install software and check everything having to do with ARM. Get the exact same error.

      posted in Firmware developers
      MikeGeppertundefined
      MikeGeppert
    • RE: Error building RepRapFirmware 3.3-dev

      Thanks so much for your response.
      It sounds good, so I downloaded the tools again and made sure all the tools are on path. I noticed that the
      I even ran them from the DOS window and get the same thing.

      N:\GitHub\RepRapFirmware\Duet3>make Duet3Firmware_MB6HC.elf
      Building target: Duet3Firmware_MB6HC.elf
      Invoking: Cross G++ Linker
      arm-none-eabi-gcc ...
      <Really Long Make line>
      arm-none-eabi-gcc.exe: error: ./src/Endstops/E: No such file or directory
      makefile:93: recipe for target 'Duet3Firmware_MB6HC.elf' failed
      make: *** [Duet3Firmware_MB6HC.elf] Error 1

      N:\GitHub\RepRapFirmware\Duet3>which arm-none-eabi-gcc.exe
      /n/Program Files (x86)/GNU Arm Embedded Toolchain/10 2020-q4-major/bin/arm-none-eabi-gcc.exe

      N:\GitHub\RepRapFirmware\Duet3>which make
      /n/Program Files/GNU ARM Eclipse/Build Tools/2.6-201507152002/bin/make

      N:\GitHub\RepRapFirmware\Duet3>

      posted in Firmware developers
      MikeGeppertundefined
      MikeGeppert
    • Error building RepRapFirmware 3.3-dev

      Building "Duet3" I get the following. Also tried to build "Duet3_Debug" it errors with "arm-none-eabi-gcc.exe: error: ./src/Fans/LocalFan.: No such file or directory".

      21:07:16 **** Incremental Build of configuration Duet3 for project RepRapFirmware ****
      make -j12 all
      Building target: Duet3Firmware_MB6HC.elf
      Invoking: Cross G++ Linker
      arm-none-eabi-gcc -L"N:\GitHub\CoreN2G\SAME70_CAN_SDHC_USB_RTOS" -L"N:\GitHub\RRFLibraries\SAME70_RTOS" -L"N:\GitHub\FreeRTOS\SAME70" -L"N:\GitHub\CANlib\SAME70_RTOS" --specs=nosys.specs -Os -Wl,--gc-sections -Wl,--fatal-warnings -mcpu=cortex-m7 -mfpu=fpv5-d16 -mfloat-abi=hard -T"N:\GitHub\RepRapFirmware\src\Hardware\SAME70\same70q20b_flash.ld" -Wl,-Map,"N:\GitHub\RepRapFirmware\Duet3/Duet3Firmware_MB6HC.map" -o "Duet3Firmware_MB6HC.elf" -mthumb -Wl,--cref -Wl,--check-sections -Wl,--gc-sections -Wl,--entry=Reset_Handler -Wl,--unresolved-symbols=report-all -Wl,--warn-common -Wl,--warn-section-align -Wl,--warn-unresolved-symbols -Wl,--start-group ./src/libcpp/eh_alloc.o ./src/libcpp/vterminate.o ./src/libc/memcmp.o ./src/libc/memcpy.o ./src/libc/memmove.o ./src/libc/memset.o ./src/libc/nano-mallocr.o ./src/libc/strptime.o ./src/bossa/Applet.o ./src/bossa/BossaFlash.o ./src/bossa/Device.o ./src/bossa/EefcFlash.o ./src/bossa/Flasher.o ./src/bossa/Samba.o ./src/bossa/WordCopyApplet.o ./src/bossa/WordCopyArm.o ./src/Tools/Filament.o ./src/Tools/Spindle.o ./src/Tools/Tool.o ./src/Storage/CRC16.o ./src/Storage/CRC32.o ./src/Storage/FileInfoParser.o ./src/Storage/FileStore.o ./src/Storage/MassStorage.o ./src/ObjectModel/ObjectModel.o ./src/Networking/LwipEthernet/Lwip/src/netif/bridgeif.o ./src/Networking/LwipEthernet/Lwip/src/netif/bridgeif_fdb.o ./src/Networking/LwipEthernet/Lwip/src/netif/ethernet.o ./src/Networking/LwipEthernet/Lwip/src/netif/lowpan6.o ./src/Networking/LwipEthernet/Lwip/src/netif/lowpan6_ble.o ./src/Networking/LwipEthernet/Lwip/src/netif/lowpan6_common.o ./src/Networking/LwipEthernet/Lwip/src/netif/slipif.o ./src/Networking/LwipEthernet/Lwip/src/netif/zepif.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv6/dhcp6.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv6/ethip6.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv6/icmp6.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv6/inet6.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv6/ip6.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv6/ip6_addr.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv6/ip6_frag.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv6/mld6.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv6/nd6.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv4/autoip.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv4/dhcp.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv4/etharp.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv4/icmp.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv4/igmp.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv4/ip4.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv4/ip4_addr.o ./src/Networking/LwipEthernet/Lwip/src/core/ipv4/ip4_frag.o ./src/Networking/LwipEthernet/Lwip/src/core/altcp.o ./src/Networking/LwipEthernet/Lwip/src/core/altcp_alloc.o ./src/Networking/LwipEthernet/Lwip/src/core/altcp_tcp.o ./src/Networking/LwipEthernet/Lwip/src/core/def.o ./src/Networking/LwipEthernet/Lwip/src/core/dns.o ./src/Networking/LwipEthernet/Lwip/src/core/inet_chksum.o ./src/Networking/LwipEthernet/Lwip/src/core/init.o ./src/Networking/LwipEthernet/Lwip/src/core/ip.o ./src/Networking/LwipEthernet/Lwip/src/core/mem.o ./src/Networking/LwipEthernet/Lwip/src/core/memp.o ./src/Networking/LwipEthernet/Lwip/src/core/netif.o ./src/Networking/LwipEthernet/Lwip/src/core/pbuf.o ./src/Networking/LwipEthernet/Lwip/src/core/raw.o ./src/Networking/LwipEthernet/Lwip/src/core/stats.o ./src/Networking/LwipEthernet/Lwip/src/core/sys.o ./src/Networking/LwipEthernet/Lwip/src/core/tcp.o ./src/Networking/LwipEthernet/Lwip/src/core/tcp_in.o ./src/Networking/LwipEthernet/Lwip/src/core/tcp_out.o ./src/Networking/LwipEthernet/Lwip/src/core/timeouts.o ./src/Networking/LwipEthernet/Lwip/src/core/udp.o ./src/Networking/LwipEthernet/Lwip/src/apps/netbiosns/netbiosns.o ./src/Networking/LwipEthernet/Lwip/src/apps/mdns/mdns.o ./src/Networking/LwipEthernet/Lwip/src/api/api_lib.o ./src/Networking/LwipEthernet/Lwip/src/api/api_msg.o ./src/Networking/LwipEthernet/Lwip/src/api/err.o ./src/Networking/LwipEthernet/Lwip/src/api/if_api.o ./src/Networking/LwipEthernet/Lwip/src/api/netbuf.o ./src/Networking/LwipEthernet/Lwip/src/api/netdb.o ./src/Networking/LwipEthernet/Lwip/src/api/netifapi.o ./src/Networking/LwipEthernet/Lwip/src/api/sockets.o ./src/Networking/LwipEthernet/Lwip/src/api/tcpip.o ./src/Networking/LwipEthernet/GMAC/ethernet_sam.o ./src/Networking/LwipEthernet/LwipEthernetInterface.o ./src/Networking/LwipEthernet/LwipSocket.o ./src/Networking/FtpResponder.o ./src/Networking/HttpResponder.o ./src/Networking/Network.o ./src/Networking/NetworkBuffer.o ./src/Networking/NetworkInterface.o ./src/Networking/NetworkResponder.o ./src/Networking/TelnetResponder.o ./src/Networking/UploadingNetworkResponder.o ./src/Movement/StepperDrivers/DriverMode.o ./src/Movement/StepperDrivers/TMC22xx.o ./src/Movement/StepperDrivers/TMC2660.o ./src/Movement/StepperDrivers/TMC51xx.o ./src/Movement/Kinematics/CoreKinematics.o ./src/Movement/Kinematics/FiveBarScaraKinematics.o ./src/Movement/Kinematics/HangprinterKinematics.o ./src/Movement/Kinematics/Kinematics.o ./src/Movement/Kinematics/LinearDeltaKinematics.o ./src/Movement/Kinematics/PolarKinematics.o ./src/Movement/Kinematics/RotaryDeltaKinematics.o ./src/Movement/Kinematics/ScaraKinematics.o ./src/Movement/Kinematics/ZLeadscrewKinematics.o ./src/Movement/HeightControl/HeightController.o ./src/Movement/BedProbing/Grid.o ./src/Movement/BedProbing/RandomProbePointSet.o ./src/Movement/DDA.o ./src/Movement/DDARing.o ./src/Movement/DriveMovement.o ./src/Movement/Move.o ./src/Movement/RawMove.o ./src/Movement/StepTimer.o ./src/Movement/StraightProbeSettings.o ./src/Linux/DataTransfer.o ./src/Linux/LinuxInterface.o ./src/Libraries/sha1/sha1.o ./src/Libraries/sd_mmc/ctrl_access.o ./src/Libraries/sd_mmc/sd_mmc.o ./src/Libraries/sd_mmc/sd_mmc_mem.o ./src/Libraries/sd_mmc/sd_mmc_spi.o ./src/Libraries/Fatfs/diskio.o ./src/Libraries/Fatfs/fattime_rtc.o ./src/Libraries/Fatfs/ff.o ./src/Libraries/Fatfs/ffunicode.o ./src/InputMonitors/InputMonitor.o ./src/Heating/Sensors/AdditionalOutputSensor.o ./src/Heating/Sensors/CpuTemperatureSensor.o ./src/Heating/Sensors/CurrentLoopTemperatureSensor.o ./src/Heating/Sensors/DhtSensor.o ./src/Heating/Sensors/LinearAnalogSensor.o ./src/Heating/Sensors/RemoteSensor.o ./src/Heating/Sensors/RtdSensor31865.o ./src/Heating/Sensors/SensorWithPort.o ./src/Heating/Sensors/SpiTemperatureSensor.o ./src/Heating/Sensors/TemperatureSensor.o ./src/Heating/Sensors/Thermistor.o ./src/Heating/Sensors/ThermocoupleSensor31855.o ./src/Heating/Sensors/ThermocoupleSensor31856.o ./src/Heating/Sensors/TmcDriverTemperatureSensor.o ./src/Heating/FOPDT.o ./src/Heating/Heat.o ./src/Heating/Heater.o ./src/Heating/HeaterMonitor.o ./src/Heating/LocalHeater.o ./src/Heating/RemoteHeater.o ./src/Heating/TemperatureError.o ./src/Hardware/SharedSpi/SharedSpiClient.o ./src/Hardware/SharedSpi/SharedSpiDevice.o ./src/Hardware/SAME70/Ethernet/ksz8081rna/ethernet_phy.o ./src/Hardware/SAME70/Ethernet/GmacInterface.o ./src/Hardware/SAME70/Devices.o ./src/Hardware/SAME70/Main.o ./src/Hardware/ExceptionHandlers.o ./src/Hardware/I2C.o ./src/Hardware/IoPorts.o ./src/Hardware/NonVolatileMemory.o ./src/Hardware/SoftwareReset.o ./src/GPIO/GpInPort.o ./src/GPIO/GpOutPort.o ./src/GCodes/GCodeBuffer/BinaryParser.o ./src/GCodes/GCodeBuffer/ExpressionParser.o ./src/GCodes/GCodeBuffer/GCodeBuffer.o ./src/GCodes/GCodeBuffer/StringParser.o ./src/GCodes/GCodeException.o ./src/GCodes/GCodeFileInfo.o ./src/GCodes/GCodeInput.o ./src/GCodes/GCodeMachineState.o ./src/GCodes/GCodeQueue.o ./src/GCodes/GCodes.o ./src/GCodes/GCodes2.o ./src/GCodes/GCodes3.o ./src/GCodes/GCodes4.o ./src/GCodes/ObjectTracker.o ./src/GCodes/RestorePoint.o ./src/GCodes/Trigger.o ./src/FilamentMonitors/Duet3DFilamentMonitor.o ./src/FilamentMonitors/FilamentMonitor.o ./src/FilamentMonitors/LaserFilamentMonitor.o ./src/FilamentMonitors/PulsedFilamentMonitor.o ./src/FilamentMonitors/RotatingMagnetFilamentMonitor.o ./src/FilamentMonitors/SimpleFilamentMonitor.o ./src/Fans/Fan.o ./src/Fans/FansManager.o ./src/Fans/LedStripDriver.o ./src/Fans/LocalFan.o ./src/Fans/RemoteFan.o ./src/Endstops/Endstop.o ./src/Endstops/EndstopsManager.o ./src/Endstops/LocalZProbe.o ./src/Endstops/RemoteZProbe.o ./src/Endstops/StallDetectionEndstop.o ./src/Endstops/SwitchEndstop.o ./src/Endstops/ZProbe.o ./src/Endstops/ZProbeEndstop.o ./src/Duet3_V06/Pins_Duet3_V06.o ./src/Comms/AuxDevice.o ./src/Comms/FirmwareUpdater.o ./src/Comms/PanelDueUpdater.o ./src/CAN/CanInterface.o ./src/CAN/CanMessageGenericConstructor.o ./src/CAN/CanMotion.o ./src/CAN/CommandProcessor.o ./src/CAN/ExpansionManager.o ./src/Logger.o ./src/OutputMemory.o ./src/Platform.o ./src/PortControl.o ./src/PrintMonitor.o ./src/RepRap.o ./src/RepRapFirmware.o ./src/Roland.o ./src/Scanner.o ./src/Stream.o ./src/Tasks.o -lCoreN2G -lRRFLibraries -lFreeRTOS -lCANlib -lsupc++ -Wl,--end-group -lm
      arm-none-eabi-gcc.exe: error: ./src/Endstops/E: No such file or directory
      makefile:93: recipe for target 'Duet3Firmware_MB6HC.elf' failed
      make: *** [Duet3Firmware_MB6HC.elf] Error 1
      "make -j12 all" terminated with exit code 2. Build might be incomplete.

      21:07:20 Build Failed. 2 errors, 0 warnings. (took 4s.448ms)

      posted in Firmware developers
      MikeGeppertundefined
      MikeGeppert
    • RE: Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC

      @Phaedrux said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

      @MikeGeppert said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

      My homing macros try and set stealthchop and sensorless homing. To do that I have to cut the current to 30% using the M913 command. So if I cut to 80% at first in the config file, do I then cut to 80% * 30%? Then set back to 80% when done?

      This is exactly why I leave M906 as the full rated current and then adjust with M913. That way I know that M913 80 is 80% of rated. And 30% is 30% of rated. It's just more direct. No percentage of a percentage.

      Mathematically I want the 80%*30%. My intention was that once Variables get implemented I would make a MAX_MOTOR_LDO that has the 2000mA value. And another variable that would have the percentage MAX_RUN_PERCENT to be like 80%. Then set the M906 to the multiplication of the two. Then I can use percentages of that MAX_RUN_VALUE.

      posted in General Discussion
      MikeGeppertundefined
      MikeGeppert
    • RE: Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC

      @Phaedrux said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

      @MikeGeppert said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

      M906 X{20000.8} M906 Y{20000.8} M906 Z{20000.8} ;M906 E{10000.9} M906 U{1000*0.9}

      If you're trying to get percentages with this, just use M913 instead. I set my current to the rated max with M906 and then use M913 to set it to a percentage of that.

      My homing macros try and set stealthchop and sensorless homing. To do that I have to cut the current to 30% using the M913 command. So if I cut to 80% at first in the config file, do I then cut to 80% * 30%? Then set back to 80% when done?

      posted in General Discussion
      MikeGeppertundefined
      MikeGeppert
    • RE: Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC

      Thanks so much for the help!

      The original Config file now works with the one change:

      M906 X{20000.8}
      M906 Y{2000
      0.8}
      M906 Z{20000.8}
      ; M906 E{1000
      0.9} ; This seems to not work
      M906 E900
      ;M906 U{1000*0.9}

      posted in General Discussion
      MikeGeppertundefined
      MikeGeppert
    • RE: Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC

      @Phaedrux said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

      @MikeGeppert said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

      M906 X{20000.8} M906 Y{20000.8} M906 Z{20000.8} ;M906 E{10000.9} M906 U{1000*0.9}

      If you're trying to get percentages with this, just use M913 instead. I set my current to the rated max with M906 and then use M913 to set it to a percentage of that.

      One more note:
      M906 U{1000*0.9} ; Works

      posted in General Discussion
      MikeGeppertundefined
      MikeGeppert
    • RE: Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC

      @Phaedrux said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

      @MikeGeppert said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

      M906 X{20000.8} M906 Y{20000.8} M906 Z{20000.8} ;M906 E{10000.9} M906 U{1000*0.9}

      If you're trying to get percentages with this, just use M913 instead. I set my current to the rated max with M906 and then use M913 to set it to a percentage of that.

      I found the culprit:
      M906 E900 ; Works
      and
      M906 E{1000*0.9} ; Gives the issue.

      Interesting that these seem to work:
      M906 X{20000.8}
      M906 Y{2000
      0.8}
      M906 Z{2000*0.8}

      posted in General Discussion
      MikeGeppertundefined
      MikeGeppert
    • RE: Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC

      @Phaedrux said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

      And for good measure can you post the results of M122 as well when configured as E?

      We could also start sending the basic axis setup commands by themselves to see what the firmware thinks is configured and see if it meets expectation.

      M201, M203, M566, M584, etc etc

      But I think we may get good results from a clean config.

      1/5/2021, 11:17:48 PM M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
      Board ID: 08DJM-956BA-NA3TJ-6JKDJ-3S86P-1T9LT
      Used output buffers: 1 of 40 (10 max)
      === RTOS ===
      Static ram: 149788
      Dynamic ram: 62828 of which 36 recycled
      Never used RAM 146180, free system stack 192 words
      Tasks: Linux(ready,102) HEAT(blocked,297) CanReceiv(blocked,927) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,19) MAIN(running,1179) IDLE(ready,19)
      Owned mutexes: HTTP(MAIN)
      === Platform ===
      Last reset 00:00:49 ago, cause: software
      Last software reset at 2021-01-05 23:16, reason: User, none spinning, available RAM 146252, slot 2
      Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
      Error status: 0x00
      Aux0 errors 0,0,0
      Aux1 errors 0,0,0
      MCU temperature: min 33.9, current 34.3, max 34.4
      Supply voltage: min 24.2, current 24.3, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
      12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
      Driver 0: position 0, standstill, reads 13340, writes 20 timeouts 0, SG min/max 0/0
      Driver 1: position 0, standstill, reads 13341, writes 20 timeouts 0, SG min/max 0/0
      Driver 2: position 0, standstill, reads 13341, writes 20 timeouts 0, SG min/max 0/0
      Driver 3: position 0, standstill, reads 13342, writes 19 timeouts 0, SG min/max 0/0
      Driver 4: position 0, standstill, reads 13341, writes 20 timeouts 0, SG min/max 0/41
      Driver 5: position 0, standstill, reads 13350, writes 11 timeouts 0, SG min/max 0/0
      Date/time: 2021-01-05 23:17:48
      Slowest loop: 0.44ms; fastest: 0.05ms
      === Storage ===
      Free file entries: 10
      SD card 0 not detected, interface speed: 37.5MBytes/sec
      SD card longest read time 0.0ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 125, maxWait 18449ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 1, completed moves 1, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], CDDA state -1
      === AuxDDARing ===
      Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === Heat ===
      Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
      Heater 1 is on, I-accum = 0.0
      === GCodes ===
      Segments left: 0
      Movement lock held by null
      HTTP* is doing "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.
      === CAN ===
      Messages queued 188, send timeouts 433, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48
      === SBC interface ===
      State: 4, failed transfers: 0
      Last transfer: 1ms ago
      RX/TX seq numbers: 1696/1696
      SPI underruns 0, overruns 0
      Number of disconnects: 0, IAP RAM available 0x2c8a8
      Buffer RX/TX: 0/0-0
      === Duet Control Server ===
      Duet Control Server v3.2.0
      Code buffer space: 4096
      Configured SPI speed: 8000000 Hz
      Full transfers per second: 35.40
      Maximum length of RX/TX data transfers: 4788/860

      posted in General Discussion
      MikeGeppertundefined
      MikeGeppert
    • RE: Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC

      @Phaedrux said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

      If everything executes cleanly you should get something like

      M98 PCONFIG.G
      HTTP is enabled on port 80
      FTP is disabled
      TELNET is disabled
      Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 893C.
      

      Well, actually, looking at your config it looks like you may not have any of the network commands and your heaters may not be overpowered.

      With the generated config file it also does not print anything to the console.

      posted in General Discussion
      MikeGeppertundefined
      MikeGeppert
    • RE: Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC

      @Phaedrux said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

      Hmm.. no, there should be a few messages if everything is good and some errors if it's not. I think something is amiss with your config.

      Can you try a basic config generated by the config tool?

      Ok so a generated Config file seems to work.
      Hmmm - I will start modifying it slowly to see what broke it.

      posted in General Discussion
      MikeGeppertundefined
      MikeGeppert
    • RE: Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC

      @MikeGeppert said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

      @Phaedrux said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

      M98 P"config.g"

      1/5/2021, 10:44:40 PM M98 P"config.g"

      Kind of unexciting? Its got a green background I think that is a good thing?

      The lights blink like I expect when I run the command. What should give an output?

      posted in General Discussion
      MikeGeppertundefined
      MikeGeppert
    • RE: Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC

      @Phaedrux Sure - give me like 30 min or so.

      posted in General Discussion
      MikeGeppertundefined
      MikeGeppert
    • RE: Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC

      @Phaedrux Great Thanks!
      Same issue. "U" works, "E" not so much...

      posted in General Discussion
      MikeGeppertundefined
      MikeGeppert
    • RE: Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC

      @Phaedrux said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

      M98 P"config.g"

      1/5/2021, 10:44:40 PM M98 P"config.g"

      Kind of unexciting? Its got a green background I think that is a good thing?

      posted in General Discussion
      MikeGeppertundefined
      MikeGeppert
    • RE: Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC

      @Phaedrux Is this right? I was expecting an rc2 somewhere:
      1/5/2021, 10:42:56 PM M115
      FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.2 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-01-05

      posted in General Discussion
      MikeGeppertundefined
      MikeGeppert
    • RE: Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC

      @dc42 Thanks for the response.

      If I do a "G1 E10" I get the same effect.
      I actually removed the stepper from the extruder and it is just sitting on the bed now. I am looking at the gear on the motor.
      If I set it up as a "U" it turns as expected with "G1 U10".
      If I set up as a "E" it vibrates with almost no torque. I can put my finger on the gear and feel almost no torque at all.

      posted in General Discussion
      MikeGeppertundefined
      MikeGeppert
    • RE: Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC

      @Phaedrux Hmmm the update did not go well. Trying to recover the system now.

      posted in General Discussion
      MikeGeppertundefined
      MikeGeppert