Re: [Machinekit] Configuring a 10Khz charge pump for a G540 gecko using BeagleBone Black running machinekit

2017-02-01 Thread Tom M
Kirk.. I was looking your post over smart phone this morning and this was
the first chance I had to really look at your links in detail...
Nice job on the analysis on the  gecko btw..
We've been really happy with the G540 and sort of curious on what made it
tick..
So... I'm pretty sure we can figure out something to buffer the voltage and
amperage signal between the beagle-bone and the gecko. That's very useful
to know  that the frequency isn't that big of a deal.   Like I side we
where getting a nice signal just hooking up to the servo thread.

Charles,
I'm glad you like our vintage scope...
(Are any of you guys come out for the makerfaire that's happening in
chicago?
https://www.eventbrite.com/e/maker-faire-chicago-town-hall-tickets-31268285283





On Wed, Feb 1, 2017 at 9:16 PM, Kirk Wallace 
wrote:

> On 02/01/2017 10:46 AM, Tom M wrote:
>
>> Thank for the quick response.
>> When we connected charge pump we got a nice 500 Hz signal albeit 3
>> volts.  When  I attempted to create a 10k thread this is what we got as
>> far as a trace.
>>
>
>
> 3 Volts isn't high enough. The current into the G540 won't start to flow
> until you get above 3 Volts. Once you get flow, you need to make sure you
> get enough current. The input is DC blocked so you need to ensure there is
> enough high and low time to get good AC. The frequency isn't that important
> -- 200 Hz to 2 kHz should be okay.
>
>
>
> --
> Kirk Wallace
> http://www.wallacecompany.com/machine_shop/
> http://www.wallacecompany.com/E45/
>

-- 
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] Configuring a 10Khz charge pump for a G540 gecko using BeagleBone Black running machinekit

2017-02-01 Thread Kirk Wallace

On 02/01/2017 10:46 AM, Tom M wrote:

Thank for the quick response.
When we connected charge pump we got a nice 500 Hz signal albeit 3
volts.  When  I attempted to create a 10k thread this is what we got as
far as a trace.



3 Volts isn't high enough. The current into the G540 won't start to flow 
until you get above 3 Volts. Once you get flow, you need to make sure 
you get enough current. The input is DC blocked so you need to ensure 
there is enough high and low time to get good AC. The frequency isn't 
that important -- 200 Hz to 2 kHz should be okay.



--
Kirk Wallace
http://www.wallacecompany.com/machine_shop/
http://www.wallacecompany.com/E45/

--
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] Configuring a 10Khz charge pump for a G540 gecko using BeagleBone Black running machinekit

2017-02-01 Thread Charles Steinkuehler
I love the old 'scope!

You will definitely have to buffer the outputs of the BeagleBone, most
of which are only rated for a few mA of drive current.  If adding an
'HCT245 style buffer (or something similar) doesn't help and you really
need to generate a 10 KHz PWM output signal, you won't be able to do it
reliably with the ARM.  You should either use one of the hardware PWM
outputs, or you can get the PRU to output a PWM signal that fast.

To use the PRU, either setup a new PWM timebase with pwm_period=10
or just run a stepgen in velocity mode and control the duty cycle with
the steplen and/or stepspace settings.

...but neither solution will help with safety if the ARM core crashes
and stops running code.  Both the hardware PWM and PRU would keep
generating the chargepump output and your drivers would remain enabled.

On 2/1/2017 12:46 PM, Tom M wrote:
> Thank for the quick response.
> When we connected charge pump we got a nice 500 Hz signal albeit 3 volts.
> When  I attempted to create a 10k thread this is what we got as far as a
> trace.
> 
> On Feb 1, 2017 9:43 AM, "Kirk Wallace"  wrote:
> 
>> On 02/01/2017 07:02 AM, Kirk Wallace wrote:
>>
>> ... snip
>>
>>
>>> I seem to recall that the scope traces that got above 3Volts worked.
>>> Such as the motherboard port set to EPP worked:
>>> http://wallacecompany.com/machine_shop/G540/g540_mb_epp.jpg
>>>
>>> But set to SPP didn't:
>>> http://wallacecompany.com/machine_shop/G540/g540_mb_epp.jpg
>>>
>>
>> ... snip
>>
>> Oops, bad link above, this should be better:
>> http://wallacecompany.com/machine_shop/G540/g540_mb_spp.jpg
>>
>>
>> --
>> Kirk Wallace
>> http://www.wallacecompany.com/machine_shop/
>> http://www.wallacecompany.com/E45/
>>
>> --
>> website: http://www.machinekit.io blog: http://blog.machinekit.io github:
>> https://github.com/machinekit
>> --- You received this message because you are subscribed to a topic in the
>> Google Groups "Machinekit" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/machinekit/Mv7X6ddtPD4/unsubscribe.
>> To unsubscribe from this group and all its topics, 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.
>>
> 


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


