fscan issueshttps://gitlab.esrf.fr/bliss/fscan/-/issues2023-08-08T14:49:59+02:00https://gitlab.esrf.fr/bliss/fscan/-/issues/14Add Trig Scan2023-08-08T14:49:59+02:00Gilles BerruyerAdd Trig ScanGilles BerruyerGilles Berruyerhttps://gitlab.esrf.fr/bliss/fscan/-/issues/9fscan: Error message "object has no attribute" when detector is not on2022-11-03T09:57:33+01:00Valentin Vallsfscan: Error message "object has no attribute" when detector is not onFeedback from ID27
Their detector was in `FATAL` state, and they was trying to fscan it.
There is maybe a way to provide a better error message in this case?
This is also maybe a problem in BLISS side -> detector could could be checke...Feedback from ID27
Their detector was in `FATAL` state, and they was trying to fscan it.
There is maybe a way to provide a better error message in this case?
This is also maybe a problem in BLISS side -> detector could could be checked at the preparation of the scan?
![image](/uploads/6962f1f6016d553e41aa5b012522c07a/image.png)https://gitlab.esrf.fr/bliss/fscan/-/issues/6f2scan: improve the error message when 2 motors are using the same channel id2021-11-05T17:14:55+01:00Valentin Vallsf2scan: improve the error message when 2 motors are using the same channel idFeedback from ID15 during help desk.
The `f2scan` with 2 motors was not working.
This 2 motors was part of the same icepap switch, connected to the same musst channel.
As result, the scan was not able to do anything, but the error mes...Feedback from ID15 during help desk.
The `f2scan` with 2 motors was not working.
This 2 motors was part of the same icepap switch, connected to the same musst channel.
As result, the scan was not able to do anything, but the error message was criptic.
```
self.musst = self.musst_list.find_musst_for_motors(pars.motor, pars.slave_motor)
File "/users/blissadm/local/fscan.git/fscan/mussttools.py", line 36, in find_musst_for_motors
f"Cannot find all motors {motor_names} on one musst {self.musst_names} !!"
ValueError: Cannot find all motors ['hrx', 'mcrz'] on one musst ['musst_eh3'] !!
```
It would be nice to provide a more explicit message in this case.
Maybe something like "`motor1` and `motor2` can't be part of the same scan cause their encoders are connected to the same Musst channel id".