Momentary switch pulse detection

there are some questions about controller inputs:

  1. Is it possible to increase the reaction rate between a physical change in the input (e.g., clicking) and reading the input of the chip? Now, the input indication led (and program reading) reacts to the button press after 1-2 seconds. This is very inconvenient, as a short press does not get into the controller. You must keep the button pressed until you see the controller.
  2. Frequency-there is no frequency at the input, but the input table shows the value 1.02. Why?
  3. Counter (1 Hz or 100 Hz) - how to reset the counter programmatically?

Chelsea will check into this and see what can be done to speed things up, stand by for news shortly.

While we wait, could you confirm that you are testing with a simple program like this to check the actual event detection and some logic running on that event.


This program will flip output1 every time you hit a switch connected to input1.

I conducted 3 experiments:

  1. Program 1 - line 10 IF+ IN1 THEN OUT 1 = NOT OUT 1, program 2-16 – zero. Button press → led (IN1) is on – reaction time~1-2 seconds. led (IN1)→led (OUT1) – reaction time ~1 second.
  2. Programs 1-16 filled with code of 1770 bytes+program 16 added line 770 IF+ IN1 THEN OUT1 = NOT OUT1. Button press → led (IN1) is on – reaction time~1-2 seconds. led (IN1)→led (OUT1) – reaction time ~1 second.
  3. Programs 1-16 filled with code of 1770 bytes + in program 1 added line 10 IF+ IN1 THEN VAR 60 = NOT VAR 60, in program 16 added line 770 OUT1 = VAR60. Button press → led (IN1) is on – reaction time~1-2 seconds. led (IN1)→led (OUT1) – reaction time ~1 second.
    Conclusion: visually change the speed of the program depending on the volume is not visible (which is surprising). The change of the Reaction between the led IN1 - pressing the button and, of the size of the program is visually not detected.
    Perhaps there is a change in speed, but visually not visible.
    I hope it’s written clearly.

All programs execute in about one second whether you have a lot of programming or very little, they will execute at about the same speed regardless of the program size.

The thing which is limiting you is the response time of the input, its slower than what a user would expect from a pushbutton which would be on the order of a ‘few 100 ms’. We sample the inputs at about one second for normal inputs. The high speed inputs can respond more quickly, while testing this we found that the high speed logic is only executed if the input is configured as a pulse counter. We’ll do a firmware update this week which samples the high speed inputs when they are configured as binary type ranges as well. We should be able to respond to a hit on the pushbutton as short as 1ms though it could take up to a second for the output to respond.

Here’s a table showing where the high speed inputs are located for all T3-XX controllers and expansion modules. Later this week you can update the firmware and repeat your test with the switch wired to one of the high speed inputs.