Yet Another LasaurApp Update, v12.08e

[Stefan Hechenberger]

We are moving quickly. Here is another release candidate. Please test! I
feel pretty confident about this one because we had the time to run it
quite extensively. I finally got USB working in VirtualBox and was able
to test on Windows and Linux in addition to OSX. We also tested on the
Beaglebone. All platforms ran the gantry flawlessly so far.

Let me know how it runs on your systems.

OSX:
https://github.com/downloads/stefanix/LasaurApp/LasaurApp-v12.08e-osx.zip

Windows:
https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08e-win.zip

Linux:
https://github.com/stefanix/LasaurApp/
(binaries and sources are in sync again)


CHANGES are as follows:
- serial communication completely rewritten
- more robust flow control
- forward error correction and error reporting
- faster speeds, now runs at 57600 bps
- firmware bugfixes in serial module dealing with concurrency issues
- workaround for pyserial bugs
- additons to the protocol, see:
http://labs.nortd.com/lasersaur/manual/gcode
- better optimizations in gcode generation
- bugfixes in com port auto-configuration on windows and linux

I can talk more about the new serial communication code. The details are
actually quite interesting. Since the serial interrupts fire so
frequently the slightest concurrency flaws can cause quite the scene.

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

[Stefan Hechenberger]

... also make sure to upload the new firmware to the controller with:
http://127.0.0.1:4444/flash_firmware

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

[Jonathan Buford]

Hi Stefan,

The serial communication problem is one I ran into with RepRaps before as well. It would be cool if your work was able to also improve the robustness for similar projects. One thing we found when having trouble with the communication is that it usually was worst with specific laptops that likely have poor grounding on the USB. Desktop machines tended to be consistently better.

Thanks,

Jon

[Dan Cotrupe]

Just been running a few files quick. It's running simple files very cleanly and efficiently. If I run a complicated file it gives me "limit hit" errors while the cut is nowhere near the edges. Furthermore, if I hit the E-stop and move it manually the error continues flashing.

Also, if I open the door the 'open door' error comes on and does not stop when i close it. I can still use direct control to move the gantry around even while the door error is going off (and the door is closed) and hitting the e-stop or turning off the chiller also sends no errors (besides the already running 'door is open' error... which is still closed).

I suspect the limit hit error might be a loose wire or the like in my machine because that was happening when we ran our own front-end as well. 

To end on a positive note, when not erroring it runs all lines of code correctly and quite efficiently.

more to come,

-Dan

[Stefan Hechenberger]

The limit hit issue is typically caused by lack of proper shielding.
Make sure you double check all your sensor wire shields. See the wiring
diagram for details. Also note that we updated this quite recently in
regard to vrel/rel, H1,H3.

Some of what you observe is proper behavior. The gantry should keep
running when the door is open or the chiller is off. See the following
for details, section Safety System:
http://labs.nortd.com/lasersaur/manual/operation Let me know if it
differs from this.

For debugging sensors you can connect to the controller directly (e.g.
with the Arduino Serial Monitor, newline, 57600baud) and send a '?' it
will then report the state of all the sensors. For example if you get
back a 'D' it means the door sensor signals 'open'. For details, section
Return Format: http://labs.nortd.com/lasersaur/manual/gcode

Let me know if the sensors function correctly when you query them with '?'.

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

> https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08e-osx.zip
> <https://github.com/downloads/stefanix/LasaurApp/LasaurApp-v12.08e-osx.zip>
>
> Windows:
> https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08e-win.zip
> <https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08e-win.zip>
>
> Linux:
> https://github.com/stefanix/__LasaurApp/

> <https://github.com/stefanix/LasaurApp/>
> (binaries and sources are in sync again)
>
>
> CHANGES are as follows:
> - serial communication completely rewritten
> - more robust flow control
> - forward error correction and error reporting
> - faster speeds, now runs at 57600 bps
> - firmware bugfixes in serial module dealing with concurrency issues
> - workaround for pyserial bugs
> - additons to the protocol, see:

> http://labs.nortd.com/__lasersaur/manual/gcode

> <http://labs.nortd.com/lasersaur/manual/gcode>
> - better optimizations in gcode generation
> - bugfixes in com port auto-configuration on windows and linux
>
> I can talk more about the new serial communication code. The details
> are actually quite interesting. Since the serial interrupts fire so
> frequently the slightest concurrency flaws can cause quite the scene.
>
> --
> Stefan Hechenberger

> studio: Nortd Labs - labs.nortd.com <http://labs.nortd.com>
> resident: F.A.T. Lab - fffff.at <http://fffff.at>
> project: Lasersaur - labs.nortd.com/lasersaur
> <http://labs.nortd.com/lasersaur>
>
>

[Gabriel Helms]

I just downloaded the update and flashed as requested. First thing I noticed was that the door open alarm was going off and couldn't get it to turn off. Second thing I noticed was that the gantry would only move at medium speed under direct control. Third thing I noticed was that the power off alert continually flashed. Final thing was that under direct control, I couldn't make the gantry moved to the far x or y limits. On further inspection, telling the gantry to move to the center of the direct control box made the gantry move to the center of the top left quadrant of the table.

Gabriel

Sent from my iPhone

[Stefan Hechenberger]

Thanks for testing, this is very helpful. Moving along ...

OSX:
https://github.com/downloads/stefanix/LasaurApp/LasaurApp-v12.08f-osx.zip

Windows:
https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08f-win.zip


Gabriel, I was able to reproduce the problem with the sticky
warnings/error messages in the gui. It was strictly a problem in the
python code and it's fixed in the above update.

I was not able to reproduce the medium speed thing and the quadrant
issue. They do sound related. Are you using different stepper drivers or
different gearing?

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

[Trevor Ruggiero]

I seem to be having the same problem with the "Power off" warning. After connecting everything works for about 20 seconds and then stops and the "Power off" warning starts flashing. If I run the homing cycle it seems to reset and I get another 20 seconds before the "Power Off" starts flashing again. This was all conducted in 12.08e, I tried 12.08f and had the exact same issue, except now going home does not reset, I have to reconnect. How does the system sense power on? It seems strange that 12.06 was running well without any power off sensor issues. Also how do I flash 12.06h back onto the arduino? I can't seem to get there through the old links. Thanks and let me know if there is any testing you would like me to try out with this power off issue. 

Regards,

Trevor Ruggiero

Mechanical Engineer

Fikst - Product Development
45 Industrial Pkwy, 2nd Flr
Woburn, MA 01801

Phone: (781) 491-0845

Email: trug...@fikst.com
Web: www.fikst.com

[Gabriel Helms]

I'm using everything in the 12.08 BOM but I had to use the Lin steppers.

Sent from my iPhone

[Gabriel Helms]

Speeds were fine on the earlier app.

Sent from my iPhone

[Stefan Hechenberger]

Hi Trevor, I just ran some more test but wasn't able to reproduce any of
your reported issues. My guess is it's probably a shielding issue with
the power sensor cable. Initially the power sensor cable was not shown
as shielded in the schematic but it should be. You might want to get in
sync with the latest schematic and double-check all your shielding
leads: http://labs.nortd.com/lasersaur/manual/wiring

If you have specific questions regarding the power sensing let me know.
FYI, it's the wire that goes from rel/vrel to the relays.

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

On 8/28/12 5:16 PM, Trevor Ruggiero wrote:
> I seem to be having the same problem with the "Power off" warning. After
> connecting everything works for about 20 seconds and then stops and the
> "Power off" warning starts flashing. If I run the homing cycle it seems
> to reset and I get another 20 seconds before the "Power Off" starts
> flashing again. This was all conducted in 12.08e, I tried 12.08f and had
> the exact same issue, except now going home does not reset, I have to
> reconnect. How does the system sense power on? It seems strange that
> 12.06 was running well without any power off sensor issues. Also how do
> I flash 12.06h back onto the arduino? I can't seem to get there through
> the old links. Thanks and let me know if there is any testing you would
> like me to try out with this power off issue.
>
> Regards,
>
> Trevor Ruggiero
> Mechanical Engineer

> Fikst - Product Development
> 45 Industrial Pkwy, 2nd Flr
> Woburn, MA 01801
>
> Phone: (781) 491-0845

> Email: trug...@fikst.com <mailto:trug...@fikst.com>
> Web: www.fikst.com <http://www.fikst.com>

>
>
>
>
> On Tue, Aug 28, 2012 at 10:30 AM, Stefan Hechenberger <ste...@nortd.com
> <mailto:ste...@nortd.com>> wrote:
>
>
>
> Thanks for testing, this is very helpful. Moving along ...
>
> OSX:

> https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08f-osx.zip
> <https://github.com/downloads/stefanix/LasaurApp/LasaurApp-v12.08f-osx.zip>
>
> Windows:
> https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08f-win.zip

> <https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08f-win.zip>
>
>
> Gabriel, I was able to reproduce the problem with the sticky
> warnings/error messages in the gui. It was strictly a problem in the
> python code and it's fixed in the above update.
>
> I was not able to reproduce the medium speed thing and the quadrant
> issue. They do sound related. Are you using different stepper
> drivers or different gearing?
>
>
>
> --
> Stefan Hechenberger

> studio: Nortd Labs - labs.nortd.com <http://labs.nortd.com>
> resident: F.A.T. Lab - fffff.at <http://fffff.at>
> project: Lasersaur - labs.nortd.com/lasersaur
> <http://labs.nortd.com/lasersaur>
>

> On 8/27/12 10:24 PM, Gabriel Helms wrote:
>
> I just downloaded the update and flashed as requested. First
> thing I noticed was that the door open alarm was going off and
> couldn't get it to turn off. Second thing I noticed was that the
> gantry would only move at medium speed under direct control.
> Third thing I noticed was that the power off alert continually
> flashed. Final thing was that under direct control, I couldn't
> make the gantry moved to the far x or y limits. On further
> inspection, telling the gantry to move to the center of the
> direct control box made the gantry move to the center of the top
> left quadrant of the table.
>
> Gabriel
>
> Sent from my iPhone
>
> On Aug 27, 2012, at 2:49 AM, Stefan Hechenberger

> <ste...@nortd.com <mailto:ste...@nortd.com>> wrote:
>
>
> The limit hit issue is typically caused by lack of proper
> shielding. Make sure you double check all your sensor wire
> shields. See the wiring diagram for details. Also note that
> we updated this quite recently in regard to vrel/rel, H1,H3.
>
> Some of what you observe is proper behavior. The gantry
> should keep running when the door is open or the chiller is
> off. See the following for details, section Safety System:

> http://labs.nortd.com/__lasersaur/manual/operation

> <http://labs.nortd.com/lasersaur/manual/operation> Let me
> know if it differs from this.
>
> For debugging sensors you can connect to the controller
> directly (e.g. with the Arduino Serial Monitor, newline,
> 57600baud) and send a '?' it will then report the state of
> all the sensors. For example if you get back a 'D' it means
> the door sensor signals 'open'. For details, section Return

> Format: http://labs.nortd.com/__lasersaur/manual/gcode

> <http://labs.nortd.com/lasersaur/manual/gcode>
>
> Let me know if the sensors function correctly when you query
> them with '?'.
>
>
> --
> Stefan Hechenberger

> studio: Nortd Labs - labs.nortd.com <http://labs.nortd.com>
> resident: F.A.T. Lab - fffff.at <http://fffff.at>
> project: Lasersaur - labs.nortd.com/lasersaur
> <http://labs.nortd.com/lasersaur>
>

> <mailto:ste...@nortd.com <mailto:ste...@nortd.com>>> wrote:
>
>
> We are moving quickly. Here is another release
> candidate. Please
> test! I feel pretty confident about this one
> because we had the time
> to run it quite extensively. I finally got USB
> working in VirtualBox
> and was able to test on Windows and Linux in
> addition to OSX. We
> also tested on the Beaglebone. All platforms ran
> the gantry
> flawlessly so far.
>
> Let me know how it runs on your systems.
>
> OSX:

> https://github.com/downloads/____stefanix/LasaurApp/LasaurApp-____v12.08e-osx.zip
> <https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08e-osx.zip>

>
> <https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08e-osx.zip
> <https://github.com/downloads/stefanix/LasaurApp/LasaurApp-v12.08e-osx.zip>>
>
> Windows:

> https://github.com/downloads/____stefanix/LasaurApp/lasaurapp-____v12.08e-win.zip
> <https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08e-win.zip>

>
> <https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08e-win.zip
> <https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08e-win.zip>>
>
> Linux:

> https://github.com/stefanix/____LasaurApp/
> <https://github.com/stefanix/__LasaurApp/>

> <https://github.com/stefanix/__LasaurApp/
> <https://github.com/stefanix/LasaurApp/>>
> (binaries and sources are in sync again)
>
>
> CHANGES are as follows:
> - serial communication completely rewritten
> - more robust flow control
> - forward error correction and error reporting
> - faster speeds, now runs at 57600 bps
> - firmware bugfixes in serial module dealing
> with concurrency issues
> - workaround for pyserial bugs
> - additons to the protocol, see:

> http://labs.nortd.com/____lasersaur/manual/gcode
> <http://labs.nortd.com/__lasersaur/manual/gcode>

> <http://labs.nortd.com/__lasersaur/manual/gcode
> <http://labs.nortd.com/lasersaur/manual/gcode>>
> - better optimizations in gcode generation
> - bugfixes in com port auto-configuration on
> windows and linux
>
> I can talk more about the new serial communication
> code. The details
> are actually quite interesting. Since the serial
> interrupts fire so
> frequently the slightest concurrency flaws can
> cause quite the scene.
>
> --
> Stefan Hechenberger
> studio: Nortd Labs - labs.nortd.com

> <http://labs.nortd.com> <http://labs.nortd.com>

> resident: F.A.T. Lab - fffff.at <http://fffff.at>
> <http://fffff.at>
> project: Lasersaur - labs.nortd.com/lasersaur
> <http://labs.nortd.com/lasersaur>

> <http://labs.nortd.com/__lasersaur
> <http://labs.nortd.com/lasersaur>>
>
>
>
>

[Steve Baker]

I wonder if anyone has given thought to characterizing the noise that gets
into this kind of low-low-frequency wiring. Maybe it would be possible to
add software to reject brief changes in signal on those kinds of wires.
Probably not a replacement for good shielding - but it would be nice to be
tolerant of that kind of thing on signals where instantaneous response to
change is not critical - but a brief spike shouldn't kill the machine.
Things like the power and door sensors and so forth could probably
tolerate a millisecond of delay needed to filter and clean up the signal.

