5th Gen connection problems

[Gazmondo]

Hi

Yesterday I took delivery of a new 5th Gen Desktop replicator (my first experience of 3D printing).

I installed the MakerBot Desktop software and can export models to a USB stick for printing but can't actually connect proper from my computer via the USB cable. Nothing happens when I plug the cable in (no USB noise, no error, just silence).

Support asked me to ensure I have the latest firmware loaded but it seems there is no way to update the firmware without a USB connection! (Or did I miss something). Furthermore, I see I only have version 1.0.1 which seems very old for a brand new machine (isn't the latest 1.0.8.84?).

Connection via ethernet is also not working. I have an IP address and can connect via a browser. The desktop software initially finds the printer and asks me to press the button to authenticate but then I get an error saying it failed to connect (below is a portion of what might be a relevant log).

Can anyone advise how to get properly connected?

Thanks!

=====

birdwing.py:355: INFO

conveyor.machine.birdwing.BirdWingMachine:get_authentication_code

2014-07-01 18:09:42,164

Retrieving auth code from {u'vid': 9153, u'ip': u'10.xx.xxx.xx', u'pid': 5, u'iserial': u'23C100053C705900120E', u'port_type': 'NetworkPort', u'port': u'9999'}

birdwing.py:355: INFO

conveyor.machine.birdwing.BirdWingMachine:get_authentication_code

2014-07-01 18:09:42,664

Retrieving auth code from {u'vid': 9153, u'ip': u'10.xx.xxx.xx', u'pid': 5, u'iserial': u'23C100053C705900120E', u'port_type': 'NetworkPort', u'port': u'9999'}

listener.py:104: INFO

conveyor.listener.TcpListener:_log_connection

2014-07-01 18:09:42,756

Accepted ('127.0.0.1', 64112) listener

birdwing.py:355: INFO

conveyor.machine.birdwing.BirdWingMachine:get_authentication_code

2014-07-01 18:09:43,164

Retrieving auth code from {u'vid': 9153, u'ip': u'10.xx.xxx.xx', u'pid': 5, u'iserial': u'23C100053C705900120E', u'port_type': 'NetworkPort', u'port': u'9999'}

birdwing.py:355: INFO

conveyor.machine.birdwing.BirdWingMachine:get_authentication_code

2014-07-01 18:09:43,665

Retrieving auth code from {u'vid': 9153, u'ip': u'10.xx.xxx.xx', u'pid': 5, u'iserial': u'23C100053C705900120E', u'port_type': 'NetworkPort', u'port': u'9999'}

birdwing.py:162: INFO

conveyor.machine.birdwing.BirdWingMachine:decorator

2014-07-01 18:09:44,165

Auth error on get_authentication_code, dropping connection

Traceback (most recent call last):

  File "python\conveyor-2.3.0-py2.7.egg\conveyor\machine\birdwing.py", line 153, in decorator

    return func(*args, **kwargs)

  File "python\conveyor-2.3.0-py2.7.egg\conveyor\machine\birdwing.py", line 356, in get_authentication_code

    return self._client_thread.get_authentication_code(client_secret,

AttributeError: 'NoneType' object has no attribute 'get_authentication_code'

jsonrpc.py:365: WARNING

conveyor.jsonrpc.JsonRpc:_invokemethod

2014-07-01 18:09:44,165

handled exception

Traceback (most recent call last):

  File "python\conveyor-2.3.0-py2.7.egg\conveyor\jsonrpc.py", line 359, in _invokemethod

    result = func(*args, **kwargs)

  File "python\conveyor-2.3.0-py2.7.egg\conveyor\server\__init__.py", line 1594, in get_authentication_code

    thingiverse_token)

  File "python\conveyor-2.3.0-py2.7.egg\conveyor\server\__init__.py", line 439, in get_authentication_code

    code = machine.get_authentication_code(client_secret, username, thingiverse_token)

  File "python\conveyor-2.3.0-py2.7.egg\conveyor\machine\birdwing.py", line 164, in decorator

    raise JsonRpcException(94, 'Authentication error', None)

JsonRpcException: (94, u'Authentication error')

listener.py:104: INFO

conveyor.listener.TcpListener:_log_connection

2014-07-01 18:09:44,775

Accepted ('127.0.0.1', 64115) listener

listener.py:104: INFO

conveyor.listener.TcpListener:_log_connection

2014-07-01 18:09:46,789

Accepted ('127.0.0.1', 64116) listener

listener.py:104: INFO

conveyor.listener.TcpListener:_log_connection

2014-07-01 18:09:48,806

Accepted ('127.0.0.1', 64117) listener

listener.py:104: INFO

conveyor.listener.TcpListener:_log_connection

2014-07-01 18:09:50,823

Accepted ('127.0.0.1', 64118) listener

[John David]

I had the same issue with my bot this weekend. After a 5 hour conversation with the Great Support team the figured it out and got my firmware to up grade. I suggest calling support as early as possible to insure a chance to not be stuck on eternal hold. once you get them they are Great to help.

He ended up using a different computer I had and he had to reconfigure the router settings to get it to work ( he went too deep for me to understand exactly what he did)

Good Luck

[Dr.P]

Just a thought for you,

When i had my 5th Gen, and played with trying to connect via WEB browser (direct IP address), the moment i hit enter, i lost connection via MakerWare Desktop.

Then only way i could get the connection back was to power cycle printer.

I thought this was strange and tried a few more time, each time, the exact same happened, lost connection.

By the way, i was trying a few basic ports, to see what i would get, and i got nothing.

Perhaps it was halting the background service in some way.

[Gazmondo]

Thanks for the advice. I'm in the UK so calling support is a little more complicated but I'll try.

USB seem totally dead. I have tried many times but it doesn't do a thing.

It is at work and so I don't have much control over the network configuration. I wonder if it is possible to connect directly via the ethernet cable? I did try with no success but wasn't 100% sure which IP address to input (I tried 127.0.0.1 and the one displayed in the network settings on the machine but it didn't find anything).

Incidentally, how much difference does updating the firmware from 1.0.1 make? Does it have a big impact on print quality?

Thanks

Gareth

[Jetguy]

Huge.  With 5th gen, it is pretty safe to say use the latest ALWAYS.

In fact, in general, there is ALWAYS a good reason to update and that is because in over 4 years, I've never seen code that wasn't riddled with so many bugs. Every iteration is hopefully 1-5 bugs fixed and maybe a good feature thrown in.

The latest was Wi-Fi support- so yes, you want the latest.

[Joe Soap]

If you are going to connect PC to bot then a standard CAT5/6 cable will not work because the transmit/receive lines haven't been swapped in the connection.

Forgive me if my terminology is wrong, but I think you need something called a patch cable - which is designed to go directly from PC to printer without going thru a switch. If you have network people at your place they'd know what was required.

--
You received this message because you are subscribed to the Google Groups "MakerBot Operators" group.
To unsubscribe from this group and stop receiving emails from it, send an email to makerbot+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

---

This email is free from viruses and malware because avast! Antivirus protection is active.

[Jetguy]

You need a cross over cable for direct connection in theory- often found with DSL modems and sometimes are red cables so you know they are X-over.

 

It's possible the ethernet on either side (the printer or the computer) is auto sensing, but unlikely.

As stated, either X-over or a hub, switch, router, or some other nework device is required in between.

http://en.wikipedia.org/wiki/Ethernet_crossover_cable

 

See, this is why they have to charge for Makercare. If the manual was a little more explicit, but no, they assume folks understand basic Ethernet rules.

[Dr.P]

Cross over cables are not always one colour.

pick up both ends and compare the coloured wires, if they match, pin for pin, then its a straight though cable, ie, standard cable.

if you see a couple of coloured cables, in different locations, then its a cross over cable.

easiest way is to put a $20 cheap linksys hub in the middle.

On Tuesday, July 1, 2014 4:58:13 PM UTC-4, Gazmondo wrote:

[Joe Soap]

And the LinkSys hub would most likely offer DHCP services for handing out IP addresses.

However DO NOT attach the LinkSys to your regular LAN. - it should be between PC and peripheral only. If there were multiple DHCP servers on the LAN it could cause a right mess :)

--
You received this message because you are subscribed to the Google Groups "MakerBot Operators" group.
To unsubscribe from this group and stop receiving emails from it, send an email to makerbot+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dr.P]

