Show all posts by user
I just went through this exorcise and what i found was the eeprom settings fro PID were not getting set as described in the other thread. I currently have to manually issue the proper M codes to set the PID values and then my Heater controls began functioning correctly.
-trout
by
Architect
-
Firmware - experimental, borrowed, and future
Sorry to interupt the config discussion going on,
But I just got back to working on getting this firm to work with repsnapper,
I was wondering if anyone has had and solved an issue with null lines pausing the print for ~20 sec
The line contains "n1 *69" (that's made up so the checksum is bs) ?
by
Architect
-
Firmware - experimental, borrowed, and future
Triffid_Hunter Wrote:
-------------------------------------------------------
> spaztik Wrote:
> > Is this correct? I really don't know what is
> going
> > on here with P I D and I_limit, is there
> something
> > I can read to help me understand?
> >
> > Edit: After thinking about this for a while, I
> am
> > wondering if I_limit should get divide
by
Architect
-
Firmware - experimental, borrowed, and future
jgilmore Wrote:
-------------------------------------------------------
> Have you looked at "correct" homing behavior vs.
> reprap standard behavior? i.e. correct behavior is
> to go to 0,0,0 even if a G92 command has moved
> 0,0,0 to some arbitrary locaiton. The more typical
> reprap behavior which is to interpret "go home" as
> "go mash the endstops and set current location t
by
Architect
-
Firmware - experimental, borrowed, and future
out of curiosity, what electronics are those of you who are successfully printing with this firmware using to control and power your heater element? I gather the rudimentary electronics would be Arduino PWM PIN -> MOSFET -> Heater with the temp_sensor and PID software controlling the PWM Pin. I assume this would be about the same for the heated bed as well.
-Arch
@edictor yeah Much prop t
by
Architect
-
Firmware - experimental, borrowed, and future
edictor Wrote:
-------------------------------------------------------
> Hmm.. That only confused me more..
>
> I attached the LEDs and they light up whenever I
> issue a manual move command from either Repsnapper
> or ReprapHost. But it seems to hang as I have to
> reset the Arduino to turn off the LEDs again.
> Motors do not move.
> Even issuing the command to move just
by
Architect
-
Firmware - experimental, borrowed, and future
that all sounds a bit complicated. I was keeping it as simple as possible. basically I want the end stops to be there for 2 reasons. homing Zero and not letting the axis crash into anything. so I put in a check (for min) right before the step call to each axis pin but do all the other house keeping i.e. count the step ans set did_step and all, just don't write the step to the pin if there is a si
by
Architect
-
Firmware - experimental, borrowed, and future
I did the same thing for awhile, man that seems like a long time ago, and its only been a month. try messing with the feed rate in repsnapper.
under the menu Edit -> Printer settings you can change the Min/Max Print settings. this is the F value when manually trying to move the axis. try about 1500 depending on your driver. I found that I can play with the value here then set the FeedRATE in
by
Architect
-
Firmware - experimental, borrowed, and future
I had the same questions when I started and the same set up.
you are correct in that DIO4 is digital Pin 4
that section of your config looks good.
what are your
STEP_PER_MM settings and MAXIMUM_FEEDRATE?
these had a lot with me getting my steppers to work.
I am working with getting repsnapper to work with this firmware at the moment too.
and the MIN settings are for the endstops.
by
Architect
-
Firmware - experimental, borrowed, and future
So, I tried the drill thing. Signal worked clean every time, even wrapped my optical sensor cables 5 times around my drill and ran it. that was fun and a little mad hatterish. so I think I have a very simple solution in place now for the stops. Don't step if the axis.direction = whats read from the axis.min_stop_pin. seems to be working very well and when I thought about it, if there is a tempor
by
Architect
-
Firmware - experimental, borrowed, and future
hm, I saw somethings last night in the code base I have that looked promising and I reviewed all the relevant posts here regarding the end stop code. I am wondering how to add "noise" to my environment for testing purposes. I am using shielded cat5 for my motor lines. which should protect the end stops for ambient noises. guess I'll find out. where were you thinking about putting in the end stop
by
Architect
-
Firmware - experimental, borrowed, and future
thanks for the info 50 C seems incredibly hot but thats around where they are, I'll check the temps while they are running.
again thanks for the info.
by
Architect
-
Stepper Motors, Servo Motors, DC Motors
thanks for the pointer. Where stands any development on using the opto stops in the latest master version of the firmware?
Is anyone currently working on a solution? if not I will put it up on my todo list.
thanks,
Karl
by
Architect
-
Firmware - experimental, borrowed, and future
Been working on my hardware and not software the last few days and i know this topic has been beaten here badly but i need some rudimentary understanding. Are the OPTO sensors hard kills to the motors or are they only used in the firmware to kill the motor when they have been activated. i ask cuz i am debating whether to use them or not. and to ask it a different way when the OPTO's are activated
by
Architect
-
Firmware - experimental, borrowed, and future
any ideas are appreciated.
I have some eBay NEMA 17 stepper motors which have resistance of 4.2 ohms across the coils. I am driving them with the pololu A4983 drivers with a power supply of 12V. they are functioning and work fine when tuned using the pot on the driver but, after a short time the motors become too hot to touch and i am afraid they may melt the mounts on my Mendel or damage the mot
by
Architect
-
Stepper Motors, Servo Motors, DC Motors
That's what i think i have implemented for repsnapper, it also sends -1 lines as well which I had to process differently.
I will check what I wrote tonight as i am getting a new 6 pack of beer and plan to code. interesting about the +2 line numbers 5D (at least the code source I have) increased N_expected to N+1 so that is what I assumed was the norm.
my next thought was to also go in and put a
by
Architect
-
Firmware - experimental, borrowed, and future
it seems my giddyness in my forum posts comes accross as a script-kiddy and noobish. sorry for that.
I'll blame it on the beers and posting, not to mention my horrific ability to communicate with the outside world.
I am doing my work on a "Unix like" Os, I am running repsnapper from my Unbunto machine.
As a side note, I use windows to see what the weather is going to be like outside and do my d
by
Architect
-
Firmware - experimental, borrowed, and future
well F'ing !a
spent all new years weekend trying to get repsnapper to work with this with line numbering and checksumming.
Could not for the life of me figure out why it wasn't working we'll the problem was staring me for 14 hrs right in the face it seems. repsnapper send "\r\n" after the code line. fair enough thats normal. 5D checks to see if it has a 10 || 13 and processes the new line. proble
by
Architect
-
Firmware - experimental, borrowed, and future
I think I resolved the checksum issue.
changed the types of checksum_read and Checksum_calculated to shorts from unsigned char
thusly when checksum_calculated is XOR with a ' ' (space char) it is a short XOR with a short instead of a char Xor with a short.. or something like that. I'm not a C programmer. anyways this seems to be working now.
the code change was in gcode_parse.h
short chec
by
Architect
-
Firmware - experimental, borrowed, and future
Put the ending space back into repsnapper here is the calculated checksum line results
Start
ok
N24 G1 X16.0 Y20.5 E1.6 F500.0 *30
rs 0 Expected checksum 62
rs 24
//Manually removed the space by hand
N24 G1 X16.0 Y20.5 E1.6 F500.0*30
ok
movement ensued.
so sometimes the checksum wants the space sometimes it doesn't this tells me its somewhere else in the code
by
Architect
-
Firmware - experimental, borrowed, and future
another issue related,
can anyone explain this out put?
19:13:25 Send >>Receivedos: 5120,3680,64,0,2000
19:13:26 Send >>Receivedst: 5120,3680,64,32,2000
19:13:26 Send >>Received:Q7/7E
19:13:26 Send >>Receivedos: 5120,3680,64,0,2000
19:13:27 Send >>Receivedst: 5120,3680,64,32,2000
19:13:27 Send >>Received:Q7/7E
19:13:28 Send >>Receivedos: 5120,3680,
by
Architect
-
Firmware - experimental, borrowed, and future
one more thing,
cuz I had an idea from that last post
N677 G1 X13.4 Y14.9 E0.5 F500.0*6
rs 0 Expected checksum 38
rs 677
so.... I'll keep pecking as I have gotten a few stls to completely process in repsnapper with no tinkering.
I like tinkering... and breaking things...
by
Architect
-
Firmware - experimental, borrowed, and future
one last issue, any idea how or why the firmware after processing 20 or 30 lines sends a resend command that must have been processed already?
23:06:19 Send >>Received: ok with parameter **************************************
23:06:19 Send >>SendData: N704 G1 X11.8 Y14.3 E1.8 F500.0*11
23:06:20 Send >>SendData: N705 G1 X10.3 Y14.1 E1.6 F500.0*12
23:06:20 Send >>Received:
by
Architect
-
Firmware - experimental, borrowed, and future
Working to get 5D running with repsnapper and I have come across this issue with the checksum
this line of code :
N111 G1 X12.8 Y19.2 E1.8 F500.0*6
give a rs signal with a bad checksum something like 38
adding a space between the F500.0 and the * it then ran
N111 G1 X12.8 Y19.2 E1.8 F500.0 *6
(in repsnapper it keep requesting this line over and over so I copied this line and ran it manually in
by
Architect
-
Firmware - experimental, borrowed, and future
Question on PINS,
my Arduino had 13 Digital outs, 6 of them are being used for X,Y, Z. I found that if I use ports 0,1 there are issues that i believe have to due with those being used for communications. I had originally plugged my Z stepper into DIO1 and DIO2 and it was acting very peculiar. The Config file says for the 328p not to use DIO9 & DIO10 because those are being used for timers.
by
Architect
-
Firmware - experimental, borrowed, and future
bug report:
for temp results from M105 command and repsnapper
I had to remove the space after "T: " in this line in temp.c
sersendf_P(PSTR("T:%u.%u\n"), temp_sensors_runtime.last_read_temp >> 2, c);
I will put a bug into github as well ( if I can figure out how too :-) )
by
Architect
-
Firmware - experimental, borrowed, and future
Running on Ubuntu 10.10 and following the install instructions for Ubuntu distro's, There were no issues with installation and compilation from the git source. thank you for a very simple install as far as compiling, dependencies and makes go. Is there anyway to run test files without a fully functioning Mendel? I am hoping to test my electronics and pieces as i build. for now the controls for e
by
Architect
-
RepSnapper