Re: Some questions about CaLab (Dariush Hampai)

[Carsten Winkler via Tech-talk <tech-talk at aps.anl.gov>]

The CA Lab does not have a function for writing multiple fields in a single channel access command.

Fields are written by adding the field name with a dot.

If you need to write to multiple fields, you can use array parameters as follows:

Carsten

Am 20.06.2025 um 21:02 schrieb tech-talk-request at aps.anl.gov:

> Send Tech-talk mailing list submissions to
> 	tech-talk at aps.anl.gov
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://mailman.aps.anl.gov/mailman/listinfo/tech-talk
> or, via email, send a message with subject or body 'help' to
> 	tech-talk-request at aps.anl.gov
>
> You can reach the person managing the list at
> 	tech-talk-owner at aps.anl.gov
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Tech-talk digest..."
>
>
> Today's Topics:
>
>    1. Re: Problem with Newport CONEX-AGAP FTDI device on Linux
>       (James P. Withrow)
>    2. Re: Problem with Newport CONEX-AGAP FTDI device on Linux
>       (Dmitry Yu. Bolkhovityanov)
>    3. Some questions about CaLab (Dariush Hampai)
>    4. RE: Problem with Newport CONEX-AGAP FTDI device on Linux
>       (Mark Rivers)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 20 Jun 2025 17:18:51 +0000
> From: "James P. Withrow" <jwithrow at cornell.edu>
> To: Mark Rivers <rivers at cars.uchicago.edu>
> Cc: tech-talk EPICS <tech-talk at aps.anl.gov>
> Subject: Re: Problem with Newport CONEX-AGAP FTDI device on Linux
> Message-ID: <EB8D328B-F88B-4848-8B6D-487C9884AA09 at cornell.edu>
> Content-Type: text/plain; charset="utf-8"
>
> Mark -
>
> It looks like the issue may be that the VID/PID pair (particularly the PID) may not be included in the currently running ftdi_sio driver.
>
> A quick Google search turned up this incantation, which may be helpful:
>
>
> echo "<VID> <PID>" >  /sys/bus/usb-serial/drivers/ftdi_sio/new_id
>
> Untested, as I?m out of the office, but hopefully this may point you in the correct direction.
>
> -Jim Withrow
>
> Sent from my iPhone
>
> On Jun 20, 2025, at 11:52, Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> wrote:
>
> 62363.524320] usb 1-4: new full-speed USB device number 11 using xhci_hcd
> [62363.655966] usb 1-4: New USB device found, idVendor=104d, idProduct=3008, bcdDevice= 6.00
> [62363.655975] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [62363.655978] usb 1-4: Product: CONEX-AGAP
> [62363.655980] usb 1-4: Manufacturer: Newport
> [62363.655982] usb 1-4: SerialNumber: A694ND5H
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.aps.anl.gov/pipermail/tech-talk/attachments/20250620/5e715c9a/attachment.html>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 21 Jun 2025 00:19:39 +0700 (+07)
> From: "Dmitry Yu. Bolkhovityanov" <D.Yu.Bolkhovityanov at inp.nsk.su>
> To: Mark Rivers <rivers at cars.uchicago.edu>
> Cc: EPICS tech-talk <tech-talk at aps.anl.gov>
> Subject: Re: Problem with Newport CONEX-AGAP FTDI device on Linux
> Message-ID: <7d7eabd-831f-f51e-dc60-161ba8b28cc at starnew.inp.nsk.su>
> Content-Type: text/plain; charset="US-ASCII"; format=flowed
>
> Hi Mark!
>
> I suppose the problem is in product's ID.
>
> Newport-CONEX-AGP's "idProduct=3006" *is* listed among supported IDs in 
> ftdi_sio_ids.h, see https://urldefense.us/v3/__https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/usb/serial/ftdi_sio_ids.h?h=v6.16-rc2__;!!G_uCfscf7eWS!cEIzCUjhW53L-KKEAV3e3SDEZCubl_LXE7ev4lxhWZfS5l5_fb1Uvx73nAo1Qmei1z1rHE3YjXYUZg_-sksd1QU4UU-cxedRxvU$ 
>
> #define NEWPORT_CONEX_AGP_PID		0x3006
>
> (and in ftdi_sio.c driver too)
>
> while CONEX-AGAP's "idProduct=3008" is not, even in the latest kernel 
> version 6.16 (AFAIR, RHEL9 uses Linux kernet 5.14).
>
>
> With best regards,
> Dmitry
>
>
>
> On Fri, 20 Jun 2025, Mark Rivers via Tech-talk wrote:
>
> > Folks,
> >
> > I have an older Newport-CONEX-AGP controller that works fine on Linux.
> > https://urldefense.us/v3/__https://www.newport.com/f/agilis-piezo-linear-stage-with-conex-controller__;!!G_uCfscf7eWS!esBpnKdccckn_TlnsWE5ruJncpjWNfxHfi8SNZ2M5qWp8ab4wjlgsB18EO_4YOzuwREd1qW6ipequMg2cHFGxsaFyd4$
> >
> > The device has a USB interface and uses FTDI.  When I plug in the device on my RHEL 9 machine I see these messages in dmesg:
> >
> > [62289.315988] usb 1-4: new full-speed USB device number 10 using xhci_hcd
> > [62289.447505] usb 1-4: New USB device found, idVendor=104d, idProduct=3006, bcdDevice= 6.00
> > [62289.447514] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> > [62289.447518] usb 1-4: Product: CONEX-AGP
> > [62289.447520] usb 1-4: Manufacturer: Newport
> > [62289.447522] usb 1-4: SerialNumber: A6UJN7YS
> > [62289.450490] ftdi_sio 1-4:1.0: FTDI USB Serial Device converter detected
> > [62289.450536] usb 1-4: Detected FT232R
> > [62289.451085] usb 1-4: FTDI USB Serial Device converter now attached to ttyUSB0
> >
> > The device is now available on /dev/ttyUSB0.
> >
> > I expected to be able to do the same thing with a newer CONEX-AGAP controller.
> > https://urldefense.us/v3/__https://www.newport.com/f/conex-piezo-absolute-positioning-mirror-mount__;!!G_uCfscf7eWS!esBpnKdccckn_TlnsWE5ruJncpjWNfxHfi8SNZ2M5qWp8ab4wjlgsB18EO_4YOzuwREd1qW6ipequMg2cHFG2VO-mdQ$
> >
> > However, when I plug in the device on my RHEL 9 machine I see these messages in dmesg:
> >
> > [62360.327898] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
> > [62360.327934] ftdi_sio 1-4:1.0: device disconnected
> > [62363.524320] usb 1-4: new full-speed USB device number 11 using xhci_hcd
> > [62363.655966] usb 1-4: New USB device found, idVendor=104d, idProduct=3008, bcdDevice= 6.00
> > [62363.655975] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> > [62363.655978] usb 1-4: Product: CONEX-AGAP
> > [62363.655980] usb 1-4: Manufacturer: Newport
> > [62363.655982] usb 1-4: SerialNumber: A694ND5H
> >
> > Note that I do not get the messages about ftdi_sio detected or the message about attaching to ttyUSBx.
> >
> > The new CONEX-AGAP works fine on Windows, where it appears as a COM port.  I can configure the COM port with EPICS:
> >
> > drvAsynSerialPortConfigure("serial1", "COM5", 0, 0, 0)
> > asynOctetSetInputEos("serial1",0,"\r\n")
> > asynOctetSetOutputEos("serial1",0,"\r\n")
> > asynSetOption("serial1",0,"baud","921600")
> > asynSetOption("serial1",0,"bits","8")
> > asynSetOption("serial1",0,"stop","1")
> > asynSetOption("serial1",0,"parity","none")
> > asynSetOption("serial1",0,"clocal","Y")
> > asynSetOption("serial1",0,"crtscts","N")
> >
> > Given the behavior on Windows, I think the CONEX-AGAP is also an FTDI device.  But if so, then why is Linux not recognizing it as such?
> >
> > Thanks,
> > Mark
> >
> >
> >       
>  	_________________________________________
>  	  Dmitry Yu. Bolkhovityanov
>  	  The Budker Institute of Nuclear Physics
>  	  Novosibirsk, Russia
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 20 Jun 2025 17:27:15 +0200
> From: Dariush Hampai <dariush.hampai at lnf.infn.it>
> To: tech-talk at aps.anl.gov
> Subject: Some questions about CaLab
> Message-ID: <239527c2-f231-4cea-b327-d81f47d38a06 at lnf.infn.it>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Hi all,
> I have some problems with CaLab, necessary to integrate epics with a 
> LabView interface. In particular now I have two big problems:
> 1) i don't understand how to use multiple field in the same CA. For 
> example, my newport IOC includes some records of the type
> mm4006:m11.HOMF
> mm4006:m11.MOVN
> etc...
> CaLab Put.vi does not include the field. What do I do? if I put (for 
> example) mm4006:m11.HOMF and mm4006:m11.MOVN as PV I find two distinct 
> PVs...
> 2) I am trying to generate a monitor of the various IOCs. When starting 
> LabView there is no PV (via CaLab info.vi). If I start the IOCs I see 
> the PVs. However if I stop the IOCs, via command prompt (caget etc...) I 
> do not see (obviously) the active CA, while via CaLab info.vi the CA are 
> still active and give me the last values read. Even after a reset of PV, 
> using CaLab_Disconnect.vi, I still see the active CAs with the last 
> value read. Where am I going wrong?
>
> Dariush
>
>

Attachment: smime.p7s
Description: Kryptografische S/MIME-Signatur