i have ordered one and will use it with an expansion board.
i will see
Posts made by joeko
-
RE: Canned ERCF board v1.0-beta2
-
RE: Canned ERCF board v1.0-beta2
@Th0mpy yes and the price
but until now i am only think about. does this mmu system works without big problems ? -
RE: Canned ERCF board v1.0-beta2
@Th0mpy ok. but is it also possible to use an Expansion board with can conneted ?
-
RE: Canned ERCF board v1.0-beta2
can i order the Canned ERCF board ?
-
ERCF EnragedRabbitProject (MMU) and duet ?
hallo,
i have found this mulifilament system here
https://github.com/EtteGit/EnragedRabbitProject
has someone this sucsessfull running on duet boards ? -
RE: Override heater fault error
i have the same error with the latest firmware (3.45)
-
RE: Skr H7 board and mini 12864 display
i got it.
i had to change the connector to the oposite. wrong cable -
RE: Skr H7 board and mini 12864 display
@jay_s_uk said in Skr H7 board and mini 12864 display:
when i connect the esp2 connctor than the board cant connect to wifiM122
M122 === Diagnostics === RepRapFirmware for STM32H7 based Boards (biquskr_3) version 3.4.4_102 (2022-11-08 14:17:34) running on STM32H7 (standalone mode) Board ID: Z1044-0S2K2-D43SJ-6KKDD-GFLRZ-70000 Used output buffers: 3 of 40 (12 max) === RTOS === Static ram: 46792 Dynamic ram: 77144 of which 28 recycled Never used RAM 291540, free system stack 145 words Tasks: NETWORK(notifyWait,9.2%,252) HEAT(notifyWait,0.0%,344) Move(notifyWait,0.0%,354) CanReceiv(notifyWait,0.0%,934) CanSender(notifyWait,0.0%,331) CanClock(delaying,0.0%,332) TMC22xx(notifyWait,0.7%,149) FSWRITE(notifyWait,0.0%,568) MAIN(running,87.9%,977) IDLE(ready,2.1%,29), total 100.0% Owned mutexes: WiFi(NETWORK) BITIO(TMC22xx) === Platform === Last reset 00:01:27 ago, cause: power on/off Last software reset at 2022-12-08 16:39, reason: User, GCodes spinning, available RAM 291540, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 0 MCU temperature: min 30.5, current 39.2, max 39.8 Supply voltage: min 24.0, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill 2209, SG min 0, reads 7249, writes 9 Driver 1: standstill 2209, SG min 0, reads 7248, writes 9 Driver 2: standstill 2209, SG min 0, reads 7248, writes 9 Driver 3: standstill 2209, SG min 0, reads 7248, writes 9 Driver 4: Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Driver 12: Driver 13: Date/time: 2022-12-08 18:20:41 Slowest loop: 5.08ms; fastest: 0.03ms === Storage === Free file entries: 10 SD card 0 detected SD card longest read time 4.8ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 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, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Movement lock held by null HTTP 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === CAN === Messages queued 785, received 0, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 437/0/0 Tx timeouts 0,0,436,0,0,347 last cancelled message type 0 dest 1 === Network === Slowest loop: 24.40ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) HTTP sessions: 1 of 8 Uploads/Errors: 0/0 = WiFi = Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 Bad header: 0/0 WiFi firmware version 1.27-01S32-D WiFi MAC address 38:10:d5:02:b0:af WiFi Vcc 0.00, reset reason Power up WiFi flash size 0, free heap 144952 WiFi IP address 192.168.250.65 WiFi signal strength -23dBm, mode 802.11n, reconnections 0, sleep mode none Clock register 00002003 Socket states: 0 0 0 0 0 0 0 0
M122 P200 === Diagnostics === RepRapFirmware for STM32H7 based Boards (biquskr_3) version 3.4.4_102 running on STM32H7 at 480Mhz Bootloader: Unknown == Supported boards == Board 0.0: generic iomode 254 Signatures: Board 1.0: fly_super5 iomode 2 Signatures: 0x2fe7ccfb Board 2.0: fly_super8h7 iomode 2 Signatures: 0x32757276 Board 2.1: fly_super8_pro iomode 2 Signatures: 0x32757276 Board 3.0: biquskr_se_bx_2.0 iomode 4 Signatures: 0xf1832a2 Board 4.0: biquskr_3 iomode 2 Signatures: 0xaa36a0c4 Board 4.1: biquskr_3_ez iomode 2 Signatures: 0xaa36a0c4 == Configurable Board.txt Settings == board = biquskr_3 Signature 0xaa36a0c4 leds.diagnostic = A.13 leds.diagnosticOn = true leds.activity = NoPin leds.activityOn = true pins.SetHigh = {NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin} pins.SetLow = {NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin} stepper.powerEnablePin = NoPin stepper.enablePins = {D.6, D.1, E.0, C.7, D.13, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin} stepper.stepPins = {D.4, A.15, E.2, D.15, D.11, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin} stepper.directionPins = {D.3, A.8, E.3, D.14, D.10, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin} stepper.digipotFactor = 0.00 stepper.TmcUartPins = {D.5, D.0, E.1, C.6, D.12, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin} stepper.numSmartDrivers = 4 stepper.num5160Drivers = 0 stepper.spiChannel = 255 stepper.TmcDiagPins = {NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin} heat.tempSensePins = {A.1, A.2, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin} heat.spiTempSensorCSPins = {NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin, NoPin} heat.spiTempSensorChannel = 255 heat.thermistorSeriesResistor = 4700.00 atx.powerPin = E.4 atx.powerPinInverted = false atx.initialPowerOn = true sdCard.internal.spiFrequencyHz = 25000000 sdCard.external.csPin = NoPin sdCard.external.cardDetectPin = NoPin sdCard.external.spiFrequencyHz = 4000000 sdCard.external.spiChannel = 255 lcd.lcdCSPin = B.1 lcd.lcdBeepPin = NoPin lcd.encoderPinA = E.7 lcd.encoderPinB = B.2 lcd.encoderPinSw = B.0 lcd.lcdDCPin = E.8 lcd.panelButtonPin = NoPin lcd.spiChannel = 0 SPI0.pins = {A.5, A.6, A.7} SPI1.pins = {B.13, B.14, B.15} SPI2.pins = {NoPin, NoPin, NoPin} SPI3.pins = {E.14, E.15, E.13} SPI4.pins = {NoPin, NoPin, NoPin} SPI5.pins = {NoPin, NoPin, NoPin} SPI6.pins = {NoPin, NoPin, NoPin} SPI7.pins = {NoPin, NoPin, NoPin} SPI8.pins = {NoPin, NoPin, NoPin} 8266wifi.espDataReadyPin = B.10 8266wifi.lpcTfrReadyPin = B.11 8266wifi.TfrReadyPin = B.11 8266wifi.espResetPin = C.14 8266wifi.csPin = B.12 8266wifi.serialRxTxPins = {D.9, D.8} 8266wifi.spiChannel = 1 8266wifi.clockReg = 0 serial.aux.rxTxPins = {NoPin, NoPin} led.neopixelPin = E.10 power.VInDetectPin = NoPin power.voltage = 24 accelerometer.spiChannel = 255 == Defined Pins == bedtemp,tb = A.1 e0temp,th0 = A.2 e1temp,th1 = A.3 xstop = C.1 ystop = C.3 zstop = C.0 e0stop,e0det = C.2 e1stop,e1det = A.0 servo0 = E.5 probe = C.13 bed,hbed = D.7 e0heat,heat0 = B.3 e1heat,heat1 = B.4 fan0,fan = B.7 fan1 = B.6 fan2 = B.5 Neopixel = E.6 PSON = E.4 PWRDET = C.15 LED = A.13 BEEP = C.5 BTNENC = B.0 LCDEN = B.1 LCDRS = E.8 LCDD4 = E.9 LCDD5 = E.10 LCDD6 = E.11 LCDD7 = E.12 LCDMISO = A.6 LCDSCK = A.5 BTNEN1 = E.7 LCDSS = A.4 BTNEN2 = B.2 LCDMOSI = A.7 LCDCD = C.4 == Hardware Serial == AUX Serial: Disabled WIFI Serial: UART 3 == PWM == 0: Pin D.7 freq 0 value 0.000000 1: Pin B.3 freq 0 value 0.000000 2: Pin B.5 freq 0 value 0.000000 3: Pin B.6 freq 0 value 0.000000 4: Pin E.5 freq 0 value 0.000000 5: Pin E.9 freq 0 value 1.000000 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: == Attached interrupt pins == 0: 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: B.10 11: 12: B.12 13: 14: 15: == MCU == AdcBits = 14 TS_CAL1 (30C) = 12254 TS_CAL2 (110C) = 16303 V_REFINCAL (30C 3.3V) = 24142 V_REFINT raw 5992 V_REF 3.322029 T_MCU raw 3175 T_MCU cal 39.090908 T_MCU calc -23.186043 T_MCU raw (corrected) 3196 T_MCU cal (corrected) 40.766407 T_MCU calc (corrected) -21.478344 Device Id 450 Revison Id 2003 CPUId r1p1 == RAM == RAM start 0x24000000 end 0x24070000 No cache RAM 1 start 0x30000000 end 0x30048000 No cache RAM 2 start 0x24070000 end 0x24080000 == USB == Read overrun 0
-
Skr H7 board and mini 12864 display
i try to connect an fystec mini v2.1 to the skr H7 board like here https://teamgloomy.github.io/skr_3_h723_screen_12864.html
but i cant use it because it stay dark. on an duet 3 mini it works without any problems but not with the skr. do i miss something ? i followed the guide without any change. do i have to modify something ?
-
RE: STM32H7 Port of RRF 3.4.1RC1 - with CAN-FD support
@jay_s_uk
overkill of course but i dont use it here at the moment because i dont use this printer -
RE: STM32H7 Port of RRF 3.4.1RC1 - with CAN-FD support
@jay_s_uk
when i try to install the duet 6 on the backside of the voron 0 than is it only possible when the corner of the duet with the io_x connector is 10 mm or fewer close to the b-nema motor. is it possible that a stepper motor disturb the duet board ? -
RE: STM32H7 Port of RRF 3.4.1RC1 - with CAN-FD support
do you know if there is a problem i.e inteference or so when the board with the io_x corner is close to a stepper motor ?
-
RE: STM32H7 Port of RRF 3.4.1RC1 - with CAN-FD support
enough for the future ?
i am building an voron 0.1 and will use duet or rrp
every time when i play with klipper i ask me for what .....
my duet 3 6 hc is too big for this little printer and the skr3 is cheap at the moment -
RE: STM32H7 Port of RRF 3.4.1RC1 - with CAN-FD support
hmm, how much memory has this board ?
there are an octopus version that cant or only reduce with rrp because not enough memory.for the skr 3 boards i cant find information about memory
-
RE: Duet3, wiring endstop to iox.in and also to iox.out ?
@fcwilt said in Duet3, wiring endstop to iox.in and also to iox.out ?:
@joeko said in Duet3, wiring endstop to iox.in and also to iox.out ?:
or do you mean why between xxx.out and ground ?
if so than offer the wirring guide this (between xxx.in and ground) ...or am i wrong ?Sorry I wasn't clear.
Why would you want to use an output for an input given the numerous inputs usually present on a Duet?
Frederick
at the moment i am building the printer and have looked for an rrf firmware or a ready config.g with nema settings and so on. i found something on discord with these endstop wiring and was confused. the xy endstop pcb has 4 cables, one for ground, 2 for x+y signal and for voltage. if there is no reason against this than is it possible with one cable (3 cables to one connector) to connect the xy endstop pcb to the toolboard or board. but of course it is also easy to use two connector for signal and they share the ground.
sorry for my english, it isnt my homelanguage
-
RE: Duet3, wiring endstop to iox.in and also to iox.out ?
@fcwilt said in Duet3, wiring endstop to iox.in and also to iox.out ?:
@joeko said in Duet3, wiring endstop to iox.in and also to iox.out ?:
ok, greate
than i connec the endstopswitch between iox.out and groundWhy would you want to do that?
Frederick
or do you mean why between xxx.out and ground ?
if so than offer the wirring guide this (between xxx.in and ground) ...or am i wrong ? -
RE: Duet3, wiring endstop to iox.in and also to iox.out ?
@fcwilt said in Duet3, wiring endstop to iox.in and also to iox.out ?:
@joeko said in Duet3, wiring endstop to iox.in and also to iox.out ?:
ok, greate
than i connec the endstopswitch between iox.out and groundWhy would you want to do that?
Frederick
for the voron you need 7 driver and the endstop are limited. and if there is no problem to configure the x+y endstops to io2.in+io2.out than i need only one io connector. some people use the io also for chamber temperture and so on. i found this on discord and was confused about it.
-
RE: Duet3, wiring endstop to iox.in and also to iox.out ?
@droftarts said in Duet3, wiring endstop to iox.in and also to iox.out ?:
@joeko @jay_s_uk is correct, but be aware that if you use an io[x].out as an input, it is only 3.3V tolerant. io[x].in are 30V tolerant.
This is noted on the Duet 3 6HC and Mini 5+ hardware pages, but not on the expansion and tool board pages. I’ll check this is universal to Duet 3 with Tony/dc42, and add it to those pages as necessary.
Ian
ok, greate
than i connec the endstopswitch between iox.out and ground -
Duet3, wiring endstop to iox.in and also to iox.out ?
hi,
i am building an voron 2.4 with an duet3 mini with toolboard.
now i have found an config.g on discord with these endstop in the config; Endstops
M574 X2 S1 P"^0.io1.in"
M574 Y2 S1 P"^0.io1.out"hmm, until now i thought the the endstop (switch) has to connect to ground and iox.in. is both possible ?