I wonder if someone can fill in the blanks. I have been developing a Mac OS X controller app for the k8055.
I have the following information which some may find useful but I am looking for someone to fill in the blanks.
K8055 ELEMENTS
Element 1 = TYPE 513 ==
Element 2 = TYPE 1 (Input) == Value of Digital inputs (0-255)
Element 3 = TYPE 1 (Input) ==
Element 4 = TYPE 1 (Input) == Value of Analog input 1 (0-255)
Element 5 = TYPE 1 (Input) == Value of Analog input 2 (0-255)
Element 6 = TYPE 1 (Input) == Value of Counter 1 (0-255)
Element 7 = TYPE 1 (Input) ==
Element 8 = TYPE 1 (Input) == Value of Counter 2 (0-255)
Element 9 = TYPE 1 (Input) ==
Element 10 = TYPE 129 (Output) == Control channel (value of 3 resets counter 1, 4 resets 2, 5 switches to DO mode)
Element 11 = TYPE 129 (Output) == Value of Digital outputs (0-255)
Element 12 = TYPE 129 (Output) == Value of Analog output 1 (0-255)
Element 13 = TYPE 129 (Output) == Value of Analog output 2 (0-255)
Element 14 = TYPE 129 (Output) ==
Element 15 = TYPE 129 (Output) ==
Element 16 = TYPE 129 (Output) ==
Element 17 = TYPE 129 (Output) ==
I understand that you have a debounce time associated with counters 1 and 2
I assume that Element 7 and 9 allows you to get the currently set debounce value? Is this the case.
Which elements are used to set the debounce on each counter?
Would I be right in thinking that Element 10 (values 1 & 2) would reset the debounce? Or is this a switch like value 5?
Finally the how does the decimal element value of the debouncers corrispond to milliseconds.
As once I know the element to send on I can only send a decimal value of 0 to 255. How is this value converted to milliseconds.
[quote=“Cacus”]I wonder if someone can fill in the blanks. I have been developing a Mac OS X controller app for the k8055.
I have the following information which some may find useful but I am looking for someone to fill in the blanks.
K8055 ELEMENTS
Element 1 = TYPE 513 ==
Element 2 = TYPE 1 (Input) == Value of Digital inputs (0-255)
Element 3 = TYPE 1 (Input) ==
Element 4 = TYPE 1 (Input) == Value of Analog input 1 (0-255)
Element 5 = TYPE 1 (Input) == Value of Analog input 2 (0-255)
Element 6 = TYPE 1 (Input) == Value of Counter 1 (0-255)
Element 7 = TYPE 1 (Input) ==
Element 8 = TYPE 1 (Input) == Value of Counter 2 (0-255)
Element 9 = TYPE 1 (Input) ==
Element 10 = TYPE 129 (Output) == Control channel (value of 3 resets counter 1, 4 resets 2, 5 switches to DO mode)
Element 11 = TYPE 129 (Output) == Value of Digital outputs (0-255)
Element 12 = TYPE 129 (Output) == Value of Analog output 1 (0-255)
Element 13 = TYPE 129 (Output) == Value of Analog output 2 (0-255)
Element 14 = TYPE 129 (Output) ==
Element 15 = TYPE 129 (Output) ==
Element 16 = TYPE 129 (Output) ==
Element 17 = TYPE 129 (Output) ==
I understand that you have a debounce time associated with counters 1 and 2
I assume that Element 7 and 9 allows you to get the currently set debounce value? Is this the case.[/quote]
No. With the original firmware of the K8055 there is no way to query the current debounce time set in the card at all. Elements 7 and 9 above would be the upper bytes of the 16 bit counter values.
[quote=“Cacus”]Which elements are used to set the debounce on each counter?
Would I be right in thinking that Element 10 (values 1 & 2) would reset the debounce? Or is this a switch like value 5?[/quote]
Other control channel values (1 and 2).
You probably want to look at these two threads to find additional detail information as well as some software, that may even compile under OS X (it does compile/work under FreeBSD against libusb 1.0).
Just to confim re counter being 16-bit. I assume then that once element 6 for example reaches 255 the next count would result in element 7 = 1 and element 6 = 0. and so on. Giving you a possible count number of 65,536.
Just to confim re counter being 16-bit. I assume then that once element 6 for example reaches 255 the next count would result in element 7 = 1 and element 6 = 0. and so on. Giving you a possible count number of 65,536.