[Machinekit] Re: Running 3D Printer using Machinekit + CRAMPS + BBB

['machinen' via Machinekit]

Hi,
I am in somewhat similar situation to yours and I have few questions for 
you:

Were you able to upgrade your installation? Because the ready-made image 
for BBB is quite old and when doing update/upgrade, the Machinekit 
package(s) is(are) being kept back and it is because dependency error. The 
same is when installing on new clean system flash (which are newer) by the 
how to in Machinekit docs.

Are you able to shutdown/poweroff/reboot your BBB with CRAMPS? I have the 
Element14 BBB rev. C with CRAMPS 2.2 and I cannot shut it down completely. 
The power on LED is still on and there are two LEDs on on CRAMPS and on the 
right side of RIJ45 connector (bank of four LEDs) there is one LED faintly 
blinking. Otherwise the BBB is turned off (I cannot SSH to it). I have to 
manually shut the power down. Are you experiencing the same?

And given the above, hoare you able to run the fabrikator Mini CRAMPS 
configuration out of the box? My system is screaming at me about missing 
fdm.config. Maybe it is because old machinekit (but as I said, currently 
the dependency is broken), the actual error is:
halcmd loadusr io started
Traceback (most recent call last):
  File "fabrikator_mini.py", line 8, in 
from fdm.config import velocity_extrusion as ve
ImportError: No module named config
Shutting down and cleaning up Machinekit...

Thanks.

On Tuesday, August 29, 2017 at 8:08:30 AM UTC+2, Pranav Pandey wrote:
>
> Hi Folks,
>
> This is my first post on this group. I am working on integrating 3d 
> printing and CNC Milling in a single machine. I have worked with Arduino 
> Mega before and have run the machine on the Marlin firmware.
>
> However I am interested in using the Machine kit platform to run my 3d 
> printer. My background is Electrical and hence have only basic knowledge 
> about coding. I would like to know if someone has successfully 3D Printed 
> using the above setup. If yes, Can you please share some links or procedure 
> for the same?
>
> Thanks
> Pranav
>

-- 
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: Running 3D Printer using Machinekit + CRAMPS + BBB

[Daren Schwenke]

I have run this in the past with no issues.  
My current testing machine is targeting the BBGW though, so it's using 
rt-preempt (so wireless works) and the BeBoPr config instead (as CRAMPS 
shares pins with the wifi/bluetooth module)
So I can't directly assist you atm.

On Sunday, September 3, 2017 at 1:35:21 PM UTC-4, machinen wrote:
>
> Hi,
> I am in somewhat similar situation to yours and I have few questions for 
> you:
>
> Were you able to upgrade your installation? Because the ready-made image 
> for BBB is quite old and when doing update/upgrade, the Machinekit 
> package(s) is(are) being kept back and it is because dependency error. The 
> same is when installing on new clean system flash (which are newer) by the 
> how to in Machinekit docs.
>
> Are you able to shutdown/poweroff/reboot your BBB with CRAMPS? I have the 
> Element14 BBB rev. C with CRAMPS 2.2 and I cannot shut it down completely. 
> The power on LED is still on and there are two LEDs on on CRAMPS and on the 
> right side of RIJ45 connector (bank of four LEDs) there is one LED faintly 
> blinking. Otherwise the BBB is turned off (I cannot SSH to it). I have to 
> manually shut the power down. Are you experiencing the same?
>
> And given the above, hoare you able to run the fabrikator Mini CRAMPS 
> configuration out of the box? My system is screaming at me about missing 
> fdm.config. Maybe it is because old machinekit (but as I said, currently 
> the dependency is broken), the actual error is:
> halcmd loadusr io started
> Traceback (most recent call last):
>   File "fabrikator_mini.py", line 8, in 
> from fdm.config import velocity_extrusion as ve
> ImportError: No module named config
> Shutting down and cleaning up Machinekit...
>
> Thanks.
>
> On Tuesday, August 29, 2017 at 8:08:30 AM UTC+2, Pranav Pandey wrote:
>>
>> Hi Folks,
>>
>> This is my first post on this group. I am working on integrating 3d 
>> printing and CNC Milling in a single machine. I have worked with Arduino 
>> Mega before and have run the machine on the Marlin firmware.
>>
>> However I am interested in using the Machine kit platform to run my 3d 
>> printer. My background is Electrical and hence have only basic knowledge 
>> about coding. I would like to know if someone has successfully 3D Printed 
>> using the above setup. If yes, Can you please share some links or procedure 
>> for the same?
>>
>> Thanks
>> Pranav
>>
>

-- 
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: Running 3D Printer using Machinekit + CRAMPS + BBB

[gary]

you could try sudo apt-get dist-upgrade for held back packages...

On Tuesday, August 29, 2017 at 2:08:30 AM UTC-4, Pranav Pandey wrote:
>
> Hi Folks,
>
> This is my first post on this group. I am working on integrating 3d 
> printing and CNC Milling in a single machine. I have worked with Arduino 
> Mega before and have run the machine on the Marlin firmware.
>
> However I am interested in using the Machine kit platform to run my 3d 
> printer. My background is Electrical and hence have only basic knowledge 
> about coding. I would like to know if someone has successfully 3D Printed 
> using the above setup. If yes, Can you please share some links or procedure 
> for the same?
>
> Thanks
> Pranav
>

