Mosquito Hotend PT1000 issues

wcmartino

Hello,

I am in the the process of swapping out the hotend on my delta to a Slice Engineering Mosquito. I have everything hooked up to the v4 smart effector. When powering on the lights on the effector come on and the temperature shows -14.3c. Current running a Duet Mini 5+ in SBC mode. Was running 3.4.5 but upgraded to the 3.5 beta to see if anyhting would change.

Current M308 line from the config.g file:
M308 S1 P"temp2" Y"pt1000" A"Extruder"

Conplete config.g
config.g

I am at a lose at thid point, is this normal for this PT1000 from Slice Engineering?

Thanks in advanced.

Phaedrux

Can you try connecting the PT1000 directly to the Duet board as a test?

Can you also send M122 and M98 P"config.g" and copy and paste the results here?

wcmartino

@Phaedrux Thanks for the quick response. Here are the results of the two commands:

1/31/2023, 10:05:02 PM	m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5beta1 (2022-12-23 18:25:34) running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: MDHLF-5296U-D65J0-40KM0-2G03Z-RL674
Used output buffers: 6 of 40 (26 max)
=== RTOS ===
Static ram: 102208
Dynamic ram: 103348 of which 12 recycled
Never used RAM 36144, free system stack 196 words
Tasks: SBC(ready,0.7%,442) HEAT(notifyWait,0.0%,359) Move(notifyWait,0.0%,359) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,342) TMC(notifyWait,0.7%,114) MAIN(running,94.8%,542) IDLE(ready,3.0%,30) AIN(delaying,0.8%,272), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:53 ago, cause: power up
Last software reset at 2023-01-31 21:04, reason: User, Platform spinning, available RAM 36144, slot 2
Software reset code 0x6000 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00489000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 53761, completed 53761, timed out 0, errs 0
Step timer max interval 1489
MCU temperature: min 23.8, current 27.6, max 27.6
Supply voltage: min 23.7, current 23.8, max 23.8, 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, SG min 0, read errors 0, write errors 0, ifcnt 14, reads 2788, writes 14, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 14, reads 2788, writes 14, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 14, reads 2788, writes 14, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 14, reads 2788, writes 14, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 2792, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2023-01-31 22:05:01
Cache data hit count 116893198
Slowest loop: 3.74ms; fastest: 0.11ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
no step interrupt scheduled
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
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, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, 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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000000
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 383, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 268/0/0
Tx timeouts 0,0,267,0,0,114 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 1083/1083
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x0e0a8
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server version 3.5.0-b1 (2022-12-23 20:41:36)
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 0.52, max time between full transfers: 504.4ms, max pin wait times: 59.7ms/30.1ms
Codes per second: 0.02
Maximum length of RX/TX data transfers: 4162/680

M98 P"config.g" returns nothing.

It will take a bit to plug the sensor directly into the board as it is buried under the bed and has a different connector. Will try and get to that tomorrow. This was working correcty when I was using the E3d hotend and thermistor.

Phaedrux

Are you sure it's a PT1000 and not a PT100? PT100 would require a daughterboard.

dc42

@wcmartino do you have a multimeter? If so, disconnect the PT1000 cable at the Duet and measure its resistance.

wcmartino

@Phaedrux I have two of them and they are both pt1000's, very hard to read but it is stamped on the part. Tried both plugged directly into the Duet with the same results.

@dc42 Measured the resistance at the connector going into the Duet and my spare PT100, at room temp they are reading about 1.1k ohms, which is about what I expect.

Phaedrux

@wcmartino said in Mosquito Hotend PT1000 issues:

Tried both plugged directly into the Duet with the same results.

Did you change the config to suit?

Does the spare PT1000 work on the Duet?

dc42

@wcmartino yes 1.1K at room temperature is about right.

Please post a photos showing how the Pt1000 is connected to the Smart Effector, and how the Smart Effector is connected to the Duet.

wcmartino

@Phaedrux Yes I changed the config to suit. I get the same results with the spare PT1000.
@dc42 Pictures attahced.

dc42

@wcmartino it's not entirely clear from your photos, but it looks to me that you have 2 black wires in the cable(s) between the Smart Effector and the Duet. One is carrying one of the PT1000 wires, the other is carrying the ground connection to the Smart Effector. Is it possible that you have those wires crossed?

Can you try connecting your spare PT1000 directly to the TEMP2 connector on the Duet in place of the cable from the Smart Effector?

wcmartino

@dc42 I tested both PT1000 on the effect and directly on the board. They both show the same issue. Everything works fine with an e3d thermister, have had this printer for years. When I get a mintue I might try and plug them into my 6HC on my CoreXY and see what it shows. Kind of at a loss.

dc42

@wcmartino it might be worth running temperature input calibration. See https://docs.duet3d.com/en/User_manual/Connecting_hardware/Temperature_connecting_thermistors_PT1000#semi-automatic-calibration.

wcmartino

@dc42 That made no difference. The current Duet Mini 5+ was a rev0.5, which was working fine with the e3d thermistor. I have a new Mini that I just ordered for a different project, so I swapped them out and it is working just fine now. Makes me question if the old Mini is broken and it has not worked right for a while.

dc42

@wcmartino did you move the SD card from the original Duet 3 Mini to the new one, or did you use a new SD card? If you used a new SD card then perhaps there is something in the config.g or config-override.g file on the original SD card that was affecting the reading and overriding the calibration, such as a H or L parameter in the M308 command for that sensor.

wcmartino

@dc42 I am in SBC mode so nothing changed between the configurations. It is possible there is just something wrong with the older board.

dc42

@wcmartino I doubt it, however they will probably need different ADC corrections. Your new board will have had the calibration done and stored during testing; your older board will not. That's why I suggested you perform the calibration. PT1000 sensors are more sensitive to calibration errors than thermistors. Are you sure that you performed the calibration correctly on the older board?

wcmartino

@dc42 Yes, tried it several times, nothing helped for either sensor. Will have to revist it antoher day, I already have the printer put back together.

dc42

@wcmartino what L and H corrections did the calibration process report?

wcmartino

@dc42 Ok reconnested the board. With the sensor disconnected H reports -6. Jumpering the connector on the effector and running the l999 says correction is 1.

With the resistor in place upon booting it shows -20.5C. If I manually set H to -127 I still show -15.3C.

dc42

@wcmartino have you tried using a different temperature input?