Re: [Emc-users] Dual boot for WIN-XP and LinuxCNC

[John Dammeyer]

I installed the
linuxcnc-2.7.14-wheezy.iso 

I want to download putty so I can access the com1 port and talk to the DC Servo 
controller for diagnostics.

Standard practice for the Pi and Beaglebone is to 
sudo apt-get update

and this is what I get with linuxCNC

Hit http://linuxcnc.org wheezy Release.gpg
Hit http://linuxcnc.org wheezy Release
Hit http://linuxcnc.org wheezy/base Sources  
Hit http://linuxcnc.org wheezy/2.7-rtai Sources
Hit http://linuxcnc.org wheezy/base i386 Packages 
Hit http://linuxcnc.org wheezy/2.7-rtai i386 Packages  
Hit http://archive.debian.org wheezy Release.gpg  
Ign http://archive.debian.org wheezy/updates Release.gpg
Ign http://linuxcnc.org wheezy/2.7-rtai Translation-en_CA
Ign http://linuxcnc.org wheezy/2.7-rtai Translation-en
Get:1 http://archive.debian.org wheezy/updates Release.gpg [1,601 B]
Ign http://linuxcnc.org wheezy/base Translation-en_CA  
Ign http://linuxcnc.org wheezy/base Translation-en
Hit http://archive.debian.org wheezy Release
Ign http://archive.debian.org wheezy/updates Release
Hit http://archive.debian.org wheezy/updates Release
E: Release file for 
http://archive.debian.org/debian-security/dists/wheezy/updates/Release is 
expired (invalid since 47d 13h 37min 5s). Updates for this repository will not 
be applied.

So it appears it's up to date but also out of date?  

Try to get putty...

john@g3616:~$ sudo apt-get install putty
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Unable to locate package putty
 
What's the next step?

Thanks
John