-- 
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: Running 3D Printer using Machinekit + CRAMPS + BBB

['machinen' via Machinekit]

The dist-aupgrade removes machinekit packages from system. There is this 
problem:
The following packages have unmet dependencies:
 machinekit-xenomai : Depends: machinekit (= 0.1.1504202989-1mk.travis.
luminizepatch1.git59e91621~1jessie) but 0.1.1486851828-1mk.travis.master.
gitcbd2dfd3~1jessie is to be installed
E: Unable to correct problems, you have held broken packages.

Problem is that as I don't speak Python, I don't know where the file 
(assembly?) fdm.config should be or better yet from which file it is 
attempting to load/import.

-- 
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: Running 3D Printer using Machinekit + CRAMPS + BBB

[schoone...@btinternet.com]

  
  

On 03/09/17 23:37, 'machinen' via
  Machinekit wrote:


  The dist-aupgrade removes machinekit packages from
system. There is this problem:

The following packages
have unmet dependencies:
 machinekit-xenomai : Depends:
machinekit (= 0.1.1504202989-1mk.travis.luminizepatch1.git59e91621~1jessie) but 0.1.1486851828-1mk.travis.master.gitcbd2dfd3~1jessie is to be
installed
E: Unable to
correct problems, you have held broken
packages.
  
  

Problem is that as I don't speak Python, I don't know where the
file (assembly?) fdm.config should be or better yet from which
file it is attempting to load/import.
  


I don't speak parseltongue either, but this is nothing to do with
python

This is the package list for Jessie armhf
http://deb.machinekit.io/debian/dists/wheezy/main/binary-armhf/Packages

As you will see the machinekit-xenomai and machinekit versions are
both at 0.1.1504202989, so if your apt is trying to fetch 0.1.1486851828 it is working from an old package
  list, which means it has not been updated
properly.

apt-get remove machinekit machinekit-xenomai
apt-get update
apt-get install machinekit-xenomai

should hopefully restore things.  ( If apt uninstalls other packages
when you do the uninstall, make sure you install those again too)

As for where the fdm stuff is installed, /usr/lib/python2.7/dist-packages/fdm
It has not changed for yonks, so updating packages achieves nothing.




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


  




-- 
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: Running 3D Printer using Machinekit + CRAMPS + BBB

[schoone...@btinternet.com]

  
  

On 04/09/17 09:02,
  schoone...@btinternet.com wrote:


  
  
  On 03/09/17 23:37, 'machinen' via
Machinekit wrote:
  
  
The dist-aupgrade removes machinekit packages
  from system. There is this problem:
  
  The
  following packages have unmet dependencies:
   machinekit-xenomai : Depends:
  machinekit (= 0.1.1504202989-1mk.travis.luminizepatch1.git59e91621~1jessie) but 0.1.1486851828-1mk.travis.master.gitcbd2dfd3~1jessie is to be
  installed
  E: Unable to
  correct problems, you have held
  broken packages.


  
  Problem is that as I don't speak Python, I don't know where
  the file (assembly?) fdm.config should be or better yet from
  which file it is attempting to load/import.

  
  
  I don't speak parseltongue either, but this is nothing to do with
  python
  
  This is the package list for Jessie armhf
  http://deb.machinekit.io/debian/dists/wheezy/main/binary-armhf/Packages
  
  As you will see the machinekit-xenomai and machinekit versions are
  both at 0.1.1504202989, so if your apt is trying to fetch
  0.1.1486851828 it is working from an old
package list, which means it has not
  been updated properly.
  
  apt-get remove machinekit machinekit-xenomai
  apt-get update
  apt-get install machinekit-xenomai
  
  should hopefully restore things.  ( If apt uninstalls other
  packages when you do the uninstall, make sure you install those
  again too)
  
  As for where the fdm stuff is installed, /usr/lib/python2.7/dist-packages/fdm
  It has not changed for yonks, so updating packages achieves
  nothing.


FYI, as I noted to someone else, but off forum, in case this is how
it has come about.

"The situation described could normally only be encountered where
the user has not updated apt-get, but tries to install a later
version of a package directly, via dpkg.
This results in the dependencies being unable to be met, because the
packages known about do not include it."

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


  




-- 
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: Running 3D Printer using Machinekit + CRAMPS + BBB

['machinen' via Machinekit]

Somehow I didn't have the fdm folder on my system - probably from mucking 
around. However I did a new flash of clean 
bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz image and sure there 
it is. Unfortunately when the first thing when I log into this new install 
I do is run machinekit and select the Fabrikator Mini CRAMPS configuration, 
then try the ./run.py script I still get the same error.

And the combination of sudo apt-get remove machinekit 
machinekit-xenomai/update/install machinekit-xenomai only removes 
machinekit packages from system and when installing it still falls on the 
same error. I will try purge next with new clean install.

