Posts made by Michael Suberg

Hello everyone, after I was able to bring my board back to life with Bossa and the latest FW 3.4 update is now running, I wanted to update the Paneldue V3 5" last but not least.
Unfortunately I get the message: M997: Aux Port 0 is not enable or not in Paneldue mode.
What do I have to do to be able to install the latest update?

The board is up and running again...thanks to Bossa.
Thanks for your help

@droftarts Sorry, but i can't find any www folder on the Duet2and3Firmware-3.0.zip
I have had the config file converted by the RepRap tool. Unfortunately, still without success. The terminal programme searches for a different FW version: Error: In-application programming binary "Duet2CombinedIAP.bin" not found<LF>ok<LF>

I am currently trying to do the following: Rename the iap4.bin file to Duet2CombinedIAP.bin. Then start the update in the terminal programme with M997 S0 and the display says Firmware Download......and nothing happens.

@droftarts Sorry, but i can't find any www folder on the Duet2and3Firmware-3.0.zip

Hello everyone, my existing problem with the update: Previous version: 2.05, wanted to update directly to 3.4....unfortunately this was probably wrong. Now I have updated the main firmware (Duet2CombinedFirmware.bin) and DuetWiFiServer.bin to 3.0 via console using M997 So and M997 S1, which also worked without errors. The terminal programme displays the following with the command M115: FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.0 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-01-03b3<LF>ok<LF>. However, I still cannot access the printer via the Duet Web Control. The browser only shows Connecting and Incompatible Firmware Version. I have read that the Config.g file also needs to be adjusted Need urgent help on this....Help....Help
And if all this works again at some point...should I take the step to version 3.4.0?

Hello,
problem found, cable from the limit switch is broken, therefore wrong switching states to the controller.

After felt 10 rolls of filament my printer starts to do strange things.
After the temperatures are reached, homing begins. The Y-axis moves normally to the limit switch and the X-axis literally creeps there (very slowly). Then the print head moves in the middle and Z-homing starts. Now the pressure starts in the middle and sometimes by a few centimeters next to it.
The printof the part is absolutely normal. The X. axis also moves at normal speed.
At the end of the print, however, the bed moves to the print head and crushes the finished print part.
Can someone help me?

Firmware 2.02 (RTOS)
WIFI Server Version 1.22
Web Interface 1.22.6

Config.g :

; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2 on Sun Dec 02 2018 19:51:47 GMT+0100 (Mitteleuropäische Normalzeit)

; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

; Network
M550 P"Subis X400" ; Set machine name
M552 S1 ; Enable network
;*** Access point is configured manually via M587
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Drives
M569 P0 S0 ; Drive 0 goes forwards
M569 P1 S0 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M584 X0 Y2 Z1 E3 ; Apply custom drive mapping
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X66.66 Y66.66 Z2400.00 E492.0 ; Set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X5000.00 Y5000.00 Z220.00 E1200.00 ; Set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; Set accelerations (mm/s^2)
M906 X1000.00 Y1000.00 Z1400.00 E1200.00 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 X390 Y390 Z340 S0 ; Set axis maxima

; Endstops
M574 X2 Y2 Z0 S1 ; Set active high endstops

; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M558 P1 H4 F120 T6000 ; Set Z probe type to modulated and the dive height + speeds
G31 P500 X35 Y10 Z1.8 ; Set Z probe trigger value, offset and trigger height
M557 X30:370 Y30:390 S40 ; Define mesh grid

; Heaters
M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 X200 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C

; Fans
M106 P0 H-1 ; Set fan 0 value, PWM signal Thermostatic control is turned off
M106 P2 T45 H1 ; Set fan 1 value, Thermostatic control is turned on

; Tools
M563 P0 D0 H1 ; 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

; Automatic saving after power loss is not enabled

; Custom settings are not configured

; M557 X10:300 Y10:300 S25

@dc42 said in IR Probe and the Fan !?!:

May I mark this as solved then?

Yes gladly

@dc42
Yes, with Windows PC and my Iphone it works well. Mesh Bed works well

Found a mistake. This only occurs with my ubuntu 16.10 notebook.
With the phone and windows pc crashes and can show everything.
The wiring and solder joints are great.

Can anybody help me further???

There are no messages in the GCode Console after rebooting

I'll check the mosfets, I can rule out a short circuit, because the fans have been working for a while.
I have looked at the datasheet of the Mosfets, these only go up to 30V, but when the fans are switched off, voltages above 24V (My supply voltage) can occur.
Maybe that's the cause?

When i use the height map, there is the same problem

Currently i have two issues that are probably related.
The first one is related to the IR sample. After the printer was set up and adjusted, I installed the fan for the components.
Since my IR Probe still works conditionally. I must switch on the fan first after switching on the printer, only then the IR probe flashes and is activated. If I do not do that, the Hotend goes to bed because the IR does not respond. When restarting the same.
The second problem is Auto Mesh Bed Compensation, where at the end no graphic but an error message is displayed.