LAOS - Laser Open Source: Issueshttps://redmine.laoslaser.org/https://redmine.laoslaser.org/favicon.ico?16780521372013-03-18T21:46:41ZLAOS - Laser Open Source
Redmine LAOS Laser - Bug #80 (Closed): Use other transport instead of TFTPhttps://redmine.laoslaser.org/issues/802013-03-18T21:46:41Zpeterpbrier@dds.nl
<p>TFTP is unreliable on some networks. <br />It is using UDP and not a TCP socket.<br />Options:<br />1) Change to a plain socket interface<br />2) Use simple HTTP server and protocol (more code/overhead, but has the option of hosting a web interface to download and view jobs)</p>
<p>For option 1 there needs to be some protocol to send metadata (like the job name to show on the display).<br />It could be simply the first line of the file, or lines that start with ";;" or something similar.</p> LAOS Laser - Bug #66 (Closed): Laser is ON at boothttps://redmine.laoslaser.org/issues/662012-12-29T17:39:59Zpeterpbrier@dds.nl
<p>The laser output can be switched ON when booting.</p> LAOS Laser - Feature #65 (Closed): Show the outline of the drawinghttps://redmine.laoslaser.org/issues/652012-12-29T17:24:25Zpeterpbrier@dds.nl
<p>The outline of the drawing is stored in the file (when using CUPS).<br />The laser should have a "preview mode" where it scans the outline to check the positioning of the drawing on the substrate.</p> LAOS Laser - Bug #64 (Closed): Make jogging and origin work as expectedhttps://redmine.laoslaser.org/issues/642012-12-29T17:23:05Zpeterpbrier@dds.nl
Currently jogging does not work.
<ul>
<li>Allow to jog diagonally (this required changes to the I2C display firmware)</li>
<li>Set origin does not work (nothing happens at the moment, it should set the new origin for the drawing)</li>
</ul> LAOS Laser - Bug #57 (Closed): Printing from Inkscape via CUPS driver generates incorrect lines (...https://redmine.laoslaser.org/issues/572012-11-16T23:09:57Zpeterpbrier@dds.nl
<p>When printing from visicut, lines are generated from the end of all sub-paths to the origin (corner) of the path.</p>
<p>Quick solution: ungroup all shapes, paths and break apart (so no subpaths are present)<br />Correct solution: Fix PS2EDIT/LAOS driver to correctly handle sub-paths</p> LAOS Laser - Bug #56 (Closed): Delete all files from SVN, and make binaries available via githubhttps://redmine.laoslaser.org/issues/562012-10-07T11:57:24Zpeterpbrier@dds.nl
<p>Currently the "official" binaries are on SVN. Remove the SVN server and make binaries available<br />via github, that match a specific source-code version.</p> LAOS Laser - Bug #55 (Closed): Delete old wikihttps://redmine.laoslaser.org/issues/552012-10-07T11:53:40Zpeterpbrier@dds.nl
<p>Check if all information is on the new redmine site, and delete old wiki</p> LAOS Laser - Feature #54 (Rejected): pull-up resistors on PWM opto out signalshttps://redmine.laoslaser.org/issues/542012-10-01T23:03:38Zpeterpbrier@dds.nl
<p>Depending on the laser power supply, it may be needed to pull-up the PWM signal to +5V (e.g. 1kOhm)<br />as there is a too-weak pullup in the laser power supply. The weak pull up will lead to non-linear power response<br />to PWM dutycycle.</p>
<p>Provide schematics for the connection of the laser power supply.</p> LAOS Laser - Bug #52 (Closed): Decoupling of the stepper driveshttps://redmine.laoslaser.org/issues/522012-10-01T22:07:59Zpeterpbrier@dds.nl
<p>The stepstick drives are prone to oscillate when driving capacitive loads (long cables) at high current setting.<br />a 100uF electrolytic capacitor close to the drive can overcome that problem.</p>
<p>Solution: provide a footprint underneath the pololu (between the contact rows) for a 100uF capacitor. <br />A radial capacitor can be bent 90degrees and placed under the driver (same solution as on ultimaker board).<br />The 4th axis does not need this (that is close to the power connector and there is no space due to the FFC connector).</p> LAOS Laser - Bug #48 (Closed): More information on the silkscreenhttps://redmine.laoslaser.org/issues/482012-09-30T14:05:10Zpeterpbrier@dds.nl
<p>Provide more info on the silkscreen:<br />- Pin functions of the pololus/stepstick<br />- Pin number and functions of the MBED</p>
<p>The LAOS logo!</p> LAOS Laser - Bug #43 (Closed): Make Laos compile on GCC4MBEDhttps://redmine.laoslaser.org/issues/432012-09-15T22:19:35Zpeterpbrier@dds.nl
<p>Make the code compile on GCC4MBED. Not requiring the online compiler</p>
<p>See this discussion: <a class="external" href="http://redmine.laoslaser.org/boards/3/topics/12">http://redmine.laoslaser.org/boards/3/topics/12</a></p> LAOS Laser - Feature #16 (Closed): Binary distribution of the CUPS-Laos driver and PSTOEDIT for w...https://redmine.laoslaser.org/issues/162012-07-20T00:00:37Zpeterpbrier@dds.nl
<p>A pre-compiled package (ZIP or debian package) should be made for simple installation.<br />Compiled for 32 and 64 bit on all systems.</p> LAOS Laser - Feature #15 (Closed): Stand-alone CUPS-laos server on openWRT or RaspberyPihttps://redmine.laoslaser.org/issues/152012-07-19T23:59:10Zpeterpbrier@dds.nl
<p>A stand-alone WiFi router (OpenWRT) or embedded linux board (e.g. Raspbery PI) could act as a true LAOS Postscript network printer,<br />A standard distribution (OS+Driver) could be made to allow plug-and-play operation.</p> LAOS Laser - Feature #14 (Closed): Change laser PWM control: rewrite using own PWM functionhttps://redmine.laoslaser.org/issues/142012-07-19T23:06:34Zpeterpbrier@dds.nl
<p>The Laser PWM control currently uses the MBED libary PWM functions:<br /><a class="external" href="http://mbed.org/handbook/PwmOut">http://mbed.org/handbook/PwmOut</a></p>
<p>The PWM function has some limitations: It is limited to the PWM1 outputs, <br />The initial state of the output cannot be set and floating point is used in the implementation to set the PWM duration.</p>
<p>A new object LaosPWM() should be implemented, that allows more flexibility.</p>
<p>Constructor: LaosPWM(pin,freq,initialpwm)<br />methods: write(pwm), read()</p>
Requirements;
<ul>
<li>it should use CMSIS and the NXP peripheral library.</li>
<li>Initially it should function for PWM1 peripheral (similar to current PWM), pin can be p21..p26</li>
<li>PWM value should be in range of 0 to 10000 for 0 to 100%</li>
<li>Writing should be fast (low overhead),inline function</li>
<li>Clipping of set value between 0 and 100%</li>
<li>Writing should be double buffered (no glitches)</li>
</ul>