Speedict Ebike - Anybody seen/tried this?

It is hard for me to explain in English sometimes I use the wrong word what can have an other interpretation

The switch i was talking about is a software button for switch between off-road and legal.

De hardware switch / bypass is only temporary till the software button is finished.
This is not a great solution because cops can follow the wires when they take the bike for research.

BUT i like the option paddle 3 times back for instant legal even more. Then cops can not find a way to unlock off-road mode.

To switch back to off-road you can program a software button for the android app.
When cops take the bike for research the don’t have the phone and the bike is legal and we get the bike back.

This little red thing getting better and better !!
 
Erikjan said:
It is hard for me to explain in English sometimes I use the wrong word what can have an other interpretation

The switch i was talking about is a software button for switch between off-road and legal.

De hardware switch / bypass is only temporary till the software button is finished.
This is not a great solution because cops can follow the wires when they take the bike for research.

BUT i like the option paddle 3 times back for instant legal even more. Then cops can not find a way to unlock off-road mode.

To switch back to off-road you can program a software button for the android app.
When cops take the bike for research the don’t have the phone and the bike is legal and we get the bike back.

This little red thing getting better and better !!

that's make sense, the backward 3 cycles not for toggle offroad / roadlegal2, it is one way switch to turn on legal mode ... only android can resume offroad back !
 
After this post:-

speedict said:
will pass your logs to our engineers for inspection, please wait for next week after our new year holiday ended

and a few more posts from me, your next post was :-

speedict said:
Speedict Mercury Android Client 1.0.8 is available on Google Play, it is highly recommend to prevent firmware upgrade failure caused by some Android ROM...

Does that mean the engineers advised that a firmware update should help my problem?

I got the Android client and tried out the throttle control again. I tried measuring the voltage out of port 4. Signal to ground was 0 volts whether port 4 output was 0 or 100. I noticed:-

Erikjan said:
I have instaled the mercury now.
6km start is better now but still soft....

So it works for Erikjan. What am I doing wrong or does he have different firmware?

speedict said:
... and the firmware server will be re-open next Monday

I didn't notice this and tried updating firmware today (Sunday). Unsurprisingly it didn't work but about 20 secs after giving up I switched to Port Status. It showed battery voltage 38 volts which was odd as it was about 34 Volts and had been showing correctly previously. Then the green led on the Speedict came on and a few seconds later the green and red led both went off. It hasn't been possible to get any response from the Speedict since. I've disconnected the power and reconnected several times.

With the power disconnected I tried connecting a laptop to the Speedict USB port but the laptop failed to detect anything connected.

What do I do now? It is looking dead, neither the green or red led comes on anymore.
 
I have some troubles now. The speedicht dont connect to the phone.
The red led is on the geen dont blink. I dont now what happend.
When i twist thorttle noting happen. Dont understand.
When i put the usb to computer nothing happens.

*edit

