[Machinekit] Re: Guidance on 3 axis retrofit

2018-05-21 Thread Jeff Pollard

Hi,

  Although I don't sell the BBB_DB25/26 any more I think it should be noted 
that I have run MachineKit with limit/home switches on all three axes 
(actually 4 since I had the Y and A axes slaved, and each had their own 
limit/home switch).  I'm not sure of your specific configuration, but the 
board *will* work with switches.  

  Your are defeating the safety setup of the board by trying to use pin 1 
as a different function.  The board was design to work with both pin DB1 
and pin DB10 working in conjunction as a safety stop loop in hardware. 

There is a solution to using physical pin 1 in an alternative fashion.  
First, you have to separate the output of the HCT541 pin 14 from the trace 
on the board by lifting the leg of the IC off the board.  Then you have to 
route that *pin* (not board trace), to the input of DB10.  This new route 
(or wire) is now  the safety circuity that would generally include a stop 
switch.  By completing that loop you complete the safety circuit as 
designed, and the HAL program will still function as intended .  After 
lifting pin 14 of the HCT541 from the board,  Pin 1 on the DB connector 
will be basically floating.  You can then wire any BBB output pin to the DB 
pin and control DB1 noting that unless you provide it, there will be no 
buffering of the BBB signal to the DB1 pin (i.e. the HCT541 can provide 
more load than the BBB).

Jeff

On Sunday, May 20, 2018 at 2:46:14 PM UTC-7, John Dammeyer wrote:
>
>
>
> On Sunday, May 20, 2018 at 5:20:57 AM UTC-7, Eric wrote:
>>
>> That looks awesome!
>>
>> Are you going to be able to manually move the axes too, or is it now 
>> going to be full CNC?
>>
>> At the speed that the XY axis turn the handles would have to be balanced 
> and not near my private parts.  That would hurt.
> The plan is full CNC.  I have both a ShuttleXpress (on my MACH3 CNC 
> router) and I'm trying out one of these on it since there's a windows 
> driver for it.
> Ebay item # 221940342899
>
> So with that I can manually move the axis.
>
> But I've run into a problem with the BBB-DB25/26 and since Xylotex doesn't 
> release schematics I'm not sure exactly how I'll fix it.   Jeff did reply 
> to a request about making the IOPWR# an active high output on pin 1 so it 
> would enable the PMDX-126 BoB.  But I've run into another issue and I'm not 
> sure if it's the BBB MachineKit or the way the Cape is wired.
>
> I pulled my LinuxCNC PC off the shelf and connected the same Probotix 
> BB-RF I was using with the Beagle.   So LinuxCNC on a parallel port.  A bit 
> of mucking around to get the correct polarity signals for Machine Enable 
> and ESTOP.  At that point I can jog in the positive direction, pull the 
> limit switch wire on the terminal strip to simulate running into a limit.
>
> At that point like the Beagle the Machine Power button on the screen goes 
> off.  The checkbox for override limits is not greyed out and I can check 
> the box.  Now I can click on the POWER button on the screen and jog in the 
> negative direction and reconnect the limit switch input to ground.  This is 
> the one that is shared for all three axis.  When I release the jog button 
> The Override checkbox is greyed out again.
>
> The MachineKit with BBB cape doesn't do that.  Hit a limit and Machine 
> POWER button goes off.  That also brings the IOPWR# low which then disables 
> the entire set of level translation buffers. And the Override limits 
> remains greyed out.  So now clicking on the Machine POWER button doesn't do 
> anything because the limit switch is still active.
>
> There may well be a solution but I haven't figured it out yet.  At the 
> moment I don't think the Xylotex cape will actually be usable with 
> MachineKit that has limit switches.
>
>

-- 
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.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.


Re: [Machinekit] Output Pulse on Start Up

2018-05-21 Thread John Dammeyer
I think I'm just too quick for it.  Just because axis.ngc is gone off the 
screen apparently doesn't mean that MachineKit is done.  

So editing a .hal or .ini file, saving the file, closing axis and then 
clicking on the desktop icon to restart machine kit results in this error.  
If I wait 30 seconds or more then I don't get the issue.

Why it takes so long I don't know.

John
  

On Friday, May 18, 2018 at 10:55:07 PM UTC-7, Schooner wrote:

> The problem with this run is right at the beginning of the error print.
>
> rtapi/rtapi_msgd.cc:247 ERROR: found existing RT instance with the same 
> instance id (0)
>
>
> Your last run did not close down properly and when it tried to create a 
> new one found the instance number already in use
> Linuxcnc was never conceived as being able to run more than a single 
> instance, so the numbers tend to be the same every time which is how this 
> error shows.
>
> Why it isn't closing down properly is another matter. 
>
> On 5/19/2018 5:18 AM, John Dammeyer wrote:
>
> I'm running a BBB with Xylotex BBB-DB25/26.  Often when I start up 
> MachineKit I get the opening banner, it vanishes and then a minute or so 
> later pops up with an error window.  Attached is the dump.  I can restart 
> and MachineKit begins normally.  Or maybe it fails again and then runs 
> correctly the third time. 
>
> Also, the Xylotex uses the DB25-1 pin as IOPWR# which is an active low 
> signal coupled through the ESTOP switch to DB25-10.  I've added a pull up 
> resistor to DB25-1 and it's coupled to an active low Relay Driver circuit.  
> The relay connects the ESTOP DB25-10 input to ground.
>
> When MachineKit starts properly it blips the DB25-1 pin low for about one 
> second before it finishes starting up and then keeps that output off (at 
> +5V) until the ON button is clicked.  And if the ESTOP button or ESTOP or 
> LIMIT switches are activated the IOPWR# also returns high and the relay 
> goes off.  So everything works correctly except for the pulse on the IOPWR# 
> pin when MachineKit starts up.  
>
> This does not happen when the Beagle boots from power up.  Only when the 
> Icon for MachineKit with my G3616 ini and hal file configuration is clicked 
> and MachineKit starts rather than fails.  When it fails and throws up the 
> log window the output is not blipped.
>
> I've mentioned them both because I don't know if they are related.
>
> Here's the failure.
> Loading Real Time OS, RTAPI, and HAL_LIB modules
> rtapi_msgd startup failed - aborting
>
> Debug file information:
> rtapi/rtapi_msgd.cc:247 ERROR: found existing RT instance with the same 
> instance id (0)
> /usr/libexec/linuxcnc/rtapi_msgd: failed to create global segment
> /usr/bin/linuxcnc: line 750:  3503 Segmentation fault  $HALCMD -i 
> "$INIFILE" -f $CFGFILE
>
>
> Is this perhaps as simple as an older version that just needs to be 
> updated?  If it's an error in the HAL file why doesn't it show up every 
> time?
>
> Thanks
>
>
> -- 
> 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+...@googlegroups.com .
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.