date:20170321

Re: [Machinekit] Re: Cheapest way to get +/-10V signal from x86 computer with encoder input

2017-03-21 Thread Chris Albertson

He is talking about a +/- 10 volt SIGNAL not a +/- 10 volt power supply.
  His servo amp converts this analog signal to velocity.  The signal works
so if it is 0V the motor stops, +5V  it runs forward at 1/2 speed and -5V
is backwards at 1/2 speed and so on.

The suggested I offered was to use a bridge made with four cheap transistor
and it would need 12 volt power.  So there is a use for the ATX power
supply outputs

On Mon, Mar 20, 2017 at 10:56 AM, Daren Schwenke 
wrote:

> You have +12v/-12v available from the ATX supply already, albeit the -12v
> is limited to about 0.5 amps.
> The simple, in your scrap box already solution would be wire a couple
> diodes in series and add two filter caps.
> 0.6v-1.2v drop per diode, add them till you are at your 10v.
>
> 0On Sunday, March 19, 2017 at 12:09:42 PM UTC-4, Pruska Modr wrote:
>>
>> 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 until
>> I figure out something better so I would like if it was cheap.
>>
>> Thank you.
>> PM
>>
> --
> 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.
>



-- 

Chris Albertson
Redondo Beach, California

-- 
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] Re: Problems with installing xhc-hb04 in my Machinekit BBB cnc project

2017-03-21 Thread Simon Mali

I have upgraded the OS with apt-get as you said. When I test proposed 
sequence I get the following output:

root@beaglebone:/home/machinekit# realtime restart
/usr/libexec/linuxcnc/rtapi_msgd: FATAL - will not run as root
rtapi_msgd startup failed - aborting
rtapi_app startup failed - aborting
halcmd: cant connect to rtapi_app: -1 (uri= 
uuid=a42c8c6b-4025-4f83-ba28-dad21114744a): rtapi_rpc(): reply timeout

halcmd: the rtapi:0 RT demon is not running - please investigate 
/var/log/linuxcnc.log
halcmd: the msgd:0 logger demon is not running - please investigate 
/var/log/linuxcnc.log
root@beaglebone:/home/machinekit# halcmd loadrt debounce
halcmd: cant connect to rtapi_app: -1 (uri= 
uuid=a42c8c6b-4025-4f83-ba28-dad21114744a): rtapi_rpc(): reply timeout

halcmd: the rtapi:0 RT demon is not running - please investigate 
/var/log/linuxcnc.log
halcmd: the msgd:0 logger demon is not running - please investigate 
/var/log/linuxcnc.log
root@beaglebone:/home/machinekit#  

linuxcnc.log printout:

Mar 21 20:17:16 beaglebone msgd:0: startup pid=1695 flavor=xenomai 
rtlevel=1 usrlevel=1 halsize=524288 shm=Posix cc=gcc 4.9.2  version=unknown
Mar 21 20:17:16 beaglebone msgd:0: ØMQ=4.0.5 czmq=2.2.0 protobuf=2.4.1 
atomics=gcc intrinsicslibwebsockets=
Mar 21 20:17:16 beaglebone msgd:0: configured: sha=32e5e60
Mar 21 20:17:16 beaglebone msgd:0: built:  Mar 20 2017 18:27:02 
sha=32e5e60
Mar 21 20:17:16 beaglebone msgd:0: register_stuff: actual hostname as 
announced by avahi='beaglebone.local'
Mar 21 20:17:16 beaglebone msgd:0: zeroconf: registering: 'Log service on 
beaglebone.local pid 1695'
Mar 21 20:17:17 beaglebone msgd:0: zeroconf: registered 'Log service on 
beaglebone.local pid 1695' _machinekit._tcp 0 TXT 
"uuid=a42c8c6b-4025-4f83-ba28-dad21114744a" 
"instance=ff04a766-0e6a-11e7-bfee-1cba8cd967d9" "service=log" 
"dsn=ipc:///tmp/0.log.a42c8c6b-4025-4f83-ba28-dad21114744a"
Mar 21 20:17:52 beaglebone rtapi:0: unload: 'trivkins' not loaded
Mar 21 20:17:52 beaglebone rtapi:0: unload: 'tp' not loaded
Mar 21 20:17:52 beaglebone rtapi:0: unload: 'xhc_hb04_util' not loaded
Mar 21 20:17:52 beaglebone rtapi:0: unload: 'threads' not loaded
Mar 21 20:17:52 beaglebone rtapi:0: unload: 'pwmgen' not loaded
Mar 21 20:17:52 beaglebone rtapi:0: unload: 'motmod' not loaded
Mar 21 20:17:52 beaglebone rtapi:0: unload: 'limit1' not loaded
Mar 21 20:17:52 beaglebone rtapi:0: unload: 'hal_pru_generic' not loaded
Mar 21 20:17:52 beaglebone rtapi:0: unload: 'hal_bb_gpio' not loaded
Mar 21 20:17:52 beaglebone rtapi:0: unload: 'abs' not loaded
Mar 21 20:17:52 beaglebone msgd:0: rtapi_app exit detected - scheduled 
shutdown
Mar 21 20:17:54 beaglebone msgd:0: msgd shutting down
Mar 21 20:17:54 beaglebone msgd:0: zeroconf: unregistering 'Log service on 
beaglebone.local pid 1695'
Mar 21 20:17:54 beaglebone msgd:0: log buffer hwm: 0% (0 msgs, 0 bytes out 
of 524288)
Mar 21 20:17:54 beaglebone msgd:0: normal shutdown - global segment detached
Mar 21 20:18:52 beaglebone msgd:0: startup pid=2897 flavor=xenomai 
rtlevel=1 usrlevel=1 halsize=524288 shm=Posix cc=gcc 4.9.2  version=unknown
Mar 21 20:18:52 beaglebone msgd:0: ØMQ=4.0.5 czmq=2.2.0 protobuf=2.4.1 
atomics=gcc intrinsicslibwebsockets=
Mar 21 20:18:52 beaglebone msgd:0: configured: sha=32e5e60
Mar 21 20:18:52 beaglebone msgd:0: built:  Mar 20 2017 18:27:02 
sha=32e5e60
Mar 21 20:18:52 beaglebone msgd:0: register_stuff: actual hostname as 
announced by avahi='beaglebone.local'
Mar 21 20:18:52 beaglebone msgd:0: zeroconf: registering: 'Log service on 
beaglebone.local pid 2897'
Mar 21 20:18:53 beaglebone msgd:0: zeroconf: registered 'Log service on 
beaglebone.local pid 2897' _machinekit._tcp 0 TXT 
"uuid=a42c8c6b-4025-4f83-ba28-dad21114744a" 
"instance=3801c576-0e6b-11e7-a045-1cba8cd967d9" "service=log" 
"dsn=ipc:///tmp/0.log.a42c8c6b-4025-4f83-ba28-dad21114744a"
Mar 21 20:19:05 beaglebone rtapi:0: unload: 'trivkins' not loaded
Mar 21 20:19:05 beaglebone rtapi:0: unload: 'tp' not loaded
Mar 21 20:19:05 beaglebone rtapi:0: unload: 'xhc_hb04_util' not loaded
Mar 21 20:19:05 beaglebone rtapi:0: unload: 'threads' not loaded
Mar 21 20:19:05 beaglebone rtapi:0: unload: 'pwmgen' not loaded
Mar 21 20:19:05 beaglebone rtapi:0: unload: 'motmod' not loaded
Mar 21 20:19:05 beaglebone rtapi:0: unload: 'limit1' not loaded
Mar 21 20:19:05 beaglebone rtapi:0: unload: 'hal_pru_generic' not loaded
Mar 21 20:19:05 beaglebone rtapi:0: unload: 'hal_bb_gpio' not loaded
Mar 21 20:19:05 beaglebone rtapi:0: unload: 'abs' not loaded
Mar 21 20:19:05 beaglebone msgd:0: rtapi_app exit detected - scheduled 
shutdown
Mar 21 20:19:07 beaglebone msgd:0: msgd shutting down
Mar 21 20:19:07 beaglebone msgd:0: zeroconf: unregistering 'Log service on 
beaglebone.local pid 2897'
Mar 21 20:19:08 beaglebone msgd:0: log buffer hwm: 0% (0 msgs, 0 bytes out 
of 524288)
Mar 21 20:19:08 beaglebone msgd:0: normal shutdown - global segment detached
Mar 21 20:22:16 beaglebone rtapi:0: rtapi_app:0: ERROR: cannot attach