On Monday, September 4, 2017 at 10:02:12 AM UTC+2, Schooner wrote:
>
>
> On 03/09/17 23:37, 'machinen' via Machinekit wrote:
>
> The dist-aupgrade removes machinekit packages from system. There is this 
> problem:
> The following packages have unmet dependencies:
>  machinekit-xenomai : Depends: machinekit (= 0.1.1504202989-1mk.travis.
> luminizepatch1.git59e91621~1jessie) but 0.1.1486851828-1mk.travis.master.
> gitcbd2dfd3~1jessie is to be installed
> E: Unable to correct problems, you have held broken packages.
>
> Problem is that as I don't speak Python, I don't know where the file 
> (assembly?) fdm.config should be or better yet from which file it is 
> attempting to load/import.
>
>
> I don't speak parseltongue either, but this is nothing to do with python
>
> This is the package list for Jessie armhf
> http://deb.machinekit.io/debian/dists/wheezy/main/binary-armhf/Packages
>
> As you will see the machinekit-xenomai and machinekit versions are both at 
> *0.1.1504202989*, so if your apt is trying to fetch *0.1**.**1486851828* 
> it is working from an old package list, which means it has not been 
> updated properly.
>
> apt-get remove machinekit machinekit-xenomai
> apt-get update
> apt-get install machinekit-xenomai
>
> should hopefully restore things.  ( If apt uninstalls other packages when 
> you do the uninstall, make sure you install those again too)
>
> As for where the fdm stuff is installed, 
> */usr/lib/python2.7/dist-packages/fdm*
> It has not changed for yonks, so updating packages achieves nothing.
>
>
> -- 
> 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] Re: Running 3D Printer using Machinekit + CRAMPS + BBB

[schoone...@btinternet.com]

  
  
Look at http://deb.machinekit.io/debian/pool/main/m/machinekit/

There is no package 0.1.1486851828-1mk.travis.master.gitcbd2dfd3~1jessie
  that serial is
  ancient.

You need to check your /etc/apt/sources.list and the files in
/etc/apt/sources.list.d and see where this is coming from

I don't know how you can be getting this error, if your one and only
machinekit reference is deb.machinekit.io, as it should be.
The package list there only refers to 0.1.1504202989

Have to suspect that your image is old and also points to
deb.dovetail-automata.com or similar, but that serial is not there
either AFAICT

As far as FDM stuff goes I have no idea I'm afraid, don't use it,
hopefully someone else can talk you through it once you get
machinekit back running.



On 04/09/17 13:38, 'machinen' via
  Machinekit wrote:


  Somehow I didn't have the fdm folder on my system -
probably from mucking around. However I did a new flash of clean
bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz image and
sure there it is. Unfortunately when the first thing when I log
into this new install I do is run machinekit and select the
Fabrikator Mini CRAMPS configuration, then try the ./run.py
script I still get the same error.

And the combination of sudo apt-get remove machinekit
machinekit-xenomai/update/install machinekit-xenomai only
removes machinekit packages from system and when installing it
still falls on the same error. I will try purge next with new
clean install.

On Monday, September 4, 2017 at 10:02:12 AM UTC+2, Schooner
wrote:

   
On 03/09/17 23:37, 'machinen' via Machinekit wrote:


  The dist-aupgrade removes machinekit
packages from system. There is this problem:

The following packages have
unmet dependencies:
 machinekit-xenomai : Depends: machinekit (= 0.1.1504202989-1mk.travis.luminizepatch1.git59e91621~1jessie) but 0.1.1486851828-1mk.travis.master.gitcbd2dfd3~1jessie is to be installed
E: Unable to correct problems, you have held broken
packages.
  
  

Problem is that as I don't speak Python, I don't know
where the file (assembly?) fdm.config should be or
better yet from which file it is attempting to
load/import.
  


I don't speak parseltongue either, but this is nothing to do
with python

This is the package list for Jessie armhf
http://deb.machinekit.io/debian/dists/wheezy/main/binary-armhf/Packages

As you will see the machinekit-xenomai and machinekit
versions are both at 0.1.1504202989, so if your apt
is trying to fetch 0.1.1486851828
  it is working from an old package list,
which means it has not been updated properly.

apt-get remove machinekit machinekit-xenomai
apt-get update
apt-get install machinekit-xenomai

should hopefully restore things.  ( If apt uninstalls other
packages when you do the uninstall, make sure you install
those again too)

As for where the fdm stuff is installed, /usr/lib/python2.7/dist-packages/fdm
It has not changed for yonks, so updating packages achieves
nothing.



 -- 
  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:/

Re: [Machinekit] Re: Running 3D Printer using Machinekit + CRAMPS + BBB

[Bas de Bruijn]

> On 04 Sep 2017, at 14:38, 'machinen' via Machinekit 
>  wrote:
> 
> Somehow I didn't have the fdm folder on my system - probably from mucking 
> around. However I did a new flash of clean 
> bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz image and sure there 
> it is. Unfortunately when the first thing when I log into this new install I 
> do is run machinekit and select the Fabrikator Mini CRAMPS configuration, 
> then try the ./run.py script I still get the same error.

why do you run machinekit with that configuration as well as the run.py script?

Am I right in that you cloned this repository?
https://github.com/machinekoder/Fabrikator-Mini-CRAMPS

if so, then cd into that directory and run the run.py script from there. No 
need to start machinekit too.

