brucedog Posted August 17, 2012 Share Posted August 17, 2012 I tried searched forums and watched the tutorial before posting so sorry if i missed something. So i took an example script and copied to the ducky with no problem but the issue i have is it will only excute when i press the button on the ducky usb. The OS i was testing on was a Win7 x64. Thanks in advance, Brucedog Quote Link to comment Share on other sites More sharing options...
Cassiopeia Posted August 17, 2012 Share Posted August 17, 2012 yeah had the same "Issue" but yay its a pretty easy one \o/. the problem itself lies in that the ducky executes the script as soon as it gets power to the board. and it happens so fast so that windows itself doesnt recognize it as a keyboard/mouse. easy fixin, just add a DELAY at the top of your script giving windows time to recognize the ducky as a HID, i run with DELAY 5000 fixed my problems atleast =) Quote Link to comment Share on other sites More sharing options...
PineDominator Posted August 17, 2012 Share Posted August 17, 2012 (edited) I had a great method for detecting when the keyboard was ready for the teensy devices. IE bool numLockTrap = numLockOn();while(numLockTrap == numLockOn()) {keyPressAmountWithDelay(KEY_NUM_LOCK, 1);delay(25);}keyPressAmountWithDelay(KEY_NUM_LOCK, 1);[/CODE]I beleve numLockOn() gets the state of numLockonce numlock changes that means that the keyboard of the teensy device is fully installed and functioning, this could be added for the ducky firmware Edited August 18, 2012 by petertfm Quote Link to comment Share on other sites More sharing options...
brucedog Posted August 17, 2012 Author Share Posted August 17, 2012 Added the "DELAY 5000" and everything worked! Thanks again! Quote Link to comment Share on other sites More sharing options...
amoeba Posted September 14, 2012 Share Posted September 14, 2012 Same problem for me, white rubberducky and DELAY 5000 worked Thanks! Quote Link to comment Share on other sites More sharing options...
Mr-Protocol Posted September 14, 2012 Share Posted September 14, 2012 Added the "DELAY 5000" and everything worked! Thanks again! Same problem for me, white rubberducky and DELAY 5000 worked Thanks! This is because you need to give it some time to be recognized by the OS. Or else your script will run as soon as power is applied and the teensy OS is loaded. If the machine already has identified the ducky/teensy on that USB port before, it will recognize it faster. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.