This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Is there a limitation on the number of signal capturing channels available for capGetSignal?

Other Parts Discussed in Thread: HALCOGEN

Currently, I am using all 8 of the [Halcogen] capture channels on HET1 with capGetSignal(). How can I increase this? It appears Halcogen creates a 58 element of HET "instructions". Is that size fixed, can I add to it somehow? This is a very useful feature for us.

  • David. No you can cap. On all het pins if you like.
    But you need to use the HET IDE to develop a program and also write corresponding drivers for this program.

    We had converted the HCG object back to HET source so it could be the basis of an incremental update to the HCG driver (like adding one or two more caps) but I am having some problems finding the forum post to which this was attached. I think that could be a start. Or the HET IDE includes a template for common timing functions that you can copy paste as the basis for a custom program.

    On the first tab for each HET there is a check box that lets you enable an advanced custom driver and disable the black box (default) driver. If you check this box and select the .c and .h files from your HET IDE project then hetInit() Will load your custom HET program. You will need to still write or modify the host side APIs yourself. (For example the function to read the correct cap register out of HET RAM. ). The HET assembler gives you a header file with the structure of your program to allow you to address the fields of the HET RAM in your program symbolically.
  • Thanks. I figured that was an artificial limit. I will be attacking this problem in the next couple of months.