Re: [Machinekit] Re: 4-axis CNC running Machinekit won't fully home.

[Charles Steinkuehler]

1) Setup homing so each axis homes sequentially.  Then if you have 
errors, you'll know exactly which axis you need to fix.


2) You're using a gantry component, but it's unclear exactly how it's 
setup.  You appear to be using the Y-min and Y-max switches as the two 
homing switches for the gantry axis?  Some sort of machine or wiring 
diagram would help to diagnose any potential problems with your config.


3) Provide a dump of the HAL state when the system has homed one of the 
axis and stopped (eg: the output of "halcmd show").


On 2/29/2020 8:15 PM, Nathaniel wrote:

Thanks Justin,

I took your advice and played with the home and home offsets. It now fully
disengages from the switch while homing, but this hasn't solved the
problem. It will home whichever axis is crossest to its switch and then
stop. Any suggestions?

Thanks,
Nathaniel



--
Charles Steinkuehler
char...@steinkuehler.net

--
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 machinekit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/2f859f0d-b7f6-aef0-7da8-a79eb27e395b%40steinkuehler.net.

[Machinekit] Re: 4-axis CNC running Machinekit won't fully home.

[Nathaniel]

Thanks Justin,

I took your advice and played with the home and home offsets. It now fully 
disengages from the switch while homing, but this hasn't solved the 
problem. It will home whichever axis is crossest to its switch and then 
stop. Any suggestions?

Thanks,
Nathaniel 

-- 
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 machinekit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/442e75f1-9bc7-40fa-92de-25adc8a02eb7%40googlegroups.com.

RE: [Machinekit] Re: PICnc with Machine Kit.

[cern via Machinekit]

Hi,

I am all in for cheap, low entry hardware. Don't care if it is PIC or ARM. I 
think that for most cases it would be enough to have just serial connection 
between PC/SBC and this board. But some simple  Ethernet based communication 
(maybe lower in the OSI model) would be nice too.

I have a feeling that to get traction, it has to be simple, it has to be 
documented and it has to have tutorials and pre-compiled usecases which are 
near the real-word wants and needs of machine builders. (Like the BBB and 
CRAMPS, simple one use device.)

Some type of free-cool-in social networking with Youtube videos would also help.

Then, I think, you have change to get involvement from general community.

And I think that the interest is there: Look for example on the YAPSC:10v 
project.

BTW, there are implementations for the smartserial protocol which could be used 
for mining operation. The STMBL guy have implementation and there are guys 
around the world who reverse-engineered it.

Cern.


Feb 29, 2020, 19:27 by jo...@autoartisans.com:

