Hello, the interaction between scratch and scratchClient is done by using variables and events. If you have a look to the pi2go-adapter in localhost:8080

then you control the leftmost variables,( there are no events for this adapters). So do not use "channel_0" but the corresponding scratch name "D11_D14_blue". Same for the motor, control 'speed_A' or 'speed_B'. Values for the PWM LED is [0..100], the motor uses [-100..100].
You control these by creating variables in scratch with exactly this name (upper, lower, underscore, no blanks), scope 'for all sprites'. My kids in school usually struggle with '-' or '_', upper and lowercase, blanks at the beginning or at the end, so simplest procedure is to copy paste the names from the adapter web page or the config file directly. When you change the variables in scratch, you should see them arriving in the web page. Start scratchClient with -guiRemote in addition to the other parameters, and you have the possiility to remotely connect a browser to your Pi.
You can change the scratch names in the adapter file. So if you do not like the "D11_D14_blue" which is just the chip names on the board, then change this in the config file to 'left_side_blue_led' or whatever you need. Do not change the adapter name 'channel_0' or the others on the middle row close to the boxes, as this is needed to route the signals to the python code.
For the sensor values (on the right of the adapter view), look for the '[ ] sensor value' block in the sensor palette. When a value is sent, then the names should be available there. The events, e.g. 'SEN1_HIGH' are arriving as broadcast events. Click them in the web view (short red flash should indicate the signal sent) and in scratch the 'when I receive[ ]'-hat will have the names in the pulldown. Of course same thing when the IR sensors toggle (they have LED associated when active, inactive driven by this processor on the board).
If you do not like broadcast events for the IR sensors, this can be changed to level signals 0,1 by using different adapters.
Hope this helps,
Gerhard
I have a beta for a scratch2 connection to scratchClient, but I would not recommend to use now as internal thread management is not yet completed.
For scratchClient, there is documentation in the scratchClient/doc folder or on my web page. For the pi2go, I do not yethave a scratch sample available.
The motors are disabled on the pi2go board if battery is low. There is a flashing LED D2 or D3 indicating this situation. I use a power supply here to work around bad batteries. This could be one reason for motor not working. Or one of the jumpers on the board are missing.