Re: [Emc-users] Firmware for Mesa 5i20+7i39+7i33TA+Opto22

[Chris Kelley]

Peter,

The firmware file is SVTP6_7I39.BIT.

The excerpt from the ini file is:

[HOSTMOT2]
DRIVER=hm2_pci
BOARD=5i20
CONFIG="firmware=hm2/5i20/SVTP6_7I39.BIT num_encoders=3 num_pwmgens=1
num_3pwmgens=2 num_stepgens=1"
[EMC]


Right now, if I comment out all the lines in the hal file that touch any of
the stepgen or pwmgen pins, the axis gui will start but there are no pins
created for the pwmgen or the stepgen. While the correct number of encoders
are created, the third (spindle through the 7i33TA) isn't showing any
movement when the spindle is turned by hand.


>From what I can tell from reading the 5i20/7i39/7i33TA manuals, hal file,
and looking at the wiring:

P2 on the 5i20 goes to the 7i39 and uses the pinout in the 7i39 manual.
This runs the X and Y BLDC servos and uses two of the encoders and the 2
3-phase pwmgens from the config line in the ini.

P3 on the 5i20 goes to the 7i33TA and uses the pinout in the 7i33TA manual.
This is used for the analog signal to the spindle drive and the spindle
encoder and uses the third encoder and the one regular pwmgen from the
config line in the ini. If the 5i20 doesn't have enough firmware space for
the other 3 pwms and encoders on the 7i33, no worries, I wasn't really
planning on using them anyway.

P3 on the 5i20 goes to a OPTO22 board. GPIO pins 48 and 49 are used for
step and direction from the stepgen. In the HAL file, they get set to open
drain and inverted but no other connections are made. Physically those two
pins go to the setp/dir pins on the Gecko drive that runs the Z-axis. The
remaining GPIO pins, 50 -71, are just used for regular field I/O (limit
switches, relays, solenoids, etc.).


-Chris


On Sat, Jan 30, 2016 at 10:04 AM, Peter C. Wallace <p...@mesanet.com> wrote:

> On Fri, 29 Jan 2016, Chris Kelley wrote:
>
> > Date: Fri, 29 Jan 2016 21:18:54 -0600
> > From: Chris Kelley <tensait...@gmail.com>
> > Reply-To: "Enhanced Machine Controller (EMC)"
> > <emc-users@lists.sourceforge.net>
> > To: "Enhanced Machine Controller (EMC)" <emc-users@lists.sourceforge.net
> >
> > Subject: [Emc-users] Firmware for Mesa 5i20+7i39+7i33TA+Opto22
> >
> > Greetings all,
> >
> > I recently "inherited" a little Smithy 622 CNC mill that had already been
> > converted to LinuxCNC.
> >
> > The machine has BLDC servos on the X and Y (run by the 7i39 on P1 of the
> > 5i20), a spindle encoder and analog drive (run from the 7i33TA on P2 of
> the
> > 5i20), and a stepper for the Z-axis (run along with the field I/O from
> the
> > Opto22 board on P3 of the 5i20).
> >
> > Before tonight, everything was working great. So, naturally, I had to
> mess
> > with it.
> >
> > The PC was running 2.5 on Ubuntu 10, so I decided to reload the machine
> > with a clean LinuxCNC 2.7/Debian Wheezy install (from the .iso).
> >
> > After the install, I copied over the (previously) working ini/hal config
> > files (attached). But, now when I try to start up LinuxCNC, I get an
> error
> > that the hm2_5i20.0.stepgen.00.enable pin cannot be found.
> >
> >> From what I can tell, even though the config is calling for 3 encoders,
> 2
> > 3-phase PWMs, 1 regular PWM, and 1 stepgen, only the encoders and 3-phase
> > PWMs are getting created.
> >
> > The only thing I can think of is that the previous owner was using a
> > modified version of the SVTP6_7I39.BIT firmware that allowed for the
> > creation of stepgens and regular pwmgens.
> >
> > Sadly, I did not think to back up the firmware folder before wiping the
> old
> > install.
> >
> > Am I missing something, or do I need some sort of custom firmware file?
> >
> > -Chris
> >
>
> What was the name of the firmware file? (should be in the hal or ini file)
> If I made the bitfile, I will have the PIN_XXX source to remake it (and the
> firmware name will help find the correct one)
> If not, the hal file will have some clues to the pinout that will help
>
> Peter Wallace
> Mesa Electronics
>
>
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>
-

Re: [Emc-users] Firmware for Mesa 5i20+7i39+7i33TA+Opto22

[Peter C. Wallace]

On Fri, 29 Jan 2016, Chris Kelley wrote:

> Date: Fri, 29 Jan 2016 21:18:54 -0600
> From: Chris Kelley <tensait...@gmail.com>
> Reply-To: "Enhanced Machine Controller (EMC)"
> <emc-users@lists.sourceforge.net>
> To: "Enhanced Machine Controller (EMC)" <emc-users@lists.sourceforge.net>
> Subject: [Emc-users] Firmware for Mesa 5i20+7i39+7i33TA+Opto22
> 
> Greetings all,
>
> I recently "inherited" a little Smithy 622 CNC mill that had already been
> converted to LinuxCNC.
>
> The machine has BLDC servos on the X and Y (run by the 7i39 on P1 of the
> 5i20), a spindle encoder and analog drive (run from the 7i33TA on P2 of the
> 5i20), and a stepper for the Z-axis (run along with the field I/O from the
> Opto22 board on P3 of the 5i20).
>
> Before tonight, everything was working great. So, naturally, I had to mess
> with it.
>
> The PC was running 2.5 on Ubuntu 10, so I decided to reload the machine
> with a clean LinuxCNC 2.7/Debian Wheezy install (from the .iso).
>
> After the install, I copied over the (previously) working ini/hal config
> files (attached). But, now when I try to start up LinuxCNC, I get an error
> that the hm2_5i20.0.stepgen.00.enable pin cannot be found.
>
>> From what I can tell, even though the config is calling for 3 encoders, 2
> 3-phase PWMs, 1 regular PWM, and 1 stepgen, only the encoders and 3-phase
> PWMs are getting created.
>
> The only thing I can think of is that the previous owner was using a
> modified version of the SVTP6_7I39.BIT firmware that allowed for the
> creation of stepgens and regular pwmgens.
>
> Sadly, I did not think to back up the firmware folder before wiping the old
> install.
>
> Am I missing something, or do I need some sort of custom firmware file?
>
> -Chris
>

What was the name of the firmware file? (should be in the hal or ini file)
If I made the bitfile, I will have the PIN_XXX source to remake it (and the 
firmware name will help find the correct one)
If not, the hal file will have some clues to the pinout that will help

Peter Wallace
Mesa Electronics

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Firmware for Mesa 5i20+7i39+7i33TA+Opto22

[Gene Heskett]

On Saturday 30 January 2016 01:53:31 Rafael wrote:

> On 01/29/2016 07:18 PM, Chris Kelley wrote:
> > Greetings all,
> >
> > I recently "inherited" a little Smithy 622 CNC mill that had already
> > been converted to LinuxCNC.
> >
> > The machine has BLDC servos on the X and Y (run by the 7i39 on P1 of
> > the 5i20), a spindle encoder and analog drive (run from the 7i33TA
> > on P2 of the 5i20), and a stepper for the Z-axis (run along with the
> > field I/O from the Opto22 board on P3 of the 5i20).
> >
> > Before tonight, everything was working great. So, naturally, I had
> > to mess with it.
>
> We charge double for cases like this.
>
> > The PC was running 2.5 on Ubuntu 10, so I decided to reload the
> > machine with a clean LinuxCNC 2.7/Debian Wheezy install (from the
> > .iso).
> >
> > After the install, I copied over the (previously) working ini/hal
> > config files (attached). But, now when I try to start up LinuxCNC, I
> > get an error that the hm2_5i20.0.stepgen.00.enable pin cannot be
> > found.
> >
> >>From what I can tell, even though the config is calling for 3
> >> encoders, 2
> >
> > 3-phase PWMs, 1 regular PWM, and 1 stepgen, only the encoders and
> > 3-phase PWMs are getting created.
> >
> > The only thing I can think of is that the previous owner was using a
> > modified version of the SVTP6_7I39.BIT firmware that allowed for the
> > creation of stepgens and regular pwmgens.
> >
> > Sadly, I did not think to back up the firmware folder before wiping
> > the old install.
>
> It's good to have a spare drive for fresh OS install when you are not
> sure about the outcome or when there is only one partition.
>
> > Am I missing something, or do I need some sort of custom firmware
> > file?
> >
> > -Chris
>
> While I cannot answer your question about the firmware issues, it's
> worthwhile to mention that all Linux installations benefit from
> partitioned disk drive so that you do not wipe out all files with
> reinstalling the OS. I hope this helps others in the future.
>
> For future installations I recommend to create at least 4 partitions:
> /  for the OS
> /var   for logs, package cache etc.
> swap
> /home  user home directories obviously.
> /tmp   optional.
>
> /home is the last partition for "the rest of the disk space.
>
> Before you upgrade the OS it's always good to save critical config
> files: mkdir /home/backup
> tar cvfp /home/backup/etc.tar /etc
> tar /home/backup/usr.local.bin.tar /usr/local/bin
> and so on.
>
> That way you preserve any config files in case you need to restore
> them later.
>
> If you run into disk space issues at some point later, you simply move
> a directory to /home and make a link. Typical example is:
>
> mkdir /home/var.cache
> (cd /var/cache; tar cfp - .) | (cd /home/var.cache; tar xvf -)
>
> cd /var
> rm -rf /var/cache; ln -s /home/var.cache cache
>
> cp -rp /lib/firmware /home   <- this would save /lib/firmware/hm2
> firmware among others.
>
> When partioning disk drive during new installation you only need to
> make sure that last partition is preserved and mounted under /home
>
> Disk drives are so low cost thee days that it's worthwhile to install
> OS on a new one and use the old one for backups.

