search

ammolytics / projects

Source code and instructions for do-it-yourself projects.
https://blog.ammolytics.com
MIT License
47 stars 20 forks source link

Installation Problems #28

Closed GTMux closed 4 years ago

GTMux commented 4 years ago

This project is great! And I would love to bring it in our shooting club for these people who like accurate reloads. Unfortunately I'm not able to get the RPi Zero running due to problems during the installation process:

. . . .

npm install

bluetooth-hci-socket@0.5.1 install /home/pi/node_modules/bluetooth-hci-socket node-gyp rebuild

make: Entering directory '/home/pi/node_modules/bluetooth-hci-socket/build' CXX(target) Release/obj.target/binding/src/BluetoothHciSocket.o In file included from ../src/BluetoothHciSocket.cpp:8: ../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker)’: ../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void ()(uv_work_t)’ {aka ‘void ()(uv_work_s)’} to ‘uv_after_work_cb’ {aka ‘void ()(uv_work_s*, int)’} [-Wcast-function-type] , reinterpret_cast(AsyncExecuteComplete)

... ... ... gyp ERR! build error gyp ERR! stack Error: make failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23) gyp ERR! stack at ChildProcess.emit (events.js:198:13) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12) gyp ERR! System Linux 4.19.75+ gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /home/pi/node_modules/bluetooth-hci-socket gyp ERR! node -v v10.17.0 gyp ERR! node-gyp -v v5.0.5 gyp ERR! not ok

erichiggins commented 4 years ago

@GTMux Thanks for reporting this! If you have the complete installation log available, would you mind including it here in the ticket, or as a separate Gist? I think some critical information from the trace may be missing.

Lastly, can you provide a little bit of detail about your setup?

Thanks again!

GTMux commented 4 years ago

Hi @erichiggins, thanks for the fast response. Setup is:

System setup started based on your description (rename, expand etc., update, install bluetooth bluez libbluetooth-dev libudev-dev, cloning project)

And than this time it seems to work fine except some warnings concerning missing pre-build resources (please see InstallLog.txt attached). Only the service installation ended with a failure (Log attached). And unfortunately I got an error message in the app on my android tab (SM-T210 Android Version 4.4.2) that no device is connected.

The difference between today and the last 5 days of installation trials: I only did: sudo apt-get update and NOT sudo apt-get upgrade and NOT sudo apt-get distr-upgrade

Maybe you have some hints for me to get this running?

Thanks for your time!

Ralf

2019-10-26_InstallLog.txt 2019-10-26_ServiceInstfail.txt

GTMux commented 4 years ago

Anyone have any ideas? I would be very happy about advice. :)

Thanks and best regards, Ralf

erichiggins commented 4 years ago

Sorry for the delay (I was traveling for work)!

I have some time this weekend to dig into this issue -- I'd first like to see if I can reproduce it.

The real solution, I believe, would be for me to provide a ready-to-flash image that has everything installed. That avoids this type of complication.

GTMux commented 4 years ago

Thanks a lot - this would be great. I was close to ask you for an image. :) Sorry to bother you with this problem...

erichiggins commented 4 years ago

Just a quick update on this: I have made some significant progress on a pre-configured image. It's nearly there, just requires a few more tweaks. Once it's ready, I'll share a link for you to give it a try. If it works for you, I'll update this repo and docs w/ an official link to it.

erichiggins commented 4 years ago

Another update: I know it's taking a while -- sorry about that! It's very close now.

More context: I'm using a system called buildroot to build a custom SD card image. The manual is long and complex, and it takes a few hours to run a complete build from scratch. So, it's not quite as easy as making a small change then being able to test it quickly. I still have to write the image to an SD card, boot a system, and see if everything is working.

It's coming along, but is very, very time-consuming. The two pieces I'm blocked on are:

  1. Getting bluetooth working correctly
  2. Getting the Open Trickler software to run correctly on boot

Thanks for your patience on this. If you happen to have any experience with buildroot, help is always appreciated!

GTMux commented 4 years ago

Hi Eric,

thanks for the update. I keep my fingers crossed that you succeed. Unfortunately, I have no idea how I could help with software related stuff...

erichiggins commented 4 years ago

Great news! I just got bluetooth working! It's late now, so I haven't tried loading the OpenTrickler software yet. I'll give that a shot tomorrow -- it's looking very promising so far!

erichiggins commented 4 years ago

