Amazing project! I am running in to an issue…
Running:
Stormcore 100D ii 5.2fw
usplit 0.12fw
Metr Pro (UART)
Metr LTE (over CAN)
OSRR Remote (UART telemetry/PWM for throttle
Metr Pro not connecting to the Metr LTE over CAN
Planning on troubleshooting this week:
Anything else i should try?
i will post back with updates
Thanks for the support and letting me know of the issue 
This is very likely going to fix your issue as the v0.13 update has alot of work done to ensure CAN forwarded comms are handled properly. If that doesnt work, then as you said, I would connect up the Metr Pro without the uSplit. If that is working, we’ll try to look for clues in the uSplit setup as to what the root cause is.
No, you gotta plug one end into your butt.
Just wanted to report that I scored a never used second round beta usplit, updated the firmware and got it installed into the board running davega and robogotchi… all without any hassle!
Kudos for your excellent documentation Matt, and thanks for a great product!
I can’t seem to get this to work. Can you or @BillGordon send me an instructional video?
Lol. Are you actually having an issue? Lets try keep it clean in here 
Thats how you unlock the secret wireless link feature
I really appreciate the support and it’s awesome to hear you are having a good experience using your uSplit!
If that changes with any future Robogotchi, DAVEga, or VESC updates, just let me know so I can get things running smoothly again 
Continuing convo - I will unplug all except the Metr and see if that works properly first.
Davega won’t work at all either, with ilogger connected
Unplugged everything to test metr only and it seems to not work still, just stuck on pairing when connected to usplit. Works fine on normal port @Ricco
I just tried and DaVega alone doesn’t work either. Is it possible I need to flip TX and RX on the usplit?
Does your usplit light up? When I had broken mine it stopped lighting up 
my Davega would still turn on when my usplit was broken because the power is just passed through (?) but it wouldn’t be able find my vesc.
It hasn’t lit up at all, this is new out of the box too (it didn’t light up before updating it either)
All I did was update the firmware on the tool from the website
@moddedlife thank you for the input, that was going to be my next question as well.
Did you have the USB cable plugged in before powering on? In that case it would not light up before the update. If the FW updater tool was able to flash the uSplit before, then that means at least the bootloader was ok at the time. I am suspecting that if you attempted to update it again, you would not be able to get it to work because the bootloader is corrupted. That can happen if the offset (shown below as number 8) entered in the updater tool is lower than “0x2000”. I have seen that once before when a typo was made and 0x200 was entered instead of 0x2000.
Can you try the reprogramming process once more to see what happens?
Yes I did
Yeah it went through the whole process successfully
You think?
I am certain I had it set to 0x2000
As for the image, I used the zip file, it didn’t say to unzip so I just used that.
I shall unzip and try reprogramming
Oooh! That’s it right there. I will add a bit to the instructions to clarify that. You should be good after unzipping and reprogramming.
Alright we shall see, it’s trying to connect to the usplit right now
Seems to just crash now when trying to connect, I shall try a different computer
Try having the uSplit connected to the computer before opening BOSSA. If you are not able to get it to connect, then you can send the uSplit back to me and I’ll exchange it for a new one.
It is possible that when the .zip file was used, it did something weird and corrupted the bootloader anyways.
Yeah had to have it connected to the PC before power
It updated successfully and seems to be working! Excellent! I will report back if there are any issues
It will be put to major work here with three data loggers going simultaneously.
Sounds great! Glad it is up and running now! Definitely let me know if any issues are seen. Feedback like yours is the only way I know if bugs exist in setups that I do not current have, so it is very valuable. If needed, I will get an iLogger and continue debugging on my side.
