Re: PiezoSytemJena motorcontroller driver problems

[Eric Norum <eric@norum.ca>]

Just a note -- if you specify COM at the end of the host information in the drvAsynIPPortConfigure command you can then set up the serial line parameters from within the st.cmd script, e.g.:

drvAsynIPPortConfigure("L0","serials8n3:4004 COM",0,0,0)

asynSetOption("L0", -1, "baud", "19200")

asynSetOption("L0", -1, "bits", "8")

asynSetOption("L0", -1, "parity", "none")

asynSetOption("L0", -1, "stop", "1")

asynSetOption("L0", -1, "clocal", "Y")

asynSetOption("L0", -1, "crtscts", "N")

On Oct 4, 2013, at 11:51 AM, "Ivashkevych, Oksana" <oksana@bnl.gov> wrote:

Hi,

                I would like to report that I successfully integrated and tested Joe Sullivan driver with d-Drive from Piezo System Jena pretty painlessly after sorting out serial communication issues. The driver takes care of special characters Jena sends at the beginning and at the end. README is a copy and paste pleasure, and descriptive enough about what is implemented and what is not.

 

For people like me integrating the motor driver for the first time I leave the paragraph below:

                It is important to create a simple serial device IOC with at least one command in proto file, just to make sure the communication part is working. In my situation, I spend the lion portion of the total time figuring out and setting the correct serial parameters on MOXA switch.

 

Sorry Ken, I didn’t look at your driver, just because this one worked.

 

Thanks for help,

 

 

-- 
Eric Norum
eric@norum.ca