Expensive brick?

[jeremy-coates 0]

I think I've got a broken UM board:

Recently bought UM kit, with UltiController - spent the weekend building it meticulously and was mostly successful. I got the system powered up, saw output on the UC, was able to see menus (got the motors to go to home position at front left) etc.

Then moved on to connecting with computer, using Cura 13.04-2 (Linux Fedora 18 x86_64), added myself to the dialout group to be able to get comms permission, ran Cura, cancelled first time wizard, switched to 115200 baud. All OK so far. Then ran first time wizard again - uploaded the latest Marlin firmware and then problems ever since:

Whilst firmware can upload and I can see comms back and forth with Arduino there's nothing from the printer itself apart from the buzz of the fan and the motors getting rather warm.

The display on the UC now just shows a row of white blocks row of blue, row of white and another row of blue. I've adjusted contrast as discussed on the forum to no avail (even tried switching the cables over - no change).

I've re-flashed the firmware several times (uploads and verifies) and get nothing different - I'm now suspecting it's the UM main board but I'm not sure how to diagnose / confirm this - any pointers?

I'd love to get up and running and do my first print but think I've hit an insurmountable brick wall and will have to get the UM board replaced before I can proceed. :(

 

[gr5 2,004]

This may sound strange but SEVERAL people had the same problem in the last few weeks and the solution for ALL of them was to carefully (very carefully) remove the arduino board form the main board, then plug the usb into arduino board only (usb powers up arduino just fine). Then upload the firmware one more time. Then unplug, power down and evern more carefully now attach the arduino board back to the main board.

I know it sounds bizarre but if you search these forums it fixed things for a few recent kits.

 

[jeremy-coates 0]

gr5: thanks for the advice, I've tried as you suggested:

cura

(<type 'exceptions.ValueError'>, ValueError("invalid literal for int() with base 10: '?'",), <traceback object at 0x42d8cf8>)

Flashing 89584 bytes

Verifying 89584 bytes

I see the tx/rx lights on the arduino flashing as you'd expect during this process, so I'm fairly sure this has worked.

I re-insert the arduino then re-power the UM - still the same, UC just gives the rows of blocks and nothing for the rest - cura reports communicaiton failure from first-run wizard. I've also tried this with all the wires disconnected from the UM apart from the UC & fan and tried with rebooting PC between flashing and re-connecting things (as sometimes USB doesn't seem to reset). Not sure what to do next really, open to suggestions?

 

[phanc60844 0]

Does it work with the UC disconnected? If it does it must be a fault with the UC, otherwise check the voltage on the main board from the power supply, could be low??????

paul

 

[jeremy-coates 0]

phanc60844: Thanks, already tried with UC disconnected same effects - nothing but communication failure and noises like the motors are trying to do something. If it's the voltage on the main board then it's faulty and simply needs replacing as far as I'm concerned.

 

[gr5 2,004]

If it's the voltage on the main board then it's faulty and simply needs replacing as far as I'm concerned.

 

Of course but you need to determine if the problem is with the board or with the power supply. They are 2 different parts. This is a kit so you are expected (I would think) to experiment a little and use a voltmeter.

I hope you didn't think this was like buying an hp ink jet. This is a hobbyist kit and the kit isn't perfect. You need to know how to use a screwdriver and a voltmeter and files and such. Fortunately there are people here who can walk you though how to use a voltmeter if necessary.

So if the power supply is putting out 19V or so while connected to the UM board and the switch is turned on, then it's probably the board. If the power supply voltage drops significantly (say to 9V?) then it's probably the power supply but not 100% definitely. It's also possible the board is draining too much current for the supply to handle. So start out by measuring the voltage.

 

[jeremy-coates 0]

Thanks for the replies and sorry it's taken a while for me to conclude this (I've been out of the country so not had time to play until now!).

It turns out the issue was uploading firmware via Cura 13.04 on Linux: I booted into windows and ran everything from there and it sprang into life after the firmware uploaded! I'm currently running my first print happily but will try from Linux again after this (just won't be uploading firmware that way again anytime soon!)

Once again thanks for the help, it's appreciated.