Gorka,
This is the blind leading the blind, but I suspect you're in
luck...
Eric Norum has written a really nice tutorial:
http://www.aps.anl.gov/epics/modules/soft/asyn/R4-12/HowToDoSerial/tutorial.pdf
which contains gems such as this one:
"If you’re using a
serial line directly attached to the IOC you need something like:
drvAsynSerialPortConfigure("L0","/dev/ttyS0",0,0,0)
asynSetOption("L0", -1, "baud", "9600")
asynSetOption("L0", -1, "bits", "8")
[..]"
IOW, a lot of your work is already done.
You don't "need" SynApps, but you will need ASYN.
I found the terminology a little confusing at times, but
it mostly means there is a ton of useful stuff available.
Specifically, I believe you will be using devGPIB, and it took
me a while to figure out which part of it is actually GPIB specific, and which
part has GPIB in the nomclature for historic reasons. You'll see what I
mean when you dig into it.
Cheers -Mathias
Hi
all,
I’m
newbie to EPICS and I need some help to start using it. I’m trying to develop
an IOC based on a Windows XP PC. I have already build EPICS Base 3.14.9 with
win32-x86 architecture and execute the “Example IOC Application” and “Channel
Access Host Example” from the Application Developers Guide.
Now,
I would like to connect a card to the IOC (PC) via RS-232. I think I need the
Asyn interface from SynApps. But, I have no clear how to do it. I have to
program something or a generic support for any RS-232 connection is already
made? Does it change depending on the card to be used? What would I need?
Record, Device and Driver support? Some of those? One of those? Maybe, another
solution…
On
the other hand, when I have to develop the database? Before or after record/driver/device
support? How to do it simply and fast?
Thanks
in advance
Gorka