-- Steve

-- Steve

[Stefan Hechenberger]

In principal a good idea, we can do some digital filtering if it's a
real problem for properly shielded systems. At this point I am not sure
it's necessary. All the reported problems so far could be solved by
assuring the shielding is in place.

The situation I would like to avoid is that digital filtering obscures
problems with faulty shielding.

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

[Steve Baker]

I suppose an alternative to digital filtering would be for the software to
measure how much unreasonably rapid fluctuation there is on these
low-frequency lines and report the quality back as an error/warning state.

At least then you'd get: "WARNING: The shielding on your door-open wire is
probably bad"...rather than just having the machine stop mysteriously
mid-cut. Since we've had quite a few people with this (and related)
problems recently, and they are tough to diagnose, it would be worth
making the software do that diagnostic for you.

-- Steve

[Stefan Hechenberger]

My first thought: that would be awesome.

If I have some time I'll give it a try. I fear it might turn out very
difficult to do. We have build a good number of Lasersaurs now and the
noise interference (whenever we forgot the shielding) has been wildly
different from almost not noticeable to all the time.

It's actually not that hard to troubleshoot since we have the warning
and error messages in the GUI now. Basically whenever you get an
error/warning message that is obviously not the case it's almost
certainly a shielding issue.

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

[Trevor Ruggiero]

Stefan, Thanks for looking into this for me. We are up to date with the latest wiring diagram, using all shielded cables. The problem seems to occur when both motors are moving full speed. My only thought is that the interference is occurring either at the lasershield or at the relay where the shielding is cut away. For now I just connected vrel and rel together and that solved the problem. Other than that the new software is running really well. 

Regards,

Trevor Ruggiero

Mechanical Engineer

Fikst - Product Development
45 Industrial Pkwy, 2nd Flr
Woburn, MA 01801

Phone: (781) 491-0845

Email: trug...@fikst.com
Web: www.fikst.com

[rdklein]

Can you try something similar as this device:

http://katalog.we-online.de/kataloge/eisos/index.php?language=xx&pf=STAR-TEC