+1000 at least on the new drive for a new install.  With terabyte plus 
drives now under an 80 dollar bill from the online people like 
tigerdirect or newegg one doesn't have very much of an excuse for the 
cost compared to the lost.

As for backups, I've been using amanda since the late '90's and my first 
linux install. Recoveries are a piece of cake, and almost disk to disk 
copy rates timewise if you spin a 3rd big, terabyte or more, drive & 
have amanda build virtual tapes as opposed to using a considerably more 
expensive tape drive. The recovery speed comes from the tape drive being 
a sequential device that has to be read from the start to find what you 
want, but the disk drive is random access, hundreds to thousands of 
times faster.

So far, smartctl has warned me of impending drive failures with enough 
advance warning that I have yet to lose a byte of data that wasn't 
overwritten by the schedule you have amanda setup to run it.

Here, it grabs the important stuff and saves it in about an hour, 
starting a bit after 1am every morning.  At any one time, I can back up 
25 to 30 days and get it back.

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 

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140

Re: [Emc-users] Firmware for Mesa 5i20+7i39+7i33TA+Opto22

[Rafael]

On 01/29/2016 07:18 PM, Chris Kelley wrote:
> Greetings all,
>
> I recently "inherited" a little Smithy 622 CNC mill that had already been
> converted to LinuxCNC.
>
> The machine has BLDC servos on the X and Y (run by the 7i39 on P1 of the
> 5i20), a spindle encoder and analog drive (run from the 7i33TA on P2 of the
> 5i20), and a stepper for the Z-axis (run along with the field I/O from the
> Opto22 board on P3 of the 5i20).
>
> Before tonight, everything was working great. So, naturally, I had to mess
> with it.

We charge double for cases like this.

>
> The PC was running 2.5 on Ubuntu 10, so I decided to reload the machine
> with a clean LinuxCNC 2.7/Debian Wheezy install (from the .iso).
>
> After the install, I copied over the (previously) working ini/hal config
> files (attached). But, now when I try to start up LinuxCNC, I get an error
> that the hm2_5i20.0.stepgen.00.enable pin cannot be found.
>
>>From what I can tell, even though the config is calling for 3 encoders, 2
> 3-phase PWMs, 1 regular PWM, and 1 stepgen, only the encoders and 3-phase
> PWMs are getting created.
>
> The only thing I can think of is that the previous owner was using a
> modified version of the SVTP6_7I39.BIT firmware that allowed for the
> creation of stepgens and regular pwmgens.
>
> Sadly, I did not think to back up the firmware folder before wiping the old
> install.

It's good to have a spare drive for fresh OS install when you are not 
sure about the outcome or when there is only one partition.

>
> Am I missing something, or do I need some sort of custom firmware file?
>
> -Chris

While I cannot answer your question about the firmware issues, it's 
worthwhile to mention that all Linux installations benefit from 
partitioned disk drive so that you do not wipe out all files with 
reinstalling the OS. I hope this helps others in the future.

For future installations I recommend to create at least 4 partitions:
/  for the OS
/var   for logs, package cache etc.
swap
/home  user home directories obviously.
/tmp   optional.

/home is the last partition for "the rest of the disk space.

Before you upgrade the OS it's always good to save critical config files:
mkdir /home/backup
tar cvfp /home/backup/etc.tar /etc
tar /home/backup/usr.local.bin.tar /usr/local/bin
and so on.

That way you preserve any config files in case you need to restore them 
later.

If you run into disk space issues at some point later, you simply move a 
directory to /home and make a link. Typical example is:

mkdir /home/var.cache
(cd /var/cache; tar cfp - .) | (cd /home/var.cache; tar xvf -)

cd /var
rm -rf /var/cache; ln -s /home/var.cache cache

cp -rp /lib/firmware /home   <- this would save /lib/firmware/hm2 
firmware among others.

When partioning disk drive during new installation you only need to make 
sure that last partition is preserved and mounted under /home

Disk drives are so low cost thee days that it's worthwhile to install OS 
on a new one and use the old one for backups.

-- 
Rafael

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

[Emc-users] Firmware for Mesa 5i20+7i39+7i33TA+Opto22

[Chris Kelley]

Greetings all,

I recently "inherited" a little Smithy 622 CNC mill that had already been
converted to LinuxCNC.

