Issues with Dygma Raise Keyboard and LoupeDeck Live

Submitted by Gadgets4grls on #1

Running registered version of VirtualHere MacOSX client, Raspberry Pi 4 Server

Having several issues. 

First one is with Dygma Raise programmable keyboard.

The keyboard operates correctly when used for normal input and Bazecor (keyboard programming application) will connect but it disconnects when attempting to update the programming on the keyboard and also corrupts the current programming as well.

Next issue LoupeDeck Live. Operates correctly when directly connected to the Mac but when connect to the VH server it doesn't operate. Looking at the VH client it shows LoupDeck Live but the LoupeDeck application is showing a LoupeDeck CT as connected and the device screen is blank after showing the green boot icons.

Below are the error log entries that are showing up.

Thanks

 

2023-04-18 08:45:08 INFO  :VirtualHere Client 5.4.5 starting (Compiled: Apr  5 2023 08:49:33)
2023-04-18 08:45:08 INFO  :Client OS is macOS Version 13.2.1 (Build 22D68)
2023-04-18 08:45:08 INFO  :Using config at /Users/-------------/Library/Preferences/vhui Preferences
2023-04-18 08:45:08 INFO  :IPC available at /tmp/vhclient
2023-04-18 08:45:08 INFO  :Auto-find using Bonjour - on
2023-04-18 08:45:08 INFO  :Auto-find using Bonjour SSL - on
2023-04-18 08:45:09 INFO  :interestHandler mt=3758096641
2023-04-18 08:45:11 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:45:11 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:45:11 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:45:11 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:45:11 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:45:11 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:45:11 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:45:11 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:45:11 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:45:11 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:45:11 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:45:11 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:45:11 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:45:11 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:45:11 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.


2023-04-18 08:47:07 INFO  :Warning, error clearing halt on ep 0x83 for device 1134, -1
2023-04-18 08:47:07 INFO  :Warning, error clearing halt on ep 0x83 for device 1134, -1
2023-04-18 08:47:07 INFO  :Warning, error clearing halt on ep 0x83 for device 1134, -1
2023-04-18 08:47:07 INFO  :Warning, error clearing halt on ep 0x81 for device 1134, -1
2023-04-18 08:47:07 INFO  :Warning, error clearing halt on ep 0x83 for device 1134, -1
2023-04-18 08:47:07 INFO  :Warning, error clearing halt on ep 0x83 for device 1134, -1
2023-04-18 08:47:07 INFO  :Warning, error clearing halt on ep 0x83 for device 1134, -1
2023-04-18 08:47:07 INFO  :Warning, error clearing halt on ep 0x83 for device 1134, -1
2023-04-18 08:47:07 INFO  :Warning, error clearing halt on ep 0x81 for device 1134, -1
2023-04-18 08:47:07 INFO  :Warning, error clearing halt on ep 0x83 for device 1134, -1
2023-04-18 08:47:07 INFO  :Warning, error clearing halt on ep 0x83 for device 1134, -1
2023-04-18 08:47:07 INFO  :Warning, error clearing halt on ep 0x83 for device 1134, -1
2023-04-18 08:47:07 INFO  :Warning, error clearing halt on ep 0x83 for device 1134, -1
2023-04-18 08:47:07 INFO  :Warning, error clearing halt on ep 0x81 for device 1134, -1
2023-04-18 08:47:07 INFO  :Warning, error clearing halt on ep 0x83 for device 1134, -1
2023-04-18 08:47:07 INFO  :Warning, error clearing halt on ep 0x83 for device 1134, -1
2023-04-18 08:47:10 INFO  :Warning, clear halt ep 0x83 device 1134 didnt return
2023-04-18 08:47:51 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:47:51 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:47:51 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:47:51 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:47:51 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:47:51 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:47:51 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:47:51 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:47:51 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:47:51 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:47:51 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:47:51 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:47:51 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:47:51 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
2023-04-18 08:47:51 INFO  :Error quiecsing p 1 ep 0x83, 18446744073172681442 Transfer completion message was not sent. The current endpoint state cannot generate transfer completions.
 

 

 

Submitted by Michael on Wed, 2023/04/19 - 08:37

#2

OK i will investigate this next week with my Dygma keyboard, I ordered one as it might be useful for me

Submitted by Gadgets4grls on Wed, 2023/04/19 - 22:05

#3

Hi Michael,

Thanks it's appreciated and if you need more input from me just let me know and I'll help however I can.

 

Submitted by Michael on Thu, 2023/04/27 - 10:18

#4

I got the keyboard and the problem seems to be that there is a bug in the keyboard firmware which doesnt allow more than one message at a time. If it receives more than one message at a time it will corrupt the memory. You will have to wait until someone fixes it from Dynma.

Not sure about the Loupe deck ,  its not something I can easily get to test with...

Submitted by Gadgets4grls on Thu, 2023/04/27 - 21:32

#5

Do you want me to post your comment over on the Dygma Reddit page or would it be better for you to contact them since now have a Raise as well as know exactly what the message bug is?

Thank you for trying.

 

Submitted by Michael on Fri, 2023/04/28 - 08:51

#6

You can post a link to this message in their forums

I did take a few hours looking at this and i suspect its this bug

https://github.com/keyboardio/Kaleidoscope/issues/1311

When loading the keyboard templates via virtualhere I can see that a USB (control) HID "GET REPORT" request comes in and immediately after a "GET DESCRIPTOR" comes in, however the GET_REPORT has not yet completed and from that point on all interaction is corrupted because subsequent CONTROL requests all fail due the MCU USB state machine getting out of sync, thinking that one control request at a time is only possible

I suspect the reason that it works locally and not via virtualhere, is that there is a tiny bit of extra latency in the communication via virtualhere and this latency brings out this bug in the firmware. 

I think however that the raise keyboard uses a SAMD chip rather than GD32 but i think the issue is the same looking at the message traces on my setup.