Universal Advanced VESC Remote Control (Photon) - Custom design

@ElskerShadow : I not worrying, he already confirmed my order is processing :slight_smile: But thatā€™s the last part i need to finish my build with @Riako :smiley: I have few questions :

  • When did you placed your order and how long it took to receive it ?
  • What do you think about this remote (vs. a GT2B, R1/R2, ā€¦)

@Wajdi : Still no emails even with the other emailā€¦ Maybe your system is not working :thinking: I also saw you might plan to change the design, will it be possible to order just the printed box ?

Have a great day !

Damn I wish @Wajdi could design a second version of his remote with two separate buttons like this.
That Evolve R2 is great ā€¦and feels great. Having two buttons was a very clever idea.

1 Like

@Zigm4 I tried to send you the order confirmation manually right now, let me know if you still donā€™t receive it. Iā€™m not changing the design any time soon, perhaps in the future I will work on an additional version.

1 Like

I agree w thisā€¦ the concept of having a ā€œdashboardā€ is cool but on a board (moreso than on a bike or a car) you really need all your focus on the road so you can react to what is happening.The data available isnā€™t really helpful unless you are prototyping/testing electronics. I passed on a coulometer for this reason.

I got it :smiley: But still no information on the expected shipping date and tracking code, normal ? :slight_smile:

Yes, you will receive an email with tracking information once it is shipped. Expected in about 10 days.

1 Like

Thanks a lot ! Please donā€™t forget to send the email directly to my email address (not with you mailing tool)

Wajdi,

I'm so excited for this combo! I purchased the remote and the receiver off your website on Feb 26 Using paypal.

Do you have an ETA for future remotes? Order ES-252. This remote is very desirable for me, as my current setup is a bit too touchy.

I have dual 80MM 6kw motors running 12s. need a better controller. :slight_smile: Mostly for brake ramp and initial startup smoothing. I will have questions too on how to hook to dual VESC and also dual BL-Control 9120 150A Escā€™s.

I just realized i may need two receivers for dual motor. Is this the case? can you invoice me for another one through paypal or something so i can make sure i have what i need? Thanks ā€“ _*

*EDIT: ElskerShadow answered this Question ^^^

No you just need canBUS and enable in the VESCtool the can FWD

Thanks! Iā€™ve been reading a few hours on vesc and software and all that. makes sense :wink:

1 Like

I got my remote today so I immediately set everything else aside and got to work on swapping remotes thinking I could knock it out quick and go for a short ride. I was wrong and I hate software sometimes. So I have tried Ackmaniakā€™s V3.10, stock V3.35, stock V3.31 and stock V3.29 firmwares. I realize some of the firmware versions arenā€™t supported but I was just giving it all I had available at the time.I have the TX and RX bound with green lights on both plus I have telemetry coming through just fine on the remote. I have the baud rate set and Iā€™ve tried setting it to UART as well as Nunchuck (not nrf) and selected current in the nunchuck menu. The remote button up front is set to cruise. However I am unable to get any throttle response from the motors and I canā€™t see any indications of stick movement in the VESC Tool with any of the firmware versions I have available to me. Unfortunately I can not find any past releases of the VESC Tool for Windows other than what I have previously downloaded. My other remote works if I set it to PPM and reconnect the servo connector so the other settings seem fine. I may be skipping something simple out of frustration but Iā€™ve done everything I can think of and Iā€™m not getting anywhere. Does anyone have any ideas or know what I may be overlooking?

Canā€™t really help but the struggle can be hard for this remote. I recieved mine 2 month ago never used it because I could never bind it. Apparently @Wajdi sent me a new RX to try but been waiting for week. Since early January iā€™m the happy owner of a 170 ā‚¬ brick remote

1 Like

@Dizzee I have been looking into this for the past few days, and I found the problem. I forked the bldc source code and applied necessary changes to get this working again. I will release a modified FW 3.34 tonight that should get cruise control, reverse, and nunchuck controls back on UART.

1 Like

I can understand your frustration. Itā€™s a lot of money to have sitting around. To Wajdiā€™s credit heā€™s taken responsibility for the original receivers and he seems be doing what he can to get it working as intended. Iā€™m more frustrated with the state of the VESC project. There is no reason given for the changes effecting products that do nothing but add value. For me the fact that thereā€™s no repository containing past releases of software and firmware is beyond frustrating. All I could find was a forked GitHub project containing previous releases for MAC OS. I donā€™t want to muddy the thread with VESC frustration. I just wanted to state what effects this project directly though. Especially if a specific range of firmware is necessary for the time being.

For those that need it and can make use of it, hereā€™s a link to the previous releases of VESC Tool for MAC OS. MAC VESC Tool Releases

I just managed to have the controls compatibility issue fixed. The modified version is FW 3.35, thats the latest release, I made changes to fix nunchuck compatibility issues with the Photon receiver. You can download the FW from my GitHub here https://github.com/wajdib/bldc/tree/master/build_all Make sure to choose the correct hardware version, and the default FW available.

For this you will need the latest version of the VESC TOOL as well, V0.88.

This also applies to anyone that wants to update to latest vesc versions and have problems with controls or telemetry, this should fix it for the old Photon receivers.

Let me know if this works for you.

3 Likes

Hi Wadji

I have tried your modified 3.35FW VESC firmware with a focbox 4.12HW and vesc tool 0.88 with following results:

  • modified 3.35 FW loaded into VESC OK

  • Cannot get FOC motor detection to work at all ( does nothing) but BLDC motor detection works OK

  • No telemetry at all on photon remote - still shows 255.2 as FW on remote

  • Any throttle command from remote brings up vesc tool error ā€œSerial Port Error- Ƅ device attached to the system is not functionalā€- only way this can be cleared is by re-booting vesc ( power-down and re-power)

  • Throttle command on remote spins motor OK on BLDC only ( with current - no reverse on Nunchuk ) even if VESC tool error is present ( as above) but no FOC at all

  • Installing this modified firmware appears to remove any VESC PPM control via RC remote if ƜART and PPM" is selected from App Settings/General

  • Cruise control seems to work OK

Any-one else tried this??

Cheers

1 Like

Hmm, thats weird, I will look into this. BTW for anyone wondering, all new receivers are compatible with latest vesc firmwares out of the box.

1 Like

Can anyone tell me which to area to short so I can bind this bad boy

Canā€™t tell you exactly but if you use the ā€œsearch on this topicā€ feature with" short" or ā€œbindā€ keywords, youā€™ll find hints. It seems to you need to read around post #498 on this topic. Thereā€™s a picture, read around.

Hope this helps

Here you go

2 Likes