On 1/10/2014 12:33 PM, Charles Steinkuehler wrote:
On 1/10/2014 9:33 AM, Charles Steinkuehler wrote:
On 1/10/2014 7:42 AM, Thomas Studwell wrote:
I can easily modify the PRU assembly and create a version that does
falling-edge step pulses for all step/dir generators. To use it, you
would
On 1/12/2014 1:19 PM, Thomas Studwell wrote:
The only oddity, which doesn't affect the motion but does affect
power consumption, is that the signals are not initialized to high
(AKA inactive state) on program startup. The signals do go high and
remain there after the first step, however. The
On 1/12/2014 2:44 PM, Thomas Studwell wrote:
Charles, I didn't see any reference to 'high' being a valid 'direction'
using the virtual GPIO pins, so I added these to the end of the setup.sh
file. If I get time later today or tomorrow, I'll update the script to
process an optional 'level'
On 1/12/2014 3:57 PM, Charles Steinkuehler wrote:
On 1/12/2014 2:44 PM, Thomas Studwell wrote:
Charles, I didn't see any reference to 'high' being a valid 'direction'
using the virtual GPIO pins, so I added these to the end of the setup.sh
file. If I get time later today or tomorrow, I'll
On 1/10/2014 7:42 AM, Thomas Studwell wrote:
Charles,
sorry to bother you directly with this. Attached is a reply I made to
the maillist to your response.
I was sort of surprised that you hadn't replied to it (given how quick
you were to respond the first time). Today I saw a related
Great! Thanks Charles! I'll try it as soon as you have it available.
The reason you didn't get my reply to the mailing list is that replies
have been blocked from viewing by project administrator. I asked why
but have not gotten a response.
Tom
BTW: You might want to send a copy to Mark
On 1/10/2014 9:33 AM, Charles Steinkuehler wrote:
On 1/10/2014 7:42 AM, Thomas Studwell wrote:
I can easily modify the PRU assembly and create a version that does
falling-edge step pulses for all step/dir generators. To use it, you
would simply point to the modified PRU binary in the HAL
WARNING: This is for short-term use ONLY! I expect to have updated
code that will support setting the step polarity via HAL within a week
or two, along with many other changes that will require significant
modification to any existing configurations (but will make pin numbering
a whole lot
On 1/10/2014 7:49 PM, Chris Morley wrote:
Looking forward to this as I have been working on BBB pages for
stepconf - I will wait for your changes
One of the reasons there's not much documentation for how things
currently work is the pin numbering is so messed up I didn't actually
want to
On 11 January 2014 02:59, Charles Steinkuehler char...@steinkuehler.net wrote:
I think I've come up with a reasonable solution
that will still work with HAL's limitations (only bit, integer, and
float data types, so no strings).
Wacky idea, why not add strings to HAL? (if you do, then I
On 1/10/2014 10:19 PM, andy pugh wrote:
On 11 January 2014 02:59, Charles Steinkuehler char...@steinkuehler.net
wrote:
I think I've come up with a reasonable solution
that will still work with HAL's limitations (only bit, integer, and
float data types, so no strings).
Wacky idea, why not
11 matches
Mail list logo