Traceback (most recent call last):
  File "fabrikator_mini.py", line 8, in 
from fdm.config import velocity_extrusion as ve
ImportError: No module named config

this error is saying it can’t find this the “config” folder like here 
https://github.com/machinekit/machinekit/tree/luminize-patch-1/lib/python/fdm/config.
in a terminal type “sudo find / -name velocity_extrusion.py” or “sudo find / 
-name base.py”
what does it say?

-- 
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: Running 3D Printer using Machinekit + CRAMPS + BBB

['machinen' via Machinekit]

I actually looked at the repository and source list as first thing, but I 
didn't see anything odd. I am for this endeavour using the "latest" 
official machinekit image 

bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz from 
elinux.org/Beagleboard:BeagleBoneBlack_Debian which is from february so I am 
not surprised that it is old.

However in sources.list there is:

deb http://httpredir.debian.org/debian/ jessie main contrib non-free
#deb-src http://httpredir.debian.org/debian/ jessie main contrib non-free

deb http://httpredir.debian.org/debian/ jessie-updates main contrib non-free
#deb-src http://httpredir.debian.org/debian/ jessie-updates main contrib 
non-free

deb http://security.debian.org/ jessie/updates main contrib non-free
#deb-src http://security.debian.org/ jessie/updates main contrib non-free

#deb http://httpredir.debian.org/debian jessie-backports main contrib non-free
##deb-src http://httpredir.debian.org/debian jessie-backports main contrib 
non-free

deb [arch=armhf] http://deb.machinekit.io/debian jessie main
#deb-src [arch=armhf] http://deb.machinekit.io/debian jessie main

#Kernel source (repos.rcn-ee.com) : 
https://github.com/RobertCNelson/linux-stable-rcn-ee
#
#git clone https://github.com/RobertCNelson/linux-stable-rcn-ee
#cd ./linux-stable-rcn-ee
#git checkout `uname -r` -b tmp
#
deb [arch=armhf] http://repos.rcn-ee.com/debian/ jessie main
#deb-src [arch=armhf] http://repos.rcn-ee.com/debian/ jessie main

And the sources.list.d folder is empty. And I didn't change anything.



On Monday, September 4, 2017 at 3:14:57 PM UTC+2, Schooner wrote:
>
> Look at http://deb.machinekit.io/debian/pool/main/m/machinekit/
>
> There is no package 0.1.1486851828-1mk.travis.master.gitcbd2dfd3~1jessie
> that serial is ancient.
>
> You need to check your /etc/apt/sources.list and the files in 
> /etc/apt/sources.list.d and see where this is coming from
>
> I don't know how you can be getting this error, if your one and only 
> machinekit reference is *deb.machinekit.io *, 
> as it should be.
> The package list there only refers to *0.1.1504202989*
>
> Have to suspect that your image is old and also points to 
> deb.dovetail-automata.com or similar, but that serial is not there either 
> AFAICT
>
> As far as FDM stuff goes I have no idea I'm afraid, don't use it, 
> hopefully someone else can talk you through it once you get machinekit back 
> running.
>
>
>
> On 04/09/17 13:38, 'machinen' via Machinekit wrote:
>
> Somehow I didn't have the fdm folder on my system - probably from mucking 
> around. However I did a new flash of clean 
> bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz image and sure there 
> it is. Unfortunately when the first thing when I log into this new install 
> I do is run machinekit and select the Fabrikator Mini CRAMPS configuration, 
> then try the ./run.py script I still get the same error.
>
> And the combination of sudo apt-get remove machinekit 
> machinekit-xenomai/update/install machinekit-xenomai only removes 
> machinekit packages from system and when installing it still falls on the 
> same error. I will try purge next with new clean install.
>
> On Monday, September 4, 2017 at 10:02:12 AM UTC+2, Schooner wrote: 
>>
>>
>> On 03/09/17 23:37, 'machinen' via Machinekit wrote:
>>
>> The dist-aupgrade removes machinekit packages from system. There is this 
>> problem:
>> The following packages have unmet dependencies:
>>  machinekit-xenomai : Depends: machinekit (= 0.1.1504202989-1mk.travis.
>> luminizepatch1.git59e91621~1jessie) but 0.1.1486851828-1mk.travis.master.
>> gitcbd2dfd3~1jessie is to be installed
>> E: Unable to correct problems, you have held broken packages.
>>
>> Problem is that as I don't speak Python, I don't know where the file 
>> (assembly?) fdm.config should be or better yet from which file it is 
>> attempting to load/import.
>>
>>
>> I don't speak parseltongue either, but this is nothing to do with python
>>
>> This is the package list for Jessie armhf
>> http://deb.machinekit.io/debian/dists/wheezy/main/binary-armhf/Packages
>>
>> As you will see the machinekit-xenomai and machinekit versions are both 
>> at *0.1.1504202989*, so if your apt is trying to fetch *0.1**.*
>> *1486851828* it is working from an old package list, which means it has 
>> not been updated properly.
>>
>> apt-get remove machinekit machinekit-xenomai
>> apt-get update
>> apt-get install machinekit-xenomai
>>
>> should hopefully restore things.  ( If apt uninstalls other packages when 
>> you do the uninstall, make sure you install those again too)
>>
>> As for where the fdm stuff is installed, 
>> */usr/lib/python2.7/dist-packages/fdm*
>> It has not changed for yonks, so updating packages achieves nothing.
>>
>>
>> -- 
>> 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.
>

