prints not completing
-
Just did it again:
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.5 (2022-11-30 19:35:23) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-956BA-NA3TJ-6J9FL-3S86L-9T9LT
Used output buffers: 4 of 40 (40 max)
=== RTOS ===
Static ram: 152760
Dynamic ram: 67596 of which 0 recycled
Never used RAM 126788, free system stack 129 words
Tasks: SBC(ready,0.7%,452) HEAT(notifyWait,0.0%,322) Move(notifyWait,1.3%,245) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,339) TMC(notifyWait,9.0%,57) MAIN(running,88.9%,923) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:56:15 ago, cause: power up
Last software reset at 2023-02-02 10:12, reason: MemoryProtectionFault mmarValid mstkErr iaccViol, GCodes spinning, available RAM 130564, slot 2
Software reset code 0x4163 HFSR 0x01100000 CFSR 0x003bafb1 ICSR 0x00400804 BFAR 0x00344080 SP 0x2041b520 Task MAIN Freestk 1680 ok
Stack: 2041b594 20419a84 20418198 00000001 00000225 00486ca3 0062a208 010f0000 00000000 0048922f 00000000 fffc9fef ffffffff ffffffff ffeeb845 ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
Error status: 0x04
Aux0 errors 0,0,0
Step timer max interval 134
MCU temperature: min 49.1, current 54.9, max 55.0
Supply voltage: min 24.5, current 24.6, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.9, current 12.0, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/974/974, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 984, reads 35761, writes 2 timeouts 0
Driver 1: standstill, SG min 0, mspos 472, reads 35761, writes 2 timeouts 0
Driver 2: standstill, SG min 0, mspos 232, reads 35760, writes 2 timeouts 0
Driver 3: standstill, SG min 0, mspos 520, reads 35760, writes 2 timeouts 0
Driver 4: standstill, SG min 0, mspos 760, reads 35760, writes 2 timeouts 0
Driver 5: standstill, SG min n/a, mspos 8, reads 35762, writes 0 timeouts 0
Date/time: 2023-02-02 11:54:42
Slowest loop: 4.43ms; 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, segments created 28, maxWait 787ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 33718, completed 33718, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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
=== 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 52158, received 48894, lost 0, boc 0
Longest wait 2ms for reply type 6013, peak Tx sync delay 252, free buffers 50 (min 45), ts 12221/12221/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 2, checksum errors: 22
RX/TX seq numbers: 773/6602
SPI underruns 22, overruns 0
State: 5, disconnects: 1, timeouts: 1 total, 1 by SBC, IAP RAM available 0x2ad48
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.5
File /opt/dsf/sd/gcodes/wall-honeycomb-224x190size(mk3s).gcode is selected, processing
File:
Buffered code: G1 E-0.8 F4800
Buffered code: G1 Z1.6 F10200
Buffered code: G1 X171.407 Y128.529
Buffered code: G1 Z1.2
Buffered code: G1 E0.8 F4800
Buffered code: G1 F4200
Buffered code: G1 X160.198 Y122.061 E0.50923
Buffered code: G1 X148.991 Y128.529 E0.50916
Buffered code: G1 X148.991 Y141.471 E0.50924
Buffered code: G1 X160.198 Y147.942 E0.5092
Buffered code: G1 X171.407 Y141.471 E0.50927
Buffered code: G1 X171.407 Y128.589 E0.50688
Buffered code: G1 X171.071 Y128.723 F10200
Buffered code: G1 F4200
Buffered code: G1 X160.198 Y122.448 E0.49398
Buffered code: G1 X149.327 Y128.723 E0.49391
Buffered code: G1 X149.327 Y141.277 E0.49399
Buffered code: G1 X160.198 Y147.554 E0.49395
Buffered code: G1 X171.071 Y141.277 E0.49402
Buffered code: G1 X171.071 Y128.783 E0.49163
Buffered code: G1 X170.736 Y129.111 F10200
Buffered code: G1 F4200
Buffered code: G1 X170.736 Y128.917 E0.00763
Buffered code: G1 X160.198 Y122.836 E0.47873
Buffered code: G1 X149.662 Y128.917 E0.47866
Buffered code: G1 X149.662 Y141.083 E0.47874
Buffered code: G1 X160.198 Y147.166 E0.4787
Buffered code: G1 X170.736 Y141.083 E0.47877
Buffered code: G1 X170.736 Y129.171 E0.46875
Buffered code: G1 X170.4 Y129.111 F10200
==> 1344 bytes
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 675
Full transfers per second: 39.08, max time between full transfers: 553.1ms, max pin wait times: 53.9ms/1.8ms
Codes per second: 13.66
Maximum length of RX/TX data transfers: 3408/1096
2/2/2023, 11:51:57 AM Cancelled printing file 0:/gcodes/wall-honeycomb-224x190size(mk3s).gcode, print time was 0h 50m
2/2/2023, 11:51:57 AM Connection to Duet established
2/2/2023, 11:51:57 AM Warning: Lost connection to Duet (SPI connection reset because the number of maximum retries has been exceeded) -
@rickgomez2003 said in prints not completing:
=== SBC interface ===
Transfer state: 5, failed transfers: 2, checksum errors: 22
RX/TX seq numbers: 773/6602
SPI underruns 22, overruns 0
State: 5, disconnects: 1, timeouts: 1 total, 1 by SBC, IAP RAM available 0x2ad48
Buffer RX/TX: 0/0-0, open files: 0I don't know much about your setup, but these errors seem like a bad thing.
Is your SBC-to Duet connection good?
I have NO experience with this interface, so although my post might be an attempt to be helpful, it might not be helpful at all. If so, I apologize.
-
@alankilian
Thank you for the reply. I have just gone and checked the connection to the SBC and duet 3 and all seams to be well. I will go back and reseat everything just incase. -
did it again
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.5 (2022-11-30 19:35:23) running on Duet 3 MB6HC v1.01 (SBC mode) Board ID: 08DJM-956BA-NA3TJ-6J9FL-3S86L-9T9LT Used output buffers: 1 of 40 (21 max) === RTOS === Static ram: 152760 Dynamic ram: 67596 of which 0 recycled Never used RAM 126788, free system stack 114 words Tasks: SBC(resourceWait:,0.7%,466) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.9%,241) CanReceiv(notifyWait,0.0%,774) CanSender(notifyWait,0.0%,328) CanClock(delaying,0.0%,339) TMC(notifyWait,8.8%,57) MAIN(running,89.5%,923) IDLE(ready,0.0%,30), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 01:19:09 ago, cause: software Last software reset at 2023-02-02 12:23, reason: User, GCodes spinning, available RAM 130564, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 134 MCU temperature: min 52.0, current 56.7, max 56.9 Supply voltage: min 24.5, current 24.6, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 11.9, current 12.0, max 12.1, under voltage events: 0 Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/800/800, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, mspos 280, reads 22742, writes 19 timeouts 0 Driver 1: standstill, SG min 0, mspos 504, reads 22742, writes 19 timeouts 0 Driver 2: standstill, SG min 0, mspos 568, reads 22742, writes 19 timeouts 0 Driver 3: standstill, SG min 0, mspos 56, reads 22743, writes 19 timeouts 0 Driver 4: standstill, SG min 0, mspos 360, reads 22743, writes 19 timeouts 0 Driver 5: standstill, SG min 0, mspos 8, reads 22751, writes 11 timeouts 0 Date/time: 2023-02-02 13:42:10 Slowest loop: 60.72ms; fastest: 0.04ms === 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, segments created 28, maxWait 1182985ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 36262, completed 36262, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 3], 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 === 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 76114, received 95547, lost 0, boc 0 Longest wait 3ms for reply type 6053, peak Tx sync delay 277, free buffers 50 (min 45), ts 23747/23746/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === Transfer state: 5, failed transfers: 1, checksum errors: 26 RX/TX seq numbers: 54820/5364 SPI underruns 24, overruns 0 State: 5, disconnects: 1, timeouts: 1 total, 1 by SBC, IAP RAM available 0x2ad48 Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server v3.4.5 File /opt/dsf/sd/gcodes/wall-honeycomb-224x190size(mk3s).gcode is selected, processing File: Buffered code: G1 X30.6 Y100.821 E0.5361 Buffered code: G1 X30.6 Y87.425 E0.52708 Buffered code: G1 X42.398 Y80.615 E0.53602 Buffered code: G1 X42.398 Y66.759 E0.54525 Buffered code: G1 X30.6 Y59.945 E0.5361 Buffered code: G1 X30.6 Y46.549 E0.52708 Buffered code: G1 X42.198 Y39.855 E0.52694 Buffered code: G1 X53.998 Y46.665 E0.53609 Buffered code: G1 X65.798 Y39.855 E0.53609 Buffered code: G1 X77.598 Y46.665 E0.53609 Buffered code: G1 X89.398 Y39.855 E0.53609 Buffered code: G1 X101.2 Y46.665 E0.53616 Buffered code: G1 X113 Y39.855 E0.53609 Buffered code: G1 X124.8 Y46.665 E0.53609 Buffered code: G1 X136.6 Y39.855 E0.53609 Buffered code: G1 X148.4 Y46.665 E0.53609 Buffered code: G1 X160.198 Y39.855 E0.53602 Buffered code: G1 X171.998 Y46.665 E0.53609 Buffered code: G1 X183.798 Y39.855 E0.53609 Buffered code: G1 X195.598 Y46.665 E0.53609 Buffered code: G1 X207.398 Y39.855 E0.53609 Buffered code: G1 X219.2 Y46.665 E0.53616 Buffered code: G1 X231 Y39.855 E0.53609 Buffered code: G1 X242.6 Y46.55 E0.527 Buffered code: G1 X242.6 Y60.175 E0.53616 Buffered code: G1 X254.4 Y66.989 E0.53617 Buffered code: G1 X254.4 Y80.385 E0.52708 Buffered code: G1 X242.6 Y87.195 E0.53609 Buffered code: G1 X242.6 Y101.051 E0.54525 Buffered code: G1 X254.4 Y107.865 E0.53617 Buffered code: G1 X254.4 Y121.261 E0.52708 Buffered code: G1 X242.6 Y128.073 E0.53613 ==> 1536 bytes Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 710 Full transfers per second: 39.15, max time between full transfers: 75.3ms, max pin wait times: 56.7ms/9.8ms Codes per second: 7.95 Maximum length of RX/TX data transfers: 3136/1104 2/2/2023, 1:39:56 PM Connection to Duet established 2/2/2023, 1:39:56 PM Warning: Lost connection to Duet (SPI connection reset because the number of maximum retries has been exceeded) 2/2/2023, 1:31:23 PM Connection to Duet established 2/2/2023, 1:31:23 PM Warning: Lost connection to Duet (SPI connection reset because the number of maximum retries has been exceeded) -
What kind of cable are you using between the Duet and Pi?
Can you try increasing your logging level on the Pi and capturing another failure for us?
https://github.com/Duet3D/DuetSoftwareFramework/wiki/SBC-Setup-Guide#troubleshooting
-
I will increase the logging and try the steps listed in the link. I am using the ribbon cable that came with the Duet 3.
Thank you once again for your time.
-
@rickgomez2003
From the journaljournalctl -u duetcontrolserver -e Feb 02 14:05:41 Mod-Railcore DuetControlServer[596]: [info] Finished macro file bed.g Feb 02 14:05:41 Mod-Railcore DuetControlServer[596]: [info] Starting macro file deployprobe.g on channel File Feb 02 14:05:41 Mod-Railcore DuetControlServer[596]: [info] Running deployprobe.g Feb 02 14:05:43 Mod-Railcore DuetControlServer[596]: [info] Lift Z in advance of deploy Feb 02 14:05:55 Mod-Railcore DuetControlServer[596]: [info] Probe Pickup complete Feb 02 14:05:59 Mod-Railcore DuetControlServer[596]: [info] Macro deployprobe.g complete Feb 02 14:05:59 Mod-Railcore DuetControlServer[596]: [info] Finished macro file deployprobe.g Feb 02 14:08:35 Mod-Railcore DuetControlServer[596]: [info] Starting macro file retractprobe.g on channel File Feb 02 14:08:35 Mod-Railcore DuetControlServer[596]: [info] running retractprobe.g macro Feb 02 14:08:51 Mod-Railcore DuetControlServer[596]: [info] Macro retractprobe.g complete Feb 02 14:08:51 Mod-Railcore DuetControlServer[596]: [info] Finished macro file retractprobe.g Feb 02 14:08:51 Mod-Railcore DuetControlServer[596]: [warn] the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh. Feb 02 14:08:51 Mod-Railcore DuetControlServer[596]: [info] 30 points probed, min error 0.069, max error 0.375, mean 0.233, deviation 0.084 Feb 02 14:08:51 Mod-Railcore DuetControlServer[596]: Height map saved to file 0:/sys/heightmap.csv Feb 02 15:50:26 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0x1ad8052f, got 0x6115fcce) Feb 02 15:50:26 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0x1ad8052f, got 0x9934e6a0) Feb 02 15:50:26 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0x1ad8052f, got 0xceae592f) Feb 02 15:50:26 Mod-Railcore DuetControlServer[596]: [warn] Lost connection to Duet (SPI connection reset because the number of maximum retries has been exceeded) Feb 02 15:50:26 Mod-Railcore DuetControlServer[596]: [info] Connection to Duet established Feb 02 15:54:26 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0xa8babc30, got 0x5eb21be9) Feb 02 15:59:12 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0x832bd8b9, got 0x8d0ae49a) Feb 02 16:01:06 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0xd74685f5, got 0x874202a8) Feb 02 16:20:19 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0xfcd4a082, got 0x0e3d35b7) Feb 02 16:20:19 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0xfcd4a082, got 0xc2242c57) Feb 02 16:23:19 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0x3d925efb, got 0x1011a829) Feb 02 16:23:19 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0x3d925efb, got 0x92b7bd24) Feb 02 16:23:28 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0xe223f5e0, got 0xb16d02b1) Feb 02 16:23:28 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0xe223f5e0, got 0x123730b3) Feb 02 16:23:44 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0xdcd2951e, got 0x15b6d86f) Feb 02 16:53:33 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0x8d27c627, got 0x021f985c) Feb 02 16:53:40 Mod-Railcore DuetControlServer[596]: [warn] Bad header CRC32 (expected 0xecb4971d, got 0x76da9b1d) Feb 02 16:53:40 Mod-Railcore DuetControlServer[596]: [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000005) Feb 02 16:53:50 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0x2621aa62, got 0x9456a1e2) Feb 02 16:55:05 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0xbe11550b, got 0x4efb7681) Feb 02 16:55:25 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0x9949948c, got 0xb1f66eaa) Feb 02 16:56:51 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0x5f2bbf70, got 0xa805d97d) Feb 02 17:40:13 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0xc2bc5005, got 0xed70967b) Feb 02 17:40:13 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0xc2bc5005, got 0xa1e08861) Feb 02 17:40:13 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0xc2bc5005, got 0xb4597201) Feb 02 17:40:13 Mod-Railcore DuetControlServer[596]: [warn] Lost connection to Duet (SPI connection reset because the number of maximum retries has been exceeded) Feb 02 17:40:13 Mod-Railcore DuetControlServer[596]: [info] Connection to Duet established Feb 02 17:42:45 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0x5b25cb20, got 0xc293ffa7) Feb 02 17:42:45 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0x5b25cb20, got 0x81d87942) Feb 02 17:42:50 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0x04a883bc, got 0x092a4cea) Feb 02 17:43:07 Mod-Railcore DuetControlServer[596]: [warn] Bad header CRC32 (expected 0x9f3f9d2b, got 0xadc5b0a0) Feb 02 17:43:07 Mod-Railcore DuetControlServer[596]: [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000005) Feb 02 17:43:54 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0x14954ec0, got 0x38b2b2c3) Feb 02 17:43:55 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0x92fc17e8, got 0x492942ae) Feb 02 17:47:31 Mod-Railcore DuetControlServer[596]: [warn] Bad header CRC32 (expected 0xb666da13, got 0xd64cbb13) Feb 02 17:47:31 Mod-Railcore DuetControlServer[596]: [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000005) Feb 02 17:47:34 Mod-Railcore DuetControlServer[596]: [warn] RepRapFirmware got a bad data checksum Feb 02 17:47:47 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0x72d0e460, got 0x32dc4936) Feb 02 17:48:03 Mod-Railcore DuetControlServer[596]: [warn] Bad data CRC32 (expected 0xd8541d93, got 0x1e9e204c) -
@chrishamm could you have a look at the journal output
-
@rickgomez2003 Yeah, that certainly looks like a bad cable.
Do you have a GOOD ground connecting the power supply of the Raspberry PI to the power supply of the Duet?
If not, you could try that.
Although the cable SHOULD supply enough ground points, clearly there's something going wrong across that communication's cable.
-
@alankilian said in prints not completing:
@rickgomez2003 Yeah, that certainly looks like a bad cable.
Do you have a GOOD ground connecting the power supply of the Raspberry PI to the power supply of the Duet?
If not, you could try that.
Although the cable SHOULD supply enough ground points, clearly there's something going wrong across that communication's cable.
Thank you for the insight, I am trying this again but this time powering the 5v via the EX_5V header from the same meanwell power supply I am using for the SBC and removing the jumper. I will update you with the progress.
Thank you!
-
@rickgomez2003 I agree with @alankilian, that does look like a bad cable. You may be able to improve signal integrity between both boards by shielding the ribbon cable or by adding a ferrite bead.
-
Thank you for the reply, I will try that and attempt to get a new cable. The system did fail again just took a lot longer. I will try your suggestion and report back.
Thank you all for your time.
@alankilian @T3P3Tony @Phaedrux @chrishamm -
@alankilian @T3P3Tony @Phaedrux @chrishamm
Please mark this as solved it was a bad cable that caused the issue. I have tested and verified the issue and resolution.
Thank you for the quick and extremely helpful responses!
-
undefined Phaedrux marked this topic as a question
-
undefined Phaedrux has marked this topic as solved
-
@rickgomez2003 EXCELLENT!!!
Thanks for taking the time to record all your observations. It will help the next person (and all of us frankly) solve their problem.