Re: [Machinekit] BeagleBone Family MachineKit image

2017-03-21 Thread alexander . roessler

I'm working on getting the Replicape to work with the Jessie Machinekit 
images. Here are my findings so far:

I had to replace the Xenomai kernel with the RT-PREEMPT kernel. I think 
some configuration for the Xenomai kernel might be missing. However, I 
think the RT-PREEMPT kernel should work fine too.

Then I tried to get the cape-universal overlays for my application. As part 
of the process I created the two PRs:
https://github.com/cdsteinkuehler/beaglebone-universal-io/pull/48
https://github.com/beagleboard/bb.org-overlays/pull/42

The Replicape uses some pins usually occupied with the HDMI audio pins and 
I experience some problems using config-pin to pinmux these pins.
sudo config-pin P9_25 in

[sudo] password for machinekit:  
bash: /sys/devices/platform/ocp/ocp*P9_25_pinmux/state: No such file or 
directory

Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_25_pinmux/state

I experience this problem with the following pins:
P9.25
P9.28
P9.29
P9.31

The slots file looks as follows:
machinekit@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots   
 0: P-  -1 Replicape 3D printer cape,0B3A,Intelligent Agen,BB-BONE-
REPLICAP

 1: PF  -1  
 2: PF  -1  
 3: PF  -1  
 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,cape-universaln




Robert, do you maybe have an idea what could be the problem?


Am Montag, 13. März 2017 21:27:04 UTC+1 schrieb Charles Steinkuehler:
>
> On 3/13/2017 1:29 PM, Robert Nelson wrote: 
> > Hey Guys, 
> > 
> > I've updated the default weekly build to now use the v4.4.x-xenomai 
> > branch. This will give BBGW and BBBW users the ability to use the 
> > built-in wifi adapter. 
> > 
> > I'll leave the old 2017-02-12 (3.8.13-xenomai) image up for a long time. 
> > 
> > 
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#microSD.2FStandalone:_.28machinekit.29_Based_on_Debian_Jessie
>  
>
> Thanks Robert! 
>
> Now we'll need to update the provided example configurations to deal 
> with the various changes between 3.8 and 4.4.  This will mostly be in 
> the various setup.sh functions that load overlays and setup pin 
> multiplexing.  I've been super-busy ITRW lately, so testers and any 
> help with fixes will be greatly appreciated!  Just open a PR on github 
> for anything broken that you fixed, and open an issue for anything 
> that doesn't work that you can't fix.  :) 
>
> -- 
> Charles Steinkuehler 
> cha...@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] Cape overlay and boot with the CRAMPS board

2017-03-21 Thread Jonathan Cohen

