I've recently purchased a Makerbot Replicator Dual clone made by CTC. I'm in the process of upgrading/adding a few parts to it, but noticed that I can't control or print via USB.
The machine prints perfectly from an SD card and I can see information in the terminal from the printer via USB in RepG and through OctoPrint - Such as M105 - but can't send any .x3g files to print or upgrade firmware (I wanted to flash Sailfish 7.7 eventually).
- Temperature auto-reporting is working
- Can send M105, M27, etc.. & get response
- Can select .x3g files from the SD card to print & the printer starts
- Can upload files (.stl, .x3G, .gco etc..) to Octopi, but even the .x3g files wont actually start on the printer.
- Tried sending
M140 T0 S200&
M106 T0 S100which received OK response, but there was no change reported, or indeed actually happening with the tool
Terminal Output from OctoPrint at connection:
Changing monitoring state from "Offline" to "Opening serial port" Connected to: <octoprint_GPX.gpxprinter.GpxPrinter instance at 0x6c9a02d8>, starting monitor Starting baud rate detection... Changing monitoring state from "Opening serial port" to "Detecting baudrate" Trying baudrate: 115200 Recv: start Send: N0 M110 N0*125 Changing monitoring state from "Detecting baudrate" to "Operational" Recv: Makerbot v7.4 Send: N0 M110 N0*125 Recv: echo: gcode to x3g translation by GPX Recv: SD card ok Recv: T:27 /0 B:21 /0 T0:27 /0 T1:26 /0 @:0 B@:0 Recv: T:27 /0 B:20 /0 T0:27 /0 T1:26 /0 @:0 B@:0 Recv: T:27 /0 B:21 /0 T0:27 /0 T1:26 /0 @:0 B@:0 Recv: ok Send: N1 M115*39 Recv: ok PROTOCOL_VERSION:0.1 FIRMWARE_NAME:Makerbot FIRMWARE_VERSION:7.4 FIRMWARE_URL:https://support.makerbot.com/learn/earlier-products/replicator-original/updating-firmware-for-the-makerbot-replicator-via-replicatorg_13302 MACHINE_TYPE:r1d EXTRUDER_COUNT:2 Send: M21 Recv: ok Recv: SD card ok Send: M20 Recv: ok Recv: Begin file list Recv: 2GB Recv: System Volume Information Recv: mesh_bed.stl Recv: xyzCalibration_cube.x3g Recv: CTCB_3DBenchy.x3g Recv: 3DBenchy.x3g Recv: ActiveCoolingDuct.x3g Recv: CTCB_ActiveDuctD4_UN.x3g Recv: UK_TROLLEY_TOKEN.x3g Recv: mesh_bed.x3g Recv: z-axis-support.x3g Recv: bed-screws.x3g Recv: spool_nut.x3g Recv: 2016_spool.x3g Recv: 2016_spool_no_raft.x3g Recv: ActiveDuctD4_UN.x3g Recv: Z_Axis_Support_Ends.x3g Recv: End file list Send: M105 Recv: ok T:27 /0 B:20 /0 T0:27 /0 T1:26 /0 @:0 B@:0 Send: M105
- The software connects to the board via USB and recognises that it is a Mightyboard running f/w 7.4
- Reports that it is an unvarified board
- Cannot use the GUI control tab to send commands to the printer
- Cannot send sliced .x3g files over USB, console shows a time out error instantly
- Saving .x3g to SD card does work
Is my Mightyboard just a dud, or is there something I can do to try and fix it?
The reason I want to try and solve this now, is that I'm planning on adding active cooling and LED lighting control so don't really want to do all that just to find out that I need to replace the board soon.
Some information meaning that the current firmware and board is reported, as well as current temperatures of the extruders and heat bed. I can print .x3g files from the SD card, but I can't send G-code commands or .x3g files through USB.
I have just tried a few G-code commands through OctoPrint terminal with mixed results.