SUCCESS! I'll share an image file today along with some instructions. It'll help if someone can try it out and make sure it works on their end before I publish it to the world.

GTMux commented 4 years ago

great - would be a pleasure for me to test it! :)

erichiggins commented 4 years ago

Test image file can be downloaded here. Please be sure to read all of the following instructions and notes.

Please let me know if you have any questions, have any issues, or (hopefully) are able to get it working!

Instructions

Notes

erichiggins commented 4 years ago

Quick update: I'm working on another image that addresses some of the missing features that I listed above. Namely:

GTMux commented 4 years ago

Hi Eric,

Thanks for your updates. I downloaded the image, decompressed it, brought it on the SD card using balena etcher with success. Due to the fact that my scale is currently borrowed by a friend I was not able to connect the scale.

Currently I can't establish a bluetooth connection and can't find the raspberry via bluetooth. Open trickler app: You are not connected to a device.

Is it necessary to connect to a scale first?

matsyngvelindgren commented 4 years ago

IT WORKS SUPER NICE !!! Awesome job man!!! Many thanks and a big hug :-D

erichiggins commented 4 years ago

@GTMux From the Android App, you need to connect to the unit. You do not need to pair with the app from your Bluetooth menu/system settings.

I'm pretty sure I demonstrated all of this in my YouTube video.

Hope this helps!

FWIW: The UI needs some updates to make this all easier based on what we've learned from using it.

GTMux commented 4 years ago

@erichiggins Thanks for the information but this is what I did. The app isn't showing any device. Of course I tapped the button on the bottem-right of the screen a couple of times. :) Maybe because of my old Android Tab. I will try with a newer model in the following days.

IMG_8405

erichiggins commented 4 years ago

@GTMux That's interesting. A few things come to mind:

The Pi won't advertise itself on Bluetooth if it cannot detect the scale. The scale has to be plugged into it, turned on, and correctly configured.

Assuming a correct setup on the Pi/Scale, the question is: Is the problem the Pi or the Android app? There are a few ways to find the answer to this. There's a free Android app called nRF Connect which is pretty useful for debugging Bluetooth devices. It will let you see every device that is advertising.

cyclepath37 commented 4 years ago

I was having the same issue as GTMux and then noticed only the boot partition was on the sd card. I’m not sure what i am doing wrong.

erichiggins commented 4 years ago

@cyclepath37 Which operating system are you using? Windows and Apple computers won't be able to see all three, but the boot and code should both be visible.

As long as your using the balena etcher program to flash the SD card, it should create the same result.

Did you configure your scale using the instructions listed in my article?

cyclepath37 commented 4 years ago

Windows and using balena etcher as suggested. Only showing boot if i etch with or without decompressing. I have an A&D HR202i, but have it configured the same as you show with the fx120.

erichiggins commented 4 years ago

@cyclepath37 I'm not familiar with that particular model, so you may want to double check the manual to verify that it's RS232 interface operates the same way. For the sake of this conversation, let's assume it does for now.

Potential causes:

I can share another image tomorrow that includes logging, which would help to diagnose these problems more easily.

With the image you have, you can configure it to connect to your WiFi then SSH into the Pi and see what's going on, if you're comfortable working with the Linux command line.

Shooter0423 commented 4 years ago

@erichiggins thanks for the updated image. I loaded to two different RPi Zero W's with different brand SD cards (1 16g, the other 32g) both connected to the scale and worked to ready the scale value in the startup are. My issue comes in 2 parts. 1) After the initial success with the 2 setups, they developed a inability to connect, it was getting late so I shut everything done. tried it just now and things are working fine again, don't know what I did different? Is there a correct way to disconnect 2) Havent been able to get the vibro motor to do its thing. I know the motor and tube work cause I can test the on an Arduino. Is there a reason that the control pin changed, don't think it is the problem but just asking

erichiggins commented 4 years ago

@Shooter0423 Glad you were able to get them working fairly easily -- now to see if we can figure out some of the issues you've run into.

Let's start with the motors not running. The reason I changed the control pin from 15 to 12 was to allow the use of PWM (Pulse Width Modulation) control on the motors.

Here's a pin out diagram for the Pi Zero W. Note that physical pin 15 is BCM 22 and physical pin 12 is BCM 18 (PWM 0)

You can check if this is the issue you're having pretty easily with two different methods:

First, power up the OpenTrickler Pi & scale in the usual way, connect w/ the app, then set a charge weight (like 10.00 gr) and hit the Play button. At this point, the motor should be running. If it's doing nothing, you can check the control pin on the Pi using a multimeter/voltmeter. You should see it turning on/off with approx 3V. If you don't, then check the other pin.

The other method you can use is to change the pin setting in the config file. Pull the microSD card out of the Pi and connect it to your computer. You should see a drive called code. On that drive, there will be a folder named opentrickler which has a file named ecosystem.config.js. Open that file with a text editor (NOT a word processor). You can change the MOTOR_PIN setting from 12 to whatever you are using. You may still want to use a multimeter in the same way I described above to verify that it's working as expected.

As for the issues you're having with disconnecting... I may need more info for that. There could be a software bug that I can fix. For now, how about we get the motor working first?

Shooter0423 commented 4 years ago

Thanks for the quick response. I had debugged the issue the way you described but the real culprit turned out to be a bad solder joint. So everything is up and running. The Bluetooth connection seem to need more time than I’m allowing, I think that will eliminates the problem, I’ll let you know.

Sent from my iPhone

On Dec 27, 2019, at 5:37 PM, Eric Higgins notifications@github.com wrote:

@Shooter0423 Glad you were able to get them working fairly easily -- now to see if we can figure out some of the issues you've run into.

Let's start with the motors not running. The reason I changed the control pin from 15 to 12 was to allow the use of PWM (Pulse Width Modulation) control on the motors.

Here's a pin out diagram for the Pi Zero W. Note that physical pin 15 is BCM 22 and physical pin 12 is BCM 18 (PWM 0)

You can check if this is the issue you're having pretty easily with two different methods:

First, power up the OpenTrickler Pi & scale in the usual way, connect w/ the app, then set a charge weight (like 10.00 gr) and hit the Play button. At this point, the motor should be running. If it's doing nothing, you can check the control pin on the Pi using a multimeter/voltmeter. You should see it turning on/off with approx 3V. If you don't, then check the other pin.

The other method you can use is to change the pin setting in the config file. Pull the microSD card out of the Pi and connect it to your computer. You should see a drive called code. On that drive, there will be a folder named opentrickler which has a file named ecosystem.config.js. Open that file with a text editor (NOT a word processor). You can change the MOTOR_PIN setting from 12 to whatever you are using. You may still want to use a multimeter in the same way I described above to verify that it's working as expected.

As for the issues you're having with disconnecting... I may need more info for that. There could be a software bug that I can fix. For now, how about we get the motor working first?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

erichiggins commented 4 years ago

@Shooter0423 Great! If you are able to reproduce the bluetooth issues, go ahead and open a new issue here on GitHub so we can track it separately.

@GTMux @cyclepath37 Have either of you had luck getting yours working?

GTMux commented 4 years ago

@erichiggins: thanks for the update. As mentioned I‘m still waiting for the scale. When the scale arrives back at my home I‘ll let you know directly.

cyclepath37 commented 4 years ago

Still stuck. I confirmed the fx & hr202i balance RS232 pins are the same. Does it need the entire breadboard motor circuit connected for the bluetooth to work? I am using an old dandy trickler and haven’t tied it in yet, so i have been trying to connect with just the bare pi zero without the motor circuit.

erichiggins commented 4 years ago

@cyclepath37 The Pi doesn't try to detect the motor circuitry at all (not even sure if that's possible), so you should be fine without it. The Pi only waits for a scale to be detected and the bluetooth drivers before it advertises itself so that the app can connect to it.

Did you follow these instructions to configure your scale? Without those steps, the Pi won't be able to communicate with the scale. It's not just as easy as plugging it in, unfortunately.

Datakalu commented 4 years ago

Having the same result as GTMux and cyclepath37. Flashed the test image using Windows & balena, fx120 connected and configuration confirmed. Pi does not advertise on Bluetooth.

Shooter0423 commented 4 years ago

Seems like I'm having a little better go at it then @GTMux, @cyclepath37 and @Datakalu. I'm working with 2 different RPi Zero W's, one has been problematic from the beginning in regards to the Bluetooth connection. #1 would connect on startup only some of the times, like 1 in 10 on average. #2 will connect on startup most of the time, but sometimes it may take 2 or 3 startups (once as many a 5 this evening). I haven't isolated anything in my work area that could causing interference, (for a short time both where working kinda consistently and then my wife would come in the room and they would quite, I sure was going to miss her). My startup procedure and some observations. I quite plugging the power in and out on the pi and use the switch on a power strip, not sure how robust the micro usb sockets are. I wait 2 minutes after turning on power to the pi to boot, I set a timer. I then start the mobile app, wait a little, go into the menu and get Bluetooth Devices, wait a little, then hit the green button. If it doesn't come back with the info from the scale in 10 or 15 seconds, it not going to because there is no connection ( I always wait for the app to tell me so ) try the green button a time or 2 more (never seems to work a second time if it didn't work the first) then turn off power, check the scale, check the cables, check that i'm not going crazy and do another startup. I know its frustrating, but this thing works. It looks like @erichiggins is using a stick powder in the video and I am working with load of Tac under a 77gr SMK, (also got a Varget load for a 6BR to work on) I haven't loaded real ammo yet, probably do that tomorrow as it looks like Wednesday will be the best day to go out this week. I built my vibro-motor different so I'm tuning the motor.js and probably will need to reimplement some speed steps that have been commented out in trickler.js. I'll start new threads with this info as I get it organized.

chaseerickson12 commented 4 years ago

@erichiggins I’m having the same problem as everyone above. @Shooter0423 does the pi require a 16 or 32g sd? I’ve tried a 4 and a 8g and can’t get anything to work. I’m going to pick up a 16g after work and a usb to micro adventure adapter and see if that makes a difference over using a micro sd to sd adapter. Is the any way to test to make sure your on the right trail.

Shooter0423 commented 4 years ago

@chaseerickson12 I was trying to run 2 pi's. One has a 16g standard Kingston, the other a 32g Ultra Scandisk. I swap the cards back and forth in the good working pi, as they both have the new image as supplied by @erichiggins recently. I use the adapter that comes with a micro card, have several laying around, don't think that matters. Anyway in my case it doesnt matter. Are you downloading the compressed image and using Belena to flash it to the card? Earlier when I was having problem with the first pi, a site suggested formatting cards with a freebie called 'SD Card Formatter', don't know that it actually fixed any problems but I use it every time before flashing cards now. Another suggested freebie, same site I think, is Note++. Works will when modifying/editing files in the code folder

erichiggins commented 4 years ago

Thanks to everyone for keeping me posted -- I know it can be frustrating but it really does help a lot to get feedback like this so that I can focus on the right problems that will work for everyone. Also thanks to @Shooter0423 for chiming in, helping others, and sharing your experience!

I think the biggest issue is that we're flying blind.

The only debugging info you have available is whether or not the app can connect to the Pi over bluetooth. There are a lot of things that could go wrong to prevent that, but without having some way to see that, it's impossible to find the root cause.

I suspect that if I can make the Pi's logs available via your web browser at http://opentrickler.local on your local Wifi, then we'd at least have a better idea of what's going right and what's going wrong, like:

The other issue that I think may be worth addressing is allowing the Mobile app to connect to the Pi even if the scale isn't connected. This requires work on the mobile app as well, so it's a bit more work to pull off -- because of this, I've been kind of avoiding it.

I'd like to get everyone's thoughts on this though before I proceed. You might have better ideas and I'd love to hear them!

erichiggins commented 4 years ago

@chaseerickson12 A 4GB or 8GB card should be fine. It would probably even work on a 1GB card, though I haven't tried it.

Shooter0423 commented 4 years ago

Thanks @erichiggins, glad to help. I think viewing a log will pay dividends faster. The mobile app is working good enough.

Datakalu commented 4 years ago

I have the wrong USB to Serial cable. I suspect that’s my problem and I’ll let you know how it plays out when I have the correct cable.

chaseerickson12 commented 4 years ago

@Shooter0423 I have not been decompressing the file. Ill give it a shot. Im interested to hear if @Datakalu serial cable was the problem

chaseerickson12 commented 4 years ago

https://www.amazon.com/gp/product/B075XHWVSJ/ref=as_li_qf_asin_il_tl?ie=UTF8&tag=ammolytics0f-20&creative=9325&linkCode=as2&creativeASIN=B075XHWVSJ&linkId=7c662ec9d4021bf3c1374f86ff1b9b0d

Do we need to be using a usb to serial that requires this adapter? The one I purchased from the recommended list didn’t require this to be plugged in. Or could this be the problem that I’m experiencing

