Messages

121

3D Printers / Re: HowTo: Compilling Lasershark 3DP with Cygwin64 on Win7 64Bit

« on: January 06, 2015, 09:26:04 AM »

Hi Veneridesign

Have you considered using CreationWorkshop with the LaserShark or are you compiling the pre-alpha lasershark_3dp code to develop your own software?

122

OpenLase Discussion / Re: LaserShark / Openlase / Raspberry Pi ?

« on: December 07, 2014, 06:07:44 PM »

Running the LaserShark or JACK isn't the issue on the PI, it's OpenLase itself. In real-time it calculates where points need to be drawn to generate lines/etc and the PI is not suited for this.

Speaking of Laserboy, this is the reason I made the lasershark_stdin app. Time keeps escaping me but I intend to either made a LaserBoy extension to output proper output for the LaserShark.. or simply make a LaserBoy WAV to LaserShark format converter. Since the display wouldn't need to be calculated in real time for this, you could definitely use a PI+LaserShark to display pre-canned shows

123

LaserShark Support / Re: Programming Interface?

« on: December 02, 2014, 08:01:56 PM »

Pardon the delayed response, I was out of town for Thanksgiving.

The LaserShark is not accessed as an audio device. I'm guessing you are confused by the use of JACK? The JACK audio components are only present in order to interact with OpenLase. The lasershark_jack host app reads off the JACK audio system, converts the samples to something the LaserShark can read, and then uses lasershark_lib.[c/h] plus libusb calls to send the data. Since OpenLase is more focused towards real-time events (i.e. games or interactive displays) I use isochronous transfers to send data.


I haven't gotten a good feel for what you are attempting to accomplish but talking directly with the LaserShark seems to be within the realm of your objectives. In this case you can ignore the lasershark_jack application and focus on the lasershark_stdin application code.

So stepping back, first you should check out  the lasershark_stdin_circlemaker app:
https://github.com/macpod/lasershark_hostapp/blob/master/lasershark_stdin_circlemaker.c

This code continuously spits out data to stdout that the lasershark_stdin application can interpret. The format of this data can be read about in the example file:
https://github.com/macpod/lasershark_hostapp/blob/master/lasershark_stdin_input_example.txt


The lasershark_stdin application...
https://github.com/macpod/lasershark_hostapp/blob/master/lasershark_stdin.c
parses data passed to it via stdin and converts it into a format suitable for transfer to the lasershark. Utilizing lasershark_lib.[c/h] and libusb it then sends this data to the LaserShark. I'm using bulk transfers here because the applications that would need to do this (i.e 3d printers) require the guaranteed display of data vs. real-time information display.

Check out the handle_sample() function to identify the format of the data sent over the usb line. In short to control the galvos and lasers you must send "samples". A "sample" is a set of values used to update the state of the x, y, a, b, c, and intl_a outputs.

Multiples of these samples which are bundled together into a "packet" are sent as one or more bulk transfer to the LaserShark. You can see how this happens by reviewing the send_samples() function.


The main function of lasershark_stdin will contain examples of how to use lasershark_lib.[c/h] to setup the LaserShark. An example of an attribute that should be setup before using the LaserShark is the ilda rate. This is a volatile attribute and must be configured every time you power-on the LaserShark.


Inside of the lasershark firmware, received packetized samples via isochronous or bulk transfers (your choice which ultimately will depend on your application) are stored in a ringbuffer. Please see  lasershark_process_data() for how this is done.
https://github.com/macpod/lasershark_firmware/blob/master/lasershark/src/lasershark.c

Based on set ilda rate, a timer fires repeatedly and removes a sample for display from the ringbuffer. You can review TIMER32_1_IRQHandler() to identify how this is done.

124

OpenLase Discussion / Re: LaserShark / Openlase / Raspberry Pi ?

« on: November 25, 2014, 07:18:59 PM »

Hi Fabrice

Booting from a USB key is slow but will work. If you have a computer with USB 3.0 ports (they are blue instead of black) then definitely try use a USB 3.0 thumb drive (it should be a little bit faster).

This will also give you an opportunity to play with linux

125

OpenLase Discussion / Re: LaserShark / Openlase / Raspberry Pi ?

« on: November 24, 2014, 09:38:48 PM »

Hi Fabrice,

For 3d printers (which use bulk transfers) the raspberry pi should be fine to use however for real-time laser projector use it won't work... or if it does it will work very poorly. The raspberry pi is simply too slow for real time laser displays.



I would encourage you to install linux on your computer for development. You can install two different operating systems on the same drive, install a new internal drive and install linux onto this, or even purchase an external hard drive and install/boot off this.

126

LaserShark Support / Re: Programming Interface?

« on: November 21, 2014, 08:05:56 PM »

Hi Karl,

What OS will you be running this custom software on?

The api used for LaserShark communications requires LibUSB so you should install this. The api can be seen on my github repo area under this project:
https://github.com/macpod/lasershark_hostapp

Specifically....
https://github.com/macpod/lasershark_hostapp/blob/master/lasershark_lib.h
https://github.com/macpod/lasershark_hostapp/blob/master/lasershark_lib.c

Demonstrations on how to use this api in conjunction with libusb can be seen with lasershark_jack (shows off isochronous transfers):
https://github.com/macpod/lasershark_hostapp/blob/master/lasershark_jack.c

....and lasershark_stdin (shows off bulk transfers):
https://github.com/macpod/lasershark_hostapp/blob/master/lasershark_stdin.c

I would encourage you to start off with the lasershark_stdin code.


The usage page will explain how to compile these examples:
http://www.macpod.net/electronics/lasershark/lasershark_usage.php

No documentation is present aside from comments, but the interface is relatively simple. There is no support in this api to send vector data, only points. If you need to draw lines/curves/etc you should consider running the lasershark_jack client and reviewing the openlase api:
https://github.com/marcan/openlase

No api documentation is provided for that project but there are a few good samples:
https://github.com/marcan/openlase/tree/master/examples

Overall that api isn't too bad, it's similar to working with opengl primitives.

127

3D Printers / Re: Questions for Lasershark wiring

« on: November 10, 2014, 04:50:26 PM »

what about this Laser it's ok.  Laser with TTL modulation  12VDC 405nm 150mw.

http://www.ebay.com/itm/New-12VDC-405nm-150mw-Blue-Violet-Laser-Diode-Module-with-0-20KHz-TTL-modulation-/130955440710

This laser WILL work with the LaserShark. The GND signal pin should be connected to the GND pin of the A, B, or C port you elect to use and the other signal pin connected to the A, B, or C signal pin.

You will still need a power supply for this laser however so make sure you procure this too.

if it's not too much trouble  would you mind explain me abit about type Laser?
it's will be knowledge for anyone who want to make 3dprinter with laser by lasershark board.
 
I see on alieexpress
http://www.aliexpress.com/w/wholesale-ttl-laser-diode-module.html
many type and power for laser which type that i can use with lasershark.
I don't know laser it's have many detail.

1.what difference about green, blue, red  laser or just color .or which color it's have affect with UV Cure Resin
2.abot nanometer (nm) I see many like 445 nm 658 nm 980 nm etc. what diference and which have affect with UV Cure Resin
3.and power about 150 mw 200 mw or 800 mw what difference  more mw it's mean more power that resin will cure faster or not.

Thank you a lot

sontaya

1. There are many different types of resins that can can be cured with light. Each type of resin is reactive to a different band (or multiple bands) of light frequencies.

Before you purchase a laser, you should review the resin you intend to use in order to select the best laser frequency. UV cure resins need ultraviolet light to cure. This means a laser between 100nm-400nm must be used.

Lasers that emit light in the visible light spectrum ~400nm-780nm such as green lasers (532nm) would not be good candidates for UV curing purposes.



2. the nanometer rating is the wavelength of light the laser produces. For example 532nm = green light, 445nm = blue light, and 658 = red light. If you search google for "electromagnet spectrum" you can read more about what wavelengths are where.


3. The power will affect how fast the resin cures. You should review your resin to identify the amount of power needed. If you obtain a laser that is not powerful enough the resin won't cure fast enough and if you obtain too powerful of a laser it may unintentionally over-cure an area or cure it too fast.


You must be VERY CAREFUL when operating lasers more powerful than 5mW. These lasers WILL cause eye damage if used improperly! At 150mW if the laser beam or a reflection enters your eye even for an instant you can be blinded. As you approach higher power levels even looking at the laser beam as it is bounced off non reflective surfaces can cause eye damage!

The smart and responsible thing to do is to ensure your setup is placed in an enclosure that blocks the laser light (direct and indirect) from entering your eyesight. You should also own a pair of laser safety goggles which are appropriate for the laser wavelength you are operating. I cannot stress this enough!

What is also important to know is that some of these lasers (i.e. those with wavelengths in the UV or close to the UV spectrum) are either not visible or appear very dim to the human eye even if they are very powerful. Despite the laser beam appearing very dim or even invisible these lasers can still blind you!

If you are new to lasers I would strongly encourage you to read the following:
http://www.repairfaq.org/sam/lasersaf.htm
In addition I would encourage you to search for laser safety classes taught in your area or discuss this with professional laser operators near you. Never underestimate the cost of your eyes!

128

3D Printers / Re: Laser shark for SLA printers

« on: November 09, 2014, 12:44:32 AM »

giorgino3d, I have split this topic since this relates to your own builds vs sontayas.

Thank you for your links. Your galvos do not have normal connections so you will need to manually wire them to the board. The following picture will show you:


I do not have enough information to help you with connecting your laser. Where did you buy this from? Is there a datasheet? Can you please take a picture of the bottom of plastic driver board?

129

3D Printers / Re: Questions for Lasershark wiring

« on: November 09, 2014, 12:18:03 AM »

Hi Sontaya,

Uh oh, you have very serious wiring problems! This absolutely will not work as is. If you applied power you will damage the lasershark and likely your computer too!

1. The Laser wiring is just plain wrong.
You appear to have obtained a laser which does not have modulation control. This laser is a very poor choice for 3d printing! Did this come as part of the pryntech kit?!

You need to obtain a laser module capable of TTL or analog modulation. TTL laser modules will be cheaper and should be fine for this application.

You will also need to obtain an appropriate power supply to power this laser module.

The lasershark does not provide power to the laser. It also does not act as a relay to toggle power directly to a laser diode (which appears to be how you are attempting to use it). The lasershark A, B, and C ports are used to output a signal used by the driver circuitry to set the power supplied to the laser diode.
Ports A and B are capable of outputting an analog output signal meaning they can tell a laser module driver to set the power to (off, 10% power, 20.1252% power,  .etc .. , on)
Port C is capable of outputting a TTL signal only thus it can only tell a laser module driver to set the power to on or off.

Which channel (A, B, or C) will be determined by what the Pryntech software expects. You will need to contact them in order to identify this.

When you obtain your new laser module capable of ttl modulation, please ensure that you are connecting the GND signal pin of this module to the GND pin of the laser output channel and the other signal pin to the output voltage port. Currently you are feeding 12V into GND!

2. The RAMPS board does not connect to the lasershark. You need a computer with at least two usb ports.
1. The RAMPS board should connect to USB port #1
2. The Lasershark board should connect to USB port #2

130

3D Printers / Re: Re: Laser shark for SLA printers

« on: November 06, 2014, 08:31:57 PM »

So that I may assist you can you please post:
1. Links to where you purchased these items
2. Pictures of the galvos and lasers.

• -Taking a picture of the back of the black plastic laser driver would be good (this has markings that indicate what connects where
• Closeups of the connectors will also help

131

3D Printers / Re: LaserShark and Creative Workshop test run

« on: September 26, 2014, 08:18:13 PM »

Hi Daniel,

Pardon the delay, I missed the board email message that said there was a new post.

D1 is the USR2 LED. This toggles on or off whenever a sample packet is received. If it remains off or appears "brighter" it is because the computer has momentarily stopped sending data to the LaserShark.

Debugging this is going to be extremely difficult due to the number of components involved.

A first step would be to identify if what you THINK is being sent to the LaserShark is correct. Has anyone analyzed the output of the scanning algorithm to determine if it is correct? Furthermore if you repeat the same scan, are the artifacts in the exact same spots?

132

3D Printers / Re: LaserShark and Creative Workshop test run

« on: September 09, 2014, 10:09:30 PM »

If it works fine with 32 and not 64, this is going to be a host-side issue vs a lasershark issue.

The URLs you posted are all 404s

133

3D Printers / Re: LaserShark and Creative Workshop test run

« on: September 07, 2014, 07:40:04 PM »

Nice work stimpy!

Just an FYI too..
You may have noticed that there is a new firmware (release V5). This came out to address an issue where if there are still samples present in the lasershark and the output is turned out before they are finished, they will not be cleared and may unintentionally be displayed when a new layer is being printed.

I suspect this update may cause issues with Creative Workshop due to an algorithm change however Steve should be able to quickly make a patch by reviewing my latest commits to the lasershark_3dp code.

134

LaserShark Discussion / Re: Doubts about voltage margin (-/+5V) or (+/-10V).

« on: June 30, 2014, 09:04:00 PM »

Hi macpod. Just yesterday I order a Laserhark board to Barcelona (Spain). I hope to receive the order soon. 




I have been reviewing the documentation regarding the LaserShark board, and I have some doubts. In the brief description you make of it, you say ... 




"Lasershark v2.0 Specifications. ILDA-standard differential + /-10V 12-bit X and Y Adjustable output to get as close as possible to the spec." 




and this picture say... (http://macpod.net/electronics/lasershark/images/lasershark_pinout_v2.jpg) descriptive that you contribute here. It appears that the voltage range is +5 / v-5v. Does that mean that the degrees of movement in the galvos are "limited" from suposed (-/+15V) to 1/3 of movement? 




I hope recived my order soon.
Thank!

The LaserShark for the X and Y channel DO follow the ILDA spec. the output range IS NOT "limited".

The +5/-5v indications in the picture are the potential of that pin compared to GND on the LaserShark board.

According to the ILDA spec, the X/Y signals are bipolar differential meaning you must compare the +X pin with the -X pin and the +Y pin with the -Y pin, not GND.

As an example:
1. If the -X pin is -5v and the +X pin is 5v, this is a 10v differential.
2. If the -X pin is 0V and the +X pin is 0V, this is a 0V differential.
3. If the -X pin is 5V and the +X pin is -5v, this is a -10v differential.


Please see:
http://www.laserist.org/StandardsDocs/ISP05-finaldraft.pdf

The specification confuses many because the "Voltage range" column for the  "X Axis (+)", "Y Axis (+)", "X Axis (-)", and "Y Axis (-)" states "+/-10V diff"

If you scroll down further in the specification you will see this is clarified with the following:

All signal receivers must have a true differential input stage! Unless otherwise indicated, the signal must always to be derived from the difference between the normal signal line and the corresponding inverted signal line. For example:

A differential voltage of +10V occurs if the normal signal line (+) has a voltage level of +10V with respect to the voltage level of the inverted signal line. (-)

135

3D Printers / Re: Laser shark for SLA printers

« on: June 28, 2014, 05:46:28 PM »

Hi Sontaya,

Currently the developer of creative workshop is working on support for the LaserShark. They are not at least for the moment working with the TwoStep boards however. Instead they are using RAMPS based boards. Their solution will likely be the easiest to use in the future if you are not comfortable with programming.

As a side note:
If you are interested in developing your own software you can review the lasershark and twostep communication code here:
https://github.com/macpod/lasershark_3dp/