Re: [Machinekit] Re: Running 3D Printer using Machinekit + CRAMPS + BBB

['machinen' via Machinekit]

>
> why do you run machinekit with that configuration as well as the run.py 
> script?
>

I probably expressed myself wrong. What I did mean is that I ran machinekit 
command, from the example configuration command selected Fabrikator Mini 
CRAMPS (so I used the config files which came with machinekit install in 
aforementioned BBB image), then cd to config directory and tried to run the 
run.py script to see if there are any errors.

>
> Am I right in that you cloned this repository?
> https://github.com/machinekoder/Fabrikator-Mini-CRAMPS
>
> if so, then cd into that directory and run the run.py script from there. 
> No need to start machinekit too.
>
> Traceback (most recent call last):
>   File "fabrikator_mini.py", line 8, in 
> from fdm.config import velocity_extrusion as ve
> ImportError: No module named config
>
> this error is saying it can’t find this the “config” folder like here 
> https://github.com/machinekit/machinekit/tree/luminize-patch-1/lib/python/fdm/config
> .
> in a terminal type “sudo find / -name velocity_extrusion.py” or “sudo find 
> / -name base.py”
> what does it say?
>

The first write back notning (shouldn't there at least be info that nothing 
was found?), the second

machinekit@beaglebone:/etc/apt$ sudo find / -name base.py
/usr/lib/python3.4/email/mime/base.py
/usr/lib/python2.7/email/mime/base.py
/usr/lib/python2.7/dist-packages/pylint/checkers/base.py
/usr/lib/python2.7/dist-packages/cryptography/hazmat/primitives/ciphers/base
.py
/usr/lib/python2.7/dist-packages/blinker/base.py
/usr/lib/python2.7/dist-packages/zmq/auth/base.py
/usr/lib/python2.7/dist-packages/pyasn1/type/base.py
/usr/share/pyshared/pyasn1/type/base.py
/usr/share/linuxcnc/examples/sample-configs/sim/qqvsim/config/base.py
/usr/share/dh-python/dhpython/build/base.py
/usr/local/lib/python2.7/dist-packages/pip/_vendor/html5lib/filters/base.py
/usr/local/lib/python2.7/dist-packages/pip/_vendor/html5lib/treewalkers/base
.py
/usr/local/lib/python2.7/dist-packages/pip/_vendor/html5lib/treebuilders/
base.py

But there is no config directory in fdm directory. I will try to add it 
from machinekit github.
 

-- 
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: Running 3D Printer using Machinekit + CRAMPS + BBB

[schoone...@btinternet.com]

  
  
OK I have found the problem.
You were unlucky, because it does not affect every flavour and OS

A problem whereby a PR submission got  pushed into the repo before
merge, has screwed some of the packages files.
The package serials for machinekit-xenomai and machinekit don't
match so dependencies can never be met

I cannot however find any reference to 0.1.1486851828-1mk.travis.master.gitcbd2dfd3~1jessie and have
no idea where that came from.

I am going to have to rebuild the repo manually, removing the rogue
packages back to the last proper merge.

Don't attempt any further update etc. until you hear back.



On 04/09/17 15:48, 'machinen' via
  Machinekit wrote:


  I actually looked at the repository and source list
as first thing, but I didn't see anything odd. I am for this
endeavour using the "latest" official machinekit image 
bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz from elinux.org/Beagleboard:BeagleBoneBlack_Debian which is from february so I am not surprised that it is old.

However in sources.list there is:

deb http://httpredir.debian.org/debian/ jessie main contrib non-free
#deb-src http://httpredir.debian.org/debian/ jessie main contrib non-free

deb http://httpredir.debian.org/debian/ jessie-updates main contrib non-free
#deb-src http://httpredir.debian.org/debian/ jessie-updates main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free
#deb-src http://security.debian.org/ jessie/updates main contrib non-free

#deb http://httpredir.debian.org/debian jessie-backports main contrib non-free
##deb-src http://httpredir.debian.org/debian jessie-backports main contrib non-free

deb [arch=armhf] http://deb.machinekit.io/debian jessie main
#deb-src [arch=armhf] http://deb.machinekit.io/debian jessie main

#Kernel source (repos.rcn-ee.com) : https://github.com/RobertCNelson/linux-stable-rcn-ee
#
#git clone https://github.com/RobertCNelson/linux-stable-rcn-ee
#cd ./linux-stable-rcn-ee
#git checkout `uname -r` -b tmp
#
deb [arch=armhf] http://repos.rcn-ee.com/debian/ jessie main
#deb-src [arch=armhf] http://repos.rcn-ee.com/debian/ jessie main

And the sources.list.d folder is empty. And I didn't change anything.




On Monday, September 4, 2017 at 3:14:57 PM UTC+2, Schooner
wrote:

   Look at http://deb.machinekit.io/debian/pool/main/m/machinekit/

