This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Server Hardware for openplotter?
#21
you ask for advise but then shoot down any that's given..i dont think your going to find anyone here to write free software so that you can sell hardware..
OP is open source so you can fork and modify it to your hearts content..
the reason most of us use OP in the first place is that its open source and parts are readily available and can be bought off the self..
another piece of hardware will just cause more problems in my opinion..
mare liberum
Reply
#22
(2019-06-17, 12:13 PM)jim321 Wrote: you ask for advise but then shoot down any that's given..i dont think your going to find anyone here to write free software so that you can sell hardware..
OP is open source so you can fork and modify it to your hearts content..
the reason most of us use OP in the first place is that its open source and parts are readily available and can be bought off the self..
another piece of hardware will just cause more problems in my opinion..
Hi Jim,
I don´t understand your Problem.  Undecided I do not ask for advise, I ask for opinions. I do not need advice for pcb design. But I think opinions are to discuss and to focus. Many peoples, many opinions…  Wink 
I do this also with other hardware environments… Regular I put the hardware and another do the software.  Also we develop own software Peaces for the hardware… As example here: https://github.com/Joey-1970/GeCoS-Modules or here: https://github.com/bgersmann/GeCoS-Server
By the way… I have taken your advise to remove the RTC....  Wink 
It´s not so easy to do this open source. Yes, I want to sell the pcb´s later. I must do test with it to conform. 
That´s the greatest coast factor and without it´s not allowed to sell them. If anybody interested he can mail me and I send the grip files. Thats no problem… But I think the most people don´t want to mount the pcb by his own...  Tongue  And believe me: If I sell them for 60€ I earn nothing. That´s more a hobby…

"parts are readily available and can be bought off the self" where you found them? I know only the USB adapters…. My opinion (I know other peoples see it differently) USB is for a office, not for a marine application…  Big Grin  I want one board with all interfaces. 
Reply
#23
Hi,
here the finish design for the Prototypes.
First I have ordered 3 pcs for testing. I hope they arrived ready in 2-3weeks and the I can check... ;-)
   
For the Powemanagement:
If Enable is on 12V the Pi starts. If 12V is switch off, the Pi gets an low signal on GPIO4 (Pin7) so that the pi can shut down over a script. After 15s a Timedelay schuts down the step down regulator. In shutdown mode the the regulator draws 20uA.
I have decide for this Case: https://www.chinaenclosure.com/products/...xes-E.html
Thomas
Reply
#24
Hi,
today I´m back in office after my (sail) holidays.
I have unboxed this :
   

I hope next week I have time to test it... Big Grin
Reply
#25
(2019-08-15, 07:46 AM)glowntiger Wrote: Hi,
today I´m back in office after my (sail) holidays.
I have unboxed this :


I hope next week I have time to test it... Big Grin

Welcome back, I am always interested. Let me know when it's ready, ciao.
Reply
#26
How is the testing going? I am also interested . . .
Reply
#27
(2019-08-15, 11:50 AM)Max1947 Wrote:
(2019-08-15, 07:46 AM)glowntiger Wrote: Hi,
today I´m back in office after my (sail) holidays.
I have unboxed this :


I hope next week I have time to test it... Big Grin

Welcome back, I am always interested. Let me know when it's ready, ciao.

Already done tests? There should be no problem with Raspy4? Appearance news, Ciao!  Smile
Reply
#28
Hi,
today I have had a little time.
I have make some tests:
the shutdown function works. but a little to fast. If you shut off the 12V enable, the powersupply shuts down after 5s. I think thats to fast. I fix that to 10s i think... The Pi must shut down savely before the power cuts. In the same moment you shut off 12V enable gpio4 switch to low. that works fine.

The CAN MCP2515 is reachable:
I have done like this:
in config.txt;
Code:
dtoverlay=mcp2515-can1,oscillator=16000000,interrupt=25
dtoverlay=spi-bcm2835-overlay

(the mcp is connected to CE1, so you must use can1)
in  "sudo vcdbg log msg" you find:

Code:
002046.685: brfs: File read: /mfs/sd/overlays/mcp2515-can1.dtbo
002065.384: Loaded overlay 'mcp2515-can1'
002065.441: dtparam: oscillator=16000000
002066.265: dtparam: interrupt=25
002155.228: brfs: File read: 1797 bytes

