View Single Post
Old November 25th, 2015   #8
dj41354
Member
 
Join Date: Nov 2015
Posts: 30
Default

I think I made some progress.. the USB data dump is showing fewer time outs..
But it is showing a time out on a GET_DEVICE_MODEL_DESCRIPTION ?
I don't have support for that command.. could this timeout be why the DMXter is still saying (NOT RESPONDING)?

PACKET HISTORY
TIME TN CC NAME RESULT CC PID PDL CC PID PDL RTY RQ
14.93 00h SET IDENTIFY DEV BROADCAST 30h 1000h 01h
* 15.02 01h SET IDENTIFY DEV GOOD RESPONSE 30h 1000h 01h 31h 1000h 00h 00h
15.10 02h GET DEV MODEL DESCR RESPONSE TIMED OUT 20h 0080h 00h
48.07 03h SET IDENTIFY DEV BROADCAST 30h 1000h 01h
* 48.16 04h GET DEVICE INFO GOOD RESPONSE 20h 0060h 00h 21h 0060h 13h 00h 01h 00h...
* 50.50 05h GET DEVICE INFO GOOD RESPONSE 20h 0060h 00h 21h 0060h 13h 00h 01h 00h...
50.59 06h GET DEV MODEL DESCR RESPONSE TIMED OUT 20h 0080h 00h
--AT END OF LIST--

CAPTURED PACKET
SC SS LEN ------DEST------ -------SRC------- TN PR MC SUBDV CC PID- PDL DATA----
REQUEST
CC 01 18 3A FC 00 00 00 01 47 44 00 41 44 83 05 01 00 00 00 20 00 60 00 04 35
RESPONSE
CC 01 2B 47 44 00 41 44 83 3A FC 00 00 00 01 05 00 00 00 00 21 00 60 13 01 00 04 00 01 01 52 34 2E 30 04 00 01 00 00 01 00 00 00 05 4C
--AT END OF LIST--

PREVIOUS PACKET
SC SS LEN ------DEST------ -------SRC------- TN PR MC SUBDV CC PID- PDL DATA----
REQUEST
CC 01 18 3A FC 00 00 00 01 47 44 00 41 44 83 06 01 00 00 00 20 00 80 00 04 56
RESPONSE

--AT END OF LIST--

RESPONDER TIMING MIN PRV MAX
RESPONSE DELAY IN us 178 178 178
BREAK LENGTH IN us 255 258 258
MAB LENGTH IN us 87 87 89
INTERSLOT TIME IN us 40 45
TOTAL LENGTH IN us 2544 4179 4179
DISC. FIRST ACTIVITY (EMPTY)
DISC. LAST ACTIVITY (EMPTY)
UNICAST 3 / 5
DISCOVER 0 / 0
UNICAST RETRY COUNT 0
NOISE BEFORE BREAK 0
NSC PACKET COUNT 1558
dj41354 is offline   Reply With Quote