>
> I do have a MESA 7i92H that works with > LinuxCNC>  on a dual boot PC.>   > I 
> have to switch to standard parallel port for MACH3 or use a USB Smooth 
> Stepper (more expensive than the 7i92H).
>
>
> I've also had my mill running with the > BeagleBone>  Black, > MachineKit>  
> and the > Xylotex>  Cape.>   > There are issues with the cape, not with the 
> BBB that had me change to a PC.
>
>
>  
>
>
> The BBB with > Xylotex>  uses the PRUs for step/> dir>  for up to 4 axis.>   
> > It can also take on Encoder input>   > Although there is a serial>   > port 
> the CAN bus port is taken up by the > Xylotex>  cape and I think SPI is too.> 
>   > Partly, IIRC, because the HDMI also uses much of the I/O.
>
>
>  
>
>
> There are LCD displays for the BBB but once again they take up all the 
> important I/O and support is minimal.>   > This screen was done in Python.
>
>
> http://www.autoartisans.com/MachineKit/BB-W1-LCD4.jpg
>
>
>  
>
>
> Once you remove the HDMI and change which pins on the BBB can be used for 
> step/> dir>  and spindle encoder the potential of using SPI or I2C for keypad 
> matrix and LCD display along with at least one Serial Port and one CAN port 
> for > CANopen>  you can address > MODbus>  VFDs and > CANopen>  based 
> hardware for tool changers and other peripherals.
>
>
>  
>
>
> That means the basic > Machinekit>  port to the BBB wouldn't have to be 
> touched, the HAL and INI files would take care of remapping the step/> dir>  
> pins but the AXIS user interface would have to go.>   > A new interface that 
> handled say 48 buttons, a graphical LCD display and an encoder knob like I 
> have on my ELS could provide the basics.
>
>
>  
>
>
> In fact, to start with and to not have to build large amounts of hardware, 
> I'd probably use my ELS with a 20x4 character screen (instead of the 20x2) 
> and the 35 buttons along with the MPG knob.>  
>
>
> For example:
>
>
> http://www.autoartisans.com/ELS/photos/ELS110D.JPG
>
>
>  
>
>
> http://www.autoartisans.com/MachineKit/FourLines2.jpg
>
>
>  
>
>
> This photo shows the RS232 connection and if the Y axis step/> dir>  pulses 
> aren't used and the CAN driver chip is installed I've had it operating as a > 
> CANopen>  User Interface Device.
>
>
> http://www.autoartisans.com/ELS/photos/ELSBottom.jpg
>
>
>  
>
>
> A prototype cape that has headers to plug in place of the PIC CPU on my ELS 
> could be the starting point as in the past I've created companion boards that 
> plug into jumper the header on the bottom of the ELS.>  
>
>
> http://www.autoartisans.com/MachineKit/IO_Interface-1.jpg
>
>
>  
>
>
> To expand a companion board with a ribbon cable to the 40 pin PIC IC socket 
> then gives access to all the I/O and the header.>   > The BBB could plug into 
> that.
>
>
>  
>
>
> And finally, since the BBB still has Ethernet it runs > MachineKit>  but can 
> perhaps talk MESA Ethernet protocol to a PC running > LinuxCNC>  or > 
> MachineKit>  for the full blown AXIS display.>   > So you get the best of 
> both worlds.>   > A small LCD/Keypad/MPG based module not much bigger than a 
> DRO for pseudo manual operation of the mill but also attach a laptop or roll 
> up a PC and you have full blown CNC.
>
>
>  
>
>
> This is all still kicking the tires.>   > Maybe a PIC32 would be an easier 
> solution.
>
>
>  
>
>
> John Dammeyer
>
>
>  
>
>
>  
>
>
>  
>
>
>  
>
>
>  
>
>
> From:>  machinekit@googlegroups.com [mailto:machinekit@googlegroups.com] > On 
> Behalf Of > mngr
> Sent:>  February-29-20 2:46 AM
> To:>  Machinekit
> Subject:>  [Machinekit] Re: PICnc with Machine Kit.
>
>  
>
>
> Hi,
>
>
>  
>
>
> In my humble opinion it should have both SPI and Ethernet connection.
>
>
> I do not see any difference in the real-time capabilities of these two 
> protocols.
>
>
>  
>
>
> cost would go up a bit, but this project could receive more attention form 
> already existing communities.
>
>
>  
>
>
> Maybe it could re-use 

Re: [Machinekit] Re: DE10 Nano suggested development environment?

[cern via Machinekit]

Hi,

Feb 26, 2020, 16:02 by blazin...@gmail.com:

> Yes the mesa firmware has been around for quite some time but only in this 
> project has it been this configurable. 
>
> Putting an fpga on a pcb isn't super easy for novices, while Mesa is 
> fantastic you are buying a board with the fpga's i/o hardware is set in 
> stone. You can reconfigure stepgens for PWM and such only because the 
> external hardware is the same. If I want to use a 7i76e but I need 6 
> stepgens,  well now I need to add a card. None of that is a major issue it's 
> good stuff but that's how it is.
>
> Couple that with the fact that there is a low end cpu attached directly to 
> that fpga and you have an all in one hmi type device that's completely 
> reconfigurable. The daughter card I made was built with the intention of 
> cramming as much stuff as possible, I now use it for prototyping everything 
> because it is literally as simple as writing a hal file and possibly making a 
> simple GUI.
>
> I can run just about any machine from my board, albeit a mill lathe, 
> whatever. My biggest issue is actually MK itself, it's too far behind 
> linuxcnc in key areas like joints+axis and since you mentioned mesa, well 
> that's rather far behind too. I wouldn't have a problem deploying mksocfpga 
> if I didn't have a problem deploying MK itself.
>
Currently, the machinekit/machinekit-cnc@master cannot be build on top of 
machnekit/machinekit-hal@master due to merge in of the so-called 
"single-module-dir" branch. I am planning to have a look at it in due time, but 
it would be helpful if someone else wanted to take a look at this.

Or do the LinuxCNC port. I, too, have been thinking about some kind of LinuxCNC 
jail where only the most trusted prisoners would be allowed access to the 
Machinekit-HAL. However, I didn't spend any significant time on this. I think 
Zultron or ArcEye did something, so maybe have a peek in theirs repositories.

Cern.

