Running Linux Pop!_OS based on Ubuntu 21.04
When I try to connect to my miniRAMBo on my laptop, it seems to work (although not every time) and spits out the following logs:
However, when I try to connect with my desktop, I get the error No start signal detected - forcing start
The output for the laptop (working) is :
17:00:12.484 : Printer reset detected - initializing
17:00:12.484 : echo:start
17:00:12.484 : Marlin 510S 2.0.7.2
17:00:12.489 : echo: Last Updated: 2020-10-15 | Author: (V1 Engineering, Ryan, 510S)
17:00:12.489 : echo:Compiled: Jul 7 2021
17:00:12.491 : echo: Free Memory: 3341 PlannerBufferBytes: 1472
17:00:12.614 : N1 M11034
17:00:12.614 : N2 M11536
17:00:12.614 : N3 M10536
17:00:12.614 : N4 M11435
17:00:12.629 : N5 M111 S698
17:00:12.630 : N6 T060
17:00:12.631 : N7 M2022
17:00:12.631 : N8 M8019
17:00:12.631 : N9 M10546
17:00:15.714 : N10 M10522
17:00:19.321 : DIGIPOTS Loading
17:00:19.321 : DIGIPOTS Loaded
17:00:19.329 : DIGIPOTS Loading
17:00:19.330 : DIGIPOTS Loaded
17:00:19.334 : echo:V82 stored settings retrieved (665 bytes; crc 51211)
17:00:19.588 : N11 M10523
17:00:19.601 : FIRMWARE_NAME:Marlin 510S 2.0.7.2 (Jul 7 2021 16:27:49) SOURCE_CODE_URL:url/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:V1CNC 510S EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff
17:00:19.601 : Cap:SERIAL_XON_XOFF:0
17:00:19.601 : Cap:BINARY_FILE_TRANSFER:0
17:00:19.603 : Cap:EEPROM:1
17:00:19.603 : Cap:VOLUMETRIC:1
17:00:19.603 : Cap:AUTOREPORT_TEMP:1
17:00:19.603 : Cap:PROGRESS:0
17:00:19.603 : Cap:PRINT_JOB:1
17:00:19.603 : Cap:AUTOLEVEL:0
17:00:19.604 : Cap:RUNOUT:0
17:00:19.604 : Cap:Z_PROBE:0
17:00:19.604 : Cap:LEVELING_DATA:0
17:00:19.604 : Cap:BUILD_PERCENT:0
17:00:19.604 : Cap:SOFTWARE_POWER:0
17:00:19.608 : Cap:TOGGLE_LIGHTS:0
17:00:19.608 : Cap:CASE_LIGHT_BRIGHTNESS:0
17:00:19.608 : Cap:EMERGENCY_PARSER:0
17:00:19.608 : Cap:PROMPT_SUPPORT:0
17:00:19.608 : Cap:SDCARD:1
17:00:19.612 : Cap:AUTOREPORT_SD_STATUS:0
17:00:19.613 : Cap:LONG_FILENAME:0
17:00:19.613 : Cap:THERMAL_PROTECTION:1
17:00:19.613 : Cap:MOTION_MODES:1
17:00:19.615 : Cap:ARCS:1
17:00:19.615 : Cap:BABYSTEPPING:0
17:00:19.615 : Cap:CHAMBER_TEMPERATURE:0
17:00:19.620 : N12 M220 S10082
17:00:19.620 : X:0.00 Y:0.00 Z:0.00 E:0.00 Count X:0 Y:0 Z:0
17:00:19.620 : N13 M221 S10082
17:00:19.624 : echo:DEBUG:INFO,ERRORS
17:00:19.625 : N14 M111 S682
17:00:19.625 : echo:No media
17:00:19.625 : echo:Unknown command: “M80”
17:00:19.625 : N15 T014
17:00:19.625 : N16 M155 S187
17:00:19.637 : echo:DEBUG:INFO,ERRORS
The output for my desktop (not working) is :
16:50:15.267 : No start signal detected - forcing start
16:50:15.268 : N1 M11034
16:50:15.268 : N2 M11536
16:50:15.268 : N3 M10536
16:50:15.268 : N4 M11435
16:50:15.272 : N5 M111 S698
16:50:15.273 : N6 T060
16:50:15.273 : N7 M2022
16:50:15.273 : N8 M8019
16:50:15.273 : N9 M10546
16:50:18.368 : N10 M10522
16:50:58.383 : Communication timeout - reset send buffer block
16:50:58.383 : N11 M10523
16:51:00.384 : N12 M10520
16:51:03.385 : N13 M10521
16:51:06.386 : N14 M10518
16:51:09.387 : N15 M10519
16:51:12.388 : N16 M10516
16:51:15.389 : N17 M10517
16:51:18.390 : N18 M10530
16:51:21.391 : N19 M10531
16:52:01.405 : Communication timeout - reset send buffer block
16:52:01.405 : N20 M10521
16:52:03.506 : N21 M10520
16:52:06.507 : N22 M10523
16:52:09.508 : N23 M10522
16:52:12.510 : N24 M10517
16:52:15.511 : N25 M10516
16:52:18.612 : N26 M10519
16:52:21.613 : N27 M10518
16:52:24.615 : N28 M10529
16:53:04.628 : Communication timeout - reset send buffer block
16:53:04.628 : N29 M10528
16:53:06.929 : N30 M10520
16:53:09.931 : N31 M10521
16:53:12.932 : N32 M10522
16:53:15.933 : N33 M10523
16:53:18.933 : N34 M10516
16:53:21.935 : N35 M10517
16:53:24.936 : N36 M10518
16:53:27.937 : N37 M10519
16:54:07.949 : Communication timeout - reset send buffer block
16:54:07.949 : N38 M10528
16:54:10.051 : N39 M10529
16:54:13.052 : N40 M10519
16:54:16.052 : N41 M10518
16:54:19.054 : N42 M10517
16:54:22.056 : N43 M10516
16:54:25.056 : N44 M10523
16:54:28.157 : N45 M10522
16:54:31.258 : N46 M10521
16:55:11.271 : Communication timeout - reset send buffer block
16:55:11.271 : N47 M10520
16:55:13.572 : N48 M10527
16:55:16.572 : N49 M10526
16:55:19.574 : N50 M10518
16:55:22.576 : N51 M10519
16:55:25.576 : N52 M10516
16:55:28.578 : N53 M10517
16:55:31.579 : N54 M10522
16:55:34.579 : N55 M10523
16:56:14.593 : Communication timeout - reset send buffer block
16:56:14.593 : N56 M10520
16:56:16.695 : N57 M10521
16:56:19.696 : N58 M10526
16:56:22.697 : N59 M10527
16:56:25.698 : N60 M10517
16:56:28.700 : N61 M10516
16:56:31.800 : N62 M10519
16:56:34.901 : N63 M10518
16:56:37.902 : N64 M10521
I will also often get gargage like : 16:58:41.040 : in?RI??t?l;~??????Vh??T?7?a<?!D?o??@?????c(?1N??I???/??????.?(8xN?T6?[CXU?????i?1J%?I??n??n??$m??D<?!N?D8?L???????f?IDCl?p?YY???!?<4N???T?7?a<?1'
Experience has told me that the serial monitor spitting out garbage is typical of a wrong baud rate, but I have it set to 250,000 just as I do on the laptop. It also wasn’t always working on the laptop, but it seems to be fine now.
any pointers?