There is no package 0.1.1486851828-1mk.travis.master.gitcbd2dfd3~1jessie
  that
  serial is ancient.

You need to check your /etc/apt/sources.list and the files
in /etc/apt/sources.list.d and see where this is coming from

I don't know how you can be getting this error, if your one
and only machinekit reference is deb.machinekit.io, as it should be.
The package list there only refers to 0.1.1504202989

Have to suspect that your image is old and also points to deb.dovetail-automata.com or similar, but that
serial is not there either AFAICT

As far as FDM stuff goes I have no idea I'm afraid, don't
use it, hopefully someone else can talk you through it once
you get machinekit back running.



On 04/09/17 13:38, 'machinen' via Machinekit wrote:


  Somehow I didn't have the fdm folder on my
system - probably from mucking around. However I did a
new flash of clean bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz
image and sure there it is. Unfortunately when the first
thing when I log into this new install I do is run
machinekit and select the Fabrikator Mini CRAMPS
configuration, then try the ./run.py script I still get
the same error.

And the combination of sudo apt-get remove machinekit
machinekit-xenomai/update/install
machinekit-xenomai only removes machinekit packages from
system and when installing it still falls on the same
error. I will try purge next with new clean install.

On Monday, September 4, 2017 at 10:02:12 AM UTC+2,
Schooner wrote:

   
On 03/09/17 23:37, 'machinen' via Machinekit
  wrote:


  The dist-aupgrade removes
machinekit packages from system. There is this
problem:

The following packages
have unmet

Re: [Machinekit] Re: Running 3D Printer using Machinekit + CRAMPS + BBB

['machinen' via Machinekit]

Oh, thanks.

I think that the 14-something serial is from the February image, trying on 
newer I have gotten something like:

Depends: machinekit (= 0.1.1504202989-1mk.travis.luminizepatch1.git59e91621~
1jessie) but 0.1.1504208693-1mk.travis.pr1265.git00ce6961~1jessie is to be 
installed



On Monday, September 4, 2017 at 5:13:34 PM UTC+2, Schooner wrote:
>
> OK I have found the problem.
> You were unlucky, because it does not affect every flavour and OS
>
> A problem whereby a PR submission got  pushed into the repo before merge, 
> has screwed some of the packages files.
> The package serials for machinekit-xenomai and machinekit don't match so 
> dependencies can never be met
>
> I cannot however find any reference to 0.1.1486851828-1mk.travis.master.
> gitcbd2dfd3~1jessie and have no idea where that came from.
>
> I am going to have to rebuild the repo manually, removing the rogue 
> packages back to the last proper merge.
>
> Don't attempt any further update etc. until you hear back.
>
>
> On 04/09/17 15:48, 'machinen' via Machinekit wrote:
>
> I actually looked at the repository and source list as first thing, but I 
> didn't see anything odd. I am for this endeavour using the "latest" 
> official machinekit image 
>
> bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz from 
> elinux.org/Beagleboard:BeagleBoneBlack_Debian which is from february so I am 
> not surprised that it is old.
>
> However in sources.list there is:
>
> deb http://httpredir.debian.org/debian/ jessie main contrib non-free#deb-src 
> http://httpredir.debian.org/debian/ jessie main contrib non-free
>
> deb http://httpredir.debian.org/debian/ jessie-updates main contrib 
> non-free#deb-src http://httpredir.debian.org/debian/ jessie-updates main 
> contrib non-free
>
> deb http://security.debian.org/ jessie/updates main contrib non-free#deb-src 
> http://security.debian.org/ jessie/updates main contrib non-free
> #deb http://httpredir.debian.org/debian jessie-backports main contrib 
> non-free##deb-src http://httpredir.debian.org/debian jessie-backports main 
> contrib non-free
>
> deb [arch=armhf] http://deb.machinekit.io/debian jessie main#deb-src 
> [arch=armhf] http://deb.machinekit.io/debian jessie main
> #Kernel source (repos.rcn-ee.com) : 
> https://github.com/RobertCNelson/linux-stable-rcn-ee##git clone 
> https://github.com/RobertCNelson/linux-stable-rcn-ee#cd 
> ./linux-stable-rcn-ee#git checkout `uname -r` -b tmp#
> deb [arch=armhf] http://repos.rcn-ee.com/debian/ jessie main#deb-src 
> [arch=armhf] http://repos.rcn-ee.com/debian/ jessie main
>
> And the sources.list.d folder is empty. And I didn't change anything.
>
>
>
>
> On Monday, September 4, 2017 at 3:14:57 PM UTC+2, Schooner wrote: 
>>
>> Look at http://deb.machinekit.io/debian/pool/main/m/machinekit/
>>
>> There is no package 0.1.1486851828-1mk.travis.master.gitcbd2dfd3~1jessie
>> that serial is ancient.
>>
>> You need to check your /etc/apt/sources.list and the files in 
>> /etc/apt/sources.list.d and see where this is coming from
>>
>> I don't know how you can be getting this error, if your one and only 
>> machinekit reference is *deb.machinekit.io *, 
>> as it should be.
>> The package list there only refers to *0.1.1504202989*
>>
>> Have to suspect that your image is old and also points to 
>> deb.dovetail-automata.com or similar, but that serial is not there 
>> either AFAICT
>>
>> As far as FDM stuff goes I have no idea I'm afraid, don't use it, 
>> hopefully someone else can talk you through it once you get machinekit back 
>> running.
>>
>>
>>
>> On 04/09/17 13:38, 'machinen' via Machinekit wrote:
>>
>> Somehow I didn't have the fdm folder on my system - probably from mucking 
>> around. However I did a new flash of clean 
>> bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz image and sure there 
>> it is. Unfortunately when the first thing when I log into this new install 
>> I do is run machinekit and select the Fabrikator Mini CRAMPS configuration, 
>> then try the ./run.py script I still get the same error.
>>
>> And the combination of sudo apt-get remove machinekit 
>> machinekit-xenomai/update/install machinekit-xenomai only removes 
>> machinekit packages from system and when installing it still falls on the 
>> same error. I will try purge next with new clean install.
>>
>> On Monday, September 4, 2017 at 10:02:12 AM UTC+2, Schooner wrote: 
>>>
>>>
>>> On 03/09/17 23:37, 'machinen' via Machinekit wrote:
>>>
>>> The dist-aupgrade removes machinekit packages from system. There is this 
>>> problem:
>>> The following packages have unmet dependencies:
>>>  machinekit-xenomai : Depends: machinekit (= 0.1.1504202989-1mk.travis.
>>> luminizepatch1.git59e91621~1jessie) but 0.1.1486851828-1mk.travis.master
>>> .gitcbd2dfd3~1jessie is to be installed
>>> E: Unable to correct problems, you have held broken packages.
>>>
>>> Problem is that as I don't speak Python, I don't know where the file 
>>> (assembly?) fdm.config sho

