reef-pi :: An opensource reef tank controller based on Raspberry Pi.

[GaryE]

So... Anyone familiar with this error while setting up a pH probe? I've never seen it before.

It's on the connector tab in configuration. It's a setup using @Michael Lane 's pH board & it's saying there's no driver for pin 0.

I have him checking to make sure his driver is set up correctly at the right address & verifying the pH probe is being seen with i2cdetect, so *hopefully* that process may give some answers. But I'd never seen this error before & thought some people here may be able to weigh in.

I get a similar error when trying to connect a camera.

 

[GaryE]

https://github.com/hajimehoshi/oto/blob/master/README.md use the one that’s relevant for your platform

It is installed.. someone must have broke something.


Linux
libasound2-dev is required. On Ubuntu or Debian, run this command:
apt install libasound2-dev

terry@serge:~/go/src/github.com/reef-pi/reef-pi$ sudo apt install libasound2-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libasound2-dev is already the newest version (1.2.2-2.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

 

[robsworld78]

Run make deb, and that will generate a Debian package,

I don't have a Mac or Linux machine so have been trying hard with a Pi and Windows but so much to learn as I've never done anything like this. The development guide is nice but need to understand other things to use it.

 

[GaryE]

I don't have a Mac or Linux machine so have been trying hard with a Pi and Windows but so much to learn as I've never done anything like this. The development guide is nice but need to understand other things to use it.

I get that.. sometimes the error messages make it pretty difficult to understand the failure..

This is the error I get trying to "make deb" on the pi4



pi@raspberrypi:~/go/src/github.com/reef-pi/reef-pi $ make deb
npm run ui
make: *** [Makefile:70: ui] Error 1



*** fixed this issue.. what next.. ;)

 

[bishoptf]

I get that.. sometimes the error messages make it pretty difficult to understand the failure..

This is the error I get trying to "make deb" on the pi4



pi@raspberrypi:~/go/src/github.com/reef-pi/reef-pi $ make deb
npm run ui
make: *** [Makefile:70: ui] Error 1



*** fixed this issue.. what next.. ;)

So just curious aare you guys trying to make the latest from github? Which version are you trying to make, pi-zero or pi? I can try to see if I can make, I used to have a build environment set up but need to poke at it, just wanted to understand what you are trying to make.

:)

 

[GaryE]

I'm just trying to get my development environment setup so that I can tinker..

It working like a charm now.

 

[bishoptf]

I'm just trying to get my development environment setup so that I can tinker..

It working like a charm now.

I'm getting the oto error but have it installed...

../../../../pkg/mod/github.com/hajimehoshi/[email protected]/context.go:69:12: undefined: newDriver

not sure what it's missing

 

[GaryE]

it works fine on my raspberry pi 4, but not on my Kubuntu box.

I have the library installed on both, that's not the issue.. I compared the source on both machines, no difference there either.


I don't know..

 

[bishoptf]

it works fine on my raspberry pi 4, but not on my Kubuntu box.

I have the library installed on both, that's not the issue.. I compared the source on both machines, no difference there either.


I don't know..

Yeah this is a linux box also, I was looking through the code and started zoning out, context.go and I see the newDriver being called out but it's not finding something it needs, oh well.

 

[bishoptf]

https://github.com/hajimehoshi/oto/blob/master/README.md use the one that’s relevant for your platform

It's not working in a linux environment, I'm looking at the context.go code but its not apparent as to what is missing, I have the dev files installed so it's something else.

 

[robsworld78]

So just curious aare you guys trying to make the latest from github? Which version are you trying to make, pi-zero or pi? I can try to see if I can make, I used to have a build environment set up but need to poke at it, just wanted to understand what you are trying to make.

:)

There was a minor issue with the Atlas pH driver when calibrating, Atlas could cope with it by my circuit code couldn't so was looking to make sure everything was good. Sounds like @GaryE has a package, now I'm trying to convince him to send me a copy. :)

 

[bishoptf]

There was a minor issue with the Atlas pH driver when calibrating, Atlas could cope with it by my circuit code couldn't so was looking to make sure everything was good. Sounds like @GaryE has a package, now I'm trying to convince him to send me a copy. :)

I was going to offer the same but it's not building on linux and it's not clear what is the issue, something to do with the new sound driver. When I get it working I can also build something if needed, just not sure what the current issue is.

 

[robsworld78]

I was going to offer the same but it's not building on linux and it's not clear what is the issue, something to do with the new sound driver. When I get it working I can also build something if needed, just not sure what the current issue is.

Thanks for the offer, @GaryE was kind enough to send me the package, what a superstar. :)

 

[bishoptf]

Thanks for the offer, @GaryE was kind enough to send me the package, what a superstar. :)

Sure no problem but we still need to figure out why its not compiling on a linux distro, something is needed and its breaking pulling in the oto stuff even though libasound2-dev is installed, I think it has to do with the linker but still looking.

 

[GaryE]

Sure no problem but we still need to figure out why its not compiling on a linux distro, something is needed and its breaking pulling in the oto stuff even though libasound2-dev is installed, I think it has to do with the linker but still looking.

I saw something about alsa, I don't think that's it though.

 

[Ranjib]

So... Anyone familiar with this error while setting up a pH probe? I've never seen it before.

It's on the connector tab in configuration. It's a setup using @Michael Lane 's pH board & it's saying there's no driver for pin 0.

I have him checking to make sure his driver is set up correctly at the right address & verifying the pH probe is being seen with i2cdetect, so *hopefully* that process may give some answers. But I'd never seen this error before & thought some people here may be able to weigh in.

probably you have deleted a driver without deleting the corresponding connectors. This breaks UI. We are in process of fixing it: https://github.com/reef-pi/reef-pi/issues/1022
github closed this for stale reasons. i;ll reopen it, we'll get it fixed soonish.

 

[Ranjib]

It's not working in a linux environment, I'm looking at the context.go code but its not apparent as to what is missing, I have the dev files installed so it's something else.

What linux distro you are using? have you installed the audio library?

 

[Ranjib]

I was going to offer the same but it's not building on linux and it's not clear what is the issue, something to do with the new sound driver. When I get it working I can also build something if needed, just not sure what the current issue is.

Just FYI, i use ubuntu and macbook pro, and able to build on both platforms. I cant do cross compile (building pi binaries on laptop or desktop), but normal development flows work.,

 

[Ranjib]

I saw something about alsa, I don't think that's it though.

Could be, but it should work as long as you dont do cross compile. i.e make go should work, make pi will not work in non-pi setup.

We should move the development discussions in slack or some place else. Its developer onboarding related and little orthogonal to the original thread.

 

[bishoptf]

Could be, but it should work as long as you dont do cross compile. i.e make go should work, make pi will not work in non-pi setup.

We should move the development discussions in slack or some place else. Its developer onboarding related and little orthogonal to the original thread.

Sorry about cluttering up the thread, I thought about this last night when going to bed, it's the cross compiling. Make is working, make pi is not. I so an old issue on the Oto stuff that referenced cross compiling, so if you need to make for a pi it needs to be on a pi. Kind of a bummer since my linux box is a whole lot faster, I guess for development and testing you can make and test on linux etc, but when needed to make for a pi it needs to be on a pi. Has it always been that way, I could have sworn in the 2.x days I could make pi on linux, but maybe not.

Thanks for clearing that up, at least for my my bench pc is using Arch. :)