Forum

Welcome Guest 

Show/Hide Header

Welcome Guest, posting in this forum requires registration.





Pages: 1 [2] 3
Author Topic: New build and attempted firmware for step/dir drivers
sandy
Administrator
Posts: 1226
Permalink
sandy
Post Re: New build and attempted firmware for step/dir drivers
on: March 26, 2012, 20:39
Quote

Brilliant, good to hear! I just finished this Gutenberg page

Image

And was heartily sick of the servo whine the time it finished, though the actual movement noise wasn't so bad. Quiet servos are not cheap though!

sn

merijnpen
Newbie
Posts: 19
Permalink
Post Re: New build and attempted firmware for step/dir drivers
on: May 9, 2012, 15:47
Quote

Hello there!
I was hoping someone here could help me...

When I use the polargraph controller, it sais that its sending out the commands, but my steppers are not moving!... The com-port seems right, and the circuit is tested and working....

Anyone here that knows a solution??

Thanks.

sandy
Administrator
Posts: 1226
Permalink
sandy
Post Re: New build and attempted firmware for step/dir drivers
on: May 9, 2012, 16:27
Quote

Hi Merijnpen, want to tell us a little more about your setup? Type of arduino, type of motorshield / circuit schematic, version of firmware etc. What testing are you doing to verify that the circuit works etc?

sn

merijnpen
Newbie
Posts: 19
Permalink
Post Re: New build and attempted firmware for step/dir drivers
on: May 10, 2012, 07:38
Quote

of course, im using an arduino uno with 2 stepstick controllers. with the exact kritzler schematics.

