Correct me if I'm wrong, but "dirstep" looks like a typo in your HAL file. All of you're other pins that reference the .ini DIRSETUP parameter are named like "hpg.stepgen.04.*dirsetup*". Your line 174 "setp hpg.stepgen.04.dirstep [AXIS_2]DIRSETUP" is trying to set a pin that probably doesn't exist in your boards component. Change it to "setp hpg.stepgen.04.dirstetup [AXIS_2]DIRSETUP"
On Tuesday, April 30, 2019 at 12:02:48 PM UTC-4, Bradley Turner wrote: > > Thank you, reading through that documentation helped me to understand a > little bit more about what all I am doing, and what things mean when I > change them. > > The power issue is not related to being physically connected, at least I > don't think. I have 12V power plugged into the Motor (MOT and GND) > connectors on the CRAMPS board. When the machine is taken out of E-Stop the > CRAMPS E-stop LED turns off, but the CRAMPS green Active LED does not come > on, so I am guessing something is wrong with the E-Stop chain like you > mentioned. I looked at the EStop chain, however I wasn't sure what I could > or should change to get that to work. > > I agree that I am having many problems with my HAL file, and I would love > to clean it up but I don't really understand yet what clean looks like, and > how to get there. I would love to learn though, so if there are some good > examples of what the files should look like please let me know. > > Regarding the Z - Axis; I added the following after reading and looking > through the MPCNC AUTOHOME .hal file I downloaded from github. I added this > to try and solve the feedback path issues that I was having. If this is not > the right thing to do please let me know. > > (On line 158 of the hal file I included.) > > # z-axis > setp hpg.stepgen.04.position-scale [AXIS_2]SCALE > setp hpg.stepgen.04.steplen [AXIS_2]STEPLEN > setp hpg.stepgen.04.stepspace [AXIS_2]STEPSPACE > setp hpg.stepgen.04.dirhold [AXIS_2]DIRHOLD > setp hpg.stepgen.04.dirsetup [AXIS_2]DIRSETUP > setp hpg.stepgen.04.maxaccel [AXIS_2]STEPGEN_MAX_ACC > net zpos-cmd axis.2.motor-pos-cmd => hpg.stepgen.04.position-cmd > net zpos-fb hpg.stepgen.04.position-fb => axis.2.motor-pos-fb > net zenable axis.2.amp-enable-out => hpg.stepgen.04.enable > > I am now getting the error "CRAMPS.hal:174: paramter or pin > 'hpg.stepgen.04.dirstep' not found 14417" > I thought this meant that I had not defined it, so I attempted to do so by > adding > > "net emcmot.04.enable <= axis2.amp.enable-out > net emcmot.04.enable => hpg.stepgen.04.enable" > > But nothing seemed to change with my errors. Please let me know what I > should try next, or what I should look up/read/learn next. > Again thank you for all the help. > > On Monday, April 29, 2019 at 9:04:52 AM UTC-4, Charles Steinkuehler wrote: >> >> On 4/27/2019 9:36 PM, Bradley Turner wrote: >> > Thank you so much for the help, I am sorry for the late reply, I wasn't >> > able to get back to the lab until now. I'm sure those things seems >> super >> > obvious, I just don't know what to look for! I did what you said to try >> and >> > it fixed the issue on the Y (Axis 1) and the A (Axis 3), however I >> still >> > get the same issue on the Z axis (Axis 2). I tried adjusting the values >> up >> > and down, but it did not seem to affect the issue on the Z axis. >> >> Your problem with the Z axis is you do not have a feedback path. Your >> HAL code: >> >> # position command and feedback >> net emcmot.02.pos-cmd <= axis.2.motor-pos-cmd >> #net emcmot.02.pos-cmd => hpg.stepgen.02.position-cmd >> >> #net motor.02.pos-fb <= hpg.stepgen.02.position-fb >> net motor.02.pos-fb => axis.2.motor-pos-fb >> >> Creates a position command net (emcmot.02.pos-cmd) that goes nowhere >> and a feedback net (motor.02.pos-fb) that is not driven. >> >> >> > I had removed the homing earlier to try and narrow down what was >> causing >> > the issue. Once I get the joint following error and other movement >> errors >> > all cleared up I am intending to try and tackle the >> auto-homing-deracking >> > as well. Should I add this back in now, or continue with one problem at >> a >> > time? >> >> Your HAL file is pretty much a mess. I would recommend cleaning it up >> substantially and enabling the homing you want to use. You can debug >> fundamental issues (like your Z problem, above) using manual jogs with >> the axis unhomed. The next step would be to get homing working as >> desired, so you'll need the homing logic in the HAL file. >> >> > Separately I am having an issue where software - wise the axes (other >> than >> > the Z) all work correctly, however none of the motors spin. I have a >> > feeling that this issue is more related to the CRAMPS board, however I >> > figured I would mention it, as I am not sure what could be causing >> this. >> >> Make sure you are supplying power to the proper header on the CRAMPS >> board (P201, labeled MOTORS). There are several different power >> supply rails on the CRAMPS board and the most common cause of "nothing >> happens" has been the power wasn't connected properly. >> >> Another thing that can cause nothing to happen is a problem with the >> ESTOP chain. When the machine is taken out of ESTOP and powered on, >> the red ESTOP LED should be off, and the green ACTIVE LED should be >> on. If the ACTIVE LED (Machine Power) is not lit, the stepper drivers >> will be disabled by hardware. >> >> > I really appreciate all the help, I have tried to self educate, however >> I >> > haven't been able to find alot of information on configuring stuff like >> > this, or errors like this on machinekit, so if there is a repository >> where >> > I could learn more about it please let me know, I would love to look >> into >> > all of that. Thank you again, I have posted the (slightly) edited .hal >> and >> > .ini files. >> >> You seem to be having the most trouble with the HAL file. This is >> basically a plain text netlist file which creates a "wiring diagram" >> or schematic of the machine control logic. As with a real world >> schematic, things like unconnected pins or undriven nets will >> typically cause problems. There is a fair amount of documentation >> available for HAL, I would recommend you read through at least the >> introduction: >> >> http://www.machinekit.io/docs/hal/intro/ >> >> You don't need all the details (eg: creating new components with C or >> python), but you should be familiar with the concept of components, >> pins, signals, and functions. >> >> -- >> Charles Steinkuehler >> [email protected] >> > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
