Jetty FW M215 Code times out

[Bill]

I sent this inquiry to Jetty, but, I'm sure he's pretty busy so I thought it better to post my question here...

So, the firmware is all installed -  with one exception I can't sort out.

Any idea why when I try to send the M215 command (with the proper parameters), the read times out? 

All other commands seemed to be sent correctly.

Any thoughts?

Bill

[Jetty]

2 possibilities I can think of.

1. You have an error in the command

OR

2. You're not using the correct RepG for the particular version of
firmware. Easiest way to solve that is to use the latest firmware
and the latest RepG from the thing: http://www.thingiverse.com/thing:17855

[Bill]

Well, I'm using the most recent versions for sure.

As for the command...There doesn't seem to be much to it.

Here's what I have

M215 X9413970 Y9413970 Z256000000 A36600134 

Im baffled.

Bill

[Jetty]

Have you tried that command all by itself? Does it still timeout?

[Bill]

I tried it previously, and again just now to be sure.  Even sending just the command by itself, nothing else, it still times out - yet, as before, all other codes appear to send fine.

So strange.

Bill

[Jetty]

That is 4 x 64 bit eeprom writes which will take a few milliseconds.

It's likely RepG is timing out before it's completed. There is a
note somewhere in the manual about that I
think.

But anyway, if it's timed out on just "1 try", it's probably not
anything to worry about.

It should have worked and you can ignore it. Unless of course, your
axis are scaled wrong, in which case
let me know.

[Bill]

I'll give it a try when I get home this afternoon - perhaps you're right.

It times out 5 times, FYI, then, it ends. I dont know if it only tries 5 times or if it fails 4 & succeeds on try 5. It does that every time.

Thanks

Bill

[Bill]

[Bill]

[Bill]

[Bill]

Sorry for the dup posts. iPhone acting wonky

[Christopher Lai]

I had this issue with a later version of repG. Try repG29 jetty edition

On May 22, 2012, at 5:32 AM, Bill <big...@gmail.com> wrote:

> Sorry for the dup posts. iPhone acting wonky
>

> --
> You received this message because you are subscribed to the Google Groups "MakerBot Operators" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/makerbot/-/AoD9EOHa6NAJ.
> To post to this group, send email to make...@googlegroups.com.
> To unsubscribe from this group, send email to makerbot+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/makerbot?hl=en.
>

[Bill]

Well, so far, it seems I'm out of luck.  I attempted to send the command & then print to see how it went...
It didn't go well. My printing attempt had the Y axis pushing against the front of the bot at the end of its travel
until I hit stop.

I guess I'm back to the drawing board for now. (meaning, regular FW).

Bill

[hellphish]

Did you try my suggestion of using a different version of RepG? 

--
You received this message because you are subscribed to the Google Groups "MakerBot Operators" group.

To view this discussion on the web visit https://groups.google.com/d/msg/makerbot/-/3kvmNgzRXjgJ.

[Jetty]

Hi Bill,

Please follow hellphish's suggestion, of using the upto date RepG from
Thingiverse, i.e. the Jetty version.
That's the no. 1. cause of a timeout, because what really happens is
the firmware gives and error,
RepG doesn't know what to do with it and times out.

If you are already doing that, then let me know and I'll investigate
further, however it'll be a couple of days before I have
time.

[Bill]

Ok. I tried several versions & it doesn't appear to work - however, the unaccelerated build (per my other thread) seems correct. That must mean even though it reported time outs, it took. You said that might happen.

Cheers,

Bill

[Aaron Double]

Dumb question,

You went into your skeinforge profile and put in larger numbers in speed, right?

> --
> You received this message because you are subscribed to the Google Groups "MakerBot Operators" group.

> To view this discussion on the web visit https://groups.google.com/d/msg/makerbot/-/tyRoa4HR-14J.

[Bill]

Oh, it's a totally fair question. I've done worse things. So, yes. I did update the profile with higher speeds. My problem is that it runs really fast but, not "accelerated". It's a terrible jerky mess ATM.

Bill

[Jetty]

> Oh, it's a totally fair question. I've done worse things. So, yes. I did update the profile with higher speeds.  My problem is that it runs really fast but, not "accelerated".  It's a terrible jerky mess ATM.

So have we solved the issue with it hitting the limits then? Or is
that still any issue?

Regarding the acceleration not taking. If it's fast, but not
accelerated, then 2 possibilities:

1. Acceleration isn't enabled (generally due to the gcode not being
sent to enable acceleration, provided it's the latest version of the
firmware, which I highly recommend).

2. You have the acceleration settings set so aggressively, that it
seems like it's not accelerated, but really it is, but using settings
that produce violence. Solution, use the recommended defaults.
Especially, Max Feed Rate, Max Acceleration and Jerk for all axis.
Those settings should be a recommended starting place, you can push
them, but not by too much.

[Jetty]

Dan pointed out 3:

Or 3, the Jetty firmware isn't installed. In that case, it is
possible
that timeouts might result when the firmware receives an unknown
command. (I seem to recall that some of the versions of the Cupcake
software would do that -- just not respond to an unknown commnad.
You had to upgrade your MB firmware when moving to a newer version
of RepG.) If RepG shows the version info and it's distinct, then
that would confirm what firmware is installed.

[Bill]

Ok...

Here's the link I got the version of RepG from - the one I'm using to send commands:
http://www.thingiverse.com/download:68548 (34 Beta)

When I tried to actually build with that version, my axes were all wrong and it hit the limits - that seems to be solved.
I fell back to version 29 from the same page, i.e.:  http://www.thingiverse.com/download:68546 and everything seemed to work well.

As far as I know, the firmware is installed.  After changing the URL in RepG, I upgraded
the firmware using the "Jetty" version that showed in RepG.  It said it was successful.

Perhaps, I should reflash it?

And as for the values I'm using...With the exception of the change of my A axis (geared extruder), I kept
all values at the default until I at least got it going. 

I'll go back tonight after work and reflash it and start all over, I guess.  I can't imagine
it didn't flash, but, the 1st thing I do when someone asks me to fix their computer is for
me to ask "is it plugged in". 


Cheers,

Bill

[Bill]

One more thing - Here's a video of my bot's current state of affairs.

http://dl.dropbox.com/u/8752060/Video%20May%2023%2C%208%2047%2048%20PM.mov

[Jetty]

> Perhaps, I should reflash it?

That's a good idea, can't hurt and out rules a few things.

Also, one really good way to test if acceleration is enabled is to
slow the axis right down in the firmware settings.

I.E. X/Y/Z Max Acceleration of 10
X/Y/Z Jerk of 1.

Failing that, the next stage will be getting a dump of eeprom to see
what it thinks it's set to.

[Bill]

Ok.  I'm going to be home over lunch (noon EST) and I'll reflash and load with the values you mention to see
what's what.

If that doesn't work - I'll look into dumping the EEPROM (Don't know how yet, but, I'm a quick learner).

Thanks for your help!!

Bill

[Bill]

Ok...

I'm home.  Reflashed firmware and set the values to the low numbers you (Jetty) suggested.

Now, it appears that acceleration is operating.  I has a nice gentle speed up and slow down on

all axes.  I think now, I need to re-tune things to work at full speed.  

I'll go back to your defaults and see what that does.

Bill

 

[Bill]

Spent my lunch break tuning it.  It appears that I still have lots of work to do, and it seems that
at least for the Cupcake, the defaults are much too high.  To get a smooth accel/decell like in your video,
it's going to need some careful tuning - mostly down.  At 100mm/s I lose Y steps.  Perhaps a belt issue. but,
that remains to be seen.  At 80 mm/s it works, but, not as smooth as the video (not close).

I'll play with it tonight and see what I can do.

Again...Thanks you (Jetty and all who commented) for helping me with this.  Seems like
I learn something every day.  And as soon as I think I know it all...I'm proven very wrong.

Bill