Re: [Machinekit] 5i25 hostmot2 problem

2017-02-01 Thread Bas de Bruijn


> On 01 Feb 2017, at 22:10, Curtis Dutton  wrote:
> 
> I'll file a bug on this, as the documentation is not jiving with actual 
> behavior. I'll dig around, I may be able to provide the fix as well.

Changing the docs would be highly appreciated. We tried to make that as easy as 
possible via the "edit this page" button on the pages

http://www.machinekit.io/docs/documenting/contributing-documentation/

> 
>> On Tue, Jan 31, 2017 at 2:19 AM, schoone...@btinternet.com 
>>  wrote:
>> As a postscript.
>> 
>> Looking at some other configs, it appears that setting max-velocity and 
>> max-acceleration to zero
>> 
>> DOES work if the stepgen is set to type 1 (velocity stepgen).
>> 
>> I use that on a config to control a spindle through a speed board that 
>> converts step frequency into an analogue
>> 
>> voltage signal to control a VFD
>> 
>> regards
>>> On 30/01/2017 17:43, schooner30@btinternet wrote:
>>> I did look at that, as all my configs have values there.
>>> However it should just mean the maximum possible as you say, so it didn't 
>>> seem to be wrong.
>>> 
>>> Glad you have it sorted
>>> 
 On 30/01/17 17:31, Curtis Dutton wrote:
 SOLVED!
 
 Thanks for your help.
 
 The stepgen maxaccel and maxvel values were being set to 0 in my config.. 
 In linux cnc this was ok. The documentation states in machinekit and 
 linuxcnc that when set to 0 that the stepgens will only be limited to the 
 step timing settings and otherwise are not limited. This does not seem to 
 be the case as when I set the values of maxaccel and maxvel on the stepgen 
 to more than 0, then the stepgen works.
 
 
 
> On Monday, January 30, 2017 at 11:22:35 AM UTC-5, Curtis Dutton wrote:
> Ok I was running a rip build from master. Commit: 
> 079b1ed4adb30c60079d0d43a173002201f34538. Which appears to be the latest 
> commit.
> 
> Do you know what commit your sim is running from? I'd like to build that 
> version and see if I get a better result.
> 
> So I guess the hm2 driver now just exposes everything in the config of 
> the 5i25 and doesn't need the commit string?
> 
> 
> I'll try the sim here later today to see if it works for me.
> 
> Thanks,
>   Curt
> 
> 
> 
>> On Sunday, January 29, 2017 at 6:33:44 AM UTC-5, Schooner wrote:
>> If you run the hm2_stepper sim you should see position-fb updated when 
>> you jog, as per screen shot.
>> Does that work?
>> 
>> Your test does not run
>> newthread servo-thread cpu=0 100
>> is asking for a new thread called servo-thread, of a period cpu=0
>> 
>> Next the hm2_pci config string 
>> loadrt hm2_pci config="num_mencoders=0 num_stepgens=5 num_pwmgens=1"
>> AFAIK has not been used for some while and will also not run
>> hence
>> https://github.com/machinekit/machinekit/blob/master/configs/hm2-stepper/5i25.ini#L11
>> https://github.com/machinekit/machinekit/blob/master/configs/hm2-stepper/hm2-stepper-5i25.hal#L44
>> 
>> the configuration is whatever the 5i25 is   
>> flashed as.
>> 
>> All of which raises the question of what you are running and on what 
>> platform.
>> 
>> On a recent pull of machinekit on a amd64 computer running Jessie, the 
>> 5i25 works fine, I have used my 
>> 5i25/7i76 combo a lot just recently.
>> 
>>> On 28/01/17 20:26, Curtis Dutton wrote:
>>> Ok I have attached a halcmd file that demonstrates the issue.
>>> 
>>> The debug.txt contains the output of the halrun session.
>>> 
>>> Notice that after the position-cmd is set, position-fb has not changed.
>>> 
>>> The firmware on the 5i25 is 5i25_7i85sspx2
>>> 
>>> 
>>> Thanks,
>>>Curt
>>> 
 On Saturday, January 28, 2017 at 2:43:18 AM UTC-5, Schooner wrote:
 Without seeing your configuration files, we cannot even begin to guess.
 
 If you have done the same as John Fairbanks on the 7i80 post, you may 
 have omitted the trajectory planner
 
 loadrt tp
 
 after trivkins or whatever is loaded and not specified
 
 tp=tp kins=trivkins at the end of the motmod configuration line
 
 These are specific to Machinekit and without them your config will act 
 more like a sim.
 
 See the sample configs for using 5i25 with Machinekit
 
 https://github.com/machinekit/machinekit/blob/master/configs/hm2-stepper/hm2-stepper-5i25.hal#L33
 regards
 
 