erichiggins commented 4 years ago

@chaseerickson12 Yes, you do need that actually. I know that you can connect the cables without it, but the adapter doesn't change the male/female interface, it changes the pin wiring arrangement. The A&D scales use a rather strange wiring setup which requires this in order to work.

chaseerickson12 commented 4 years ago

@erichiggins i think I’m slowly eliminating my problems one at a time lol 😂. I’ll report back now that I’m trying the adapter

chaseerickson12 commented 4 years ago

@erichiggins i can get Bluetooth connection 👍🏻 Now time to figure out where my wiring is messed up lol so the trickler works. If any of you used a mini solderless breadboard if you can post a photo that would be appreciated. I’m not 100% on if I followed the diagram on the main directions correctly.

erichiggins commented 4 years ago

@chaseerickson12 let's follow up on that over email tomorrow. Send me photos of what you have and I'll see if I can help sort it out.

erichiggins commented 4 years ago

Update

I've made the logs available via web browser on the OpenTrickler with the following uSD image for the Pi. After you flash the uSD card with the following image, you will need to modify the boot / wpa_supplicant.conf file with the details for your WiFi network so that the Pi can connect to it.

Once booted, you can view the logs by visiting http://opentrickler.local/ in the web browser of any computer or mobile device that's on the same WiFi network. If it does not resolve, the most likely issue is a misconfigured wpa_supplicant.conf file.

Do not share the contents of your wpa_supplicant.conf files here, as they will contain the password for your WiFi network and it may compromise your network security.

Documentation for wpa_supplicant.conf can be found online. Here's one example.

uSD Pi Image

This image is considered alpha quality and is intended only for testing purposes until these issues can be resolved and verified by all interested parties. Afterward, I'll provide some cleanups and a new image, which everyone should expect to download and reflash their uSD cards with.

Download opentrickler-1.1.6-ALPHA.img.zx

Checksums

Optional, in case you want to verify the image after downloading and extracting

Successful OpenTrickler Log Example

Setting: process.env[ NODE_ENV ] =  production
Setting: process.env[ MOTOR_PIN ] =  12
Setting: process.env[ SCALE_BAUD_RATE ] =  19200
Setting: process.env[ SCALE_DEVICE_PATH ] =  /dev/ttyUSB0
Setting: process.env[ DEVICE_NAME ] =  Trickler
===== STARTING UP =====
setting speed from undefined to {"true":60,"false":150}
Opening trickler...
Serial port open
weight: 0, unit: null, status: null, stable: false, stableTime: 0
weight: 0, unit: 0, status: null, stable: false, stableTime: 0
Scale is ready!
Trickler is ready! true
Scale weight reads: 0 0, stableTime: undefined
weight: 0, unit: 0, status: 0, stable: true, stableTime: 8
on -> stateChange: poweredOn
Scale is ready!
weight: 0, unit: 0, status: 0, stable: true, stableTime: 82
scale: undefined
Checking if ready... TRICKLER: true SCALE: true BT: true
on -> advertisingStart: success
advertising services...

Unsuccessful OpenTrickler Log Example

Checking if ready... TRICKLER: false SCALE: false BT: true
weight: null, unit: null, status: null, stable: false, stableTime: 0
scale: undefined
Checking if ready... TRICKLER: false SCALE: false BT: true
weight: null, unit: null, status: null, stable: false, stableTime: 0
scale: undefined
Checking if ready... TRICKLER: false SCALE: false BT: true
Datakalu commented 4 years ago

Haven’t flashed the latest image but I’ve install the correct serial cable and was able to connect on a couple of occasions. However, it drops the connection before I can run the motor circuit.

Datakalu commented 4 years ago

Motor circuit runs, turns out it was me when returning to the main screen. Haven’t thrown powder yet but works as described. Bluetooth connection is hit and miss.

erichiggins commented 4 years ago

@Datakalu The logging capability in the latest image should give more insight as to why you may be having Bluetooth connection issues. I've seen a couple occasions where the USB/Serial driver acts strangely.

Datakalu commented 4 years ago

@erichiggins I’ve never played around with tech projects like this and it’s been an education getting to this point. I’ll keep slowly chipping away at it but I’m learning as I go. Great project and support, thank you!

MrMr-No commented 4 years ago

Can we get Pi password?

erichiggins commented 4 years ago

@MrMr-No Yes! I actually shared it in an earlier post on this thread.