Axoloti Core Rev 1.2 Board DOA (powers up kind of I guess)?

#21

I think if you don't just happily accept the fact that it works now, but instead try to "get to the bottom of it" you'll probably stir the wrath of the programming gods/devils and your axo board will just go up in flames. Just leave it as is.

That being said, i definately fried a STM32F4 board from a different platform with these shitty little dupont jumper cables. Shorts on shorts on shorts. Imagine all these little electrons travelling down the wire, and then one of them sees it and is like is "fuck guys we are doomed theres a dupont ahead. Pray to the gods so at least half of us will make it through. Ahhhhhrrrrrr its not connected at aaaaaaaalllllllllll" and falling off the voltage cliff. or something like that.

#22

Hey @steveo, thanks for the reply. At least we're not alone here.

So I haven't really messed around with this Axo since last weekend. It appeared to be working fine for awhile until I left it powered up for an indeterminate amount of time and walked away. When I came back, it looked like it was in a constant reboot cycle. It definitely seems like it has a mind of its own. Sometimes it'll work for awhile, other times it will go into the reboot cycle any time I plug a USB cable into it to power it (either via a computer or one of those USB AC adapters). I've been too frustrated with it to really dig in and troubleshoot since my last post when I thought everything was solved.

I haven't seen the unresponsive dim red LED since last post, but again, I got frustrated with it and haven't spent too much time with it since.

I ordered a 2.1mm 9V AC adapter a few days ago to try and see if it would be stable using something other than USB power. It came today and I've had it powered on for about an hour without issue (just powered running whatever start-up patch I had loaded onto the thing). I briefly attempted to hook it up to my PC to see if it would communicate successfully with the patcher (and it appeared to work fine). In the meantime I plan on just leaving it powered via the new AC adapter for a few hours and see if it goes into the same weird reboot cycle and reevaluate my troubleshooting strategy depending on what happens.

#23

I think you may have a point with your dupont theory. Seems to be quite literally the weakest link. I won't be using them again in future Axo projects

#24

Hey !

How are your axolot mypetrobot since last year?

I've the same problem describe on this post.

The fact i've conclude is when my house is too hot like now (30degres cel ) , axoloty not working.

I've checked other post that describ this problem on the forum , and they have in common that they are posted during summer...

Like you said : When i put it on the fridge, he work a little bit then... disconnect.

Heat is it a problem for all axolot ? or a consequence of something else ? Ho can we protect them ?

#25

I haven't had any heat-relatied issues as far as I know, but what I did notice is that the usb-power from my computer is barely enough to power 1 axoloti, but starts having trouble when connecting two. So I can imagine that the usb-power is often the limiting factor in connecting the axoloti to your (old?) computer. Mine is starting to be a bit old and the usb hardly even reaches 5v. I think the best you can do is to use an externally powered usb-splitter between the computer and the axoloti's to make sure there's more then enough power to run them all.
Also, what I did, was to write arturia to ask them to sell me their usb-y splitter seperately. This one allows for seperate connections for power and computer/usb device. Works perfectly and you can daisy-chain your axoloti's without them having them to power each other.

#26

Y-splitters are readaly available..
Found this one over here
I have used some in the past for other purposes (external HD enclosures) and they worked for me. I always check if the grounds are connected though.

usb2haubyx.main.jpg600x600 20.3 KB

#27

I think it was the laptop USB power. I'm using a fairly old Macbook and it seems to cause problems when the battery is low, or going below about 20%.

I can imagine @Skurtim 's problem could have something to do with heat making the CPU fan stay on and using up extra power.

I think it's some kind of dumb Mac "design" feature to ensure I "always get the best performance experience". Anyway, I always use external power these days and this particular issue seems to have resolved.