I purchased the board from Pico Systems (http://pico-systems.com/).  I 
assumed that the eeprom had been programmed.  I do not believe that I have 
been loading an overlay unless it was actually in one of the build which 
seems to have been a bad assumption.  Do you believe that could be causing 
the pesky problem that I have been having with the ADC freezing ?  

On Tuesday, March 21, 2017 at 8:39:46 AM UTC-4, Charles Steinkuehler wrote:
>
> On 3/20/2017 11:41 AM, Jonathan Cohen wrote: 
> > Is there a specific overlay for using the CRAMPS board and HDMI that 
> should 
> > be installed or called that is not part of the machinekit build that RCN 
> > puts out ?  One nagging thing on my mind is some of the "error" codes 
> that 
> > come up during the boot.  I have not gone and changed anything in the 
> > bootloader file and was wondering if I really need to address that.   
> > 
> > This was a picture of a boot from a couple of months ago.  I am 
> wondering 
> > if some source of problems have to do with the configuration at startup. 
>   
>
> The CRAMPS board uses the "cape-universal" overlay.  It looks like your 
> EEPROM is not programmed (causing the "Invalid signature ''" 
> error).  That is OK, but it means you will have to somehow load the 
> overlay prior to launching machinekit (manually or more typically via a 
> script run at the start of your HAL file).  If you want to program your 
> EEPROM, you can use this file: 
>
>
> https://github.com/cdsteinkuehler/bobc_hardware/blob/CRAMPS/CRAMPS/CRAMPS.00A0.eeprom
>  
>
> -- 
> Charles Steinkuehler 
> cha...@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] Cape overlay and boot with the CRAMPS board

2017-03-21 Thread Charles Steinkuehler

On 3/20/2017 11:41 AM, Jonathan Cohen wrote:
> Is there a specific overlay for using the CRAMPS board and HDMI that should 
> be installed or called that is not part of the machinekit build that RCN 
> puts out ?  One nagging thing on my mind is some of the "error" codes that 
> come up during the boot.  I have not gone and changed anything in the 
> bootloader file and was wondering if I really need to address that.  
> 
> This was a picture of a boot from a couple of months ago.  I am wondering 
> if some source of problems have to do with the configuration at startup.  

The CRAMPS board uses the "cape-universal" overlay.  It looks like your
EEPROM is not programmed (causing the "Invalid signature ''"
error).  That is OK, but it means you will have to somehow load the
overlay prior to launching machinekit (manually or more typically via a
script run at the start of your HAL file).  If you want to program your
EEPROM, you can use this file:

https://github.com/cdsteinkuehler/bobc_hardware/blob/CRAMPS/CRAMPS/CRAMPS.00A0.eeprom

-- 
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] time vs timev2

2017-03-21 Thread schoone...@btinternet.com


  
  
Please check the last 15 or so posts in
[Machinekit] Machinekit not starting: seems to be attempting to
start incorrect rtapi app
Re: [Machinekit] Re: Problems with installing xhc-hb04 in my
Machinekit BBB cnc project

There was a problem, which was fixed yesterday, doing a fresh pull
should sort it

On 21/03/17 08:31,
  fr...@franksworkshop.com.au wrote:


  Thanks for the fix, but pulling your fix and the
others on master seems to have made things worse.  Now I'm
getting lots of Segmentation Faults during the make setuid
phase...



  (gdb) bt
  #0  0xb6e2dba4 in strlen () from
/lib/arm-linux-gnueabihf/libc.so.6
  #1  0x00011458 in default_flavor () at
rtapi/rtapi_compat.c:249
  #2  0x00011024 in main (argc=1, argv=0xbee5c7f4) at
rtapi/flavor.c:43
  (gdb)
  
  
  
  
  The code in rtapi_compat.c seems to be doing a strlen on