The machine has BLDC servos on the X and Y (run by the 7i39 on P1 of the
5i20), a spindle encoder and analog drive (run from the 7i33TA on P2 of the
5i20), and a stepper for the Z-axis (run along with the field I/O from the
Opto22 board on P3 of the 5i20).

Before tonight, everything was working great. So, naturally, I had to mess
with it.

The PC was running 2.5 on Ubuntu 10, so I decided to reload the machine
with a clean LinuxCNC 2.7/Debian Wheezy install (from the .iso).

After the install, I copied over the (previously) working ini/hal config
files (attached). But, now when I try to start up LinuxCNC, I get an error
that the hm2_5i20.0.stepgen.00.enable pin cannot be found.

>From what I can tell, even though the config is calling for 3 encoders, 2
3-phase PWMs, 1 regular PWM, and 1 stepgen, only the encoders and 3-phase
PWMs are getting created.

The only thing I can think of is that the previous owner was using a
modified version of the SVTP6_7I39.BIT firmware that allowed for the
creation of stepgens and regular pwmgens.

Sadly, I did not think to back up the firmware folder before wiping the old
install.

Am I missing something, or do I need some sort of custom firmware file?

-Chris


5i20.ini
Description: application/wine-extension-ini


hm2-servo-sine.hal
Description: Binary data
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Firmware for Mesa 5i20+7i39+7i33TA+Opto22

[Chris Kelley]

Yeah, our +/- 9 other machines all use either the regular parallel port or
5i25+7i76/7i77. So I'm just not used to working with setups that modify
more than just the files in their configuration folders.

On Sat, Jan 30, 2016 at 12:53 AM, Rafael  wrote:

>
>
> On 01/29/2016 07:18 PM, Chris Kelley wrote:
> > Greetings all,
> >
> > I recently "inherited" a little Smithy 622 CNC mill that had already been
> > converted to LinuxCNC.
> >
> > The machine has BLDC servos on the X and Y (run by the 7i39 on P1 of the
> > 5i20), a spindle encoder and analog drive (run from the 7i33TA on P2 of
> the
> > 5i20), and a stepper for the Z-axis (run along with the field I/O from
> the
> > Opto22 board on P3 of the 5i20).
> >
> > Before tonight, everything was working great. So, naturally, I had to
> mess
> > with it.
>
> We charge double for cases like this.
>
> >
> > The PC was running 2.5 on Ubuntu 10, so I decided to reload the machine
> > with a clean LinuxCNC 2.7/Debian Wheezy install (from the .iso).
> >
> > After the install, I copied over the (previously) working ini/hal config
> > files (attached). But, now when I try to start up LinuxCNC, I get an
> error
> > that the hm2_5i20.0.stepgen.00.enable pin cannot be found.
> >
> >>From what I can tell, even though the config is calling for 3 encoders, 2
> > 3-phase PWMs, 1 regular PWM, and 1 stepgen, only the encoders and 3-phase
> > PWMs are getting created.
> >
> > The only thing I can think of is that the previous owner was using a
> > modified version of the SVTP6_7I39.BIT firmware that allowed for the
> > creation of stepgens and regular pwmgens.
> >
> > Sadly, I did not think to back up the firmware folder before wiping the
> old
> > install.
>
> It's good to have a spare drive for fresh OS install when you are not
> sure about the outcome or when there is only one partition.
>
> >
> > Am I missing something, or do I need some sort of custom firmware file?
> >
> > -Chris
>
> While I cannot answer your question about the firmware issues, it's
> worthwhile to mention that all Linux installations benefit from
> partitioned disk drive so that you do not wipe out all files with
> reinstalling the OS. I hope this helps others in the future.
>
> For future installations I recommend to create at least 4 partitions:
> /  for the OS
> /var   for logs, package cache etc.
> swap
> /home  user home directories obviously.
> /tmp   optional.
>
> /home is the last partition for "the rest of the disk space.
>
> Before you upgrade the OS it's always good to save critical config files:
> mkdir /home/backup
> tar cvfp /home/backup/etc.tar /etc
> tar /home/backup/usr.local.bin.tar /usr/local/bin
> and so on.
>
> That way you preserve any config files in case you need to restore them
> later.
>
> If you run into disk space issues at some point later, you simply move a
> directory to /home and make a link. Typical example is:
>
> mkdir /home/var.cache
> (cd /var/cache; tar cfp - .) | (cd /home/var.cache; tar xvf -)
>
> cd /var
> rm -rf /var/cache; ln -s /home/var.cache cache
>
> cp -rp /lib/firmware /home   <- this would save /lib/firmware/hm2
> firmware among others.
>
> When partioning disk drive during new installation you only need to make
> sure that last partition is preserved and mounted under /home
>
> Disk drives are so low cost thee days that it's worthwhile to install OS
> on a new one and use the old one for backups.
>
> --
> Rafael
>
>
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users