I try to control individual track level with the Intech PO16 and the Intech Knot.
Each track is set to a midi channel from 1 to 16.
The PO16 is connected to the Knot via usb and the Knot to the DTK2 via Midi-TRS to the Midi in.
I’ve tried both type A and B (with the switch on the Knot).
I’ve tried CC 95. no success (midi_send(2, 95, cc, val))
NRPN (1 -100) nu success. midi_send(ch, 176, 99, 1) /midi_send(ch, 176, 98, 100) / midi_send(ch, 176, 6, val)
Dont know what to do else.
What are your midi settings in the digitakt menu for port configuration?
You said you set the channels, but what else did you configure?
Knot is a USB midi host device, you should be able to use this host to interface the USB controller with digitakt, so either your controller is broken, your host device is broken, or your settings are wrong. I’m guessing it’s the settings, but I don’t know. Have you successfully used your controller with any other gear recently?
First thing to do is elaborate on your settings and maybe I or someone else will see the problem, as of right now what you’re doing sounds correct, but there’s not enough information given to tell you the problem.
When in doubt, always try a different cable. Both USB and TRS, some devices are picky about USB cables. You have a bipolar setting for TRS A/B but if the cable itself is bad, it won’t matter how it’s wired.
Let us know so it’s easier to help you figure it out, thanks.
Here are the MIDI settings:
If the knot allows bias selection type A/B cables should both be fine.
I’m looking at this thread below which I copied from and checking out your manual for the po16. See if anything in the thread or the grid documentation linked here is useful for identifying any differences between your set up and the one described.
"
d4ydream
It’s pretty straight forward once you look through some of the Grid documentation:
Choose one of the guides below!
I’ve done custom stuff for Digitone and Loopy Pro. I have 2x EF44, and EN16 and a PO16. I can post some code and instructions if you have an idea of what you’re looking to do.
It’s getting late here though and I’m super bagged from spin. Car’s in the shop tomorrow so I’m working from home. Give me an idea about what you’re looking for and I’ll see if I have time to script something up."
So just because it’s for the octatrack, don’t try and copy the settings shown, but you should be able to use it to see what they were doing. Looks like it requires a software editor, is that not the case for po16?
Adding: Ok well their site says with a standalone host you should be good to go. Here’s some troubleshooting from the knot guide, what is the status of the led lights?
Your LUA commands are wrong. I can post code after dinner which should be here in 20 minutes.
midi_send() takes 4 parameters: channel, command, CC/note number, value.
If you want to control DTII track value, the CC is ‘95’. If you’re controlling a track setup on MIDI channel 1, your midi_send() function would be:
midi_send(0,176,95,val)
‘val’ is usually defined as a local variable that has the current value of the element you are using. This would be done in a code block with the default code but it would like this in a ‘Code Block’:
val = self:potmeter_value()
And element is a physical control on a Grid controller. That function is called each time an element event occurs. So, you turn a pot, slide a fader, press a button etc., you generate an event and midi_send() transmits the current value on the MIDI channel defined in the first parameter.
If you are intending on using NRPNs, there is a NRPN code block available but I’ve not used it. I wanted to control some NRPN parameters on my DN and needed to learn a bit more about how to transmit NRPRs. You’re essentially using 3 (sometimes 4) midi_send() calls for each event.
I go over it in this forum post on the Intech forums:
If you need a bit more guidance with your PO16 setup, I’m more than happy to assist. I’m a bit busy this weekend but might have some time on Sunday. Feel free to post questions here but expect some delays in replies.
Cheers!
Wow ! I did not expect an answer this thorough!
I’ll try it. thank you !
There’s certainly a bit more needed but hopefully this points you in the right direction 
Note that variables such as ‘cc’, ‘ch’, ‘val’ etc. are, by default, defined on the ‘Init’ tab of the element you’re working on. ‘val’, for example, is always assigned to the element type’s value:
val = self:potmeter_value()
val = self:button_value()
val = self:encoder_value()
‘cc’ and ‘ch’, by default, use formulae to auto-assign themselves unique and non-overlapping values so that you can just plug them in and map them to parameters in your DAW. You can replace those formulae with explicit values to suit your needs. So, the first potmeter’s ‘Init’ tab, you’d likely set ‘ch’ to ‘0’ (for MIDI channel 1. Intech uses 0-15 for channels) and ‘cc’ to the CC number you want to assign to that element.
It works.
I used midi_send(ch, 176, cc, val).
Then midi_send() function was unclear to me.
Awesome. Have fun!