Negative,

a switch (router) and a hub are different animals.

A HUB does not offer DHCP, or anything else, it is not a router, and has no smart console or web login, its dumb and just passes tcp/ip.

http://www.ebay.com/itm/Linksys-EFAH05W-EtherFast-10-100-5-Port-Auto-Sensing-Workgroup-Hub-/170711449551

This could be used instead of a cross over cable. This would only be used as an intermediate connection from your PC directly to "it", then from "it" to the printer. It would be a replacement for not having a cross over cable, but using two standard Ethernet cables with "it" in between.

http://i.msdn.microsoft.com/dynimg/IC105624.gif

On Tuesday, July 1, 2014 4:58:13 PM UTC-4, Gazmondo wrote:

[Jetguy]

Well, the OTHER giant gaping hole in this discussion is OK, you get the physical layer working but the MakerBot is DHCP only. The peer to peer connection isn't going to cut it here.

The MakerBot will not get an address and you won't be able to do anything.

There is a potential workaround. If you have wireless connection in the laptop and are running Windows, you can share the wireless connecto to the Ethernet network using ICS (Internet Connection Sharing) and that does turn your PC into a DHCP server and grant the MakerBot an IP. At that point and time, you can then connect with MakerBot Desktop to the machine, update the firmware, and then configure the wireless so it's on your wireless network and move forward to printing.

