problem I found is that after compiling it changes port… so I compiled to see if everything was fine and then upload while holding reset button, as soon you see the programmer (set upload to verbose in preferences) searching for ports you let the resetbutton go and it find the right port automagically.
another possibilty is that your laptop doesn’t provide enough power so you can try it with an USB hub in between.
@BoRRoZ Ok, I have been trying all sorts of “press reset”-scenarios, but was unable to to succeed. This ports switching seems to confuse the avrdude program. The best result I got was this one:
Found programmer: Id = “CATERIN”; type = S
Software Version = 1.0; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=128 bytes.
Programmer supports the following devices:
Device code: 0x44
avrdude: devcode selected: 0x44
avrdude: AVR device initialized and ready to accept instructions
@BoRRoZ, I also followed the suggestion of the Sparkfun website: https://learn.sparkfun.com/tutorials/pro-micro--fio-v3-hookup-guide/troubleshooting-and-faq#ts-reset . It seems you have more time to access the bootloader, but still no success. Coming thursday I can test on Apple and Windows. This device is not really convenient to use with Arduino and Ubuntu. Weird that you were succesfull and I can’t manage to get it working.
I think the method from Sparkfun for the Pro Micro is not as elegant as the normal Uno and others from Arduino family. The port switchting is really confusing and unstable.
that’s typical 32U4 behavior and not very well implemented under Ubuntu … virtual serial port works under windows but can also give sometimes problems.
My gateway works as expected, and so did one of the Arduinos. My other Arduino didn’t see the radio, i.e., the radio wasn’t responsive to commands via the serial connection. My Things Node had a broken radio, which only worked in a narrow temperature window.
Now I received exchange parts for those two broken devices. The new Arduino does the job, however, the new Things Node doesn’t show up as USB/COM when connected to a computer. So I’m still without a working Things Node.
That makes 3 out of 5 end devices faulty, in one way or another. Am I the only one with really bad luck? Or are we looking at a quality issue with the kit? Don’t get me wrong – this is not to moan about the Kickstarter campaign or the TTN crew. I think they’re doing a terrific job. I just want to check if I’m the only one experiencing weird hardware issues and have all odds against me…
I moved your question to this topic because it seems that your gateway is working and you’re having a problem with the nodes, and this is TTN NODE central
I think that what I read is normal behavior, a 32U4 connected to an usb port behaves different then a arduino with a dedicated onboard usb serial connection and sometimes it’s really annoying.
especially with an arduino IDE under linux.
I’m all ears. Funnily enough, the Things Node with the broken radio quite happily connected like an Arduino. I hope I don’t need a JTAG programmer or something…
but you have to open the the things node, remove batteries , remove 2 screws so you see this and the reset button (the one on the left on the PCB) is exposed.
I am a bit busy today (and tomorrow) so there is a big chance that I can’t respond/continue immediately
yes I forgot, at the beginning of this topic, in December you allready had this problem.
Last week we solved a similair problem with a simple ‘swap USB cable and port’ sounds stupid but worh a try
In terms of numbers of people using thta combination ? You should do a google search on Linux and arduino then, because ubuntu is just one flavor of that OS.
Using a Dell Inspiron 17 (3721) laptop running Windows 10, I just successfully followed Johan Stokking’s excellent video https://www.youtube.com/watch?v=tapK6EINx1k after some false starts. Thanks to BoRRoZ here and Todd Cottle in the YouTube comments for helpful hints.
In the node, which arrived this week, I spent some time tugging at the board seeking to smoothly extricate it from the case like Stokking did in the video, before realizing I needed to get out my smallest Torx screwdriver to remove the two inside screws beneath the batteries after using a Phillips screwdriver to remove the two visible ones from outside the closed case.
And I needed to be careful under the tools menu to not only consistently ensure that Sparkfun Pro Micro was selected as the board but also to go to the Port option and select, in my case, the COM3 port since otherwise the Arduino IDE seemed by default to look on COM4. And also needed to be patient and wait till the sketches were fully done uploading rather than jump too quickly to the serial monitor. And when copying and pasting the payload function careful to copy just the same parts of the sketch that Johan copied.
After my earlier failed attempt the node’s light was chronically red. But after removing the board I was able to hit the reset button that BoRRoZ had helpfully pointed out as the one on the left when the Microchip radio is on the bottom (with the other button above the Microchip chip being the one that triggers immediate sending of sensor data), and then start fresh.
Good luck to those running other machines/OSs, etc.
Note: the Sparkfun Pro Micro board (used as a basis for the TTN Node) has a reputation for troublesome USB access. I’ve encountered it as well. Swapping cables did the trick for me, for some it is using a USB hub. Check this link:
Just a brief note that I fixed my ThingsNode USB connectivity issue.
I tried like twenty permutations of USB cables, USB ports and Windows/Mac computers. In the end, I resorted to a complete reinstall of the Arduino IDE on a Windows 10 machine, followed by the usual drivers and Arduino libraries, and an extra-short USB cable. That fixed it.