After sudo ip link set can0 up type can bitrate 250000
you find Can0 in "ifconfig"

Code:
pi@raspberrypi:~ $ ifconfig
can0: flags=193<UP,RUNNING,NOARP>  mtu 16
       unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 10000                      (UNSPEC)
       RX packets 0  bytes 0 (0.0 B)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 0  bytes 0 (0.0 B)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Next step is to test with hardware on NMEA2000. But at the moment all NMEA devices on board... Sad 
I test next time.

The NMEA0183:
I think there is a mistake anywere. Huh  2 of the three devices are reachable.... I must search.
But to works fine. I have done like this:
in config.txt:

Code:
dtoverlay=sc16is752-i2c,int_pin=6,addr=0x48
dtoverlay=sc16is752-i2c,int_pin=12,addr=0x49
# dtoverlay=sc16is752-i2c,int_pin=33,addr=0x4A

after this you find the new uarts in /dev/
there you now find ttySC0-ttySC3 (4,5 is missing becouse device is not reachable??
This you can found directly in opencpn.
Next step is to test with hardware.
If I have some time, i start with... Sad 

Also I must check the 1wire i2c server and the i2c line for I/O devices...
The 1-wire server is reachable...

Code:
pi@raspberrypi:~ $ i2cdetect -y 1
    0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- 18 -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- UU UU -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Reply
#29
(2019-08-28, 01:38 PM)glowntiger Wrote: Hi,
today I have had a little time.
I have make some tests:
the shutdown function works. but a little to fast. If you shut off the 12V enable, the powersupply shuts down after 5s. I think thats to fast. I fix that to 10s i think... The Pi must shut down savely before the power cuts. In the same moment you shut off 12V enable gpio4 switch to low. that works fine.

The CAN MCP2515 is reachable:
I have done like this:
in config.txt;
Code:
dtoverlay=mcp2515-can1,oscillator=16000000,interrupt=25
dtoverlay=spi-bcm2835-overlay

(the mcp is connected to CE1, so you must use can1)
in  "sudo vcdbg log msg" you find:

Code:
002046.685: brfs: File read: /mfs/sd/overlays/mcp2515-can1.dtbo
002065.384: Loaded overlay 'mcp2515-can1'
002065.441: dtparam: oscillator=16000000
002066.265: dtparam: interrupt=25
002155.228: brfs: File read: 1797 bytes

After sudo ip link set can0 up type can bitrate 500000
you find Can0 in "ifconfig"

Code:
pi@raspberrypi:~ $ ifconfig
can0: flags=193<UP,RUNNING,NOARP>  mtu 16
       unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 10000                      (UNSPEC)
       RX packets 0  bytes 0 (0.0 B)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 0  bytes 0 (0.0 B)
       TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Next step is to test with hardware on NMEA2000. But at the moment all NMEA devices on board... Sad 
I test next time.

The NMEA0183:
I think there is a mistake anywere. Huh  2 of the three devices are reachable.... I must search.
But to works fine. I have done like this:
in config.txt:

Code:
dtoverlay=sc16is752-i2c,int_pin=6,addr=0x48
dtoverlay=sc16is752-i2c,int_pin=12,addr=0x49
# dtoverlay=sc16is752-i2c,int_pin=33,addr=0x4A

after this you find the new uarts in /dev/
there you now find ttySC0-ttySC3 (4,5 is missing becouse device is not reachable??
This you can found directly in opencpn.
Next step is to test with hardware.
If I have some time, i start with... Sad 

Also I must check the 1wire i2c server and the i2c line for I/O devices...
The 1-wire server is reachable...

Code:
pi@raspberrypi:~ $ i2cdetect -y 1
    0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- 18 -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- UU UU -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

Ciao, good job, you let me have the cost in PM.  Thank you.
Reply
#30
Hi Max1947,
if Im ready with testing prototyp i can send you one. For first test I give 3pcs for half price If I get some feedback... ;-)
But first I fix all issues on the hardware. The Problem with the third sc16is752 I have found... There was a bad soldering. (Prototypes produce is handmate and no batch production)
I think the Price for the PCB is later arround 60-65€ without case. The Price for the case will be round about 15€.
Thomas
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)