You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Part of #2
An initial target of the PMAC simulation is to have a ticket device that can trick EPICS into thinking it is connected to a real PMAC to the extent that an IOC can be started against it. For this, no simulation logic is needed, we just need to have the device respond to IOC start up/status commands in such a way that the IOC doesn't immediately break.
This will require DiamondLightSource/tickit#80 to strip off the 8 byte headers from EPICS PMAC commands within the message interpreter. EPICS sends multiple commands in a single message, so DiamondLightSource/tickit#82 will also be needed to split up each message into the individual commands within the device's message interpreter.
The text was updated successfully, but these errors were encountered:
* Updated 'Creating a Simulation' configuration file to be correct; some typos corrected
* Edited formatting and typos
* Changed the 'Creating a Device' page Shutter object to use the correct update time statement
* Fixed typo
* Update docs/tutorials/creating-a-device.rst
Co-authored-by: Garry O'Donnell <[email protected]>
Co-authored-by: Garry O'Donnell <[email protected]>
Part of #2
An initial target of the PMAC simulation is to have a ticket device that can trick EPICS into thinking it is connected to a real PMAC to the extent that an IOC can be started against it. For this, no simulation logic is needed, we just need to have the device respond to IOC start up/status commands in such a way that the IOC doesn't immediately break.
This will require DiamondLightSource/tickit#80 to strip off the 8 byte headers from EPICS PMAC commands within the message interpreter. EPICS sends multiple commands in a single message, so DiamondLightSource/tickit#82 will also be needed to split up each message into the individual commands within the device's message interpreter.
The text was updated successfully, but these errors were encountered: