I've just updated my BBB 3D printer to that latest image and notice my run
timer is no longer ticking along.
I'm using the time component. The pins look correct, and a floating thread
is calling the function, but the time is not updating.
I noticed there is a timev2 component with different
Thank you, Robert. I have now tested a few things with the 3-12 image.
The default TI-Xemomai kernel does not work with the installed
machinekit-xenomai package for some reason. Machinekit does not seem to
detect the correct FLAVOR but even after enforcing export FLAVOR=xenomai I
get problems
There is a problem with the time component, I will let you know when
it is sorted
I think the thread functions need updating.
v2 is for atomic operations across cores and of no relevance here
On 19/03/17 09:26,
fr...@franksworkshop.com.au wrote:
Refer to the DE0-Nano-SoC schematic (found on the CD-ROM:
http://www.terasic.com/downloads/cd-rom/de0-nano-soc/) and you will
see that the signal GPIO_0 16 is physically on header JP1, pin 19 and
signal GPIO_0 17 is physically on header JP1, pin 20.
In addition to the different starting pin
OK I have pushed a PR, which fixes this and adds some enhancements
to `time`
When it is merged, time will work as before, but there is also a
`zero` pin, which can be used to reset the counter,
either whilst running or when start is set to 0
If you attached
With this correction:
92 92 proc pin_exists {name} {
93 - set line [show pexists $name]
94 - if {"$line" != "Exists"} {
95 -puts stderr "FAILED: show pexists $name, returned $line"
93 + set line [show pin $name]
94 + if {[string first $name $line 0] <
On 19/03/17 16:38, Simon Mali wrote:
With this correction:
92 92 proc pin_exists {name} {
93 - set line [show pexists $name]
94 - if {"$line" != "Exists"} {
95 -puts stderr "FAILED: show pexists $name, returned $line"
On 19/03/17 17:06, Simon Mali wrote:
No problem. I will reactivate the old file which I
saved before changing this tcl file.
Yes I am driving Beagle Bone Black.
I have made an upgrade with proposed commands and among others
also
See also this re the previous report
https://github.com/machinekit/machinekit/issues/1161
On 19/03/17 14:40,
schoone...@btinternet.com wrote:
What image or package version are you using?
There was a problem where the multicore
On 19/03/17 17:22, Simon Mali wrote:
After system restart and reactivating old tcl file
machinekit even don't wan't to start anymore. What does this
means:
Debug file information:
Warning -
No problem. I will reactivate the old file which I saved before changing
this tcl file.
Yes I am driving Beagle Bone Black.
I have made an upgrade with proposed commands and among others also
machinekit was upgraded:
Preparing to replace machinekit-xenomai
Hi,
is there any way how to connect to computer of the x86 platform to servo
amplifiers which require +/-10V for velocity loop and to encoders working on
the 5V logic and do the PID position control loop inside Machinekit besides the
MESA FPGA+7i77 cards? It would be only temporary solution
How exactly to check which image or package version is currently installed
on my memory card?
How to upgrade to newer code?
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to
You haven't said what you are running on.
Assuming you are using a BBB and a recent SD card image, you should
just be able to
sudo apt-get update
sudo apt-get dist-upgrade
That will fetch machinekit package which has the updated halcmd
Probably
I have restarted the system but nothing substancially has changed. You said
that I should test this: /usr/src/machinekit/src/hal/utils
My folder /usr/src is empty.
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this
How to make an iso file out of deb package? For instance out of:
http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit_0.1.1489929991-1mk.travis.master.git187f851f~1jessie_armhf.deb
> On 20 Mar 2017, at 04:17, Brian Schousek wrote:
>
>
> I'm trying to get a basic Machinekit up and running on an older PC. I've
> apparently successfully installed and started an RT-PREEMPT kernel (see ref
> 1), properly installed the appropriate machinekit packages
I'm trying to get a basic Machinekit up and running on an older PC. I've
apparently successfully installed and started an RT-PREEMPT kernel (see ref
1), properly installed the appropriate machinekit packages (see ref2), and
tried to start things up with various configurations. Ref 3 shows a
18 matches
Mail list logo