LasaurApp v12.08 ready for testing

[Stefan Hechenberger]

Hi list, please help me test the latest LasaurApp.

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

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

NOTE, this version requires a firmware update. After starting LasaurApp
simply open http://127.0.0.1:4444/flash_firmware . This should now also
work flawlessly on Windows (tested on windows 7).

Thanks to everybody who gave feedback in the last couple of weeks,
especially for helping debug the firmware woes on windows.


Changed and Additions
----------------------
+ status reporting
sensor input is now reported in the GUI, no need to check the
console to figure out if inputs signal any of:
chiller off, limit hit, power off, door open
For example if a limit switch was hit the GUI will show a
"limit hit" error (to reset 'saur run homing cycle).

+ "chiller off" is no longer a stop mode condition
(like when a limit was hit) but only triggers a warning
(the hard-logic still disables the laser though). This allows for
testing the gantry without a chiller running.

+ windows serial port auto-find
Just double-clicking the exe should work without having
to specify serial port. (tested on Windows 7)

+ windows firmware flashing (like in osx now)
BUGFIX: libusb0.dll missing
BUGFIX: having to press reset button
Also the flashing routine should find the serial port
now automatically.

+ When running the LasaurApp in dev setup it's no longer
necessary to install pyserial as it's now included in the
LasaurApp sources.




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

[Justin Krull]

Windows 7 64bit firmware flashing works perfectly whether or not the COM port is specified in the GUI. "lasaurapp.exe -f COM#" and  http://127.0.0.1:4444/flash_firmware work.

The auto COM port detection is not working when launching the lasaurapp for normal use or using "lasaurapp.exe -f" to flash. You need to flash the firmware in the GUI to get auto COM port detection when just launching the lasaurapp without specifying the COM port.

Justin

[jet]

I'm having trouble pulling changes to the branches. I'm guessing you've
checked things in, but have you taken the outstanding pull requests yet?
In the past this has caused problems on other github projects that I'm
not sure how to fix.

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

[Mischa Schaub]

Hi Stef

While trying to http://127.0.0.1:4444/flash_firmware I got the message on OS X  10.8:

Flashing failed!
Check Log window for possbile errors. Most likely Lasaur App could not find the right serial port.

Any idea what to do?

Kind regards
Mischa

2012/8/9 jet <allar...@gmail.com>

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

[Stefan Hechenberger]

Hi Mischa, thnaks for the bug report.

I don't have mountain lion yet to test this. But maybe I can tell what
is going on if you sent me the output from the console window (LasaurApp
opens a console window and a browser).

Best,

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

On 8/9/12 12:23 PM, Mischa Schaub wrote:
> Hi Stef
>
> While trying to http://127.0.0.1:4444/flash_firmware I got the message
> on OS X 10.8:
>
> Flashing failed!
> Check Log window for possbile errors. Most likely Lasaur App could not
> find the right serial port.
>
> Any idea what to do?
>
> Kind regards
> Mischa
>
>

> 2012/8/9 jet <allar...@gmail.com <mailto:allar...@gmail.com>>

>
> I'm having trouble pulling changes to the branches. I'm guessing
> you've checked things in, but have you taken the outstanding pull
> requests yet? In the past this has caused problems on other github
> projects that I'm not sure how to fix.
>
>
>
>
> On 2012-08-08 19:41, Stefan Hechenberger wrote:
>
>
> Hi list, please help me test the latest LasaurApp.
>
> Windows:

> https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08-win.zip
> <https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08-win.zip>
> MD5: 614aa7da8669cbf35c9559cf3d8a5b__6f
>
> OSX:
> https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08-osx.zip
> <https://github.com/downloads/stefanix/LasaurApp/LasaurApp-v12.08-osx.zip>
> MD5: fe355a975759b7aa32010da74e5ba6__26

>
> NOTE, this version requires a firmware update. After starting
> LasaurApp

> simply open http://127.0.0.1:4444/flash___firmware

> 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>
>
>
>
>
> --
> HyperWerk Institute for Postindustrial Design
> Totentanz 17 / CH-4051 Basel / +41 61 2699 227

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

[Mischa Schaub]

Hi Stef

So now I get this message in the browser:

Error 404: Not Found

Sorry, the requested URL http://127.0.0.1:4444/flash___firmware caused an error:

Not found: /flash___firmware





And this I get from the console window:


Adding to queue 2 lines
.....1.0.0.127.in-addr.arpa - - [10/Aug/2012 09:57:39] "GET /status HTTP/1.1" 200 276

...1.0.0.127.in-addr.arpa - - [10/Aug/2012 09:57:41] "GET /flash___firmware HTTP/1.1" 404 693

Any ideas welcome!

Mischa

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

[Stefan Hechenberger]

Mischa, there should only be one underscore in:
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

On 8/10/12 10:05 AM, Mischa Schaub wrote:
> Hi Stef
>

> So now I get this message in the browser:
>
>
> Error 404: Not Found
>
> Sorry, the requested URL http://127.0.0.1:4444/flash___firmware caused
> an error:
>
> Not found: /flash___firmware
>
>
>
>
>
> And this I get from the console window:
>
>
> Adding to queue 2 lines
> .....1.0.0.127.in-addr.arpa - - [10/Aug/2012 09:57:39] "GET /status HTTP/1.1" 200 276
>
> ...1.0.0.127.in-addr.arpa - - [10/Aug/2012 09:57:41] "GET /flash___firmware HTTP/1.1" 404 693
>
>
>
> Any ideas welcome!
>
> Mischa
>
>
>

> 2012/8/9 Stefan Hechenberger <ste...@nortd.com <mailto:ste...@nortd.com>>

>
>
> Hi Mischa, thnaks for the bug report.
>
> I don't have mountain lion yet to test this. But maybe I can tell
> what is going on if you sent me the output from the console window
> (LasaurApp opens a console window and a browser).
>
> Best,
>
>
>
> --
> 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/9/12 12:23 PM, Mischa Schaub wrote:
>
> Hi Stef
>

> While trying to http://127.0.0.1:4444/flash___firmware

> <http://127.0.0.1:4444/flash_firmware> I got the message
> on OS X 10.8:
>
> Flashing failed!
> Check Log window for possbile errors. Most likely Lasaur App
> could not
> find the right serial port.
>
> Any idea what to do?
>
> Kind regards
> Mischa
>
>
> 2012/8/9 jet <allar...@gmail.com

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

>
>
> I'm having trouble pulling changes to the branches. I'm
> guessing
> you've checked things in, but have you taken the
> outstanding pull
> requests yet? In the past this has caused problems on
> other github
> projects that I'm not sure how to fix.
>
>
>
>
> On 2012-08-08 19:41, Stefan Hechenberger wrote:
>
>
> Hi list, please help me test the latest LasaurApp.
>
> Windows:

> https://github.com/downloads/____stefanix/LasaurApp/lasaurapp-____v12.08-win.zip
> <https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08-win.zip>
>
> <https://github.com/downloads/__stefanix/LasaurApp/lasaurapp-__v12.08-win.zip
> <https://github.com/downloads/stefanix/LasaurApp/lasaurapp-v12.08-win.zip>>
> MD5: 614aa7da8669cbf35c9559cf3d8a5b____6f
>
> OSX:
> https://github.com/downloads/____stefanix/LasaurApp/LasaurApp-____v12.08-osx.zip
> <https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08-osx.zip>
>
> <https://github.com/downloads/__stefanix/LasaurApp/LasaurApp-__v12.08-osx.zip
> <https://github.com/downloads/stefanix/LasaurApp/LasaurApp-v12.08-osx.zip>>
> MD5: fe355a975759b7aa32010da74e5ba6____26

>
>
> NOTE, this version requires a firmware update. After
> starting
> LasaurApp

> simply open http://127.0.0.1:4444/flash_____firmware

> <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>>
>
>
>
>
> --
> J. Eric Townsend, IDSA
> design <http://www.allartburns.org>
> hacking <http://www.flatline.net>
> fabrication <watch this space>
>
>
>
>
> --
> HyperWerk Institute for Postindustrial Design
> Totentanz 17 / CH-4051 Basel / +41 61 2699 227

> <tel:%2B41%2061%202699%20227>
> www.hyperwerk.ch <http://www.hyperwerk.ch> <http://www.hyperwerk.ch>

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

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

[cw&t]

Hi stefan
I have the new firmware installed and the app running.

a couple issues (not sure if did something wrong)
I get the door is open warning when the door is closed, and disappears
when it's open.
With the chiller off (i get the warning), the gantry moves for a
second, then stops. After homing, i can move it for a second again,
but stops again.

--
Che-Wei Wang [pron. say-way]
+1-718-757-2247
cwwang.com | cwandt.com

[Stefan Hechenberger]

Dang! Thanks for testing, though. I should have an update early next
week when I can actually do some more testing on our 'saur.

If you need to downgrade till then older releases can be found on the
github page:
https://github.com/stefanix/LasaurApp/downloads

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

[jet]

Do you want me to try and replicate his results or is that enough for
you to start fixes?

[Stefan Hechenberger]

Please help me test the update of the update (aka v12.08b).

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

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

Linux:
use the sources, it's easy ;)


So I just ran some more thorough test on our Lasersaur and had to make a
few minor fixes. Then everything ran fine. I couldn't find anything
unusual.

Cheewee was right that the door sensor was in fact inversed. This is
fixed now. On the other hand I couldn't reproduce the issue with the
'saur failing if the chiller is off (FYI, the new behavior is to keep
running the gantry and only disabling the laser (same for door open)).
Please let me know if this problem persists.

Happy testing,

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

On 8/10/12 5:46 PM, cw&t wrote:

[Stefan Hechenberger]

Hey jet,

Just posted fixes. I couldn't reproduce the chiller off issue cheewee
was having. With the new release the machine should run when the chiller
is off (H1, H3 disconnected, laser stays disabled). For him it only runs
for 1sec and then stops. I would be curious what happens on your machine
if you switch the chiller off.

Also if any of you happen to have a Mountain Lion (OSX 10.8) system
already. Mischa had problems with flashing when calling:
http://127.0.0.1:4444/flash_firmware

I also cannot reproduce this because I don't have OSX 10.8. Help testing
this appreciated.

Thanks,

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

[Che-Wei Wang]

Thanks Stefan

I'll check the chiller thing tomorrow. I've been running mountain lion with no problems flashing the firmware.

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

[jet]

Getting ready for dinner, will try it in the am.

I'm fixed on 10.6 for now, the upgrade to 10.8 costs too much for 3rd
party software upgrades. I do have Win7 and Ubuntu, so I'll try and
test all three.

[Che-Wei Wang]

Just tried running this again
The firmware flashes properly.

I get the chiller and door warnings properly, but i still can't move
the gantry for more than a second. This happens even when the door is
closed and the chiller is on. About a second into running a cut file
or direct controlling the gantry, it stops abruptly and i get a power
off warning and info to turn lasersaur on and home (it's definiltey
on). I can then click on home to get the gantry move to home and the
power off warning goes away. Then if i try to move again it stops
after a second and the power warning shows up again.

running osx 10.8

[Stefan Hechenberger]

This appears to be noise on the power sensor cable (from relay to
rel/vrel). As a test try connecting rel/vrel directly with a jumper
cable and see if the problem goes away.

It's possible that we also need to use a shielded cable for this. The
wiring schematic might have to be updated for this.

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

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

[cw&t]

I added a shielded wire. Thanks! That worked for getting rid of the
power off warning, but my gantry still stops after a second of
movement (sometimes less). Nothing unusual in the console or logs
(motion request sent shows up). I'm not sure what's causing the
problem. I don't have any issues running v12.06e.

[Justin Krull]

I have the same issues with my machine. I had to go back to 12.06 also to get the machine running correctly.

Regards,

Justin

[Stefan Hechenberger]

Cheewee, Justin,

Do I understand this correctly, this also happens when the chiller is on
(not just when it is off)?

Can you run a homing cycle then send a longer job (e.g the lasersaur
logo) and look at the output in the console. After the gantry stops does
the console still print periods (e.g lines starting with periods). This
is an indicator that the firmware is still processing g-code lines (but
for some reason doesn't actually trigger the stepper motors).

Also after it stopped can you disconnect LasaurApp and then connect to
it with the Arduino Serial Monitor and send '?' like this:
http://www.flickr.com/photos/stfnix/7746226640/in/photostream

You should get an extended status string returned which you can send me
or decipher yourself (see Return Format section):
http://labs.nortd.com/lasersaur/manual/gcode

In the Adruino Serial Monitor can you still move the gantry if you send
a "G0 X100 Y100", for example?

Let me know how it goes,

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

[cw&t]

HI Stefan
Just tested it
Yes. the gantry stops whether the chiller is on or off.

flashed firmware
Ran the homing cycle, and ran the lasersaur logo.

Clicked home
logs show: Homing cycle...
gantry moves to home
logs show:Offset reset
Clicked send to lasersaur
Logs show: G-code sent to serial
Logs show: Done.

Console shows multiple lines of "..."

? via serial returns
# LasaurGrbl 12.08b

sending G0 X100 Y100 doesn't move the gantry

[Stefan Hechenberger]

> Console shows multiple lines of "..."

Does the console keep adding '.' after the gantry stopped?
What when you send another job?

> ? via serial returns
> # LasaurGrbl 12.08b

This should return something like:
DCPX0.000Y0.000V12.08b

have you set the drop-downs to "newline" and "9600"?
http://www.flickr.com/photos/stfnix/7746226640

[cw&t]

got it working!
sorry about all this.
The power off warning showed up again, so i checked the wires again.
It turns out the culprit was the shielded power sensor cable that
wasn't properly grounded.

gantry movement with door open and chiller off works!

Thank you!

[Stefan Hechenberger]

win!

As a result from all this I revised the wiring diagram:
http://labs.nortd.com/lasersaur/manual/wiring

The wiring for the sensor cable shields is now either going to one of
the "blk" or the "grn" pins. It was incorrect to have them connected to
either "H1" or "rel" as they are only indirectly connected to the gnd
through a resistor.

As always changes are listed on the revisions page:
http://labs.nortd.com/lasersaur/manual/revisions

@justin looks like you have to double-check your shield leads. To be on
the safe side refer to the new wiring diagram.

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

[jet]

With or without the chiller I'm getting "Power is off!" warnings
followed by "Turn on Lasersaur power[...]" messages in a constant
stream. My laser power supply is unplugged so I can test some stuff
without wearing safety glasses, but would that prevent xy movement? How
does the board know my laser is unplugged?

I'll reflash and try again, just in case that went hokey.

On 2012-08-12 17:28, Stefan Hechenberger wrote:
>

[jet]

The uncompressed OSX binary has a time stamp of 18 May, 2012.

[jet]

[corrected]

The OSX binary has a time stamp of 18 May, 2012 while the Windows has a
time stamp of 12 August, 2012.

On 2012-08-12 17:17, Stefan Hechenberger wrote:
>

[jet]

I think the 12.08b OSX build is messed up. I down-revved to 12.06h for
OSX and couldn't create the power-off errors. However 12.06h is also
sending negative voltages on A4 and A5 instead of positive voltages.

I merged from mainline to my work branch and built, I'm seeing the
following problems on OSX:

- previously mentioned "power is off / turn on the lasersaur [...]"
error message. I made a note about this with a prior version that says
"app.py can throw this error, but the browser thinks it is connected:
Error: Power Off"

- the Adobe Unit Types error message in app.py

- A4 and A5 are sending negative voltages (relative to the arduino and
power ground pins) instead of positive voltages.

On 2012-08-12 17:17, Stefan Hechenberger wrote:
>

[jet]

loaded and flashed from my Win7 laptop, version 12.08c (not b) reported.
Things didn't work well

- can't find the com port after flashing. browser says it's connected
and throws no errors, app says it can't find the correct com port.

- manually connected using COM10 and the CLI, no movement, no error
messages.

- tried to reconnect from OSX, still no movement, but did get a version
number back when app.py connected

- reflashed from OSX source to version 12.08b, was able to connect and
move the head

- tried to use 12.08b flash on win7, app.py through this message the
first time

sarasara - - [22/Aug/2012 22:52:28] "GET /img/notice.png HTTP/1.1" 304 0
sarasara - - [22/Aug/2012 22:52:28] "GET /img/close.gif HTTP/1.1" 304 0
sarasara - - [22/Aug/2012 22:52:28] "GET /queue/list HTTP/1.1" 200 2
sarasara - - [22/Aug/2012 22:52:28] "GET /library/list HTTP/1.1" 200 119
sarasara - - [22/Aug/2012 22:52:31] "GET /serial/1 HTTP/1.1" 200 0
sarasara - - [22/Aug/2012 22:52:32] "GET /status HTTP/1.1" 200 276
Traceback (most recent call last):
File "<string>", line 469, in <module>
File "<string>", line 428, in run_helper
File "<string>", line 89, in run_with_callback
File
"c:\Users\noema\git\LasaurApp\other\build\pyi.win32\app\out01-PYZ.pyz\serial_manager",
line 258, in send_queue_as_ready
File
"c:\Users\noema\git\LasaurApp\other\build\pyi.win32\app\out01-PYZ.pyz\serial.serialwin32",
line 270, in write
serial.serialutil.SerialTimeoutException: Write timeout

I exited and started again then got this message on the reflash attempt:



avrdude: stk500_getsync(): not in sync: resp=0x24

avrdude done. Thank you.

On 2012-08-12 17:17, Stefan Hechenberger wrote:
>

[Stefan Hechenberger]

Hi Jet, I am currently a bit consumed by the serial com bug but should
have this all cleaned up in a few days.

The v12.08x LasaurApp is still subject to testing and is not meant for
production.

> power off
... has nothing to do with laser power but system power. It basically
senses if the e-stop was pressed. See the following for details on the
safety system and how sensors affect operation:
http://labs.nortd.com/lasersaur/manual/operation

> windows
Any chance the serial port was still open in another app?

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

[jet]

> > power off
> ... has nothing to do with laser power but system power. It basically
> senses if the e-stop was pressed. See the following for details on the

Hm, and I don't have an e-stop, just a big on/off switch. I'll check
connections, maybe it's picking up static from a loose wire? I
switched all of my cables to shielded/grounded, but I might have
something iffy on vrel/rel.

> > windows
> Any chance the serial port was still open in another app?

I checked, but Win7 can be slow to update drivers some times. I'll
reboot and try again this afternoon.

[Stefan Hechenberger]

For this update I've added forward error correction. This should deal
with minor transmission errors.

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

It's late, I will post more extensive info later and also the windows
binary.

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

[Stefan Hechenberger]

make sure to also flash the controller with
http://127.0.0.1:4444/flash_firmware and to regenerate any gcode you may
have (added some more optimization).

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

[Dan Cotrupe]

Awesome. Can't wait for the windows stuff to be updated too. Thanks! Also, we looked into some of the serial errors/limit switch problems we've been having and it seems that while SENSE_LIMITS defined function detects that a limit has been tripped, and as such prints an L; however, when it gets further into the process gcode function and checks which of the 4 limits (SENSE_X1_LIMIT, etc) have been tripped it does not find a match in the if statements. As such, only L is output and not L and then L1, L2, L3, or L4.