Re: [Machinekit] Re: Running 3D Printer using Machinekit + CRAMPS + BBB

[schoone...@btinternet.com]

  
  

On 04/09/17 16:38, 'machinen' via
  Machinekit wrote:


  Oh, thanks.

I think that the 14-something serial is from the February image,
trying on newer I have gotten something like:


Depends:
machinekit (= 0.1.1504202989-1mk.travis.luminizepatch1.git59e91621~1jessie) but 0.1.1504208693-1mk.travis.pr1265.git00ce6961~1jessie is to be
installed
  
  
  


Yes that is the error you should have had.
Neither of those packages should be in the repo.

There is a new build in progress to bring all the serials up to a
new number, which should solve the issues.
Takes a couple of hours to fully complete however.


  


On Monday, September 4, 2017 at 5:13:34 PM UTC+2, Schooner
wrote:

   OK I have found the
problem.
You were unlucky, because it does not affect every flavour
and OS

A problem whereby a PR submission got  pushed into the repo
before merge, has screwed some of the packages files.
The package serials for machinekit-xenomai and machinekit
don't match so dependencies can never be met

I cannot however find any reference to 0.1.1486851828-1mk.travis.master.gitcbd2dfd3~1jessie
and have no idea where that
came from.

I am going to have to rebuild the repo manually, removing
the rogue packages back to the last proper merge.

Don't attempt any further update etc. until you hear back.



On 04/09/17 15:48, 'machinen' via Machinekit wrote:


  I actually looked at the repository and
source list as first thing, but I didn't see anything
odd. I am for this endeavour using the "latest" official
machinekit image 
bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz from elinux.org/Beagleboard:BeagleBoneBlack_Debian which is from february so I am not surprised that it is old.

However in sources.list there is:

deb http://httpredir.debian.org/debian/ jessie main contrib non-free
#deb-src http://httpredir.debian.org/debian/ jessie main contrib non-free

deb http://httpredir.debian.org/debian/ jessie-updates main contrib non-free
#deb-src http://httpredir.debian.org/debian/ jessie-updates main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free
#deb-src http://security.debian.org/ jessie/updates main contrib non-free

#deb http://httpredir.debian.org/debian jessie-backports main contrib non-free
##deb-src http://httpredir.debian.org/debian jessie-backports main contrib non-free

deb [arch=armhf] http://deb.machinekit.io/debian jessie main
#deb-src [arch=armhf] http://deb.machinekit.io/debian jessie main

#Kernel source (repos.rcn-ee.com) : https://github.com/RobertCNelson/linux-stable-rcn-ee
#
#git clone https://github.com/RobertCNelson/linux-stable-rcn-ee
#cd ./linux-stable-rcn-ee
#git checkout `uname -r` -b tmp
#
deb [arch=armhf] http://repos.rcn-ee.com/debian/ jessie main
#deb-src [arch=armhf] http://repos.rcn-ee.com/debian/ jessie main

And the sources.list.d folder is empty. And I didn't change anything.




On Monday, September 4, 2017 at 3:14:57 PM UTC+2,
Schooner wrote:

   Look at http://deb.machinekit.io/debian/pool/main/m/machinekit/

There is no package 0.1.1486851828-1mk.travis.master.gitcbd2dfd3~1jessie
  that

  serial is ancient.

You need to check your /etc/apt/sources.list and the
files in /etc/apt/sources.list.d and see where this
is coming from

I don't know how you can be getting this error, if
your one and only machinekit reference is deb.machinekit.io, as it should
be.
The package list there only refers to 0.1.1504202989

