Recent Posts

11
v2.0 / Re: Bad actuator?
« Last post by Tibbitts on November 30, 2018, 12:28:48 PM »
I'll have to listen for the actuator itself while switches are operated. So far I haven't noticed any changes while the motors running. Brake switch does nothing.  Pretty sure the veins are always wide open right now
12
v2.0 / Re: Bad actuator?
« Last post by hakcenter on November 30, 2018, 12:17:24 PM »
When you emulate, can you hear the actuator moving when you hit your brake / cruise switches, or with the motor running can you get that hairdryer whine with the brake on, and it goes away with brake off ?

If so ya it's just the VR integration not counting well.
13
v2.0 / Re: Bad actuator?
« Last post by Tibbitts on November 30, 2018, 12:09:02 PM »
 Thanks for the info.  It's a he351ve. I'll take a look at the vr sensor
14
v2.0 / Re: Bad actuator?
« Last post by hakcenter on November 30, 2018, 09:14:58 AM »
The LBB code is setup to wait for 2 things. First is the actuator needs to communicate back. Otherwise it'll never drop into the main loop. At the main loop, everything waits for the VR sensor / turbo to be spinning atleast 1000rpm.

If your actuator responds to your brake/cruise switches after enabling emulate.. You might have a VR problem. If it doesn't respond the actuator doesn't respond at all, even with emulate, there-in lies your issue.

What kind of actuator is it ? 351ve ? 300vg ?
15
v2.0 / Bad actuator?
« Last post by Tibbitts on November 29, 2018, 06:44:12 PM »
Thinking i might have a bad actuator.  Main screen on android app is just dashes, however emulate function responds to brake/cruise switches.  Actuator does power on.  The pins seem to be placed and secured in harnesses properly.  Trying to find a known working actuator locally to check against. Any thoughts?
thanks
16
v2.0 / Re: LBB Common Code
« Last post by hakcenter on November 27, 2018, 04:09:14 PM »
v3.0.0 update

Major Changes:
  • Bluetooth serial communication is extremely specific now.
    • All responses are byte length specific.
    • Ask commands are written with length of data to be sent first, then the LBB receive will know how many bytes to expect before timing out
    • So do not try to communicate through USB while connected via Bluetooth. It'll break both.

Code: [Select]
byte[] bytes = "bt_data".getBytes();
bt_out.write(bytes.length);
bt_out.write(bytes);
bt_out.flush();

Translates as, send 7, send "bt_data". LBB knows to expect 7 bytes, waits up to 0.5s before timing out waiting for said bytes to come in.
17
v2.0 / Re: Android development
« Last post by hakcenter on November 20, 2018, 01:44:06 PM »
Okay so this is basically ready to go. I'm going to drive around on it for another week before letting the update rip.. but  it's basically all good to go.
18
General Discussion / Re: Starting a new build
« Last post by hakcenter on November 17, 2018, 04:10:49 PM »
mmmmmmmmmmmmmmmmmmmmm
19
General Discussion / Re: Starting a new build
« Last post by Chewy1576 on November 16, 2018, 10:21:15 AM »
Not really. The problem with these trucks is that there is no room for an air-to-air IC in the front. Between the radiator, AC condenser, and oil/trans coolers, there's no room. A water-to-air IC is possible, but I'm not interested in that right now. If I do anything, I'll add water-meth injection, run by the controller. Also, I'm only going to allow 15-16 PSI max so an IC isn't really needed.
20
General Discussion / Re: Starting a new build
« Last post by Rx7man on November 16, 2018, 10:04:44 AM »
looks good.. are intercoolers an option you can add though?