ATTENDEES:
Till, Tom, Terri, Stephanie, Debbie, Qing, Sonya, Ernest, Kukhee, Diane
NOTES:
My notes are pretty cryptic. Please feel free to email additions or add to the wiki page.
suggestion - it would be great to get the diagrams with even greater detail, including EVR interface, MPS, BSA
suggestion - we should eventually get all diagnostic devices onto this network, could be used as source for BSA
the room agreed that the function-ptr table was the best option for choosing the 'flavor' of udpComm for each bpm ioc.
Steph and Till have a couple BSA related items to discuss off-line. Changes to the EVR modifiers and possible ways to speed up BSA processing. Just a reminder here...
Till pointed out that in the current design, if a BPM does not work, then the entire packet of BPM data will not be sent. This may not be much of a problem for feedbacks but on further thought it would not be very good for most other use cases - BSA for example. It is worth the time to try to devise a not-to-difficult scheme that will allow the data from the working BPMs to be delivered.
Till or Sonya needs to set the timestamp TSE = -2 or something like that...
It was agreed that the subnet should be called FNET (Fast Net; lclsfnet) and DNS names for FCOM should use -fnet, not -fbck, since this subnet may be used for more than just fast feedback.
ACTION ITEMS:
FCOM IDs and blobs
- Debbie and Diane - publish pvname-to-FcomID mapping and API for fast feedback IOCs
- Debbie - implement the above API as shareable module
- Till - you will be first to produce a shareable header file containing structure(s) defining the order of data in an fcom blob
- Terri, Till, Antonio - work out an acceptable range for FCOM multicast IDs
DNS names for 2nd NIC
- Sonya, Kukhee, Sheng/Qing - fill out DNS name request forms for all their subsystem IOCs and EIOCs 2nd NIC:name format to be <current ioc-name>-fnet eg: ioc-in20-bp01-fnet
- Terri - change the DNS names for IOCs previously assigned; from <ioc-name>-fbck to <ioc-name>-fnet
Status
- Till - pursue a not-too-difficult (timeout?) scheme for the BPM IOC to send out data even when one (or more) BPM is not working
- Till- propose a list of statuses that the BPMs could report with a blob of data.
Mcast ID for vme-coldfire communications
- Till, Kukhee, Sonya, Sheng/Qing - by email, work out a scheme for mapping the vmes & coldfires to multicast group IDs. Define the API and how it will be implemented - in the start-up script? Define a dns name naming convention for these multicast groups. Till please get this going by emailing your suggestions.
- Diane - formally document the vme-coldfire communications scheme and DNS naming conventions
udpComm
- Till - use the function-ptr table to udpComm approach
- Till - make udpComm shareable, it should be used by RF, BLEN, MPS subsystems - work with Stephen Norum...