(used for emv shielding to supress HF noise. Place it close to the circuit board. This might get rid of noise which comes in at the start of the cables or due to magnetic interference. There are lot of similar ferrits like this - but would be interessting
 if this helps. I had to use one of those things to get nosie away to pass the EMV/CE/FCC checkup for on of my projects. Without there was lot of noise on the cables (shielding was not helping).
regards
rolf-dieter klein

[Stefan Hechenberger]

Good to hear the v12.08f is running smooth.

Given that the false sensor inputs disappear when you jumper rel to vrel
is a pretty clear indicator that the noise comes from this cable.

What do you mean with, the relay shielding is cut away? The cable from
the shield to the relay should be shielded all the way. We changed this
quite recently in the diagram and also where the shield leads are
connected to the board.

Do you have this cable running close to one of the stepper cables or
laser PSU? Really strange you are getting spikes on it.

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

On 8/30/12 5:33 PM, Trevor Ruggiero wrote:
> Stefan, Thanks for looking into this for me. We are up to date with the
> latest wiring diagram, using all shielded cables. The problem seems to
> occur when both motors are moving full speed. My only thought is that
> the interference is occurring either at the lasershield or at the relay
> where the shielding is cut away. For now I just connected vrel and rel
> together and that solved the problem. Other than that the new software
> is running really well.
>
> Regards,
>
> Trevor Ruggiero
> Mechanical Engineer

> Fikst - Product Development
> 45 Industrial Pkwy, 2nd Flr
> Woburn, MA 01801
>
> Phone: (781) 491-0845
> Email: trug...@fikst.com <mailto:trug...@fikst.com>
> Web: www.fikst.com <http://www.fikst.com>
>
>
>
>

> On Tue, Aug 28, 2012 at 7:09 PM, Stefan Hechenberger <ste...@nortd.com
> <mailto:ste...@nortd.com>> wrote:
>
>
> Hi Trevor, I just ran some more test but wasn't able to reproduce
> any of your reported issues. My guess is it's probably a shielding
> issue with the power sensor cable. Initially the power sensor cable
> was not shown as shielded in the schematic but it should be. You
> might want to get in sync with the latest schematic and double-check
> all your shielding leads:

> http://labs.nortd.com/__lasersaur/manual/wiring

> <http://labs.nortd.com/lasersaur/manual/wiring>
>
> If you have specific questions regarding the power sensing let me
> know. FYI, it's the wire that goes from rel/vrel to the relays.
>
>
>
> --
> Stefan Hechenberger

> studio: Nortd Labs - labs.nortd.com <http://labs.nortd.com>
> resident: F.A.T. Lab - fffff.at <http://fffff.at>
> project: Lasersaur - labs.nortd.com/lasersaur
> <http://labs.nortd.com/lasersaur>
>

> Phone: (781) 491-0845 <tel:%28781%29%20491-0845>
> Email: trug...@fikst.com <mailto:trug...@fikst.com>
> <mailto:trug...@fikst.com <mailto:trug...@fikst.com>>
> Web: www.fikst.com <http://www.fikst.com> <http://www.fikst.com>

>
>
>
>
>
> On Tue, Aug 28, 2012 at 10:30 AM, Stefan Hechenberger
> <ste...@nortd.com <mailto:ste...@nortd.com>

> <mailto:ste...@nortd.com <mailto:ste...@nortd.com>>> wrote:
>
>
>
> Thanks for testing, this is very helpful. Moving along ...
>
> OSX:

> https://github.com/downloads/____stefanix/LasaurApp/LasaurApp-____v12.08f-osx.zip
> <https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08f-osx.zip>

>
> <https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08f-osx.zip
> <https://github.com/downloads/stefanix/LasaurApp/LasaurApp-v12.08f-osx.zip>>
>
> Windows:

> https://github.com/downloads/____stefanix/LasaurApp/lasaurapp-____v12.08f-win.zip
> <https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08f-win.zip>

>
>
> <https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08f-win.zip
> <https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08f-win.zip>>
>
>
> Gabriel, I was able to reproduce the problem with the sticky
> warnings/error messages in the gui. It was strictly a
> problem in the
> python code and it's fixed in the above update.
>
> I was not able to reproduce the medium speed thing and the
> quadrant
> issue. They do sound related. Are you using different stepper
> drivers or different gearing?
>
>
>
> --
> Stefan Hechenberger
> studio: Nortd Labs - labs.nortd.com <http://labs.nortd.com>

> <http://labs.nortd.com>
> resident: F.A.T. Lab - fffff.at <http://fffff.at>
> <http://fffff.at>
> project: Lasersaur - labs.nortd.com/lasersaur
> <http://labs.nortd.com/lasersaur>
> <http://labs.nortd.com/__lasersaur
> <http://labs.nortd.com/lasersaur>>
>

> On 8/27/12 10:24 PM, Gabriel Helms wrote:
>
> I just downloaded the update and flashed as requested.
> First
> thing I noticed was that the door open alarm was going
> off and
> couldn't get it to turn off. Second thing I noticed was
> that the
> gantry would only move at medium speed under direct
> control.
> Third thing I noticed was that the power off alert
> continually
> flashed. Final thing was that under direct control, I
> couldn't
> make the gantry moved to the far x or y limits. On further
> inspection, telling the gantry to move to the center of the
> direct control box made the gantry move to the center
> of the top
> left quadrant of the table.
>
> Gabriel
>
> Sent from my iPhone
>
> On Aug 27, 2012, at 2:49 AM, Stefan Hechenberger
> <ste...@nortd.com <mailto:ste...@nortd.com>

> <mailto:ste...@nortd.com <mailto:ste...@nortd.com>>> wrote:
>
>
> The limit hit issue is typically caused by lack of
> proper
> shielding. Make sure you double check all your
> sensor wire
> shields. See the wiring diagram for details. Also
> note that
> we updated this quite recently in regard to
> vrel/rel, H1,H3.
>
> Some of what you observe is proper behavior. The gantry
> should keep running when the door is open or the
> chiller is
> off. See the following for details, section Safety
> System:

> http://labs.nortd.com/____lasersaur/manual/operation
> <http://labs.nortd.com/__lasersaur/manual/operation>

>
> <http://labs.nortd.com/__lasersaur/manual/operation
> <http://labs.nortd.com/lasersaur/manual/operation>> Let me
> know if it differs from this.
>
> For debugging sensors you can connect to the controller
> directly (e.g. with the Arduino Serial Monitor,
> newline,
> 57600baud) and send a '?' it will then report the
> state of
> all the sensors. For example if you get back a 'D'
> it means
> the door sensor signals 'open'. For details,
> section Return
> Format:

> http://labs.nortd.com/____lasersaur/manual/gcode
> <http://labs.nortd.com/__lasersaur/manual/gcode>
>
> <http://labs.nortd.com/__lasersaur/manual/gcode
> <http://labs.nortd.com/lasersaur/manual/gcode>>
>

> Let me know if the sensors function correctly when
> you query
> them with '?'.
>
>
> --
> Stefan Hechenberger
> studio: Nortd Labs - labs.nortd.com

> <http://labs.nortd.com> <http://labs.nortd.com>
> resident: F.A.T. Lab - fffff.at <http://fffff.at>
> <http://fffff.at>
> project: Lasersaur - labs.nortd.com/lasersaur
> <http://labs.nortd.com/lasersaur>
> <http://labs.nortd.com/__lasersaur
> <http://labs.nortd.com/lasersaur>>
>

> https://github.com/downloads/______stefanix/LasaurApp/__LasaurApp-____v12.08e-osx.zip
> <https://github.com/downloads/____stefanix/LasaurApp/LasaurApp-____v12.08e-osx.zip>

>
> <https://github.com/downloads/____stefanix/LasaurApp/__LasaurApp-__v12.08e-osx.zip
> <https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08e-osx.zip>>
>
>
>
> <https://github.com/downloads/____stefanix/LasaurApp/__LasaurApp-__v12.08e-osx.zip
> <https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08e-osx.zip>
>
> <https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08e-osx.zip
> <https://github.com/downloads/stefanix/LasaurApp/LasaurApp-v12.08e-osx.zip>>>
>
> Windows:

> https://github.com/downloads/______stefanix/LasaurApp/__lasaurapp-____v12.08e-win.zip
> <https://github.com/downloads/____stefanix/LasaurApp/lasaurapp-____v12.08e-win.zip>
>
> <https://github.com/downloads/____stefanix/LasaurApp/__lasaurapp-__v12.08e-win.zip
> <https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08e-win.zip>>
>
>
>
> <https://github.com/downloads/____stefanix/LasaurApp/__lasaurapp-__v12.08e-win.zip

> <https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08e-win.zip>
>
> <https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08e-win.zip
> <https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08e-win.zip>>>
>
> Linux:

> https://github.com/stefanix/______LasaurApp/
> <https://github.com/stefanix/____LasaurApp/>

> <https://github.com/stefanix/____LasaurApp/
> <https://github.com/stefanix/__LasaurApp/>>
>
>
> <https://github.com/stefanix/____LasaurApp/
> <https://github.com/stefanix/__LasaurApp/>
> <https://github.com/stefanix/__LasaurApp/
> <https://github.com/stefanix/LasaurApp/>>>
> (binaries and sources are in sync again)
>
>
> CHANGES are as follows:
> - serial communication completely rewritten
> - more robust flow control
> - forward error correction and error
> reporting
> - faster speeds, now runs at 57600 bps
> - firmware bugfixes in serial module
> dealing
> with concurrency issues
> - workaround for pyserial bugs
> - additons to the protocol, see:

> http://labs.nortd.com/______lasersaur/manual/gcode
> <http://labs.nortd.com/____lasersaur/manual/gcode>

> <http://labs.nortd.com/____lasersaur
> <http://labs.nortd.com/__lasersaur>
> <http://labs.nortd.com/__lasersaur
> <http://labs.nortd.com/lasersaur>>>
>
>
>
>
>

[jet townsend]

I just installed 12.08f for OSX and flashed to 12.08f.   Is there a tree I can branch to get the code for recent changes or is it really the same as the 12.08f in the main tree?

All my cables are shielded and I have rel/vrel going to the relay, they are active.   The water cooler is running but the laser is powered down for safety but I don't know how the daughterboard would know about this.

That being said, two real problems:

1)   Still having the "Power is off" error, including *after* a script has finished.   It also happens with Direct Control, the  motion goes about half-way, then I get the "Power is off" error.  Everything stops, but if I do a "Home" command it moves the head to home.  I don't see any messages in the driver window that look like error messages, only this:

..localhost - - [06/Sep/2012 18:04:33] "GET /status HTTP/1.1" 200 335
..localhost - - [06/Sep/2012 18:04:35] "POST /gcode HTTP/1.1" 200 19
Adding to queue 21 lines
......................................localhost - - [06/Sep/2012 18:04:37] "GET /queue_pct_done HTTP/1.1" 200 0
localhost - - [06/Sep/2012 18:04:38] "GET /status HTTP/1.1" 200 335