Have to suspect that your image is old and also
points to deb.dovetail-automata.com or similar,
but that serial is not there either AFAICT

As far as FDM stuff goes I have no idea I'm afraid,
don't use it, hopefully someone else can talk you
through it once you get machinekit back running.



On 04/09/17 13:38, 'machinen' via Machinekit
  wrote:
 

Re: [Machinekit] Re: Running 3D Printer using Machinekit + CRAMPS + BBB

[schoone...@btinternet.com]

  
  

On 04/09/17 16:46,
  schoone...@btinternet.com wrote:


  
  
  On 04/09/17 16:38, 'machinen' via
Machinekit wrote:
  
  
Oh, thanks.
  
  I think that the 14-something serial is from the February
  image, trying on newer I have gotten something like:
  
  
  Depends:
  machinekit (= 0.1.1504202989-1mk.travis.luminizepatch1.git59e91621~1jessie) but 0.1.1504208693-1mk.travis.pr1265.git00ce6961~1jessie is to be
  installed



  
  
  Yes that is the error you should have had.
  Neither of those packages should be in the repo.
  
  There is a new build in progress to bring all the serials up to a
  new number, which should solve the issues.
  Takes a couple of hours to fully complete however.


The new packages are built.
The serial string you should now get is 0.1.1504538312-1mk.travis.master.gitde24b276

Note machinekit-xenomai for Jessie armhf now depends upon the
correct serial version of machinekit
Package: machinekit-xenomai
Source: machinekit
Version: 0.1.1504538312-1mk.travis.master.gitde24b276~1jessie
Architecture: armhf
Maintainer: John Morris 
Installed-Size: 6529
Depends: machinekit (= 0.1.1504538312-1mk.travis.master.gitde24b276~1jessie), libavahi-client3 (>= 0.6.16), libavahi-common3 (>= 0.6.16), libc6 (>= 2.15), libczmq2 (>= 2.2.0), libgcc1 (>= 1:4.4.0), libprotobuf9, libstdc++6 (>= 4.3.0), libudev1 (>= 183), libuuid1 (>= 2.16), libxenomai1, libzmq3 (>= 3.2.3+dfsg), yapps2-runtime, xenomai-runtime
Enhances: machinekit
Breaks: machinekit-dev
Provides: machinekit-rt-threads
Priority: extra
Section: misc
Filename: pool/main/m/machinekit/machinekit-xenomai_0.1.1504538312-1mk.travis.master.gitde24b276~1jessie_armhf.deb
Size: 1008094
SHA256: 164585cc5441756c2b2be72c26477079cce42526365d6219152264e3f0fc6f14
SHA1: 159446e0c8f1f2b2950d3a5de1b167df39c10daa
MD5sum: e0814dc15139ef0372e44d4baa24ee14
Description: PC based motion controller for real-time Linux
 Machinekit is the next-generation Enhanced Machine Controller which
 provides motion control for CNC machine tools and robotic
 applications (milling, cutting, routing, etc.).
 .
 This package provides components and drivers that run on a Xenomai
 realtime system, with userspace threads.

Hopefully your problems will be one fewer now  ;-) 

  
  

  
  
  On Monday, September 4, 2017 at 5:13:34 PM UTC+2, Schooner
  wrote:
  
 OK I have found the
  problem.
  You were unlucky, because it does not affect every flavour
  and OS
  
  A problem whereby a PR submission got  pushed into the
  repo before merge, has screwed some of the packages files.
  The package serials for machinekit-xenomai and machinekit
  don't match so dependencies can never be met
  
  I cannot however find any reference to 0.1.1486851828-1mk.travis.master.gitcbd2dfd3~1jessie

  and have no idea where that
  came from.
  
  I am going to have to rebuild the repo manually, removing
  the rogue packages back to the last proper merge.
  
  Don't attempt any further update etc. until you hear back.
  
  
  
  On 04/09/17 15:48, 'machinen' via Machinekit wrote:
  
  
I actually looked at the repository and
  source list as first thing, but I didn't see anything
  odd. I am for this endeavour using the "latest"
  official machinekit image 
  bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz from elinux.org/Beagleboard:BeagleBoneBlack_Debian which is from february so I am not surprised that it is old.

However in sources.list there is:

deb http://httpredir.debian.org/debian/ jessie main contrib non-free
#deb-src http://httpredir.debian.org/debian/ jessie main contrib non-free

deb http://httpredir.debian.org/debian/ jessie-updates main contrib non-free
#deb-src http://httpredir.debian.org/debian/ jessie-updates main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free
#deb-src http://security.debian.org/ jessie/updates main contrib non-free

#deb http://httpredir.debian.org/debian jessie-backports main contrib non-free
##deb-src http://httpredir.debian.org/debian jessie-backports main contrib non-free

deb [arch=armhf] http://deb.machinekit.io/debian jessie main
#deb-src [arch=armhf] http://deb.machinekit.io/debian jessie main

#Kernel source (repos.rcn-ee.com) : https://github.com/RobertCNelson/linux-stable-rcn-ee
#
#git clone https://github.com/RobertCNelson/linux-stab