Advanced Search

Thayloreing  i have the same problem

That's awesome it is moving forward.
I'm not in a huge hurry at the moment but I'll probably be pretty interested in testing out the dev branch once it's available.

Unfortunately I have confirmed that especially the projects I would be most interested in using my rack with will need some real chip protection. So I need to design some kind of pneumatic, electric, solenoid powered cover or something like that. So it would be kind of a novelty till I get that implemented. Hopefully I can pull that together pretty soon though.

Hello,
is it possible that Gmoccapy shows the User Defined M-Codes M100-M199, too?

Thanks!

Hello,
is there an other way to set the output complete off?
Is there something like a shutdown.hl, but for e-stop?
I controll a cutting unit with this M100/M101. After reset the e-stop it should not start automatically.
I have VOLATILE_HOME = 1 that after an e-stop homing is necessary. So the user have to start the program again and the start of M100 come to the right time.

Thanks!

As I saw, all the download links on the "Contributed Components" page are not working.

 

I missed the too, I'll fix that formatting error when I get a chance.
 

PCW wrote:

Not sure what you mean by output pin.

 

Ah, sorry that's a bit of a brainfart. Had to look at the stepgen setup to realize they do the exact same thing.

There's probably nothing wrong other than I was expecting to see scale, etc pins where they are actually parameters. That doc actually does say they are parameters, the word "parameters" is just shifted so I didn't notice it.

I believe I can add this option to my circuit as well. I just have to add a output connector and set all pins to output.

When I find time to design the PCB I will include this feature.

Scale and output types are parameters, not pins.
That does seem to be an error in the hostmot2
man page (it shows them as pins)

Not sure what you mean by output pin.
 

What is the name of your output pin?

The hm2....pwmgen stuff was setup when I was messing with it over a year ago but I know it did work because I was testing it with a small DC vacuum pump.

I didn't realize setting the scale wrong could make the output pin disappear but now that you mention it I do have  scale and output-type setp'd in the hal file for 2 of the 3 pwmgens. The config doesn't fail with "pin does not exist" when loaded but $ halcmd show pin does not show the scale or output-type pins either. According to the docs these are pins and not parameters so I don't know what's going on.

I'll go mess with the scale and such but that seems like a hm2 component bug or something if that's what's causing it

Fixed! Thanks for the bug report!

github.com/LinuxCNC/linuxcnc/commit/d359...3acf64a5cabe4665e5d3

It works for me:
halcmd -kf
halcmd: loadrt hostmot2
Note: Using POSIX realtime
hm2: loading Mesa HostMot2 driver version 0.15
halcmd: loadrt hm2_eth board_ip=10.10.10.10

---

halcmd: loadrt threads
halcmd: addf hm2_7i92.0.read thread1
halcmd: addf hm2_7i92.0.write thread1
halcmd: setp hm2_7i92.0.pwmgen.00.enable true
halcmd: setp hm2_7i92.0.pwmgen.01.enable true
halcmd: setp hm2_7i92.0.pwmgen.02.enable true
setp hm2_7i92.0.pwmgen.00.value .5
setp hm2_7i92.0.pwmgen.01.value .5
setp hm2_7i92.0.pwmgen.02.value .5

And I get square waves on all three PWM pins


Is its a PWM scale issue? (default scale is 1.0)

Ooops, you also need to add grotius-tp  here too
github.com/LinuxCNC/linuxcnc/blob/master/src/Makefile#L1330

Looking at my chromebook with 2.10 installed from a .Deb, tpmod.so is installed in
/usr/lib/linuxcnc/modules

My thinking is that you could just deploy your new files in the right location in a stand alone deb.

But I think you also do more than just create a new tpmod version because you change some other files. I think that results in a new motmod.so
If that's the case, its loaded in the hal file so the modular approach of Linuxcnc still lets you keep it compartmentalised and add everything to the core Linuxcnc build just by adding some new folders under /src/emc

The trajectory planner is in
src/emc/tp
So if you made a new folder
src/emc/grotius-tp 
for your planner and included a Submakefile in that folder, you  just need to edit the main make file to include the new folder.
Here is the main tpmod makefile entry
github.com/LinuxCNC/linuxcnc/blob/master/src/Makefile#L1230

You could also use the same approach for changes to motion
github.com/LinuxCNC/linuxcnc/blob/master/src/Makefile#L1215

I suspect the Debian .deb build will include all .so files built, so it may not need changing.

I tested this methodology once by building a new module plasmatask because Andy thought that might be a good approach for plasma. I copied the  /src/emc/task folder to /src/emc/plasmatask and updated the main make file as I describe. Everything built perfectly and I could load plasmatask in the ini file no problems.

If you could do this, grotius-tp would be super simple to include in the main distribution.
 

PCW, any idea why I'm missing all of the PWM output pins? None of the 3 pwmgens have been usable with the new firmware. The pwmgens have no output and the gpio pins that correspond have no output pin either.