Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Macpod

Pages: [1] 2 3 ... 12
1
General Discussion / Re: About the Lasershark projector
« on: September 19, 2018, 01:51:04 PM »
For a prototype you could use wood/screws and thin cardboard (i.e. cereal box) to shim/align items. If you have access to a 3-d printer you could design a mount that way.

I personally have not used openlase under windows 10. I have also only compiled lasershark_jack for Linux which is needed to use a LaserShark with OpenLase.

While it is important to match PSU voltages it is not a problem if your power supply can supply more current than the laser/etc designate. Normally when I spec I PSU for a project I make sure the current rating is at least 20% higher than what the circuit calls for.


2
General Discussion / Re: About the Lasershark projector
« on: September 13, 2018, 11:54:34 PM »
A TTL laser will let you turn the laser on or off. An analog laser will let you make the laser brighter or dimmer. This is useful as it would allow you to have different line brightnesses in a lasershow. For example if you spelled out LASER, you could make the L very bright while the R could be made very dimm.

You can also make the laser look brighter or dimmer by turning it on/off very quickly with a ttl laser too but to make this happen with a lasershark you would need more hardware.


Quote
2.Emitter subsystem: At first we found this.520nm Green Laser Diode Module
It is straightly powered by a DC input power supply optional. But we found that it has no TTL modulation or analog modulation.
While you could use this laser, it would have to always be on (because there is no way for the lasershark to control it). I would not recommend this as the beam can still look very bright if the galvos are not moving. There will also be traces between shapes

Quote
And here are some other alternative lasers(feels hard to find a 5mW or about ones. ):
     1.w/12V AC Adapter 515nm 520nm 50mw Grass Green Laser LINE Module Osram LD TTL
This is a line laser module As opposed to drawing a dot, it draws a line. You would not want this

Quote
     2.10mW 515-520nm Direct Diode Green Laser Module (Adjustable Focus) with TTL Modulation (12V)
This one would be OK. It is greater than 5mW and would require a variance in the U.S. in some use scenarios. To make it dimmer you may be able to adjust the potentiometer but be careful as you can also make it brighter if you turn it the wrong way. You may find the block-format the laser is in very helpful for mounting reasons (you will have to align the laser with the galvo mirrors carefully)

I like that this unit has a fan too. I also see LaserLands sells these for a little cheaper (this is not an endorsement for laserlands):
https://www.laserlands.net/diode-laser-module/520nm-laser-module/3350-520d.html

They also have a 20mW laser that could likely be dialed down power-wise 20mW would still be very bright for your application:
https://www.laserlands.net/diode-laser-module/520nm-laser-module/focusable-515nm-20mw-green-laser-module-osram-ld-in-12v.html


Quote
3.Scanning subsystem:
     1.40Kpps High Speed galvo scanner for laser show lighting/RGB Laser system ScannerIt says that it acquires the "Deflection angle: max 70 optical (factory calibration @25)" and we are not sure whether it is enough to project patterns in the height of 1-1.5m to the 2-3m far distance from where it is set.

     2.
30Kpps HightSpeed Galvo scanner for Laser light show or 3D printer (max50Kpps)

It looks like that all the galvos detailers have the similar description of the spec details



I would recommend using geometry compute how wide a scan angle you need. Both of these galvos kits seem more expensive than they should be.

Quote
4.And some cables or board to set them up. Or maybe a laser glasses?

Safety glasses are a great idea. You will need to purchase glasses according to the wavelength of light you will be using. They usually protect against one or more ranges. I.e these pair covers 190-540nm with an OD5 rating:
https://www.survivallaser.com/Eagle_Pair_190540nm_OD5_Standard_Laser_Safety_Goggles/p556088_2780808.aspx

Frequently the galvos kits come with the cables to connect the gavo amplifiers to the Lasershark. I would reccomend waiting for those to come in before buying cables. You should start thinking about making a mount to align the laser with the galvo mirrors.



3
General Discussion / Re: About the Lasershark projector
« on: September 09, 2018, 12:16:28 PM »
In the U.S. anything 5mW and over requires a variance. A 400mW laser would not be responsible to use in this application as it is both extremely dangerous and far too bright to look at!

For experimentation I would suggest a 4.999mW 520nm laser. I would suggest a 520nm direct drive vs a 532nm DPSS laser as you do not need to worry about leaky infrared light:
https://www.youtube.com/watch?v=iR1Ku5dnbH8
532DPSS lasers are also sensitive to temperature and can take a while to heat up if operated in a cold environment. 
Human eyes are particularly sensitive to green light so you do not need much (In a darker room I have used a 520nm projected on a projection screen 5M away to demonstrate lasers to students).

Galvos are usually sold as a kit consisting of the galvo, galvo amplifier, and power supply so you will not need to worry about matching these. You will need to determine the necessary KPPS (kilo-points per second) rating of the galvo. This will be dependent on how complex your shapes are. The faster the galvos are, the more traces per second you can draw and this will reduce "flickering" of the images.
Since you will be projecting images onto a surface in close proximity to the ground you will also need to account for the maximum galvo angle your galvos support.

4
General Discussion / Re: About the Lasershark projector
« on: September 06, 2018, 10:27:09 PM »
Hi, thanks for re-posting this on the forums. Answering the question in the public forums helps others searching for this information to find it.

Unfortunately I do not sell full projectors. This would classify me as a laser projector manufacturer and significantly increases requirements such as the need to handle laser variances.
Speaking of this, for your application, please verify that for your application your projector work follows all necessary laws and regulations in your area.

I am happy to review components if you post them here to determine if they will work or not.

Can you describe in more detail the complexity of these images you would like to trace? Do you have examples? This will impact the speed requirements of your galvos.

Do you also know what surface you will project onto, how far away this surface will be, the brightness of the room, and finally the laser colors you wish to use?


5
3D Printers / Re: First test run
« on: August 13, 2018, 09:01:54 PM »
Hi again, I was out at defcon and wasn't checking this. Glad to hear you found your wiring problem.

For lasershark_stdin_displayimage what is your current problem? The image must be less than or equal to 4096x4096 pixels in size. If you run lasershark_stdin_displayimage with -h help will be printed out

Since you are using a ttl laser you will want to use the monochrome mode. The following will display a png named test.png at 10,000 kpps in monochrome. to use a syntax like
Code: [Select]
lasershark_stdin_displayimage -p test.png -r 10 -m

I would suggest printing a black and white checker board pattern for testing. If you have a smartphone/camera you can use a long-exposure app to get a more complete (and very neat) looking photo :)

6
3D Printers / Re: First test run
« on: August 04, 2018, 07:11:25 PM »
Glad you got the galvo part working but I do not think the galvo swap should have been necessary.

Are you using the pre-compiled lasershark_stdin.exe and lasershark_circlemaker.exe for windows? I'm concerned about the B channel working but the C channel not.

If you look at the circlemaker code:
https://github.com/macpod/lasershark_hostapp/blob/master/lasershark_stdin_circlemaker.c
Each line is drawn where A is set to 4095 (max), B is set to 4095 (max), and C is set to 1 (max) This should cause a laser connected to any of these channels to turn on.
Code: [Select]
printf("s=%u,%u,%u,%u,%u,%u\n",
         float_to_lasershark_xy(x_f),  float_to_lasershark_xy(y_f), 4095,4095,1,1); // x, y, a, b, c, intl_a

If you have the lasershark plugged in but not running, what is the voltage between the C channel + and GND pins? (It should be close to if not 0v).
If you pipe circlemaker into lasershark_stdin and probe, what is the voltage between the C channel+ and GND pins? (It should be close to 5v).

I will help you with the lasershark_displayimage debugging after we get this solved. Trying to diagnose displayimage without first resolving circlemaker adds unknowns which makes debugging the overall problem more complex.

7
3D Printers / Re: First test run
« on: August 03, 2018, 10:34:46 PM »
Quote from: sla_newbie
I have a concern in my power supply I am using  galvo drivers that takes 15V as input and the laser driver takes 12V input. So is anything wrong with the power supply I am using?
It is perfectly fine to use several voltage supplies of different values (i.e. one 15v supply for the galvos and one 12v supply for the laser diode driver board).

Quote from: sla_newbie
the laser is always ON before operation and even after operation.
The LaserShark pulls A/B/C lines low when the data buffer is empty (i.e. before  and after circlemaker is run). The laser should turn off when the ttl + line is pulled low and turn on when the ttl + line is puled high.
Are you sure the lines between the LaserShark C header and Laser A-13 TTL header are correct? I can't see what colors are going to what pins from the pictures.


Quote from: sla_newbie
1. Also when I pipe circlemaker to stdin the mirrors are moving too fast and no image is being projected (Maybe I am overdriving the mirrors like you said. I am looking to replace the galvo setup to 20kpps)
The LaserShark should still work with your galvos. No need to replace them yet. Just know they won't be as fast. In your application it may not matter.

Does your laser stay on if the ttl pins are plugged in? What image is drawn via the laser if so with circlemaker? I need to see what is being drawn (even if wrong) to diagnose the problem.

Are you using the pre-compiled lasershark_stdin.exe and lasershark_circlemaker.exe for windows?

8
3D Printers / Re: First test run
« on: July 31, 2018, 07:57:25 PM »
I mentioned the kpps rating as I see from your output you are running at a rate of 20,000kpps. For circlemaker that is probably fine but for the displayimage app you may need to reduce that.

1. To start diagnostics, lets focus on the laser on/off state. The laser should be off before you run circlemaker and should turn off after you stop circlemaker. If it is not, something is not wired correctly. Did you solder the provided polarized headers to the LaserShark board and connect wire? Did you verify gnd is going to gnd and the other line is going to +?

2. For diagnostics lets just stick with the circlemaker output. If everything works as expected this should draw a circle. What do you currently see drawn? Have you verified the laser is properly reflecting from one mirror to the other? If it does not draw a circle, what does the output look like?

9
3D Printers / Re: First test run
« on: July 29, 2018, 01:48:11 PM »
I do not believe you have been sold 20k galvos. Normally the mirrors on higher-speed galvos are smaller and trimmed at the corners to reduce weight and allow faster speed operation. I suspect these are 10/15K galvos

It is normal for galvos to heat up but not excessively so. Perhaps a better metric to determine if the galvos are being over-driven is the sound. If it sounds bad/scratchy/etc it is :)

Based on your other post I see you have compiled the lasershark host applications yourself. Have you tried piping in the circlemaker input into lasershark_stdin? This would be a good test to make sure lasershark_stdin has been compiled properly.

 

10
3D Printers / Re: Using lasershark_stdin_displayimage
« on: July 29, 2018, 01:40:49 PM »
Hi, I was on vacation. Glad you figured it out

For others who search this topic these errors indicate functions necessary for the program to operate were not found and this is because they were not compiled. There is a Makefile included and this should be used to compile. Ideally you should use a Linux vs Windows OS too.

11
Hi CupOfTea,

Thanks for posting your modified code for others to review/modify! Those are some interesting print lines. :)

12
3D Printers / Re: LaserShark Wiring Questions
« on: June 25, 2018, 08:46:30 PM »
Hello,

Your wiring looks like you have everything OK. In case you missed them, check the lasershark packaging for connectors for the galvos, they should have been wrapped in blue painter tape. Also, it is fine if you connect the ttl input to port A. B is also fine too.


13
3D Printers / Re: New to lasers and SLA and need some info
« on: March 31, 2018, 05:46:47 PM »

Maybe I should phrase this differently. Since you have a much stronger knowledge of galvos, and coding and all the areas where I'm lacking, if someone came to you and said "I have this galvo head (the one I included the manual for in the last post) can you turn it into a laser sla 3d printer?" How would you go about it? Would you prefer a digital or analogue head since it can come as either one? What are the missing components and where would I source them in order to pull it all together.

With my limited knowledge and experience it seems like the best way would be to find some way to reconfigure a basic marlin/repetier firmware to drive a galvo instead of steppers on the XY axis, and swap the extruder bits for laser ttl on/off commands, and just use a ramps board to do it all. But I have no idea how to go about doing that, and I don't want to have to manually modify massive amounts of Gcode manually before doing a print. The solutions are definitely out there because people are doing it fairly inexpensively. I just keep running into brick walls, so maybe I need to take a whole new approach all together.
I would probably go with a digital head if it wasn't significantly more money and after I determined the speed would be sufficient (vs an analog head). Before I purchased anything I would make sure software existed and if not write the software.

There are two software approaches, one is to modify a slicer to export images, then draw pixel by pixel. The other means is to make a g-code to x-y point converter and use that in conjunction with either an xy2-100 head (easier and already integrated in) or lasershark board attached to an analog head (maybe faster).

14
3D Printers / Re: New to lasers and SLA and need some info
« on: March 29, 2018, 11:56:39 PM »
Sorry, I totally forgot to include the datasheet/manual they sent me with the stats on it. It seems like if it can interpret the digital signals, that it would already have a similar board type thing in the head, but I could be wrong. If not, I think going to the lasershark route is definitely the best and simplest way to go. I'm probably going to be purchasing the CW software license since that looks like the smoothest way to itegrate everything since I'm already way out of my knowledge base on this one.
It should for a digital head. The logic board I am referring to that would attach to an Arduino/etc would be for the purpose of level shifting (think 3.3v to 5v TTL Level conversion or TTL to RS232.. very simple/common) vs a processing or analog to digital module.

Before purchasing a copy of CW make I would encourage you to reach out to the developer to verify it still supports the LaserShark. CW used to be freely downloadable and supported the LaserShark but this support was removed and the product went to a license-based model. According to another post on this forum the LaserShark is not supported by the latest CW.

15
It looks like something changed with gcc and I'll need to update the code to have it compile.

In the meantime in the Makefile you can remove "lasershark_twostep" from the following line and run make again. This should build everything fine:
all: lasershark_jack lasershark_stdin lasershark_stdin_circlemaker lasershark_stdin_displayimage lasershark_twostep

I'll try and fix this gcc issue this weekend but since you probably don't have a twostep board the result likely won't matter much for you

edit: I have removed the inlines and corrected some code that was throwing warning too as a bonus :)

Pages: [1] 2 3 ... 12