I can get the motors moving with this code: http://pastebin.com/hYW02QPE
Also, when i add a move command in the setup void of your code (// latest update 20120206 lanthan) they move at startup.

the problem seems to be recieving the commands from the plargraph controller.
I had problems connecting to my arduino before, but solved this by reinstalling the usb drivers. I am not sure if this is still a driver issue...

hope you can help, thanks

sandy
Administrator
Posts: 1226
Permalink
sandy
Post Re: New build and attempted firmware for step/dir drivers
on: May 10, 2012, 09:30
Quote

So what version of firmware are you using? (I mean, where did you get it from?) Lanthan's amendment is in more than one place, his code, my code.

The Kritzler code uses
MotorA step - pin 9
MotorA dir - pin 10
MotorB step - pin 11
MotorB dir - pin 12

So I'm guessing your wiring reflects that?

The test code you have has motorA (x) on
dir - pin 8
step - pin 9
enable - pin 10

So that doesn't match the kritzler code - not sure why it works for you.

Probably isn't a driver issue if you're getting movement using the test sketch.

The most recent version of the controller uses new comms protocol, where it appends a CRC rather that does a reply and confirm to make sure it's got the right command. I'm pretty sure all the firmwares I've published have been updated to do this, but I'm also pretty sure none of the firmwares I've published have their stepper pins mapped out the same way as der kritzler, so all of them will require a minor amendment to get them to work. If you haven't done the amendment, then that's probably the problem.

If the commands are disappearing out of the command queue in the controller quickly enough (the status line goes yellow, and says "BUSY ... " for a second), then the communication is working ok.

sn

merijnpen
Newbie
Posts: 19
Permalink
Post Re: New build and attempted firmware for step/dir drivers
on: May 10, 2012, 09:55
Quote

I have got the firmware from here: https://github.com/lanthan/polargraph4dirstep
I have changed the pins to match mine in the test code to get it to work.

I have also checked if the pins in the firmware are the same as the ones that I have connected the stepsticks to. Is there anything else that should be checked?

The commands are disappearing and the line goes yellow. so that is also working.
Im going to try a simple code to check if I can get communication with processing going then....

sandy
Administrator
Posts: 1226
Permalink
sandy
Post Re: New build and attempted firmware for step/dir drivers
on: May 10, 2012, 10:30
Quote

Ok, lanthan's code doesn't do the CRC check, so although it eventually goes green and issues a READY, it has actually just ignored the previous commands. For something like a "set home", it just just flicker BUSY for less than a second. On my testing here, lanthan's stays BUSY for a couple of seconds.

I would, if I were you, use my code from this branch:

Polargraph firmware - serial stepper driver

This is configured to use serial stepper drivers, and to use CRCs on the comms. It's set up to use the ITead motorshield, but just change the lines to point to your pins you need as you did for Lanthan's firmware. You can safely ignore the "..Microstepx" variables, they don't get used in the code. They're just there if you want to change microstepping programmatically rather than with jumpers etc.

sn

merijnpen
Newbie
Posts: 19
Permalink
Post Re: New build and attempted firmware for step/dir drivers
on: May 10, 2012, 10:37
Quote

Thanks, I will give it a try.

merijnpen
Newbie
Posts: 19
Permalink
Post Re: New build and attempted firmware for step/dir drivers
on: May 10, 2012, 10:43
Quote

Works!!! At first it didnt, but resetting the arduino and suddenly the motors started singing!

Thanks a lot

sandy
Administrator
Posts: 1226
Permalink
sandy
Post Re: New build and attempted firmware for step/dir drivers
on: May 10, 2012, 10:47
Quote

Champion! Glad to hear it. That code has the servo motor (pen lift) running off pin A0, so you might need to change that too. It also has no "enable" pin, so the motor drivers can't actually be turned off - I guess you have them tied to ground already. (It's just because the ITead shield doesn't break the enable pins out.)

cheers!
sn

merijnpen
Newbie
Posts: 19
Permalink
Post Re: New build and attempted firmware for step/dir drivers
on: May 10, 2012, 10:50
Quote

Great! I'll go get my gears from the lasercutter now! 😉

Is there a solution for the random moving of the motors when the arduino is resetting or stuff is getting uploaded onto the arduino? Its not a big problem, but might be annoying later on.

sandy
Administrator
Posts: 1226
Permalink
sandy
Post Re: New build and attempted firmware for step/dir drivers
on: May 10, 2012, 10:54
Quote

Never had the problem Marijnpen, better off asking the designer of the circuit about that. One solution would be to make sure they are not enabled until you want them to - so they are disabled by default, and only get enabled when required. It's a hardware thing, I don't have much insight into that.

sn

merijnpen
Newbie
Posts: 19
Permalink
Post Re: New build and attempted firmware for step/dir drivers
on: May 10, 2012, 10:56
Quote

ok thanks, I will look at that when it gets too anoying. thanks for the help and software anyways!

sandy
Administrator
Posts: 1226
Permalink
sandy
Post Re: New build and attempted firmware for step/dir drivers
on: May 10, 2012, 11:00
Quote

You're welcome! Happy scribbling!

merijnpen
Newbie
Posts: 19
Permalink
Post Re: New build and attempted firmware for step/dir drivers
on: May 13, 2012, 11:25
Quote

Hey!
There seems to be a problem with c17 commands. vector files worked perfectly before, but for no reason, now it doesnt react to the c17 commands any more. Moves every now and then when another command passes.

Does anyone know how this suddenly changed? and how it can be solved?

Thanks!

sandy
Administrator
Posts: 1226
Permalink
sandy
Post Re: New build and attempted firmware for step/dir drivers
on: May 13, 2012, 11:47
Quote

So c17 sometimes works, but other times not? Or just never works? I'm using it ok here, but I just had someone else report it was misbehaving for them too. In their case it could only draw to a point if it was in a small area right in the centre of the machine. Does that seem familiar?

sn

merijnpen
Newbie
Posts: 19
Permalink
Post Re: New build and attempted firmware for step/dir drivers
on: May 13, 2012, 12:19
Quote

It was working the first time that I started the machine, now it doesnt anymore. Makes no difference where I put the vector.
It is strange, since I didnt really change anything...

sandy
Administrator
Posts: 1226
Permalink
sandy
Post Re: New build and attempted firmware for step/dir drivers
on: May 13, 2012, 12:42
Quote

Is the controller showing the full vector ok? If you've uploaded new firmware remember you need to re-upload your machine spec again (setup tab -> upload machine spec) which sets steps per rev, mm per rev, machine size etc. That might be throwing the machines idea of it's own size off? The machine doesn't care about it's own size for most stuff, but it does for c17 because it does the coordinate translation. Only thing I can think of at the moment.

merijnpen
Newbie
Posts: 19
Permalink
Post Re: New build and attempted firmware for step/dir drivers
on: May 13, 2012, 13:01
Quote

I think the machine spec are correct, the pen moves to the right position, but when it gets the c17 commands, it stands still. No sound from the motors. The vector in the controller is ok and slowly disappears while the commands are sent.
Turns out this is not the only problem, when i try to make a scribble drawing, the pen moves to the right position, then starts scribbling at that point but stays scribbling at that point. The commands in this case are not disappearing and the controller stays busy.

I will spend some more time trying out different stuff, I will let you know if I manage to fix it.

merijnpen
Newbie
Posts: 19
Permalink
Post Re: New build and attempted firmware for step/dir drivers
on: May 13, 2012, 13:12
Quote

if i try to use the move direct tool, it uses a C17 command and the machine does nothing, when I use move pen to point, the C01 command works perfectly, just like when drawing vectors.

Pages: 1 [2] 3
Mingle Forum by cartpauj
Version: 1.0.34 ; Page loaded in: 0.199 seconds.