>
> On Wed, Feb 26, 2020, 4:41 AM Bas de Bruijn <> b...@basdebruijn.com> > wrote:
>
>>
>>
>> > On 26 Feb 2020, at 01:34, justin White <>> blazin...@gmail.com>> > wrote:
>>  > 
>>  > Its amazing that mksocfpga doesn't get more interest/support, I dont 
>> think people realize how powerful the idea is.
>>  
>>  Do you mean the reconfigurability? If not, the Mesa FPGA is around already 
>> for a long time, and it is great that the FPGA runs on such a small platform 
>> too.
>>  
>>  The reason I think it is not used very much is that for real use, in a 
>> production/manufacturing  environment, there is no hardware that one can 
>> “just buy and works”.
>>  
>>  If I want to use this in a customer project, from an integrator point of 
>> view, my concerns are about longtime availability of the hardware. I do not 
>> want to buy components, solder etc. I just want to open the box, attach 
>> wires to terminals and configure the machine.
>>  
>>  If something breaks or need to make another machine then I want to order 
>> the _exact_ same hardware, use the same code/version of the original and it 
>> should just work.
>>  
>>  This holds for BBB’s too btw. For customers I only use pc’s with the Mesa 
>> cards. There are other considerations than just the cost price of the board. 
>> Development time, hardware availability and support far outweigh the cost of 
>> the board.
>>  
>>  Just my 2 ct.
>>  
>>  
>>  
>>
>
>
>
> --
>  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 > machinekit+unsubscr...@googlegroups.com> .
>  To view this discussion on the web visit > 
> https://groups.google.com/d/msgid/machinekit/CA%2BQ02MN0Uiof8LE7m%2BWxx%2BPLKonQfug3GbixdXd6ZqzN3bDFTg%40mail.gmail.com
>  
> >
>  .
>

-- 
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 machinekit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/M1IRL95--3-2%40tuta.io.

RE: [Machinekit] Re: PICnc with Machine Kit.

[John Dammeyer]

I do have a MESA 7i92H that works with LinuxCNC on a dual boot PC.  I have to 
switch to standard parallel port for MACH3 or use a USB Smooth Stepper (more 
expensive than the 7i92H).
I've also had my mill running with the BeagleBone Black, MachineKit and the 
Xylotex Cape.  There are issues with the cape, not with the BBB that had me 
change to a PC.
 
The BBB with Xylotex uses the PRUs for step/dir for up to 4 axis.  It can also 
take on Encoder input  Although there is a serial  port the CAN bus port is 
taken up by the Xylotex cape and I think SPI is too.  Partly, IIRC, because the 
HDMI also uses much of the I/O.
 
There are LCD displays for the BBB but once again they take up all the 
important I/O and support is minimal.  This screen was done in Python.
http://www.autoartisans.com/MachineKit/BB-W1-LCD4.jpg
 
Once you remove the HDMI and change which pins on the BBB can be used for 
step/dir and spindle encoder the potential of using SPI or I2C for keypad 
matrix and LCD display along with at least one Serial Port and one CAN port for 
CANopen you can address MODbus VFDs and CANopen based hardware for tool 
changers and other peripherals.
 
That means the basic Machinekit port to the BBB wouldn't have to be touched, 
the HAL and INI files would take care of remapping the step/dir pins but the 
AXIS user interface would have to go.  A new interface that handled say 48 
buttons, a graphical LCD display and an encoder knob like I have on my ELS 
could provide the basics.
 
In fact, to start with and to not have to build large amounts of hardware, I'd 
probably use my ELS with a 20x4 character screen (instead of the 20x2) and the 
35 buttons along with the MPG knob.  
For example:
http://www.autoartisans.com/ELS/photos/ELS110D.JPG
 
http://www.autoartisans.com/MachineKit/FourLines2.jpg
 
This photo shows the RS232 connection and if the Y axis step/dir pulses aren't 
used and the CAN driver chip is installed I've had it operating as a CANopen 
User Interface Device.
http://www.autoartisans.com/ELS/photos/ELSBottom.jpg
 
A prototype cape that has headers to plug in place of the PIC CPU on my ELS 
could be the starting point as in the past I've created companion boards that 
plug into jumper the header on the bottom of the ELS.  
http://www.autoartisans.com/MachineKit/IO_Interface-1.jpg
 
To expand a companion board with a ribbon cable to the 40 pin PIC IC socket 
then gives access to all the I/O and the header.  The BBB could plug into that.
 
And finally, since the BBB still has Ethernet it runs MachineKit but can 
perhaps talk MESA Ethernet protocol to a PC running LinuxCNC or MachineKit for 
the full blown AXIS display.  So you get the best of both worlds.  A small 
LCD/Keypad/MPG based module not much bigger than a DRO for pseudo manual 
operation of the mill but also attach a laptop or roll up a PC and you have 
full blown CNC.
 
This is all still kicking the tires.  Maybe a PIC32 would be an easier solution.
 
John Dammeyer
 
 
 
 
 
From: machinekit@googlegroups.com [mailto:machinekit@googlegroups.com] On 
Behalf Of mngr
Sent: February-29-20 2:46 AM
To: Machinekit
Subject: [Machinekit] Re: PICnc with Machine Kit.
 