___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Increasingly OT: [Was: Re: How come.... --> Low voltage system

[Chris Albertson]

The low volts significantly raise the cost.  I remember buying wire (some
years ago) for a system on my sailboat and paying $5 per foot.

OK, I just looked up the cost of wire that is suitable for a 4KW low volt
system.  Home Depot sells a 12 foot run of black and red #0 wire for $93.
That is less then what I paid but the quality is not as good.   And then
the size of the bus bars and the switches and fuses is also huge.   Every
time you double the volts you about cut the cost of the parts in half.
until you get to about 400 to 500 volts and then you can use normal house
wiring.

Electrocution risk?   We assume you are a skilled electrician or can afford
to hire one.   And then after installation, the ENTIRE system is inside a
grounded metal cabinet that is locked.   You don't leave something like
this on a bench with wires exposed.

As it turns out for tiny system of a few KW the cost is low no matter what
you do.  But if the goal is to power an entire house then you have to
design carefully to contain the cost.

You find that it is hard to buy the parts for the price of a Power Wall.
In fact, you can't unless to luck into some one-time deal with salvaged
parts

On Mon, May 27, 2019 at 8:26 AM Nicklas Karlsson <
nicklas.karlsso...@gmail.com> wrote:

> On Sun, 26 May 2019 13:07:51 -0400
> Dave Cole  wrote:
>
> > There are some good reasons to use a 24 or 48 volt DC bus power system
> > for smaller systems.
> > The chance of electrocution is pretty low for a 48 volt DC system in a
> > dry environment.
> > Once you get above 50 volts or so things change.
>
> Yes stay below 50 volts is good for electrocution but fire may be a
> problem for higher power since current must be higher.
>
> 48 volt I think is standard in telecom and some electric fork lifts or
> similar use it.
>
> >
> > 24 volts is quite a practical voltage level for smaller systems.
>
> Have nothing to say against it.
>
> > Do a search for 24 volt inverters and you will find many.   48 volt, not
> > as many.
> >
> > I'm thinking hunting cabin, small cottage, larger boat, remote shed, etc.
> >
> > Now if you want to do your entire house and have typical house loads it
> > seems like a 120V+ DC bus system would make more sense.
>
> For entire house standard voltage is probably the solution but if there
> are high power loads with a rectifier choosing same or diode voltage drop
> above this might be a good choice.
>
>
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>


-- 

Chris Albertson
Redondo Beach, California

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Dual boot for WIN-XP and LinuxCNC

[John Dammeyer]

> >
> > But it was there once.  So far only a reboot has fixed this.  I'm not sure
> > why.
> 
> 
> Sometimes you can end up with kernel modules that claim to be dependent
> on
> each other, and the kernel won't let either fo them go.
> (at this point it is rather out of LinuxCNC's hands)
> 
> You can diagnose this situation with lsmod.
> You may find that hal_parport is still there, and in theory  modprobe
> should be able to unload it, but sometimes it seems to refuse to try.
> 
> What does it actually say in the middle section of the error dump? (That is
> typically where the useful information is, and in the last few lines of the
> dmesg output)
> 
> --
> atp


I finally got the Charge Pump working by removing the dependence on estop.  
Then the board enable on pin 1  is fooled with
net xenable => parport.0.pin-01-out

I now have motion.

A few more details to work out and I can try and get the second parallel port 
working.

John




___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Dual boot for WIN-XP and LinuxCNC

[John Dammeyer]

So new problem.

Using the config program I've made up a 4 axis parallel port hal/ini with just 
the one parallel port since importing the MACH3 config blows up with the second 
parallel port issue.  I'll work on that later.

The PMD_126 BoB has the Charge Pump mapped to 
net charge-pump => parport.0.pin-17-out
and this prevents any physical motion.

As the PC boots (regardless of WIN-XP or LinuxCNC) the charge pump outputs 
remains low.  Once MACH3 starts it starts toggling this output.  If MACH stops. 
 So does the charge pump. 

LinuxCNC should be the same.  The config program generated this:
##
loadrt charge_pump
net estop-out charge-pump.enable iocontrol.0.user-enable-out
net charge-pump <= charge-pump.out
##

I don't think I want the ESTOP controlling the charge pump enable.  If I 
understand the above line
net estop-out charge-pump.enable iocontrol.0.user-enable-out
The value of estop-out (TRUE or FALSE) is connected to  charge-pump.enable and 
iocontrol.0.user-enable-out

So if the estop-out is true then the little machine power button beside the 
stop button is enabled and so is the charge pump? 

John




___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Dual boot for WIN-XP and LinuxCNC

[andy pugh]

On Mon, 27 May 2019 at 23:50, John Dammeyer  wrote:

>
> But it was there once.  So far only a reboot has fixed this.  I'm not sure
> why.


Sometimes you can end up with kernel modules that claim to be dependent on
each other, and the kernel won't let either fo them go.
(at this point it is rather out of LinuxCNC's hands)

You can diagnose this situation with lsmod.
You may find that hal_parport is still there, and in theory  modprobe
should be able to unload it, but sometimes it seems to refuse to try.

What does it actually say in the middle section of the error dump? (That is
typically where the useful information is, and in the last few lines of the
dmesg output)

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is designed
for the especial use of mechanical geniuses, daredevils and lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1916

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Dual boot for WIN-XP and LinuxCNC

[John Dammeyer]

> > When I run Linux with a customized hal and config file it will crash
> > with the window with the errors.  But after that I can't even run the
> > stock single parallel port version without it crashing.  It's like the
> > 0x378 port has now vanished.
> >
> It has. You will need to blacklist ppdev as its grabbing the port before
> LCNC can.  The manpage for modprobe should explain how to blacklist it.
> 

Gene,
I think this is a problem within LinuxCNC itself and MachineKit because I ran 
into this with the BBB too.  If the hal/ini file has a certain type of error it 
won't run LinuxCNC and instead throws up a dialog box with all the error 
information.  Very extensive error information too.

So imagine this scenario.
1. Run LinuxCNC for the parallel port with the standard Stepper Motor example. 
2. LinuxCNC runs.  G-Code can be loaded.
3. Exit LinuxCNC and run it again but this time with a hal/ini file that has an 
error.
4. I get the window with the debugging information.
5. Run LinuxCNC for the parallel port with the standard Stepper Motor example 
as step 1.
6. Get the same debug window as step 4.


I believe what happens is that with the bad hal file, Linux CNC manages to 
capture the parallel port at 0x378 but then chokes on the second one at 0x2000. 
   Or if there is only one parallel port it captures it but then fails on some 
improperly formed hal command.  Then it throws up the diagnostic window.  At 
that point it should have released ownership of the 0x378 port but it doesn’t 
(I think).

And so the next time you try and run with a good hal/ini file the failure 
window is put up because now the 0x378 port isn't available anymore still held 
by something that didn't release it.

But it was there once.  So far only a reboot has fixed this.  I'm not sure why.

John





___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] POSITION_FILE

[andy pugh]

On Mon, 27 May 2019 at 20:15, Maxime Lemonnier 
wrote:

>
> When I reload linuxcnc, and want to use the MDI, I have to home all axis
> But then I'd loose the current position (reset to zero).


The machine moves to the home position, but your G554 (etc) offsets stay
the same.
So you should be able to stop mid job, turn off the machine, restart,
re-home and all the work coordinate systems should be in exactly the same
place.
(This is the case even without the POSITION_FILE.)


> Now you're thinking : use
> the 'NO_FORCE_HOMING = 1' option. But if I do I loose the ability to use
> the
> soft limits, which I need.
>

Have you tested this? My impression is that this all should work, though
you might _also_ need to exclude your axes from the homing sequence.


> (homing sequence or moving the machine back to 0 and etc is not an option,
> because of the precision (0.1deg backlash) of my roatry axes)
> I just don't want the machine to accumulate error after multiple reboot.


The error shouldn't accumulate. It should, at worst never be more than the
backlash.

In fact you are more likely to accumulate errors by not homing.

As you have servos, can you swap to absolute encoders? That ought to be a
complete solution.

(And, as an exotic option, my lathe uses a combination of POSITUOIN_FILE
and the single-turn absolute nature of resolvers to be absolute without a
homing move. Most of the time. I do sometimes have to re-home, I have not
quite figured out why yet. I think part of the reason is that I have two
complete versions of LinuxCNC on that machine and only one has the updated
resolver code)

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is designed
for the especial use of mechanical geniuses, daredevils and lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1916

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

[Emc-users] POSITION_FILE

[Maxime Lemonnier]

Hi all,

Simple question for you. I know I can use the

config.ini
--
...
[TRAJ]
POSITION_FILE = foo.txt

--
option to have linuxcnc remember the position in which the machine shut
down.

When I reload linuxcnc, and want to use the MDI, I have to home all axis
But then

I'd loose the current position (reset to zero). Now you're thinking : use
the
'NO_FORCE_HOMING = 1' option. But if I do I loose the ability to use the
soft limits,
which I need. So, is there a way I can have it all, e.g. how can I tell the
machine
to assume being homed, without resetting DRO to 0s?

(homing sequence or moving the machine back to 0 and etc is not an option,
because of the precision (0.1deg backlash) of my roatry axes)

I just don't want the machine to accumulate error after multiple reboot.
right now I can position the axis +/-0.02deg from
the set point, which is small, but if I reset that to 0 every boot, thees
0.02 could add up to something large

(yes, its a servo setup)

Thanks.

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Dual boot for WIN-XP and LinuxCNC

[Gene Heskett]

On Monday 27 May 2019 01:24:13 am John Dammeyer wrote:

> Thanks everyone.  I booted from the LinuxCNC live DVD I created.  
> Once I realized that the single partition I'd reserved for Linux
> needed to be turned into two partitions, one for the swap file and one
> for the data disk things went smoothly.
>
> Now I can boot from GRUB.  Select a number of different options
> including WIN-XP.
>
> WIN-XP still runs and accesses both the parallel port at 0x378 and the
> second PCI plug in card Parallel port that lists i/o at 2000 got 8
> bytes and 2008 for 8 bytes with IRQ 14 available if needed.
>
> Way back when I was doing this with a BeagleBone and Xylotex cape
> everything went smoothly because the hardware was known.  But now...
>
> Under Linux from DMESG:
> [   15.162377] lp0: using parport0 (interrupt-driven).
> [   15.446380] ppdev: user-space parallel port driver
>
> The command
> john@g3616:~$ lspci -v
>
> has a the end the following which suggests the PCI card has been
> found.
>
> 11:0a.0 Parallel controller: Device 1c00:2170 (rev 0f) (prog-if 01
> [BiDir]) Subsystem: Device 1c00:2170
>   Flags: medium devsel, IRQ 10
>   I/O ports at 2008 [size=8]
>   I/O ports at 2000 [size=8]
>
> I found this site.
> https://forum.linuxcnc.org/forum/18-computer/18917-faq-pci-parallel-po
>rt-cards
>
> Would I set
> loadrt hal_parport cfg="0x378 out 0xd000 out 0xd008 in"
>
> When I run Linux with a customized hal and config file it will crash
> with the window with the errors.  But after that I can't even run the
> stock single parallel port version without it crashing.  It's like the
> 0x378 port has now vanished.
>
It has. You will need to blacklist ppdev as its grabbing the port before 
LCNC can.  The manpage for modprobe should explain how to blacklist it.
 
> Suggestions?
> Thanks
> John
>
>
>
>
>
>
>
>
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 



___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Increasingly OT: [Was: Re: How come.... --> Low voltage system

[Nicklas Karlsson]

On Sun, 26 May 2019 13:07:51 -0400
Dave Cole  wrote:

> There are some good reasons to use a 24 or 48 volt DC bus power system 
> for smaller systems.
> The chance of electrocution is pretty low for a 48 volt DC system in a 
> dry environment.
> Once you get above 50 volts or so things change.

Yes stay below 50 volts is good for electrocution but fire may be a problem for 
higher power since current must be higher.

48 volt I think is standard in telecom and some electric fork lifts or similar 
use it.

> 
> 24 volts is quite a practical voltage level for smaller systems.

Have nothing to say against it.

> Do a search for 24 volt inverters and you will find many.   48 volt, not 
> as many.
> 
> I'm thinking hunting cabin, small cottage, larger boat, remote shed, etc.
> 
> Now if you want to do your entire house and have typical house loads it 
> seems like a 120V+ DC bus system would make more sense.

For entire house standard voltage is probably the solution but if there are 
high power loads with a rectifier choosing same or diode voltage drop above 
this might be a good choice.


___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Dual boot for WIN-XP and LinuxCNC

[andy pugh]

On Mon, 27 May 2019 at 06:26, John Dammeyer  wrote:

But after that I can't even run the stock single parallel port version
> without it crashing.  It's like the 0x378 port has now vanished.


Try a simple config with one parallell port at a time.

halrun
loadrt hal_parport cfg="0xd000 out"
exit

And so on, see which ones work and which give errors.

I suspect that the onboard one has been grabbed by lp or some other
process. (especially if the error is "device in use")
lsmod might help elucidate what.

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is designed
for the especial use of mechanical geniuses, daredevils and lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1916

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users