Now i have a second problem when i connect the old first speedict i make a mistake and change polarity.
That one is dead to now i dont have a working speedict. :(
Is there a way i can fix the old speedict? When i connect to pc the leds burn so it is nog compleet dead.
Only when connect with battery i do nothing. :(
 
Ken Taylor said:
With the power disconnected I tried connecting a laptop to the Speedict USB port but the laptop failed to detect anything connected.

Speedict Mercury doesn't support USB and PC Client

Ken Taylor said:
What do I do now? It is looking dead, neither the green or red led comes on anymore.

if both red and green led not flashing it is mean your speedict mercury might damage (perhaps hardware) ? need to investigate, before you ship it back, can you tell me :

1. did you upgrade speedict mercury android client to 1.0.8.
2. did you upgrade the firmware (we had closed the internet version, but you might have local 1.0.3 copy) recently before android client 1.0.8
3. when's it happened ? after firmware upgrade ?
 
Erikjan said:
I have some troubles now. The speedicht dont connect to the phone.
The red led is on the geen dont blink. I dont now what happend.
When i twist thorttle noting happen. Dont understand.
When i put the usb to computer nothing happens.

did you upgrade firmware ? with or without mercury android client 1.0.8 ?


Erikjan said:
Now i have a second problem when i connect the old first speedict i make a mistake and change polarity.
That one is dead to now i dont have a working speedict. :(
Is there a way i can fix the old speedict? When i connect to pc the leds burn so it is nog compleet dead.
Only when connect with battery i do nothing.

no, the voltage regulator component was completely damaged because unlike speedict mercury, speedict ebike has no inverse polarity protection, when you plug in usb the mcu is now supplied by computer 5v that's why you can connect with usb to synchronize data in old day.
 
speedict said:
Speedict Mercury doesn't support USB and PC Client

OK. That explains why computer didn't see a USB device.

speedict said:
if both red and green led not flashing it is mean your speedict mercury might damage (perhaps hardware) ? need to investigate, before you ship it back, can you tell me :

1. did you upgrade speedict mercury android client to 1.0.8.
Yes
speedict said:
2. did you upgrade the firmware (we had closed the internet version, but you might have local 1.0.3 copy) recently before android client 1.0.8
I don't know. I selected Firmware upgrade on the Android client options. I saw a screen with one version listed and couldn't find any way to tell it to upgrade. I think the listed version was the one in the device but I wasn't sure. I don't think it upgraded but I don't know how to tell. A little circle spun for a long time. It didn't look like it would stop so I gave up and hit the back button. If I go to that screen now (without connecting to the broken Speedict) I see it is version 1.0.3 (Cloud). I can't remember the version number that was there yesterday but I'm pretty sure it didn't say "(Cloud)".
speedict said:
3. when's it happened ? after firmware upgrade ?
About 20 secs after I gave up on the firmware upgrade and changed to the Port Status screen the Bluetooth connection was lost. The green led flashed for a few seconds. Then the green and red led went out at about the same time. Maybe it was part way through a firmware upgrade when I changed to the Port Status screen and this caused problems.

I don't think it was hardware because I was only playing with the Android app when it failed but I guess there is no way to reflash the firmware without the blue tooth connection?
 
Danny,

I did not update firmware. The software at my phone is version 1.0.8
I dont uderstand what happen.

I had the battery and motor connect to the wrong side for a few weeks, and for that reson the software give negative amps.
Sunday i had some time to resolder the connectors and i connect the battery and controller at the good side. (with the mercury i never change polarity only use input as output and output as input)
But now it dont connect to my phone anymore. Only the red led burn and the green led burns a little bit but you can hardly see.
 
speedict said:
if both red and green led not flashing it is mean your speedict mercury might damage (perhaps hardware) ? need to investigate...

Another thought, I measured the +5V to gnd pins on two ports and got 0 volts. I expect this means it is a hardware failure and not firmware problem. I think there should be 5V there as soon as power is applied regardless of the microprocessor state. Is that right?

Erikjan said:
Danny,
..I dont uderstand what happen...
Same for me.
 
Ken Taylor said:
Another thought, I measured the +5V to gnd pins on two ports and got 0 volts. I expect this means it is a hardware failure and not firmware problem. I think there should be 5V there as soon as power is applied regardless of the microprocessor state. Is that right?

yes if 0v measured on middle pin AND no RED and GREEN led, that's mean the hardware damage, please send it back !
 
speedict said:
yes if 0v measured on middle pin AND no RED and GREEN led, that's mean the hardware damage, please send it back !

Bother. What is the return address?
 
My mercury still have 5 Volt at the port 1 - 4 and i have a red led burn.
Only the green led off it glow only a little bit.
When i try to connect with the phone nothing happen.

Do this mean it is software problem?

I have a video, you can see the original speedict before i damage it and the mercury.
The original have the red led and the green led blinking.
The mercury have the red led and the geen burn only little bit.

http://www.youtube.com/watch?v=4-xC9tFsWBA
 
Erikjan said:
My mercury still have 5 Volt at the port 1 - 4 and i have a red led burn.
Only the green led off it glow only a little bit.
When i try to connect with the phone nothing happen.

Do this mean it is software problem?

I have a video, you can see the original speedict before i damage it and the mercury.
The original have the red led and the green led blinking.
The mercury have the red led and the geen burn only little bit.

http://www.youtube.com/watch?v=4-xC9tFsWBA

Mine did exactly the same thing... Died for no apparent reason. Only red led and no connection to the phone.
I have it now in a package on its way to Danny...

Are you Swedish by the way?

/Anders
 
Hi,

I I am interested to buy a speedict mercury for my new bike but would like some informations about the PAS when used to control the motor current:
Is there a delay or a minimum of pulses count for the throttle activation/deactivation ?
Is the throttle immediately cut when pedalling in backward direction ?

I have a bike with a coaster brake and will install a 12 magnets PAS, so when braking (pedaling backward) there will be 1 or 2 pulses that will be in the opposite direction. I will put a sensor on the front brake but of course it is not possible for the back one.
So I would like the throttle to be cut when detecting a pulse in the other direction, not 1 second later as it is generally the case with the stock controllers.

EDIT: 12 magnets, not 10.
 
Erikjan said:
My mercury still have 5 Volt at the port 1 - 4 and i have a red led burn.
Only the green led off it glow only a little bit.
When i try to connect with the phone nothing happen.

Do this mean it is software problem?

I have a video, you can see the original speedict before i damage it and the mercury.
The original have the red led and the green led blinking.
The mercury have the red led and the geen burn only little bit.

http://www.youtube.com/watch?v=4-xC9tFsWBA

yes it was software issues, might be caused by firmware upgrade failed, have to confirm when received
 
romelec said:
Hi,

I I am interested to buy a speedict mercury for my new bike but would like some informations about the PAS when used to control the motor current:
Is there a delay or a minimum of pulses count for the throttle activation/deactivation ?
Is the throttle immediately cut when pedalling in backward direction ?

I have a bike with a coaster brake and will install a 12 magnets PAS, so when braking (pedaling backward) there will be 1 or 2 pulses that will be in the opposite direction. I will put a sensor on the front brake but of course it is not possible for the back one.
So I would like the throttle to be cut when detecting a pulse in the other direction, not 1 second later as it is generally the case with the stock controllers.

EDIT: 12 magnets, not 10.

however speedict mercury has no pedaling backward detection !
 
Ok i hope so. I send the speedict back 2 days ago.

Let me now when you received it.

Thanx
 
This little orange Mercury....

I'm having issues so I'd like to hear from you guys, how many of you have no issues at all with this little beast?
And if you do have issues, what are they?

Here's whats happened to mine, in short....
It's very difficult to analyze what is going on, is there a HW problem, SW problem in the client, FW issues, Bluetooth issues on my phone or what???

First one was bricked during FW upgrade, ok that can of course happen...
Danny sent me two new ones, a lite version to be used for FW upgrade test and one with the correct FW as a replacement for the bricked one.

Installed in the bike I had issues synchronizing data from the start, I couldn't figure out what made it work, because sometimes it worked.
All of a sudden it just died... I took the bike apart and had a look... Only red LED would come on.

So the lite version was installed, I have a 36V battery so no problem with voltage....
It kinda works... Sometimes... GPS speed is never correctly displayed in the live view, seems to be mph instead of kph even though I have set kph in the settings.
In the trip records it is either 0 or 270 kph something... The correct GPS coordinates are recorded though.

Having the phone on the handlebar is working when Live View is on. Syncing needs to be done by putting the phone, out of its case, directly on top of the compartment where the Speedict is located. Box is plastic btw.
Thinking that it must be the range of the bluetooth on the phone, I tried several other phones as well... About the same result.
Live View looses signal about 4 m from the Speedict.

Today, the data looks very strange indeed and the trip record downloaded is about 360 entries long, even though it should be 35 minutes...
 
The last time I have tried out the Mercury was about 2 months ago. Outside it started freezing so I have only tested the Mercury during a short ride. During my ride I noticed that the blu- tooth connection failed. I haven't touched the bike since because I preferred to wait for sofware improvements like the instant road legal option f.i. by 3 times reverse pedalling. With the problems I have read about bricking and failures during updates lately, I won't dare to update right now.
 
Back
Top