Hi,
 
In my humble opinion it should have both SPI and Ethernet connection.
I do not see any difference in the real-time capabilities of these two 
protocols.
 
cost would go up a bit, but this project could receive more attention form 
already existing communities.
 
Maybe it could re-use the MESA protocol over ethernet, allowing for mutiple 
slaves to be connected, reusing work on the machinekit side, and attracting the 
attention of the LinuxCNC community. I am in europe, I cannot buy MESA because 
it came out way too expensive.
There already are some open source motor driver, like Odrive or VESC. Maybe we 
could reuse something from here (BLDC are not stepper, i know, but hey, stepper 
are way easyer!)
How hard do you think it is to move the MESA protocol from an FPGA, VHDL, to a 
microcontroller?
 
I would use something like an ATSAME54, which is a cortex m4. I feel that atmel 
start libraries are well made, but I am not a seasoned developer.
 
I can work on this, but I need the guide of a experienced one.
 
Regards,
 
mngr

Il giorno venerdì 28 febbraio 2020 16:11:23 UTC+1, Mr Greg ha scritto:
@ JohnD
 
Re your OP
The answer is yes.
I have been using a Picnc + RPi2 -Jessy OS combo with machinekit for several 
yrs. Looking to upgrade/resurect/or move on if necessary.
I'm personally not the chap to do the detail code, but am working with a dev 
who has an interest and can contribute some limited time and effort.
 
I am currently exploring Pi4 + Buster with a view to either Mesa or Picnc? TBD
 
@ Tomp
I understand you have had Picnc successfully running on a Pi3 ?
I can't seem to get it to behave on a Pi3. Not with Jessie + MK anyways. All 
motors just spiral out of control soon as MK is started :(
All the SPI and dma addressing looks compatible They are both 2837
Any ideas?
 
@ All

[Machinekit] Re: PICnc with Machine Kit.

[mngr]

Hi,

In my humble opinion it should have both SPI and Ethernet connection.
I do not see any difference in the real-time capabilities of these two 
protocols.

cost would go up a bit, but this project could receive more attention form 
already existing communities.

Maybe it could re-use the MESA protocol over ethernet, allowing for mutiple 
slaves to be connected, reusing work on the machinekit side, and attracting 
the attention of the LinuxCNC community. I am in europe, I cannot buy MESA 
because it came out way too expensive.
There already are some open source motor driver, like Odrive or VESC. Maybe 
we could reuse something from here (BLDC are not stepper, i know, but hey, 
stepper are way easyer!)
How hard do you think it is to move the MESA protocol from an FPGA, VHDL, 
to a microcontroller?

I would use something like an ATSAME54, which is a cortex m4. I feel that 
atmel start libraries are well made, but I am not a seasoned developer.

I can work on this, but I need the guide of a experienced one.

Regards,

mngr

Il giorno venerdì 28 febbraio 2020 16:11:23 UTC+1, Mr Greg ha scritto:
>
> @ JohnD
>
> Re your OP
> The answer is yes.
> I have been using a Picnc + RPi2 -Jessy OS combo with machinekit for 
> several yrs. Looking to upgrade/resurect/or move on if necessary.
> I'm personally not the chap to do the detail code, but am working with a 
> dev who has an interest and can contribute some limited time and effort.
>
> I am currently exploring Pi4 + Buster with a view to either Mesa or Picnc? 
> TBD
>
> @ Tomp
> I understand you have had Picnc successfully running on a Pi3 ?
> I can't seem to get it to behave on a Pi3. Not with Jessie + MK anyways. 
> All motors just spiral out of control soon as MK is started :(
> All the SPI and dma addressing looks compatible They are both 2837
> Any ideas?
>
> @ All
> By way of a little history. I did quite a bit of testing & verification 
> for Kinsa' on the original Picnc v1.  ( circa 2012/13) This was on a Pic764 
> which had potential to run faster with more IO
> I'm not sure of how much info there is left for that version. I may have 
> some stuff archived?
>
> Cheers
> MrGreg
>
> On Thursday, 27 February 2020 06:42:41 UTC, John Dammeyer wrote:
>>
>> This project seems to have lapsed 5 years ago.  
>>
>> https://github.com/kinsamanka/PICnc-V2/wiki
>>
>>  
>>
>> Any interest in resurrecting it?
>>
>>  
>>
>> John Dammeyer
>>
>>  
>>
>> "ELS! Nothing else works as well for your Lathe"
>>
>> Automation Artisans Inc.
>>
>> www dot autoartisans dot com 
>>
>>  
>>
>

-- 
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 machinekit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/228f471a-3292-4373-9fe8-08bf92f8fd3c%40googlegroups.com.