> On 27/01/2017 22:07, Curtis Dutton wrote:
> I'm experimenting with running my laser engraver with machinekit. 
> Currently I'm running linuxcnc master and have it set up and 
> operating properly.
> 
> 

Re: [Machinekit] Configuring a 10Khz charge pump for a G540 gecko using BeagleBone Black running machinekit

2017-02-01 Thread Kirk Wallace

On 01/31/2017 10:10 PM, Tom M wrote:


We almost almost finished configuring our cnc build at the makerspace I
belong to.

Since the G540 has a charge pump, we thought we would take advantage of it.
(We we're debating if we even need to since we don't think the bbb has
the start issues that a pc parallel port does.

My understanding is that the G540 needs a charge pump frequency of 10Khz


It is my understanding that the frequency is much less important than 
the drive current. The pump input circuit has a DC blocking capacitor, 
diode bridge, and charge capacitor that needs to be charged. I found 
that a 5 Volt pull-up resistor or a buffer IC than can source 24ma works 
well. This should allow going down to 500Hz or just about any convenient 
frequency. I have some notes here:

http://wallacecompany.com/machine_shop/G540/

I seem to recall that the scope traces that got above 3Volts worked.
Such as the motherboard port set to EPP worked:
http://wallacecompany.com/machine_shop/G540/g540_mb_epp.jpg

But set to SPP didn't:
http://wallacecompany.com/machine_shop/G540/g540_mb_epp.jpg

I did a little bit of circuit tracing here:
http://wallacecompany.com/machine_shop/G540/G540_upper_bottom_z-1b.png

Pin 16 is the input, C is the series DC blocking capacitor, next comes 
the half-wave diode bridge (KL4 Y8), a filter capacitor on the output 
(two bottom pins), and the opto-coupler input LED and current limit 
resistor (201) to ground.


I haven't done any work with the Beagle Bone but I suspect any buffer 
circuit that can convert the BB low voltage to 5Volts at 24ma should 
work at any convenient frequency.



--
Kirk Wallace
http://www.wallacecompany.com/machine_shop/
http://www.wallacecompany.com/E45/

--
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.


[Machinekit] Re: de0 nano soc for MK

2017-02-01 Thread Schooner
Just to clarify, because there are a plethora of different kits and boards 
with similar names etc.

The DE0-NANO-Soc we used is the PO286-ND
http://www.digikey.co.uk/product-detail/en/P0286/P0286-ND/5222193?WT.mc_id=IQ_7628_G_pla5222193=1=cpc=1=s=106285396226===c

I inadvertently referred to another kit at £67, this correct one is £83 
from Digikey, which appears to be the cheapest available,
with Mouser a few £ more

On Friday, 27 January 2017 14:42:45 UTC, Klemen Zhivko wrote:
>
> Does anybody know where in Europe I can buy de0 nano soc (Cyclone 5 i 
> think).
> I would like to control 3 servos - with machinekit.
> Are stepper and servo configuration posibble on machinekit (on de nano 
> soc) ?
>
> regards
>

-- 
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.