search

SainsburyWellcomeCentre / aeon_experiments

Experiment workflows for Project Aeon
BSD 3-Clause "New" or "Revised" License
2 stars 0 forks source link

Rfid firmware and indicator issues #441

Open jkbhagatio opened 8 months ago

jkbhagatio commented 8 months ago

Some weird things I notice with the rfids:

  1. When viewing the visualizer for the Rfid Parse node, it always displays the last rfid detected, even on a fresh restart of the Bonsai workflow.
  2. Even with the 'OperationLed', 'OperationMode', and 'VisualIndicator' properties set appropriately, the rfids are not buzzing nor the led indicator light turning on during a detection

Interestingly, 2.only happens on the aeon3 rfids, but the indicators work on the aeon4 rfids.

glopesdev commented 8 months ago

When viewing the visualizer for the Rfid Parse node, it always displays the last rfid detected, even on a fresh restart of the Bonsai workflow.

This is the Rfid reporting the state of the event register on startup. It will not go in the chunked data since it is a Read message and thus will be stored only in the binary file storing the initial device state. We can possibly improve online filtering further to take this into account but it won't be a blocker for now.

Even with the 'OperationLed', 'OperationMode', and 'VisualIndicator' properties set appropriately, the rfids are not buzzing nor the led indicator light turning on during a detection

I think this is likely an issue with device configuration registers. We actually intended for sounds and lights to be off on RFID detection to avoid cueing the animal, but it's likely that one arena is configured and the other not. Probably the best approach would be to check the device initialization routine to make sure that this configuration is set every single time on device initialization.

glopesdev commented 8 months ago

make sure that this configuration is set every single time on device initialization.

@jkbhagatio actually I was just checking this and it's already there and on both arenas the hardware notifications are set to None, so in principle if you run the full workflow you should not get any notifications from the readers.

If you want to have them for testing and calibration we can make a separate workflow where we just turn them on. The relevant property is HardwareNotifications on the RfidReader module.