I’m in the market for a remote. Lmk, when they are in stock and ready to ship.
Your 
QualityAssurance kitty makes sure that everything is in good 
shape 
Hey @georgebenett I wouldn’t like to be that guy… but it’s 2 months since I paid for the remote… this is getting a bit irritating long time for you to ship it. Do we have any updates regarding this? I am sure @jack.luis would like the same info.
Thanks
1 Like
hi @EreTroN I’m so sorry for such a long delay, I’m ashamed it took so much longer to ship, I’m going to the post station right now to ship it, you’ll receive an email with the tracking code and you’ll get it at the end of this week. Thank you for supporting the project and for your patience.
7 Likes
Hi,
Could you send me my tracking number when you have a chance?
Also I relate to your full time job + starting a company position. So no hard feelings. Maybe we can restart our conversation about my company helping yours in the US… My DMs are open.
Thanks
3 Likes
Hi @jack.luis I have shipped your remote 15 days ago, I’ll reach out on your DM
1 Like
@georgebenett i have issues connecting the receiver to the vesc’s, i put also 120 ohm resistor on esp sidebut with no luck, is there any aditional hardware needed for receiver?
Can you take a look on the below log:
I (1874) USB_SERIAL: USB Serial task started
I (1884) BLDC_CAN: CAN interface initialized - auto-detecting VESC ID(s)
I (1894) FAILSAFE: Failsafe initialized (priority=10, stopped_threshold=300 ERPM)
I (1894) THROTTLE: Throttle initialized
I (1904) BLDC_CAN: CAN RX task started
I (1904) BLDC_CAN: RX: EID=0x00000901 len=8 (first frame)
I (1914) BLDC_CAN: Primary VESC detected: ID=1
I (1914) BLDC_CAN: Additional VESC detected: ID=2 (primary: 1)
I (1924) main_task: Returned from app_main()
W (1974) BLDC_CAN: CAN bus-off (TEC=128), initiating recovery
W (1974) BLDC_CAN: CAN transmit failed after 3 retries: ESP_ERR_INVALID_STATE
W (1974) BLDC_CAN: CAN driver stopped, restarting
W (1974) BLDC_CAN: CAN transmit failed after 3 retries: ESP_ERR_INVALID_STATE
I (2004) BLDC_CAN: CAN transmit recovered after 2 failure(s)
W (2024) BLDC_CAN: CAN bus-off (TEC=128), initiating recovery
W (2034) BLDC_CAN: CAN transmit failed after 3 retries: ESP_ERR_INVALID_STATE
I (2034) BLDC_CAN: CAN transmit recovered after 1 failure(s)
W (2054) BLDC_CAN: CAN bus-off (TEC=128), initiating recovery
I got mine a few days ago. Unfortunately throttle trigger was stucking in full throttle position, so quite scary scenario.
Ended up opening the remote, and then using a dremel shaved of some meterial on the shell so the trigger would travel without friction.
Now its ok. Still working on a board so not yet tested it out.
So far it feels good in hand and the display is really nice.
8 Likes
@jack.luis I haven’t posted it yesterday, it’s been a week with them, it’s vacationing time here in Sweden and everything moves slowly.
@EreTroN I had too tight clearances on the remotes and the manufacturer couldn’t handle it so sometimes some parts would collide, i fixed it and waiting for the new batch of shells to test it.
2 Likes
No problems at all. I am well aware this is a one person project and I dont have any issues doing a little touch up. I posted it here so it could help someone in the future.
Keep up the good work.
1 Like
thanks! that made my day!
2 Likes
dual throttle touchscreen is working, and in test, has basic touchscreen UI for now
i’m testing the vesc express with my remotes so the users can ditch the receiver, so the remotes can pair with the vesc express by running a lisp script, that would bring down the cost of the remote. more info on how to use it here: VESC Express as Receiver | GB Engineering
4 Likes