2) I can't get M7 or M8 to trigger a pin.  There are no error messages but the power board I have attached never goes off.  If I attach it to D2 on an Arduino board it works just fine.  I see -1.2v on A4 and -3.7v on A5 constantly, the value doesn't change during M7, M8, or M9.  (3.3v puts out 0.4v, which also isn't right).

[jet townsend]

Hm, there's a problem that I thought was speed related but happens on all speeds.  The head gets to roughly X100 Y100 then everything stops and I get a power Off message.  If I'm on high speed it just happens more quickly, but it looks to be in the same place.

At the same time, all of the switches are clear but the steppers are almost too hot to touch.

On Sun, Aug 26, 2012 at 8:31 PM, Stefan Hechenberger <ste...@nortd.com> wrote:

[David Armstrong]

i’d guess a possible problem your having is the stepper drivers are switching off perhaps , due to drawing too much current , and therefore they are shutting down

once the temp reduces then they will reset ...

have you checked your current draw ? , it’s normal for steppers to get hot , and surprisingly they are designed to handle it , but not to the point of being able to cook eggs ...

remember steppers actualy draw more current when stationary than when moving , so if they are idle for a long period they can get pretty hot .

most drivers can handle this by going into a semi operational state to save power ... depends on what stepper drivers you are using

so if this is happening it can result in intermittent operations .

 

if the motors are becoming hot very quickly from cold then i’d suspect you are driving them to hard , so reduce current draw and perhaps voltage too

running at too high microstepping can also result in similar results but for different reasons .

 

or you have a some noisy wiring picking up rubbish which is crashing the system

[jet]

Previously they weren't getting enough power to turn properly. I read
the Gecko and Lin manuals and changed the resistors to increase the
amount of amps available.

In prior releases I could easily run the table without anything locking
up and geting the "power off" messages.

I'll try and do some printf debugging and figure out exactly what's
going on. It looks like the rest of 2012 is "debug stepper controllers
tasks". :-)

On 2012-09-06 18:38, David Armstrong wrote:
> i’d guess a possible problem your having is the stepper drivers are
> switching off perhaps , due to drawing too much current , and therefore
> they are shutting down
> once the temp reduces then they will reset ...
> have you checked your current draw ? , it’s normal for steppers to get
> hot , and surprisingly they are designed to handle it , but not to the
> point of being able to cook eggs ...
> remember steppers actualy draw more current when stationary than when
> moving , so if they are idle for a long period they can get pretty hot .
> most drivers can handle this by going into a semi operational state to
> save power ... depends on what stepper drivers you are using
> so if this is happening it can result in intermittent operations .
> if the motors are becoming hot very quickly from cold then i’d suspect
> you are driving them to hard , so reduce current draw and perhaps
> voltage too
> running at too high microstepping can also result in similar results but
> for different reasons .
> or you have a some noisy wiring picking up rubbish which is crashing the
> system

> *From:* jet townsend <mailto:allar...@gmail.com>
> *Sent:* Thursday, September 06, 2012 11:15 PM
> *To:* lase...@googlegroups.com <mailto:lase...@googlegroups.com>
> *Subject:* Re: [lasersaur] Yet Another LasaurApp Update, v12.08e

> Hm, there's a problem that I thought was speed related but happens on
> all speeds. The head gets to roughly X100 Y100 then everything stops
> and I get a power Off message. If I'm on high speed it just happens
> more quickly, but it looks to be in the same place.
>
> At the same time, all of the switches are clear but the steppers are
> almost too hot to touch.
>
> On Sun, Aug 26, 2012 at 8:31 PM, Stefan Hechenberger <ste...@nortd.com
> <mailto:ste...@nortd.com>> wrote:
>
>
> We are moving quickly. Here is another release candidate. Please
> test! I feel pretty confident about this one because we had the time
> to run it quite extensively. I finally got USB working in VirtualBox
> and was able to test on Windows and Linux in addition to OSX. We
> also tested on the Beaglebone. All platforms ran the gantry
> flawlessly so far.
>
> Let me know how it runs on your systems.
>
> OSX:

> https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08e-osx.zip
> <https://github.com/downloads/stefanix/LasaurApp/LasaurApp-v12.08e-osx.zip>
>
> Windows:

> https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08e-win.zip
> <https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08e-win.zip>
>
> Linux:

> https://github.com/stefanix/__LasaurApp/

> <https://github.com/stefanix/LasaurApp/>
> (binaries and sources are in sync again)
>
>
> CHANGES are as follows:
> - serial communication completely rewritten
> - more robust flow control
> - forward error correction and error reporting
> - faster speeds, now runs at 57600 bps
> - firmware bugfixes in serial module dealing with concurrency issues
> - workaround for pyserial bugs
> - additons to the protocol, see:

> http://labs.nortd.com/__lasersaur/manual/gcode

> <http://labs.nortd.com/lasersaur/manual/gcode>
> - better optimizations in gcode generation
> - bugfixes in com port auto-configuration on windows and linux
>
> I can talk more about the new serial communication code. The details
> are actually quite interesting. Since the serial interrupts fire so
> frequently the slightest concurrency flaws can cause quite the scene.
>
> --
> Stefan Hechenberger

> studio: Nortd Labs - labs.nortd.com <http://labs.nortd.com>
> resident: F.A.T. Lab - fffff.at <http://fffff.at>
> project: Lasersaur - labs.nortd.com/lasersaur
> <http://labs.nortd.com/lasersaur>
>

--
J. Eric Townsend, IDSA
design <http://www.allartburns.org>
hacking <http://www.flatline.net>
fabrication <watch this space>

[Stefan Hechenberger]

Hi Jet,

> power off error
Typically I would guess this is a shielding problem on the line attached
to rel/vrel. Please try to verify this by connecting these inputs
directly with a jumper cable.

I also think David has a good point. If you overdrive your steppers with
too much current the drivers may very well show the behavior you are
describing. The 203V have over-temp protection and switch off when
getting too hot. Like all Gecko's they also reduce current when idle. So
they shouldn't get too hot under normal circumstance.


> air assist pins
We had a some board runs where the air assist header is mislabeled. It's
quite possible you have one of these boards. Here is a previous thread
with details:
https://groups.google.com/d/topic/lasersaur/NuDLCpFxZBM/discussion

From top to bottom the pins are even if the labels may say something
else: A5, A4, 3.3V, GND

Also be careful when controlling the valve solenoid. They tend to have a
pretty strong inductive kickback (30-300V). And also make sure you don't
use any relays that draw more than the atmega328 approved 40mA. Feel
free to start a new thread about this circuitry. I have recently shopped
around for components regarding this and can brain dump if you want.

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com

resident: F.A.T. Lab - fffff.at

project: Lasersaur - labs.nortd.com/lasersaur

[jet]

On 2012-09-07 12:57, Stefan Hechenberger wrote:
>
> Hi Jet,
>
> > power off error
> Typically I would guess this is a shielding problem on the line attached
> to rel/vrel. Please try to verify this by connecting these inputs
> directly with a jumper cable.

Will do. I am running a shielded cable here, but there's no ground for
the rel/vrel line come to think of it. It

> > air assist pins
> We had a some board runs where the air assist header is mislabeled. It's
> quite possible you have one of these boards.

I thought I verified that I didn't but will check again. I'll start a
new thread for the air controller, I'm using power transistors and a 24V
line and haven't seen any significant power release when the solenoid
shuts off on an Arduino. I'll need to measure that again, then start a
new thread.

[jet]

On 2012-09-07 12:57, Stefan Hechenberger wrote:

> I also think David has a good point. If you overdrive your steppers with
> too much current the drivers may very well show the behavior you are
> describing. The 203V have over-temp protection and switch off when

Just to be clear, if the board is idle, that is there is no job being
executed, the steppers are not under power, correct?

This was a huge PITA on the MakerBot, it'd be sitting there doing
nothing but the steppers would be locked down and under power. That's
what mine seem to be doing: there are no commands being executed but
they are powered on and I can't move the chassis by hand.

[David Armstrong]

with steppers idle they are under power , thats how they appear in a locked
position i.e you cant move the shaft
hence they become hot as all coils are activated to hold position

[David Armstrong]

also forgot to add , stepper motors are designed to be under power , and
therefore generate heat
the option is not to allow them to become over hot , this is shown easily ,
if the drive is left stationary for say 4 mins , they should be
warm to touch , but not over hot where you cannot bear to touch ... but they
can withstand heat ..

if they show a tendancy to be over hot then it's normaly the fact that the
motors are drawing too much current , so therefore change the resistors to
bring the current down and
reduce heat

-----Original Message-----
From: jet
Sent: Friday, September 07, 2012 6:24 PM
To: lase...@googlegroups.com

[jet]

On 2012-09-07 12:57, Stefan Hechenberger wrote:
>

> Hi Jet,
>
> > power off error
> Typically I would guess this is a shielding problem on the line attached
> to rel/vrel. Please try to verify this by connecting these inputs
> directly with a jumper cable.

Yup, that fixes it. Not sure why this wasn't a problem before, but it's
easy to add the ground to the common ground.

[Stefan Hechenberger]

nice.

Maybe double check the shield leads. About a month ago we updated the
wiring diagram because some of the shielding was connected to the ground
through 10k resistors which is probably not optimal.

http://labs.nortd.com/lasersaur/manual/wiring

So my question is if you connect the shielding of the rel/vrel line to
"blk" of "x1" (as shown) does this solve the problem?

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

[Craig Dorety]

Hey all,

Is there  a place to get previous releases of the lasaurapp? I just switched to 12.08f and now the machine gives me the "Limit Hit" errors. I flashed the grbl with the 127.0.0.1:4444/flash_firmware link.

Jamie and I were using 12.06? i think? today with no problems. I had a system crash and need to get my win7 laptop setup to cut.

please advise


--Craig Dorety
415.350.9509
http://craigdorety.com

*To:* lase...@googlegroups.com <mailto:lasersaur@googlegroups.com>

[Stefan Hechenberger]

Old versions are on the github page:
https://github.com/stefanix/LasaurApp/downloads

A heads up: For the binaries we had some problems in the flashing
routine on windows. At this point I forgot at what point we have fixed this.

Also if you install from sources all major updates are tagged:
https://github.com/stefanix/LasaurApp/tags
https://github.com/stefanix/LasaurGrbl/tags

The "Limit Hit", is it always on or do you just occasionally get it?

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com

resident: F.A.T. Lab - fffff.at

project: Lasersaur - labs.nortd.com/lasersaur

On 9/9/12 4:09 AM, Craig Dorety wrote:
> Hey all,
>
> Is there a place to get previous releases of the lasaurapp? I just
> switched to 12.08f and now the machine gives me the "Limit Hit" errors.
> I flashed the grbl with the 127.0.0.1:4444/flash_firmware

> <http://127.0.0.1:4444/flash_firmware> link.

>
> Jamie and I were using 12.06? i think? today with no problems. I had a
> system crash and need to get my win7 laptop setup to cut.
>
> please advise
>
>
> --Craig Dorety

> 415.350.9509 <tel:415.350.9509>
> http://craigdorety.com
> <http://komegamusic.com>

> <mailto:lase...@googlegroups.com>
> <mailto:lasersaur@__googlegroups.com
> <mailto:lase...@googlegroups.com>>

> *Subject:* Re: [lasersaur] Yet Another LasaurApp Update, v12.08e
>
> Hm, there's a problem that I thought was speed related but
> happens on
> all speeds. The head gets to roughly X100 Y100 then everything
> stops
> and I get a power Off message. If I'm on high speed it just happens
> more quickly, but it looks to be in the same place.
>
> At the same time, all of the switches are clear but the steppers are
> almost too hot to touch.
>
> On Sun, Aug 26, 2012 at 8:31 PM, Stefan Hechenberger
> <ste...@nortd.com <mailto:ste...@nortd.com>

> <mailto:ste...@nortd.com <mailto:ste...@nortd.com>>> wrote:
>
>
> We are moving quickly. Here is another release candidate.
> Please
> test! I feel pretty confident about this one because we had
> the time
> to run it quite extensively. I finally got USB working in
> VirtualBox
> and was able to test on Windows and Linux in addition to
> OSX. We
> also tested on the Beaglebone. All platforms ran the gantry
> flawlessly so far.
>
> Let me know how it runs on your systems.
>
> OSX:

> https://github.com/downloads/____stefanix/LasaurApp/LasaurApp-____v12.08e-osx.zip
> <https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08e-osx.zip>

>
> <https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08e-osx.zip
> <https://github.com/downloads/stefanix/LasaurApp/LasaurApp-v12.08e-osx.zip>>
>
> Windows:

> https://github.com/downloads/____stefanix/LasaurApp/lasaurapp-____v12.08e-win.zip
> <https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08e-win.zip>

>
> <https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08e-win.zip
> <https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08e-win.zip>>
>
> Linux:

> https://github.com/stefanix/____LasaurApp/
> <https://github.com/stefanix/__LasaurApp/>

> <https://github.com/stefanix/__LasaurApp/
> <https://github.com/stefanix/LasaurApp/>>
> (binaries and sources are in sync again)
>
>
> CHANGES are as follows:
> - serial communication completely rewritten
> - more robust flow control
> - forward error correction and error reporting
> - faster speeds, now runs at 57600 bps
> - firmware bugfixes in serial module dealing with
> concurrency issues
> - workaround for pyserial bugs
> - additons to the protocol, see:

> http://labs.nortd.com/____lasersaur/manual/gcode
> <http://labs.nortd.com/__lasersaur/manual/gcode>

>
> <http://labs.nortd.com/__lasersaur/manual/gcode
> <http://labs.nortd.com/lasersaur/manual/gcode>>
> - better optimizations in gcode generation
> - bugfixes in com port auto-configuration on windows and linux
>
> I can talk more about the new serial communication code.
> The details
> are actually quite interesting. Since the serial interrupts
> fire so
> frequently the slightest concurrency flaws can cause quite
> the scene.
>
> --
> Stefan Hechenberger
> studio: Nortd Labs - labs.nortd.com <http://labs.nortd.com>
> <http://labs.nortd.com>
> resident: F.A.T. Lab - fffff.at <http://fffff.at>
> <http://fffff.at>
> project: Lasersaur - labs.nortd.com/lasersaur
> <http://labs.nortd.com/lasersaur>

> <http://labs.nortd.com/__lasersaur

[Craig Dorety]

Hey there,

I found 12.06d on git hub and all is well now. Jamie re-flashed the grbl this morning from his mac.

The 'limit hit' error was occurring every time the machine attempted to move. It would move 3 inches or less, stop, and give the error.

bear in mind that at no point prior to this have we had any limit or door switch issues so we are pretty darned sure it is not line noise issue.

anyhow, back to 12.06d for now. thanks!!

--Craig Dorety
415.350.9509
http://craigdorety.com

        <mailto:lasersaur@googlegroups.com>

        <mailto:lasersaur@__googlegroups.com

        <mailto:lasersaur@googlegroups.com>>

[Luke Weston]

On Sat, Sep 8, 2012 at 2:57 AM, Stefan Hechenberger <ste...@nortd.com> wrote:

>
> From top to bottom the pins are even if the labels may say something else:
> A5, A4, 3.3V, GND
>
> Also be careful when controlling the valve solenoid. They tend to have a
> pretty strong inductive kickback (30-300V). And also make sure you don't use
> any relays that draw more than the atmega328 approved 40mA. Feel free to
> start a new thread about this circuitry. I have recently shopped around for
> components regarding this and can brain dump if you want.
>

You would need to drive the solenoid valves using a MOSFET (or BJT),
not directly from the AVR.
You could use a small MOSFET/BJT to switch a relay coil which then
switches the solenoid valve, but assuming that the solenoid valves run
from the 24V DC rail (not 120VAC) personally I would switch them
directly from the microcontroller using an appropriately rated power
FET. Personally I dislike the use of electromechanical, low-tech,
noisy, moving relays when solid-state silicon can easily and cheaply
do the same job without a relay. And, yes, you'll want a
reverse-biased diode across the coil (either in the solenoid valve or
in the relay) as usual to protect the transistor.

You would, presumably, need a small extra PCB connected to the A4/A5
assist gas solenoid header on the board which controls those
solenoids.

Cheers,
Luke

[Erik Moon]

Sorry - recently started a build, so I might have missed this if discussed earlier.

Is there a reason to not run air assist continuously while running a cut / etch job?


-- -- -- -- --- -- -- -- --
Erik Moon

[Stefan Hechenberger]

Running air assist continuously is fine. It just means that the
compressor will run more. Also if you use nitrogen assist you will find
yourself turning the gas on and off a lot.

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

[Stefan Hechenberger]

Craig, I don't really have a good answer to make v12.08f work for you.
One way would be to just wait and see if anybody else runs into similar
problems.

I still think there is a small chance it's a line noise issue. The
v12.08f firmware has a slightly changed acceleration profile. It's
possible that this is enough to cause some issues if you were just under
the threshold before. One way to find out very quickly is to jumper the
sensor inputs.

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

On 9/9/12 10:20 PM, Craig Dorety wrote:
> Hey there,
>
> I found 12.06d on git hub and all is well now. Jamie re-flashed the grbl
> this morning from his mac.
>
> The 'limit hit' error was occurring every time the machine attempted to
> move. It would move 3 inches or less, stop, and give the error.
>
> bear in mind that at no point prior to this have we had any limit or
> door switch issues so we are pretty darned sure it is not line noise issue.
>
> anyhow, back to 12.06d for now. thanks!!
>
>
>
> --Craig Dorety

> 415.350.9509 <tel:415.350.9509>
> http://craigdorety.com
> <http://komegamusic.com>

>
>
>
> On Sun, Sep 9, 2012 at 2:52 AM, Stefan Hechenberger <ste...@nortd.com
> <mailto:ste...@nortd.com>> wrote:
>
>
> Old versions are on the github page:

> https://github.com/stefanix/__LasaurApp/downloads

> <https://github.com/stefanix/LasaurApp/downloads>
>
> A heads up: For the binaries we had some problems in the flashing
> routine on windows. At this point I forgot at what point we have
> fixed this.
>
> Also if you install from sources all major updates are tagged:

> https://github.com/stefanix/__LasaurApp/tags
> <https://github.com/stefanix/LasaurApp/tags>
> https://github.com/stefanix/__LasaurGrbl/tags

> <https://github.com/stefanix/LasaurGrbl/tags>
>
> The "Limit Hit", is it always on or do you just occasionally get it?
>
>
> --
> Stefan Hechenberger

> studio: Nortd Labs - labs.nortd.com <http://labs.nortd.com>

> resident: F.A.T. Lab - fffff.at <http://fffff.at>

> project: Lasersaur - labs.nortd.com/lasersaur
> <http://labs.nortd.com/lasersaur>
>
>

> On 9/9/12 4:09 AM, Craig Dorety wrote:
>
> Hey all,
>
> Is there a place to get previous releases of the lasaurapp? I just
> switched to 12.08f and now the machine gives me the "Limit Hit"
> errors.
> I flashed the grbl with the 127.0.0.1:4444/flash_firmware
> <http://127.0.0.1:4444/flash_firmware>

> <http://127.0.0.1:4444/flash___firmware

> <http://127.0.0.1:4444/flash_firmware>> link.
>
>
> Jamie and I were using 12.06? i think? today with no problems. I
> had a
> system crash and need to get my win7 laptop setup to cut.
>
> please advise
>
>
> --Craig Dorety

> 415.350.9509 <tel:415.350.9509> <tel:415.350.9509

> <tel:415.350.9509>>
> http://craigdorety.com
> <http://komegamusic.com>
>
>
>
>
> On Thu, Sep 6, 2012 at 4:15 PM, jet <allar...@gmail.com
> <mailto:allar...@gmail.com>

> <mailto:allar...@gmail.com <mailto:allar...@gmail.com>>__>

> <mailto:allar...@gmail.com
> <mailto:allar...@gmail.com>>__>

> *Sent:* Thursday, September 06, 2012 11:15 PM
> *To:* lase...@googlegroups.com

> <mailto:lase...@googlegroups.com>
> <mailto:lasersaur@__googlegroups.com
> <mailto:lase...@googlegroups.com>>

> <mailto:lasersaur@
> <mailto:lasersaur@>__googlegrou__ps.com <http://googlegroups.com>
>
> <mailto:lasersaur@__googlegroups.com
> <mailto:lase...@googlegroups.com>>>

> https://github.com/downloads/______stefanix/LasaurApp/__LasaurApp-____v12.08e-osx.zip
> <https://github.com/downloads/____stefanix/LasaurApp/LasaurApp-____v12.08e-osx.zip>

>
> <https://github.com/downloads/____stefanix/LasaurApp/__LasaurApp-__v12.08e-osx.zip
> <https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08e-osx.zip>>
>
>
>
> <https://github.com/downloads/____stefanix/LasaurApp/__LasaurApp-__v12.08e-osx.zip
> <https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08e-osx.zip>
>
> <https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08e-osx.zip
> <https://github.com/downloads/stefanix/LasaurApp/LasaurApp-v12.08e-osx.zip>>>
>
> Windows:

> https://github.com/downloads/______stefanix/LasaurApp/__lasaurapp-____v12.08e-win.zip
> <https://github.com/downloads/____stefanix/LasaurApp/lasaurapp-____v12.08e-win.zip>
>
> <https://github.com/downloads/____stefanix/LasaurApp/__lasaurapp-__v12.08e-win.zip
> <https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08e-win.zip>>
>
>
>
> <https://github.com/downloads/____stefanix/LasaurApp/__lasaurapp-__v12.08e-win.zip

> <https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08e-win.zip>
>
> <https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08e-win.zip
> <https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08e-win.zip>>>
>
> Linux:

> https://github.com/stefanix/______LasaurApp/
> <https://github.com/stefanix/____LasaurApp/>

> <https://github.com/stefanix/____LasaurApp/
> <https://github.com/stefanix/__LasaurApp/>>
>
> <https://github.com/stefanix/____LasaurApp/
> <https://github.com/stefanix/__LasaurApp/>
> <https://github.com/stefanix/__LasaurApp/
> <https://github.com/stefanix/LasaurApp/>>>
> (binaries and sources are in sync again)
>
>
> CHANGES are as follows:
> - serial communication completely rewritten
> - more robust flow control
> - forward error correction and error reporting
> - faster speeds, now runs at 57600 bps
> - firmware bugfixes in serial module dealing with
> concurrency issues
> - workaround for pyserial bugs
> - additons to the protocol, see:

> http://labs.nortd.com/______lasersaur/manual/gcode
> <http://labs.nortd.com/____lasersaur/manual/gcode>

> <http://labs.nortd.com/____lasersaur
> <http://labs.nortd.com/__lasersaur>

[Mischa Schaub]

Lieber Stefan

Habe Mühe mit dem Runterladen - sagt mir immer "this is not the page you are looking for. Und wenn ich das Teil direkt runterlade, dann ist es nur 21 K gross. Stimmt was nicht mit Github?

Beste Grüsse

Mischa

2012/8/27 Stefan Hechenberger <ste...@nortd.com>

We are moving quickly. Here is another release candidate. Please test! I feel pretty confident about this one because we had the time to run it quite extensively. I finally got USB working in VirtualBox and was able to test on Windows and Linux in addition to OSX. We also tested on the Beaglebone. All platforms ran the gantry flawlessly so far.

Let me know how it runs on your systems.

OSX:

https://github.com/downloads/stefanix/LasaurApp/LasaurApp-v12.08e-osx.zip

Windows:
https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08e-win.zip

Linux:

https://github.com/stefanix/LasaurApp/
(binaries and sources are in sync again)


CHANGES are as follows:
- serial communication completely rewritten
  - more robust flow control
  - forward error correction and error reporting
  - faster speeds, now runs at 57600 bps
  - firmware bugfixes in serial module dealing with concurrency issues
  - workaround for pyserial bugs
  - additons to the protocol, see:

    http://labs.nortd.com/lasersaur/manual/gcode
- better optimizations in gcode generation
- bugfixes in com port auto-configuration on windows and linux

I can talk more about the new serial communication code. The details are actually quite interesting. Since the serial interrupts fire so frequently the slightest concurrency flaws can cause quite the scene.

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com

resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

--
HyperWerk Institute for Postindustrial Design
Totentanz 17  /  CH-4051 Basel  / +41 61 2699 227  
www.hyperwerk.ch

[Stefan Hechenberger]

Hi Mischa, the v12.08f links should work ...

OSX:
https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08f-win.zip

Win:
https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08f-win.zip

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

On 9/13/12 1:55 PM, Mischa Schaub wrote:
> Lieber Stefan
>
> Habe M�he mit dem Runterladen - sagt mir immer "this is not the page you

> are looking for. Und wenn ich das Teil direkt runterlade, dann ist es
> nur 21 K gross. Stimmt was nicht mit Github?
>

> Beste Gr�sse
>
> Mischa
>
>
> 2012/8/27 Stefan Hechenberger <ste...@nortd.com <mailto:ste...@nortd.com>>

>
>
> We are moving quickly. Here is another release candidate. Please
> test! I feel pretty confident about this one because we had the time
> to run it quite extensively. I finally got USB working in VirtualBox
> and was able to test on Windows and Linux in addition to OSX. We
> also tested on the Beaglebone. All platforms ran the gantry
> flawlessly so far.
>
> Let me know how it runs on your systems.
>
> OSX:

> https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08e-osx.zip
> <https://github.com/downloads/stefanix/LasaurApp/LasaurApp-v12.08e-osx.zip>
>
> Windows:

> https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08e-win.zip
> <https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08e-win.zip>
>
> Linux:

> https://github.com/stefanix/__LasaurApp/

> <https://github.com/stefanix/LasaurApp/>
> (binaries and sources are in sync again)
>
>
> CHANGES are as follows:
> - serial communication completely rewritten
> - more robust flow control
> - forward error correction and error reporting
> - faster speeds, now runs at 57600 bps
> - firmware bugfixes in serial module dealing with concurrency issues
> - workaround for pyserial bugs
> - additons to the protocol, see:

> http://labs.nortd.com/__lasersaur/manual/gcode

> <http://labs.nortd.com/lasersaur/manual/gcode>
> - better optimizations in gcode generation
> - bugfixes in com port auto-configuration on windows and linux
>
> I can talk more about the new serial communication code. The details
> are actually quite interesting. Since the serial interrupts fire so
> frequently the slightest concurrency flaws can cause quite the scene.
>
> --
> Stefan Hechenberger

> studio: Nortd Labs - labs.nortd.com <http://labs.nortd.com>
> resident: F.A.T. Lab - fffff.at <http://fffff.at>
> project: Lasersaur - labs.nortd.com/lasersaur
> <http://labs.nortd.com/lasersaur>
>
>
>
>

> --
> HyperWerk Institute for Postindustrial Design
> Totentanz 17 / CH-4051 Basel / +41 61 2699 227

> www.hyperwerk.ch <http://www.hyperwerk.ch>

[Mischa Schaub]

Aehem...

Besten Dank

Mischa

2012/9/13 Stefan Hechenberger <ste...@nortd.com>

Hi Mischa, the v12.08f links should work ...

OSX:
https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08f-win.zip

Win:
https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08f-win.zip


--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

On 9/13/12 1:55 PM, Mischa Schaub wrote:

Lieber Stefan

Habe Mühe mit dem Runterladen - sagt mir immer "this is not the page you

are looking for. Und wenn ich das Teil direkt runterlade, dann ist es
nur 21 K gross. Stimmt was nicht mit Github?

Beste Grüsse

[jet]

Exactly. And forgetting to turn it on or off can be expensive. It's
trivial to add the gas on/off codes to the g-code generator.

[j. eric townsend]

[resend -- and if you didn't see my branch announcement let me know and
I'll send it as well]

Check the build I just posted -- I made each sensor an individual
#define and fixed the SCI lasersaur by removing the power sensor.

[Erik Moon]

Hey All-

Jason and I have posted more build log… We also have first movement video posted!

http://www.replicatemypart.com/

We have both axes moving now and most of the chassis build is complete. We also found some zip-ties that have screw eyes on the ends -- they are a very convenient way to clean up the water hoses and the cable bundles. I think it is a much better approach than hot glue...

We noticed that the wiring diagram does not appear to be correct for both stepper motors and the left / right X-axis limit switches appear to be reversed.

When I get a chance to write it up, I'll explain what I had to do to the stepper wiring.

We should have "first light" in the next few days. Will post more updates and videos…

-Erik & Jason

[Erik Moon]

Hi All-

Ok -- our Lasersaur is now cutting!!

Videos of our first cut:

replicatemypart.com

We were able to cut 1/4" MDF and 4 mm Acrylic sheet on our first day. It is looking pretty good.

I can't tell you how frustrating laser alignment was to complete… I think there is a serious need for some documentation on the best procedure for doing that. We stumbled onto a good solution, but I'm pretty sure we did not take the easy way to getting that done.

-Erik & Jason

[Stefan Hechenberger]

congrats! looking good.

Did you see the manual page about alignment? It's normal to take a bit
of time but should not be terribly hard. It usually takes me about 20min
the first time.

http://labs.nortd.com/lasersaur/manual/optics_setup

Thanks for the video,

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

On 11/03/2012 06:09 PM, Erik Moon wrote:
> Hi All-
>
> Ok -- our Lasersaur is now cutting!!
>
> Videos of our first cut:
>

> replicatemypart.com <http://replicatemypart.com>

>
>
> We were able to cut 1/4" MDF and 4 mm Acrylic sheet on our first day. It
> is looking pretty good.
>

> I can't tell you how frustrating laser alignment was to complete� I

[Steve Baker]

One of my (all-too-many) pet hates is websites that don't have favicons.

I've attached a couple of suitable candidates - a black lasersaurus on the
bright yellow background...if they are OK, all someone needs to do is to
dump them into the top level directory of the lasersaur website and
everything will magically work.

-- Steve

[Stefan Hechenberger]

Thanks Steve, good point.

I just made a multi-resolution favicon in gimp (needed one for all of
nortd labs not just lasersaur).

BTW: Replying will cause your message to be posted in the same thread in
most email clients and on the web interface. Only sending a new mail to
lase...@googlegroups.com will reliably start a new thread.

Thanks,

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur