Jim,
Thank you for your quick answer. I have the latest (0.13.1 - 2012-09-18)
version of ScanLab's RTC5 driver installed and running. As said, my
homegrown application works well.
Of course, when I use BeamConstruct, no other RTC-using app is running.
My app configures the output power on 8 bits, with bit 2 being the
signal bit (inverted).
So within BeamConstruct project properties, I set Laserport 1 (8 bit) as
the Output Port, with bit 2 as output number.
In the card configuration panel, I set the correction file and firmware
directory that work well with my app (here is the bug I wrote about: the
textfield does not take the whole path when picking the directory
graphically).
I left power output to none, since one cannot set the power output to
Laserport 1 in both places.
And finally I followed the tuto in the manual to get a triangle lasered.
Hereby another question: how are the power (pen) parameters passed on to
the laser? In my app, I use a serial port, but in BeamConstruct, I did
not found any such configuration panel.
Best regards,
Axel
Le 20.11.12 06:59, Jim Hart a écrit :
Axel,
there are some preconditions required in order to get it working:
- you have to compile and install the kernel-modules (provided by Scanlab)
- you have to copy the libslrtc5.so (provided by Scanlab) to a
lib-directory where it can be accessed by applications (check
ldconfig)
- the device needs to be user read- and writeable (which isn't by
default policies)
If all these conditions are met and you still have troubles please let
me know, then I'll provide a special debugging version of the RTC5
plug-in to you that will tell us a bit more.
Kind regards
Jim
On 19/11/2012, Axel von Arnim <a.vonarnim(a)frewitt.com> wrote:
> Hi there,
>
> Having followed the manual and configured the RTC5 card in the
> Project/Settings, I keep on having a "Can't allocate required
resources"
> error when calling the "Mark" dialog.
>
> I have Fedora 17 and the latest OpenAPC.
> I gave the correct firmware path (where the .dat resides), and the right
> correction files and output port, as configured in my other working
> in-house program.
>
> I saw there is some kind of bug: when I choose the firmware directory
> graphically, it is not reported in the textfield. I have to write it by
> hand. Is it possible that something is not take into account there? Is
> there a way to see the config/project file contents to check that
> everything is right?
>
> Best regards
>
> Axel
>
> _______________________________________________
> openapc mailing list
> openapc(a)lists.fedorahosted.org
>
https://lists.fedorahosted.org/mailman/listinfo/openapc
>