Help with trying to et a printer to work please

I have recently acquired a 3d printer with no name it looks very similar to my anet a8, but then I suppose they all do.

It has a GT2560 motherboard and shows Marlin 1.1.8 and https://marlin.fx.org on the screen when powered up.

Which then changes to a view of temperatures and ‘i3 Pro C ready’.

When I open my copy of repetier and click on connect it looks to connect to the printer in the same way my a8 does, the screen refreshes and repetier says ‘connected’.

The printer jumps as if the motors have been energized for a moment.

I assume the fact it says marlin 1.1.8 means the firmware is loaded and ok?

My a8 has omni 3d firmware and works fine from the same repetier software.

If I manually jog one of the steppers on the a8 the printer moves but nothing happens on the suspect printer.

When connected to the A8 it shows a list of items on the manual page including the hot bed, this is missing when I connect the suspect printer? If I click on the extruder to turn it on it fails to warm up on the suspect but works on my A8.

Everything looks to be connected.

The fuses on the GT2560 are fine.

Before I try to install a different set of firmware might someone have an idea what I could try to get some improvement?

thanks.

You can learn more about this machine you have by googling “i3 Pro C 3D printer”.

By any chance did you change the Repetier Host software so that the machine definition is Marlin vs what’s set for your A8?

1 Like

You could also try running Printrun to see if it works.

Yes, that’s another good GCode sender app but regardless of which software is tried, the OP must set which firmware the software is communicating with.

1 Like

Thank you for the replies, I googled the i3 pro and got simplyprint that I downloaded but it insisted I used a raspberry pi for some reason? so I then found easyprint, downloaded and succeeded in connecting but with the same result as the repetier. I then downloaded pronterprint with the same result but it did say ‘got rubbish reply from com3 at baud rate 115200. Maybe a bad baud rate’ and I had read somewhere that some of the printers use 250000 so I changed it to that, at first it said ‘bad baud rate’ etc but then said ‘printer is now on line.

I did a run and everything worked correctly.

I went back to easyprint, altered the baud rate and got the same result, everything worked correctly so I went back to my favourite software, repetier , did the same and got the same result it works fine.

So… thanks for your input, your prompts that even though it has connected there may still be problems has helped and solved my problem.

I hope you don’t disagree if I put the first one as the solution. and thank you all.

4 Likes

And now you know that communications between sender app and device requires the correct protocol(firmware type) selection and correct baud rate setting. Good to hear you found your way to the solution.

1 Like