Thanks again! Appreciate it.
On Friday, February 24, 2017 at 9:17:20 AM UTC-6, Schooner wrote:
>
> OK
>
> If you would like to 'donate' the driver, I can add it to the repo and it
> will get built properly, automatically
> at any rebuild,
>
> Just tested and
>
> root@INTEL-i7:/usr/src/machinekit
OK
If you would like to 'donate' the driver, I can add it to the repo
and it will get built properly, automatically
at any rebuild,
Just tested and
root@INTEL-i7:/usr/src/machinekit# DEBUG=5 realtime restart
root@INTEL-i7:/usr/src/machi
I missed the attachments - apologies
Can we take this to the tracker as originally requested in the post
"Please report any problems via the tracker at https://github.com/machinekit/machinekit/issues/1123"
It makes things a lot easier and doesn't rely upon noticing
Well I think I might of broke something very bad...running the command *nm
-C hal_p260c* *| grep " U " *gave this:
U cfsetispeed@@GLIBC_2.2.5
U cfsetospeed@@GLIBC_2.2.5
U close@@GLIBC_2.2.5
U hal_exit
U hal_e
Are the attached files not the component code? Why would this work prior to
the "merge"?
On Friday, February 24, 2017 at 3:34:18 AM UTC-6, Schooner wrote:
>
>
> On 23/02/17 19:39, Daniel Skrlin wrote:
>
> This issue has been resolved by manually installing icomps. However now I
> ran into anothe
On 23/02/17 19:39, Daniel Skrlin wrote:
This issue has been resolved by manually installing
icomps. However now I ran into another issue with a custom
driver/protocol for my IO hardware (communicates via USB to
RS485) Please see attached files
This issue has been resolved by manually installing icomps. However now I
ran into another issue with a custom driver/protocol for my IO hardware
(communicates via USB to RS485) Please see attached files and error
messages. Any help would be greatly appreciated since I am merely just a
power us
Hello guys do not know if this pertains to this but just did a recent
upgrade/update and got this on my once working config
File "hal/init.py", line 14, in
import motion
File "/home/pmcs/Downloads/pmcs-sim_OLD/hal/motion.py", line 14, in
convert = rt.newinst('float2u32', 'convert.a
On 17/02/17 15:02, Robert Nelson wrote:
On Sun, Feb 12, 2017 at 12:40 PM, Alexander Rössler
wrote:
I have not checked recently, but there was problem with the USB Ethernet
not working I think. Last time I tested it was mid December.
Machinekit for Wheezy & Jessie share the same ancient 3.8.13
On Sun, Feb 12, 2017 at 12:40 PM, Alexander Rössler
wrote:
> I have not checked recently, but there was problem with the USB Ethernet
> not working I think. Last time I tested it was mid December.
Machinekit for Wheezy & Jessie share the same ancient 3.8.13 kernel..
So if that was an issue in je
On 2/9/2017 3:24 PM, Charles Steinkuehler wrote:
>
> ...we don't have a proper gcc-4.7 cross tool chain and are using
> gcc-4.9. The build issue is a bit of missing c++ abi that got added
> and 4.9 is expecting to use but the 4.7 libraries we have to link with
> don't have the new function (__cxa
I have not checked recently, but there was problem with the USB Ethernet
not working I think. Last time I tested it was mid December.
Robert Nelson writes:
> On Wed, Feb 8, 2017 at 11:37 AM, Marius Alksnys wrote:
>>
>> 02/08/2017 03:13 PM, schoone...@btinternet.com rašė:
>>>
>>>
>>> On 08/02/17
On 2/8/2017 7:13 AM, schoone...@btinternet.com wrote:
>
> If you won't upgrade to Jessie for some reason, your code will
> continue as now, but you just won't get any package updates.
>
> Unfortunately support has to end somewhere and Wheezy has been a
> problem for some while to keep going.
> De
What is broken? it's using the same 3.8.13 based kernel as the old
wheezy image..
Probably there where issues with BeagleBone Green, (which I am using a
lot) and Debian Jessie image.
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
-
On 08/02/2017 17:37, Marius Alksnys wrote:
02/08/2017 03:13 PM, schoone...@btinternet.com rašė:
On 08/02/17 12:13, Marius Alksnys wrote:
What does it mean for BeagleBone machinekit existing and new
applications?
Hi
I don't see it changes anything
There is no reason I am aware of to use
On Wed, Feb 8, 2017 at 11:37 AM, Marius Alksnys wrote:
>
> 02/08/2017 03:13 PM, schoone...@btinternet.com rašė:
>>
>>
>> On 08/02/17 12:13, Marius Alksnys wrote:
>>>
>>> What does it mean for BeagleBone machinekit existing and new
>>> applications?
>>>
>>>
>> Hi
>>
>> I don't see it changes anythi
02/08/2017 03:13 PM, schoone...@btinternet.com
rašė:
On 08/02/17 12:13, Marius Alksnys wrote:
What does it mean for BeagleBone machinekit existing and new
applications?
Hi
I don't see it changes anything
There is no reason I am aware of to use a Wheezy based image with BBB.
The Robert Ne
On 08/02/17 12:13, Marius Alksnys wrote:
What does it mean for BeagleBone machinekit existing and new
applications?
Hi
I don't see it changes anything
There is no reason I am aware of to use a Wheezy based image with BBB.
The Robert Nelson image is based upon Jessie, so in a couple of week
What does it mean for BeagleBone machinekit existing and new applications?
02/07/2017 01:51 PM, schoone...@btinternet.com
rašė:
...
There is however a problem on the ARM architecture running Wheezy which
makes it unlikely it will build
All builds fine on jessie-armhf and raspbian-armhf build
19 matches
Mail list logo
