ReplicatorG 17: firmware.xml not found
1,447 views
Skip to first unread message
Opalite
Jun 24, 2010, 10:47:06 AM6/24/10
to MakerBot Operators
Ever since I installed 0017, I've been getting the following error
upon starting it up:
"The firmware description file 'firmware.xml' was not found. You may
see this message if you're running ReplicatorG for the first time and
are not connected to the internet, or if you are running ReplicatorG
on a read-only system."
The computer is connected to the internet (wireless); it's running
Vista as a non-administrator, but IIRC this didn't cause problems with
0016. The error doesn't interfere any with printing, but it's also
showing up when I try to install the motherboard update, which is a
bit of a problem.
Perhaps there's some blindingly, stupidly obvious solution to this,
but I don't know what it is.
upon starting it up:
"The firmware description file 'firmware.xml' was not found. You may
see this message if you're running ReplicatorG for the first time and
are not connected to the internet, or if you are running ReplicatorG
on a read-only system."
The computer is connected to the internet (wireless); it's running
Vista as a non-administrator, but IIRC this didn't cause problems with
0016. The error doesn't interfere any with printing, but it's also
showing up when I try to install the motherboard update, which is a
bit of a problem.
Perhaps there's some blindingly, stupidly obvious solution to this,
but I don't know what it is.
Opalite
Jun 24, 2010, 2:12:18 PM6/24/10
to MakerBot Operators
Further investigation reveals that firmware.xml is present neither in
the folder nor in the zip, no matter how many times I download it.
There's a firmware.xml in the folder for 0016, should I just copy that
over? Or would that be fatally stupid?
the folder nor in the zip, no matter how many times I download it.
There's a firmware.xml in the folder for 0016, should I just copy that
over? Or would that be fatally stupid?
Opalite
Jun 28, 2010, 10:57:01 AM6/28/10
to MakerBot Operators
Copied over the firmware.xml from 0016. It doesn't complain anymore,
but it also doesn't show the update for 2.2 as being available; it
only goes up to 2.1.
but it also doesn't show the update for 2.2 as being available; it
only goes up to 2.1.
ddurant
Jun 28, 2010, 11:14:04 AM6/28/10
to MakerBot Operators
Can you get to this link? http://firmware.makerbot.com/firmware.xml
If you can, open ReplicatorG, do Preferences in the File menu and make
sure that's the link in the "Firmware update URL" field.
If you can, open ReplicatorG, do Preferences in the File menu and make
sure that's the link in the "Firmware update URL" field.
Opalite
Jun 28, 2010, 11:41:10 AM6/28/10
to MakerBot Operators
Yes, I can, and yep, that's the URL it uses. Still no luck, though.
On Jun 28, 10:14 am, ddurant <dduran...@gmail.com> wrote:
> Can you get to this link?http://firmware.makerbot.com/firmware.xml
On Jun 28, 10:14 am, ddurant <dduran...@gmail.com> wrote:
> Can you get to this link?http://firmware.makerbot.com/firmware.xml
ddurant
Jun 28, 2010, 12:01:49 PM6/28/10
to MakerBot Operators
Weird.
I'm pretty much out of ideas then, except that you can probably use
the file you get from that link to check for FW updates.
Any chance you're logged in as somebody who can't create/replace files
in the directory where repg is installed?
> > > only goes up to 2.1.- Hide quoted text -
>
> - Show quoted text -
I'm pretty much out of ideas then, except that you can probably use
the file you get from that link to check for FW updates.
Any chance you're logged in as somebody who can't create/replace files
in the directory where repg is installed?
>
> - Show quoted text -
Opalite
Jun 28, 2010, 12:12:10 PM6/28/10
to MakerBot Operators
Logged on as the user with administrative permissions, and not only
did it ping me about there BEING a firmware update on startup, it
worked perfectly.
I could have sworn I tried logging on as that user before, but maybe I
didn't and forgot I hadn't?...
In any case, many thanks for your help. Looks like this is resolved.
did it ping me about there BEING a firmware update on startup, it
worked perfectly.
I could have sworn I tried logging on as that user before, but maybe I
didn't and forgot I hadn't?...
In any case, many thanks for your help. Looks like this is resolved.
ddurant
Jun 28, 2010, 12:17:49 PM6/28/10
to MakerBot Operators
> Looks like this is resolved.
Great!
Reply all
Reply to author
Forward
0 new messages