http://windows.microsoft.com/en-us/windows/using-internet-connection-sharing#1TC=windows-7

[Dr.P]

Jetguy,

agree, i got sucked into the cross over cable conversation, just like you say, you need to give the printer an address to start with, otherwise its dead in the water anyhow.

Of course, you could be running windows server, and have DHCP service enabled, and still use crossover cable, but that may get to deep for many users.

On Tuesday, July 1, 2014 4:58:13 PM UTC-4, Gazmondo wrote:

[Gazmondo]

Thanks for all the great help.

I'll try to get help from our network guys as it's not really my thing!

Unfortunately I'm off for two weeks so will have to put it on hold. Maybe I'll get a more useful reply from the MakerBot support by then!

[lassi kinnunen]

you'd be surprised about how many laptops nowadays are auto-sensing. nowadays I just assume if it's reasonably new that it is autosensing. BUT since you have to get dhcp server running your laptop/desktop for 5th gen to connect, I see it as a bit problematic if one doesn't know what he's doing(enabling network sharing will put on a dhcp server/nat, so if you set windows to share your wifi connection for your ethernet, it should do it).

and as to dr p,    hub = connects all ports with all other ports, not so often seen nowadays(every port can see all traffic). a switch sends just to the port it knows the packet is going to and a router does ip routing...  and a router doesn't need to be offering dhcp services or such for it to be a router(and I got a bunch of switches that aren't routers).

so anyhow, most foolproof is to just take a small home office kinda wifi router+switch and connect only the bot and the computer to it.. but I would have tried to just direct connecting with a cable first, crossover cable or not. you can also create a crossover cable from a spare cable in a pinch with scissors.

[Joe Soap]

Sorry, terminology error. You are correct.

--
You received this message because you are subscribed to the Google Groups "MakerBot Operators" group.
To unsubscribe from this group and stop receiving emails from it, send an email to makerbot+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dan Newman]

> and as to dr p, hub = connects all ports with all other ports, not so
> often seen nowadays(every port can see all traffic). a switch sends just to
> the port it knows the packet is going to and a router does ip routing...

Yes, those beasts are a dying breed unless you have a managed switch and can
enable port mirroring. I actually have saved a couple of ancient hubs that
allow packet snooping. One of the hubs is so old, it still has a "thickwire"
ethernet connector (10Base5) while the other has a thinwire ethernet connector
(10Base2).

Dan