a NULL pointer.
  
  
  
  
  
  
  
  On Monday, March 20, 2017 at 1:55:38 AM UTC+11, Schooner
  wrote:
  
 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 it to a momentary switch it would act as a
  reset.
  
  So now you can start and stop and the count is cumulative,
  or you can reset at will.
  
  To test run
  
  # !/bin/bash
  
  DEBUG=5 realtime restart
  halcmd loadrt time
  halcmd newthread servo 100 fp
  halcmd addf time.0 servo
  halcmd start
  halcmd setp time.0.start 1
  halcmd show pin
  sleep 5
  halcmd setp time.0.start 0
  halcmd show pin
  halcmd setp time.0.zero 1
  halcmd setp time.0.zero 0
  sleep 5
  halcmd setp time.0.start 1
  halcmd show pin
  sleep 5
  halcmd show pin
  halrun -U
  
  It will show you it counting to 5 secs , then stopping and
  zeroing, restarting and counting to 5 secs again.
  
  If you want to display time in a pyvcp panel, you could
  just use the pyvcp_timer widget I wrote ages ago
  https://github.com/machinekit/machinekit/blob/master/lib/python/pyvcp_widgets.py#L1040
  It just uses system time, rather than the thread period
  
  On 19/03/17 10:33, schoo...@btinternet.com
wrote:
  
   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:


  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 syntax to access pins.  Is this what I
  need to use?  When did that change?


Thanks,
Frank
  
  -- 
  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:

Re: [Machinekit] time vs timev2

2017-03-21 Thread frank

Thanks for the fix, but pulling your fix and the others on master seems to 
have made things worse.  Now I'm getting lots of Segmentation Faults during 
the make setuid phase...

(gdb) bt
#0  0xb6e2dba4 in strlen () from /lib/arm-linux-gnueabihf/libc.so.6
#1  0x00011458 in default_flavor () at rtapi/rtapi_compat.c:249
#2  0x00011024 in main (argc=1, argv=0xbee5c7f4) at rtapi/flavor.c:43
(gdb)


The code in rtapi_compat.c seems to be doing a strlen on a NULL pointer.




On Monday, March 20, 2017 at 1:55:38 AM UTC+11, Schooner wrote:
>
> 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 it to a momentary switch it would act as a reset.
>
> So now you can start and stop and the count is cumulative, or you can 
> reset at will.
>
> To test run
>
> # !/bin/bash
>
> DEBUG=5 realtime restart
> halcmd loadrt time
> halcmd newthread servo 100 fp
> halcmd addf time.0 servo
> halcmd start
> halcmd setp time.0.start 1
> halcmd show pin
> sleep 5
> halcmd setp time.0.start 0
> halcmd show pin
> halcmd setp time.0.zero 1
> halcmd setp time.0.zero 0
> sleep 5
> halcmd setp time.0.start 1
> halcmd show pin
> sleep 5
> halcmd show pin
> halrun -U
>
> It will show you it counting to 5 secs , then stopping and zeroing, 
> restarting and counting to 5 secs again.
>
> If you want to display time in a pyvcp panel, you could just use the 
> pyvcp_timer widget I wrote ages ago
>
> https://github.com/machinekit/machinekit/blob/master/lib/python/pyvcp_widgets.py#L1040
> It just uses system time, rather than the thread period
>
> On 19/03/17 10:33, schoo...@btinternet.com  wrote:
>
> 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:
>
> 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 syntax to access 
> pins.  Is this what I need to use?  When did that change?
>
> Thanks,
> Frank
> -- 
> 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+...@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.

Re: [Machinekit] Machinekit not starting: seems to be attempting to start incorrect rtapi app

2017-03-21 Thread schoone...@btinternet.com


Yes, there was another update after that.

Thanks for confirming



On 21/03/2017 05:14, Brian Schousek wrote:
A new build must have happened after you posted this: 0.1.1490033988 
fixes my real time problem. Now I just need to get the parallel port 
configured properly.


Brian
Package: machinekit
Version: 0.1.1490033988-1mk.travis.master.git32e5e609~1jessie

On Monday, March 20, 2017 at 7:49:14 AM UTC-5, Schooner wrote:

The new packages have built

The new ones begin with
*machinekit_0.1.1490008219-1mk.travis.master.git8e4b140c*

Whoever tries them first, please confirm that they work

regards

On 20/03/17 12:33, Brian Schousek wrote:

Thanks for the response. I was able to try the flavor commands
this morning: all variants segfaulted with different codes. I
will try the reverted packages (or the updated packages depending
on timing) this evening.

B

On Monday, March 20, 2017 at 5:44:32 AM UTC-5, Schooner wrote:


On 20/03/17 09:06, schoo...@btinternet.com wrote:

Just an update on this

It is just possible there is a corruption in the machinekit
repo, which is causing problems with recent package builds too
We have just tried a build from a fresh clone of the repo
and get all sorts of errors

Brian - If you know how, are you able to revert packages
back to something produced at around 8th March and try those?

http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit_0.1.1488973272-1mk.travis.master.git187524c9~1jessie_i386.deb


and the matching flavor package

Simon - likewise, but don't screw up your system if you are
not sure

We are looking at it , but it may take a while to resolve


The problem has been found and a correcting PR made.

There was an unexpected knock on from another recent change,
which did not show up in test builds and even allowed
packages to build without errors,
despite them not having setuid on required files and flavor
segfaulting and not getting the proper kernel flavour, so it
defaulted to posix.

The build process will take a while, I will advise once new
packages are available, until then do not update

Reverting to the packages I suggested will work if you are
desperate to use your system and have the non working
packages installed





On 20/03/17 08:33, schoo...@btinternet.com wrote:

Can you try running the flavor binary in /usr/libexec

Running flavor on its own should give the kernel flavour

Also run flavor -m , flavor -b and flavor -d

This seems similar to Simon Mali's problem when he
upgraded, the kernel flavour was not being detected and a
default of posix was being tried.

On 20/03/17 03: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 (see ref2),
and tried to start things up with various configurations.
Ref 3 shows a representative error (through iterations I
determined that just trying to run 'realtime' yields the
same errors as starting the whole package, and errors out
much quicker.) My interpretation of ref 3 is that it is
trying to run rtapi_posix (not installed) instead of
rt-preempt. As can be seen in ref 4 there is an executable
for rtapi_app_rt-preempt but no rtapi_app_posix so it's no
great surprise there is an error in ref 3.

What simple thing am I missing here? I've been
unsuccessful in finding a solution in this forum and on
the machinekit website.


*Ref 1*
{
brian@surely:/usr/libexec/linuxcnc⇒  uname -a
Linux surely 4.1.19-rt22mah #1 SMP PREEMPT RT Tue Mar 15
09:12:20 CET 2016 i686 GNU/Linux
}

*Ref 2*
{
brian@surely:/usr/libexec/linuxcnc⇒  apt list --installed
| grep machine
machinekit/stable,now
0.1.1489960089-1mk.travis.master.git7df8d183~1jessie i386
[installed,automatic]
machinekit-dev/stable,now
0.1.1489960089-1mk.travis.master.git7df8d183~1jessie i386
[installed]
machinekit-rt-preempt/stable,now
0.1.1489960089-1mk.travis.master.git7df8d183~1jessie i386
[installed]
}

*Ref 3*
{brian@surely:~⇒  sudo realtime start
Warning - /usr/libexec/linuxcnc/rtapi_app_posix not setuid
'sudo make setuid' missing?
/usr/bin/realtime: line 111: test: =: unary operator expected

Re: [Machinekit] Re: Cheapest way to get +/-10V signal from x86 computer with encoder input

Re: [Machinekit] Re: Problems with installing xhc-hb04 in my Machinekit BBB cnc project

Re: [Machinekit] BeagleBone Family MachineKit image

Re: [Machinekit] Cape overlay and boot with the CRAMPS board

Re: [Machinekit] Cape overlay and boot with the CRAMPS board

Re: [Machinekit] time vs timev2

Re: [Machinekit] time vs timev2

Re: [Machinekit] Machinekit not starting: seems to be attempting to start incorrect rtapi app

8 matches

Site Navigation

Mail list logo

Footer information