Fixme.ch - User contributions [en]

CffDisplay

2015-11-18T11:19:55Z

Jhu: /* Double H bridge board */

[[Category:Ongoing_Projects]]
==Overview==

The CFF display is a project where a system drives 2 old clock displays for hours and minutes, which are found @Fixme's lab. The displays are composed each by a dual coils step by step 12V motor (I = 170 mA). This means first to build 2 double H bridge optocoupled slaves boards. The slave's board is wanted to be a home made exercise, even if everything exist already on the electronic's market. I decided to drive these slave's boards with a Raspberry Pi B+ master board via USB. The master sends the desired position to the slaves (hours : 1 - 12, minutes : 1 - 59). The Raspi's date is often updated by NTP, the system's source code is writen in python. The signals for the motors are generated inside the slave's board by a [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010208 PIC16F627A]. The PIC16F627A has its own internal master clock of 4 Mhz. The source code inside the PIC is writen in C with the old Microchip MPLab IDE, compiled by the free [http://www.bknd.com/cc5x/ CC5X compiler] and flashed with the [http://www.microchip.com/DevelopmentTools/ProductDetails.aspx?PartNO=dv164005 ICD2] in the PIC via [https://en.wikipedia.org/wiki/In-system_programming ICSP].

===Double H bridge board===

* The [https://drive.google.com/file/d/0ByeP0iLaCXmBV25jTy00WDBhTGc/view?usp=docslist_api schematic]
* The [[PCB]] comes soon!
* The [[source code in C of the PIC16F627A]] comes later.
* The [[pictures]] will probably never come ;-)

===Raspberry Pi===

* The [[schematic of the connections]]
* The [[source code in python]]
* The [[pictures]]

>>> PLEASE LET ME KNOW YOUR THOUGHTS AND COMMENT(S) to joelhuser2@gmail.com

CffDisplay

2015-11-17T10:01:57Z

Jhu: /* Overview */

==Overview==

The CFF display is a project where a system drives 2 old clock displays for hours and minutes, which are found @Fixme's lab. The displays are composed each by a dual coils step by step 12V motor (I = 170 mA). This means first to build 2 double H bridge optocoupled slaves boards. The slave's board is wanted to be a home made exercise, even if everything exist already on the electronic's market. I decided to drive these slave's boards with a Raspberry Pi B+ master board via USB. The master sends the desired position to the slaves (hours : 1 - 12, minutes : 1 - 59). The Raspi's date is often updated by NTP, the system's source code is writen in python. The signals for the motors are generated inside the slave's board by a [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010208 PIC16F627A]. The PIC16F627A has its own internal master clock of 4 Mhz. The source code inside the PIC is writen in C with the old Microchip MPLab IDE, compiled by the free [http://www.bknd.com/cc5x/ CC5X compiler] and flashed with the [http://www.microchip.com/DevelopmentTools/ProductDetails.aspx?PartNO=dv164005 ICD2] in the PIC via [https://en.wikipedia.org/wiki/In-system_programming ICSP].

===Double H bridge board===

* The [[schematic]] is almost ready!
* The [[PCB]] comes soon!
* The [[source code in C of the PIC16F627A]] comes later.
* The [[pictures]] will probably never come ;-)

===Raspberry Pi===

* The [[schematic of the connections]]
* The [[source code in python]]
* The [[pictures]]

>>> PLEASE LET ME KNOW YOUR THOUGHTS AND COMMENT(S) to joelhuser2@gmail.com

CffDisplay

2015-11-17T10:01:34Z

Jhu: /* Overview */

CffDisplay

2015-11-17T10:01:24Z

Jhu: /* Overview */

==Overview==

The CFF display is a project where a system drives 2 old clock displays for hours and minutes, which are found @Fixme's lab. The displays are composed each by a dual coils step by step 12V motor (I = 170 mA). This means first to build 2 double H bridge optocoupled slaves boards. The slave's board is wanted to be a home made exercise, even if everything exist already on the electronic's market. I decided to drive these slave's boards with a Raspberry Pi B+ master board via USB. The master sends the desired position to the slaves (hours : 1 - 12, minutes : 1 - 59). The Raspi's date is often updated by NTP, the system's source code is writen in python. The signals for the motors are generated inside the slave's board by a [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010208 PIC16F627A]. The PIC16F627A has its own internal master clock of 4 Mhz. The source code inside the PIC is writen in C with the old Microchip MPLab IDE, compiled by the free [http://www.bknd.com/cc5x/ CC5X compiler] and flashed with the [http://www.microchip.com/DevelopmentTools/ProductDetails.aspx?PartNO=dv164005 ICD2] in the PIC via [https://en.wikipedia.org/wiki/In-system_programming ICSP].

===Double H bridge board===

* The [[schematic]] is almost ready!
* The [[PCB]] comes soon!
* The [[source code in C of the PIC16F627A]] comes later.
* The [[pictures]] will probably never come ;-)

===Raspberry Pi===

* The [[schematic of the connections]]
* The [[source code in python]]
* The [[pictures]]

PLEASE LET ME KNOW YOUR THOUGHTS AND COMMENT(S) @ joelhuser2@gmail.com

CffDisplay

2015-11-17T10:00:10Z

Jhu: /* Overview */

==Overview==

The CFF display is a project where a system drives 2 old clock displays for hours and minutes, which are found @Fixme's lab. The displays are composed each by a dual coils step by step 12V motor (I = 170 mA). This means first to build 2 double H bridge optocoupled slaves boards. The slave's board is wanted to be a home made exercise, even if everything exist already on the electronic's market. I decided to drive these slave's boards with a Raspberry Pi B+ master board via USB. The master sends the desired position to the slaves (hours : 1 - 12, minutes : 1 - 59). The Raspi's date is often updated by NTP, the system's source code is writen in python. The signals for the motors are generated inside the slave's board by a [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010208 PIC16F627A]. The PIC16F627A has its own internal master clock of 4 Mhz. The source code inside the PIC is writen in C with the old Microchip MPLab IDE, compiled by the free [http://www.bknd.com/cc5x/ CC5X compiler] and flashed with the [http://www.microchip.com/DevelopmentTools/ProductDetails.aspx?PartNO=dv164005 ICD2] in the PIC via [https://en.wikipedia.org/wiki/In-system_programming ICSP].

===Double H bridge board===

*[[Schematic]] comes very soon!
*[[PCB]] comes soon!
*[[Source code in C of the PIC16F627A]] comes later.
*[[Pictures]] will probably never come ;-)

===Raspberry Pi===

*[[schematic of the connections]]
*[[Source code in python]]
*[[Pictures]]

PLEASE LET ME KNOW YOUR THOUGHTS AND COMMENT(S) @ joelhuser2@gmail.com

CffDisplay

2015-11-17T09:58:38Z

Jhu: /* Overview */

==Overview==

The CFF display is a project where a system drives 2 old clock displays for hours and minutes, which are found @Fixme's lab. The displays are composed each by a dual coils step by step 12V motor (I = 170 mA). This means first to build 2 double H bridge optocoupled slaves boards. The slave's board is wanted to be a home made exercise, even if everything exist already on the electronic's market. I decided to drive these slave's boards with a Raspberry Pi B+ master board via USB. The master sends the desired position to the slaves (hours : 1 - 12, minutes : 1 - 59). The Raspi's date is often updated by NTP, the system's source code is writen in python. The signals for the motors are generated inside the slave's board by a [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010208 PIC16F627A]. The PIC16F627A has its own internal master clock of 4 Mhz. The source code inside the PIC is writen in C with the old Microchip MPLab IDE, compiled by the free [http://www.bknd.com/cc5x/ CC5X compiler] and flashed with the [http://www.microchip.com/DevelopmentTools/ProductDetails.aspx?PartNO=dv164005 ICD2] in the PIC via [https://en.wikipedia.org/wiki/In-system_programming ICSP].

===Double H bridge board===

*[[Schematic]] comes very soon!
*[PCB] comes soon!
*[Source code in C of the PIC16F627A] comes later.
*[Pictures] will probably never come ;-)

===Raspberry Pi===

*[schematic of the connections]
*[Source code in python]
*[Pictures]

CffDisplay

2015-11-17T09:57:43Z

Jhu: /* Overview */

==Overview==

The CFF display is a project where a system drives 2 old clock displays for hours and minutes, which are found @Fixme's lab. The displays are composed each by a dual coils step by step 12V motor (I = 170 mA). This means first to build 2 double H bridge optocoupled slaves boards. The slave's board is wanted to be a home made exercise, even if everything exist already on the electronic's market. I decided to drive these slave's boards with a Raspberry Pi B+ master board via USB. The master sends the desired position to the slaves (hours : 1 - 12, minutes : 1 - 59). The Raspi's date is often updated by NTP, the system's source code is writen in python. The signals for the motors are generated inside the slave's board by a [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010208 PIC16F627A]. The PIC16F627A has its own internal master clock of 4 Mhz. The source code inside the PIC is writen in C with the old Microchip MPLab IDE, compiled by the free [http://www.bknd.com/cc5x/ CC5X compiler] and flashed with the [http://www.microchip.com/DevelopmentTools/ProductDetails.aspx?PartNO=dv164005 ICD2] in the PIC via [https://en.wikipedia.org/wiki/In-system_programming ICSP].

===Double H bridge board===

*[Schematic] comes very soon!
*[PCB] comes soon!
*[Source code in C of the PIC16F627A] comes later.
*[Pictures] will probably never come ;-)

===Raspberry Pi===

*[schematic of the connections]
*[Source code in python]
*[Pictures]

CffDisplay

2015-11-17T09:57:19Z

Jhu: Created page with "==Overview== The CFF display is a project where a system drives 2 old clock displays for hours and minutes, which are found @Fixme's lab. The displays are composed each by a..."

==Overview==

The CFF display is a project where a system drives 2 old clock displays for hours and minutes, which are found @Fixme's lab. The displays are composed each by a dual coils step by step 12V motor (I = 170 mA). This means first to build 2 double H bridge optocoupled slaves boards. The slave's board is wanted to be a home made exercise, even if everything exist already on the electronic's market. I decided to drive these slave's boards with a Raspberry Pi B+ master board via USB. The master sends the desired position to the slaves (hours : 1 - 12, minutes : 1 - 59). The Raspi's date is often updated by NTP, the system's source code is writen in python. The signals for the motors are generated inside the slave's board by a [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010208 PIC16F627A]. The PIC16F627A has its own internal master clock of 4 Mhz. The source code inside the PIC is writen in C with the old Microchip MPLab IDE, compiled by the free [http://www.bknd.com/cc5x/ CC5X compiler] and flashed with the [http://www.microchip.com/DevelopmentTools/ProductDetails.aspx?PartNO=dv164005 ICD2] in the PIC via [https://en.wikipedia.org/wiki/In-system_programming ICSP].

===Double H bridge board===

*[Schematic] comes very soon!
*[PCB] comes soon!
*[Source code in C of the PIC16F627A] comes later.
*[Pictures] will probably never come ;-)

===Raspberry Pi source code===

*[schematic of the connections]
*[Source code in python]
*[Pictures]

DVPWM

2014-10-23T11:46:18Z

Jhu:

[jhu corrections]

DVPWM is a PWM driver [/dimmer] originally designed for very simple LED lighting. It is built to [be] small, robust and convenient.

It has one single control: a rotating knob with on/off switch attached. In "off" position, [the] circuitry is completely offline.

* '''Input''': 6-15 VDC. [With input voltage polarity] inversion protectioon, suitable for dirty or noisy power supplies [Yes!!!].
* '''Output''': "high" frequency [? kHz] PWM with duty cycle ranging from almost zero to almost 100% [Yes!!!]
* '''Maximum admissible current''': 5A with SMD fuse on-board. This makes it probably overkill for small lighting, but will allow you to power about 25m of standard LED stripe or even small electric motors [Yes because there is a beefy high voltage spikes free wheel diode protection].
* In most cases, more than one DVPWM can be combined for RGB lighting ('''common ground''') [Yes!!!]

== Schematic ==
Thanks to Joël H for the schematic. He made it with Kicad and his little brain [I maybe have a relationship with Homer Simpson, which is actually my idol]

[[Media:DVPWM Schematic.pdf|Schematic (PDF)]]

== PCB ==
[[File:DVPWM render top.png|200px|thumb|right|PCB top view]]
[[File:DVPWM render bottom.png|200px|thumb|right|PCB bottom view]]

PCB design was achieved with [http://eda.eremex.com/products/topor/ Topor], a piece of software which truly amazes me. Through recursive contemplation of the routing algorithm, I was able to shorten the track lengths to an almost minimum and reduce the number of vias to zero. [!!!] The output from Topor was then imported into Kicad again, because we couldn't be bothered to learn new things so early after sunrise.

PCB size is 26x37mm. Height from frontplate (if applicable: circuit secured to frontplate using the knob's nut): 22mm

Most text is made unreadable when the components are in place, but we didn't care much about this ; priority was the size, and it was time for a nap.

== Component list ==
To achieve the very small size, most components are SMD type. Only exceptions are the rotating knob, and one capacitor. Due to the relatively small amount of components and their size, this circuit is an ideal for anyone who would like to learn SMD soldering.

[[Media:DVPWM ComponentsList105.pdf|Component list (PDF)]]

Suggestions for cheaper alternates are welcome.

== Kits ==
Kits are available for CHF 30.- a piece, cheaper for larger quantities. This includes the PCB and all the necessary components. While this may seem relatively expensive, the knob is far from cheap (and no alternative was found at the time) and so is one of the capacitors. There is also some provision for development costs, so we can continue to offer you more useful circuits.

Please contact [mailto:electro-shop@pg21.org electro-shop@pg21.org] to order.

DVPWM

2014-10-23T11:34:57Z

Jhu: /* Schematic */

DVPWM is a PWM driver originally designed for very simple LED lighting. It is built to small, robust and convenient.

It has one single control: a rotating knob with on/off switch attached. In "off" position, circuitry is completely offline.

* '''Input''': 6-15 VDC. Inversion protected, suitable for dirty or noisy power supplies.
* '''Output''': "high" frequency PWM with duty cycle ranging from almost zero to almost 100%
* '''Maximum admissible current''': 5A with SMD fuse on-board. This makes it probably overkill for small lighting, but will allow you to power about 25m of standard LED stripe or even small electric motors.
* In most cases, more than one DVPWM can be combined for RGB lighting ('''common ground''')

== Schematic ==
Thanks to Joël H for the schematic. He made it with Kicad and his little brain (jhu: 4 littles too well educated lonely neurons)

[[Media:DVPWM Schematic.pdf|Schematic (PDF)]]

== PCB ==
[[File:DVPWM render top.png|200px|thumb|right|PCB top view]]
[[File:DVPWM render bottom.png|200px|thumb|right|PCB bottom view]]

PCB design was achieved with [http://eda.eremex.com/products/topor/ Topor], a piece of software which truly amazes me. Through recursive contemplation of the routing algorithm, I was able to shorten the track lengths to an almost minimum and reduce the number of vias to zero. The output from Topor was then imported into Kicad again, because we couldn't be bothered to learn new things so early after sunrise.

PCB size is 26x37mm. Height from frontplate (if applicable: circuit secured to frontplate using the knob's nut): 22mm

Most text is made unreadable when the components are in place, but we didn't care much about this ; priority was the size, and it was time for a nap.

== Component list ==
To achieve the very small size, most components are SMD type. Only exceptions are the rotating knob, and one capacitor. Due to the relatively small amount of components and their size, this circuit is an ideal for anyone who would like to learn SMD soldering.

[[Media:DVPWM ComponentsList105.pdf|Component list (PDF)]]

Suggestions for cheaper alternates are welcome.

== Kits ==
Kits are available for CHF 30.- a piece, cheaper for larger quantities. This includes the PCB and all the necessary components. While this may seem relatively expensive, the knob is far from cheap (and no alternative was found at the time) and so is one of the capacitors. There is also some provision for development costs, so we can continue to offer you more useful circuits.

Please contact [mailto:electro-shop@pg21.org electro-shop@pg21.org] to order.

ElectroJam4

2014-08-19T12:24:00Z

Jhu: /* Participants */

[[Category:Ongoing_Projects]]
== Description ==
''In French'' :

Après une petite interruption les '''ElectroJam''' reprennent, celles-ci auront lieu 4x par années, mais qu'est-ce donc qu'une ElectrJam à FIXME : le/la participant(e) jouera à nouveau quelques partitions à base d'électronique, d'informatique et de mécanique, pour que des projets prennent vie !!!

''In English'' :

After one pause the '''ElectroJam''' start again, these will take place 4x by year, but what is the ElectrJam at FIXME : The player will play with the electronic, informatics, and mechanical base, for the some projects begin to live !!!

For Reminder : [[ElectroJam1]] // [[ElectroJam2]] // [[ElectroJam3]]

== Schedule ==
* DATE : the september 12, 2014
* Appointment at the Fixme : from 20:00
* Event page:

== Goal ==
''In French'' :

durant cette soirée/nuit (pour les plus courageux), le but est d'utiliser les différents éléments qu'offre le Fixme (composants, outils, apport de matériels de chacun) pour laisser s'exprimer le côté "brut" de la technique, et ainsi commencer, poursuivre ou terminer un/des projet

''In English'' :

During this evening (or night), the goal is using different elemens there has at Fixme local (components, tools, gifts user) to leave your spirit express to begin, continue or finish one or some project.

Activities examples :
---------------------
* Programming (uC, uP, web page, script,...)
* Electronics (making a prototype on verroboard or on PCB, software using : KICAD, SCILABS, ... discover electronics components and their working with datasheet)
* Mechanical (making 3D printing, cut, saw, drill,... )
* People (share knowledge, find out others, ...)

== Obstacles ==
* your limits !!!
* arrangement, yes, yes

== Component ==
* Electronics components (resistor, capacity, diode, transistor, IC, uC, uP, motor, led,...)
* PC's
* Electronics Book
* Pizza
* Beer
* Stuff to open your spirit

== Project in the back ==

''In French''

Avec le lien ci-dessous, tu peux déjà choisir sur quel projet tu aimerais venir apporter, partager ou découvrir tes connaissances... n'hésite pas non plus a rajouter ton projet

''In English''

With the link below, you can choice the projet or offer your project

Example of project :

* Fixme_Y_choice (suite)
* Arbre Twitter - Fixme (suite)
* Affichage Hack-CFF (suite)
* DMX protocole (Special Fixme RS485 home-made protocol)
* Workshop Kicad / PCB (New)
* your project

== Participants ==
* [[User:Binary_Brain]] ???
* [[User:dgellow]]
* [[User:Nemen]] ???
* [[User:Rorist]] ???
* [[User:gcmalloc]] ???
* [[User:Marcha]] ???
* [[User:Noskill]] ???
* [[User:Philoux]] ???
* [[User:Jhu]] ElectroJam... for sure !
* and you (members or not members of Fixme) ???

== Photos ==
A completer par vos photos

<gallery>
File:Twitter tree wires.jpg
File:Twitter tree lcd screen.jpg
File:fixmebus1.jpg
File:fixmebus2.jpg
</gallery>

== See also ==
* [[ElectroJam1]]
* [[ElectroJam2]]

ElectroJam4

2014-08-19T12:23:38Z

Jhu: /* Participants */

[[Category:Ongoing_Projects]]
== Description ==
''In French'' :

Après une petite interruption les '''ElectroJam''' reprennent, celles-ci auront lieu 4x par années, mais qu'est-ce donc qu'une ElectrJam à FIXME : le/la participant(e) jouera à nouveau quelques partitions à base d'électronique, d'informatique et de mécanique, pour que des projets prennent vie !!!

''In English'' :

After one pause the '''ElectroJam''' start again, these will take place 4x by year, but what is the ElectrJam at FIXME : The player will play with the electronic, informatics, and mechanical base, for the some projects begin to live !!!

For Reminder : [[ElectroJam1]] // [[ElectroJam2]] // [[ElectroJam3]]

== Schedule ==
* DATE : the september 12, 2014
* Appointment at the Fixme : from 20:00
* Event page:

== Goal ==
''In French'' :

durant cette soirée/nuit (pour les plus courageux), le but est d'utiliser les différents éléments qu'offre le Fixme (composants, outils, apport de matériels de chacun) pour laisser s'exprimer le côté "brut" de la technique, et ainsi commencer, poursuivre ou terminer un/des projet

''In English'' :

During this evening (or night), the goal is using different elemens there has at Fixme local (components, tools, gifts user) to leave your spirit express to begin, continue or finish one or some project.

Activities examples :
---------------------
* Programming (uC, uP, web page, script,...)
* Electronics (making a prototype on verroboard or on PCB, software using : KICAD, SCILABS, ... discover electronics components and their working with datasheet)
* Mechanical (making 3D printing, cut, saw, drill,... )
* People (share knowledge, find out others, ...)

== Obstacles ==
* your limits !!!
* arrangement, yes, yes

== Component ==
* Electronics components (resistor, capacity, diode, transistor, IC, uC, uP, motor, led,...)
* PC's
* Electronics Book
* Pizza
* Beer
* Stuff to open your spirit

== Project in the back ==

''In French''

Avec le lien ci-dessous, tu peux déjà choisir sur quel projet tu aimerais venir apporter, partager ou découvrir tes connaissances... n'hésite pas non plus a rajouter ton projet

''In English''

With the link below, you can choice the projet or offer your project

Example of project :

* Fixme_Y_choice (suite)
* Arbre Twitter - Fixme (suite)
* Affichage Hack-CFF (suite)
* DMX protocole (Special Fixme RS485 home-made protocol)
* Workshop Kicad / PCB (New)
* your project

== Participants ==
* [[User:Binary_Brain]] ???
* [[User:dgellow]]
* [[User:Nemen]] ???
* [[User:Rorist]] ???
* [[User:gcmalloc]] ???
* [[User:Marcha]] ???
* [[User:Noskill]] ???
* [[User:Philoux]] ???
* [[User:Jhu]] For sure !
* and you (members or not members of Fixme) ???

== Photos ==
A completer par vos photos

<gallery>
File:Twitter tree wires.jpg
File:Twitter tree lcd screen.jpg
File:fixmebus1.jpg
File:fixmebus2.jpg
</gallery>

== See also ==
* [[ElectroJam1]]
* [[ElectroJam2]]

ElectroJam4

2014-08-19T12:23:24Z

Jhu: /* Participants */

[[Category:Ongoing_Projects]]
== Description ==
''In French'' :

Après une petite interruption les '''ElectroJam''' reprennent, celles-ci auront lieu 4x par années, mais qu'est-ce donc qu'une ElectrJam à FIXME : le/la participant(e) jouera à nouveau quelques partitions à base d'électronique, d'informatique et de mécanique, pour que des projets prennent vie !!!

''In English'' :

After one pause the '''ElectroJam''' start again, these will take place 4x by year, but what is the ElectrJam at FIXME : The player will play with the electronic, informatics, and mechanical base, for the some projects begin to live !!!

For Reminder : [[ElectroJam1]] // [[ElectroJam2]] // [[ElectroJam3]]

== Schedule ==
* DATE : the september 12, 2014
* Appointment at the Fixme : from 20:00
* Event page:

== Goal ==
''In French'' :

durant cette soirée/nuit (pour les plus courageux), le but est d'utiliser les différents éléments qu'offre le Fixme (composants, outils, apport de matériels de chacun) pour laisser s'exprimer le côté "brut" de la technique, et ainsi commencer, poursuivre ou terminer un/des projet

''In English'' :

During this evening (or night), the goal is using different elemens there has at Fixme local (components, tools, gifts user) to leave your spirit express to begin, continue or finish one or some project.

Activities examples :
---------------------
* Programming (uC, uP, web page, script,...)
* Electronics (making a prototype on verroboard or on PCB, software using : KICAD, SCILABS, ... discover electronics components and their working with datasheet)
* Mechanical (making 3D printing, cut, saw, drill,... )
* People (share knowledge, find out others, ...)

== Obstacles ==
* your limits !!!
* arrangement, yes, yes

== Component ==
* Electronics components (resistor, capacity, diode, transistor, IC, uC, uP, motor, led,...)
* PC's
* Electronics Book
* Pizza
* Beer
* Stuff to open your spirit

== Project in the back ==

''In French''

Avec le lien ci-dessous, tu peux déjà choisir sur quel projet tu aimerais venir apporter, partager ou découvrir tes connaissances... n'hésite pas non plus a rajouter ton projet

''In English''

With the link below, you can choice the projet or offer your project

Example of project :

* Fixme_Y_choice (suite)
* Arbre Twitter - Fixme (suite)
* Affichage Hack-CFF (suite)
* DMX protocole (Special Fixme RS485 home-made protocol)
* Workshop Kicad / PCB (New)
* your project

== Participants ==
* [[User:Binary_Brain]] ???
* [[User:dgellow]]
* [[User:Nemen]] ???
* [[User:Rorist]] ???
* [[User:gcmalloc]] ???
* [[User:Marcha]] ???
* [[User:Noskill]] ???
* [[User:Philoux]] ???
* [[User:Jhu]] Sure !
* and you (members or not members of Fixme) ???

== Photos ==
A completer par vos photos

<gallery>
File:Twitter tree wires.jpg
File:Twitter tree lcd screen.jpg
File:fixmebus1.jpg
File:fixmebus2.jpg
</gallery>

== See also ==
* [[ElectroJam1]]
* [[ElectroJam2]]

ElectroJam4

2014-08-19T12:23:08Z

Jhu: /* Photos */

[[Category:Ongoing_Projects]]
== Description ==
''In French'' :

Après une petite interruption les '''ElectroJam''' reprennent, celles-ci auront lieu 4x par années, mais qu'est-ce donc qu'une ElectrJam à FIXME : le/la participant(e) jouera à nouveau quelques partitions à base d'électronique, d'informatique et de mécanique, pour que des projets prennent vie !!!

''In English'' :

After one pause the '''ElectroJam''' start again, these will take place 4x by year, but what is the ElectrJam at FIXME : The player will play with the electronic, informatics, and mechanical base, for the some projects begin to live !!!

For Reminder : [[ElectroJam1]] // [[ElectroJam2]] // [[ElectroJam3]]

== Schedule ==
* DATE : the september 12, 2014
* Appointment at the Fixme : from 20:00
* Event page:

== Goal ==
''In French'' :

durant cette soirée/nuit (pour les plus courageux), le but est d'utiliser les différents éléments qu'offre le Fixme (composants, outils, apport de matériels de chacun) pour laisser s'exprimer le côté "brut" de la technique, et ainsi commencer, poursuivre ou terminer un/des projet

''In English'' :

During this evening (or night), the goal is using different elemens there has at Fixme local (components, tools, gifts user) to leave your spirit express to begin, continue or finish one or some project.

Activities examples :
---------------------
* Programming (uC, uP, web page, script,...)
* Electronics (making a prototype on verroboard or on PCB, software using : KICAD, SCILABS, ... discover electronics components and their working with datasheet)
* Mechanical (making 3D printing, cut, saw, drill,... )
* People (share knowledge, find out others, ...)

== Obstacles ==
* your limits !!!
* arrangement, yes, yes

== Component ==
* Electronics components (resistor, capacity, diode, transistor, IC, uC, uP, motor, led,...)
* PC's
* Electronics Book
* Pizza
* Beer
* Stuff to open your spirit

== Project in the back ==

''In French''

Avec le lien ci-dessous, tu peux déjà choisir sur quel projet tu aimerais venir apporter, partager ou découvrir tes connaissances... n'hésite pas non plus a rajouter ton projet

''In English''

With the link below, you can choice the projet or offer your project

Example of project :

* Fixme_Y_choice (suite)
* Arbre Twitter - Fixme (suite)
* Affichage Hack-CFF (suite)
* DMX protocole (Special Fixme RS485 home-made protocol)
* Workshop Kicad / PCB (New)
* your project

== Participants ==
* [[User:Binary_Brain]] ???
* [[User:dgellow]]
* [[User:Nemen]] ???
* [[User:Rorist]] ???
* [[User:gcmalloc]] ???
* [[User:Marcha]] ???
* [[User:Noskill]] ???
* [[User:Philoux]] ???
* [[User:Jhu]] ???
* and you (members or not members of Fixme) ???

== Photos ==
A completer par vos photos

<gallery>
File:Twitter tree wires.jpg
File:Twitter tree lcd screen.jpg
File:fixmebus1.jpg
File:fixmebus2.jpg
</gallery>

== See also ==
* [[ElectroJam1]]
* [[ElectroJam2]]

File:Fixmebus2.jpg

2014-08-19T12:22:26Z

Jhu: Second brainstorming of the fixmebus

Second brainstorming of the fixmebus

File:Fixmebus1.jpg

2014-08-19T12:22:04Z

Jhu: first brainstorming of the fixmebus

first brainstorming of the fixmebus

FixmeBus

2014-05-04T04:04:27Z

Jhu:

__TOC__
__TOC__
==Overview==

[[File:len.png|thumb|500px]]
[[File:RS-485.gif|thumb|500px]]
[[File:20140412 190054t.jpg|thumb|500px]]
FixmeBus is a field bus based on the half duplex [http://en.wikipedia.org/wiki/RS-485 RS485] famous hardware protocol. It is a master / slave architecture, with every slave chained together.

===The communication protocol is a standard UART...===
... which has these following parameters:

*38,400 bauds
*8 data bits
*1 start and 1 stop bit
*no parity
*no flow control

Each end of the bus is terminated with a 1% 120R resistor. The A/B lines are biased once at the gateway with 2x 1kOhms resistors.

The maximum length @38,400 bauds is 4 kFt = 1.2 km (see the graphic on the right).

===Every data frame contain chronologically:===

*2 bytes of slave adress (ID_HIGH and ID_LOW) => 65536 slave adress at all
**ID = 0 => Master
**ID = 65535 => order to all slaves (no ack)
**ID = 65000 to 65499 => order to a group of slave (no ack)
**ID = 1000 to 64999 => order to a unique slave (ack)
*2 bytes for the function (FCT_HIGH and FCT_LOW)
*1 byte for the number of data bytes to transmit (N_BYTE)
*n byte(s) of data (DATA) bytes (max. 200 bytes per frame)
*2 bytes for the [http://en.wikipedia.org/wiki/Cyclic_redundancy_check CRC] [http://en.wikipedia.org/wiki/Modbus Modbus] (CRC_HIGH and CRC_LOW)

{| class="wikitable" style="text-align: center; color: green;"
|b0
|b1
|b2
|b3
|b4
|b5
|...
|bn+4
|bn+5
|bn+6
|-
!ID_HIGH
!ID_LOW
!FCT_HIGH
!FCT_LOW
!N_BYTE
!DATA[0]
!...
!DATA[n-1]
!CRC_HIGH
!CRC_LOW
|}

The CRC Modbus can be calculated [http://www.lammertbies.nl/comm/info/crc-calculation.html here]

==White board #2 - 3 mai electrojam #3==
[[File:Wb2.jpg|thumb|500px]]

*Y aura 1 board slave avec du 3v3, 1 board avec du 5v !

*Les esclaves pourront parler sur le bus, mais seulement pour faire du reporting d'événements, pas pour faire des requêtes. Les esclaves n'ont AUCUNE intelligence. (Ce n'est que pure coïncidence avec mon semblant de segregationiste !).

*Version 1 : seul le maître peut parler
*Version 2 : les esclaves peuvent parler mais sans donner d'ordre.
*Version 3 : les esclaves peuvent se donner des ordres parmi et se livrent une bataille de pouvoir (long Power sur 32 bits = pouvoir).... le maître peut être réduit à l'esclavage !!! ... un peu comme la reine d'Angleterre...

*Les esclaves seront alimentés par un POE "fait maison" 24VDC 5A, avec alim industrielle sur rail DIN Schneider Electric. Chaque esclave doit comsommer max 50 mA sous 24VDC (= 1.2 W max) => 100 Esclaves par Fixme bus

*La règle pour parler, c'est premièrement d'écouter 50 ms sur le Bus, y compris le master. En cas de collision, c'est à dire de CRC faux, le maître reprend le contrôle du bus, et commande aux slaves qui ont parlé, mais qui n'ont pas reçu de ack (les 2 slave émetteurs malchanceux) de rejouer leur partie après un delay de n [ms] prix aléatoirement. Pour cela le firmware de la roue de la fortune pourra être repris.

*But financier :
**Prix de revient du hardware : 33.- CHF
**Développement C pour la gestion du bus bas niveau, développement python des parties gestion des droits, data frame output, base de donnée et APIs + développement PHP pour service client, packaging : 33.-
**Bénéfice pour réserve développements projets FIXME : 33.- CHF
**Total : 99.- le module tout public = slave 3v3 ou slave 5v ou FBG (FixmeBus Gateway)... prix spéciaux...

*J'ai oublié : DANS LE SERIAL FRAME IL FAUT RAJOUTER L'EXPEDITEUR (2 BYTES).

==Technical Documents==
#[[Hardware]]
#[[...]]

FixmeBus

2014-05-04T04:02:22Z

Jhu:

FixmeBus

2014-05-04T03:45:59Z

Jhu:

__TOC__
__TOC__
==Overview==

[[File:len.png|thumb|500px]]
[[File:RS-485.gif|thumb|500px]]
[[File:20140412 190054t.jpg|thumb|500px]]
FixmeBus is a field bus based on the half duplex [http://en.wikipedia.org/wiki/RS-485 RS485] famous hardware protocol. It is a master / slave architecture, with every slave chained together.

===The communication protocol is a standard UART...===
... which has these following parameters:

*38,400 bauds
*8 data bits
*1 start and 1 stop bit
*no parity
*no flow control

Each end of the bus is terminated with a 1% 120R resistor. The A/B lines are biased once at the gateway with 2x 1kOhms resistors.

The maximum length @38,400 bauds is 4 kFt = 1.2 km (see the graphic on the right).

===Every data frame contain chronologically:===

*2 bytes of slave adress (ID_HIGH and ID_LOW) => 65536 slave adress at all
**ID = 0 => Master
**ID = 65535 => order to all slaves (no ack)
**ID = 65000 to 65499 => order to a group of slave (no ack)
**ID = 1000 to 64999 => order to a unique slave (ack)
*2 bytes for the function (FCT_HIGH and FCT_LOW)
*1 byte for the number of data bytes to transmit (N_BYTE)
*n byte(s) of data (DATA) bytes (max. 200 bytes per frame)
*2 bytes for the [http://en.wikipedia.org/wiki/Cyclic_redundancy_check CRC] [http://en.wikipedia.org/wiki/Modbus Modbus] (CRC_HIGH and CRC_LOW)

{| class="wikitable" style="text-align: center; color: green;"
|b0
|b1
|b2
|b3
|b4
|b5
|...
|bn+4
|bn+5
|bn+6
|-
!ID_HIGH
!ID_LOW
!FCT_HIGH
!FCT_LOW
!N_BYTE
!DATA[0]
!...
!DATA[n-1]
!CRC_HIGH
!CRC_LOW
|}

The CRC Modbus can be calculated [http://www.lammertbies.nl/comm/info/crc-calculation.html here]

==White board #2 - 3 mai electrojam #3==
[[File:Wb2.jpg|thumb|500px]]

Y aura 1 board slave avec du 3v3, 1 board avec du 5v !

Les esclaves pourront parler sur le bus, mais seulement pour faire du reporting d'événements, pas pour faire des requêtes. Les esclaves n'ont AUCUNE intelligence. (Ce n'est que pure coïncidence avec mon semblant de segregationiste !).

Version 1 : seul le maître peut parler
Version 2 : les esclaves peuvent parler mais sans donner d'ordre.
Version 3 : les esclaves peuvent se donner des ordres parmi et se livrent une bataille de pouvoir (long Power sur 32 bits = pouvoir).... le maître peut être réduit à l'esclavage !!! ... un peu comme la reine d'Angleterre...

Les esclaves seront alimentés par un POE "fait maison" 24VDC 5A, avec alim industrielle sur rail DIN Schneider Electric. Chaque esclave doit comsommer max 50 mA sous 24VDC (= 1.2 W max) => 100 Esclaves par Fixme bus

La règle pour parler, c'est premièrement d'écouter 50 ms sur le Bus, y compris le master. En cas de collision, c'est à dire de CRC faux, le maître reprend le contrôle du bus, et commande aux slaves qui ont parlé, mais qui n'ont pas reçu de ack (les 2 slave émetteurs malchanceux) de rejouer leur partie après un delay de n [ms] prix aléatoirement. Pour cela le firmware de la roue de la fortune pourra être repris.

==Technical Documents==
#[[Hardware]]
#[[...]]

FixmeBus

2014-05-04T03:09:25Z

Jhu:

File:Wb2.jpg

2014-05-04T03:05:25Z

Jhu: White board #2

White board #2

FixmeBus

2014-05-04T03:02:27Z

Jhu:

FixmeBus

2014-04-13T08:51:39Z

Jhu: /* Overview */

FixmeBus

2014-04-13T01:25:55Z

Jhu: /* Overview */

File:Len.png

2014-04-13T01:25:25Z

Jhu:

FixmeBus

2014-04-13T01:25:08Z

Jhu: /* Overview */

__TOC__
__TOC__
==Overview==

[[File:len.png|thumb|260px]]
[[File:RS-485.gif|thumb|260px]]
[[File:20140412 190054t.jpg|thumb|260px]]
FixmeBus is a field bus based on the half duplex [http://en.wikipedia.org/wiki/RS-485 RS485] famous hardware protocol. It is a master / slave architecture, with every slave chained together.

===The communication protocol is a standard UART...===
... which has these following parameters:

*38,400 bauds
*8 data bits
*1 start and 1 stop bit
*no parity
*no flow control

Each end of the bus is terminated with a 1% 120R resistor. The A/B lines are biased once at the gateway with 2x 1kOhms resistors.

===Every data frame contain chronologically:===

*2 bytes of slave adress (ID_HIGH and ID_LOW) => 65536 slave adress at all
**ID = 0 => Master
**ID = 65535 => order to all slaves (no ack)
**ID = 65000 to 65499 => order to a group of slave (no ack)
**ID = 1000 to 64999 => order to a unique slave (ack)
*2 bytes for the function (FCT_HIGH and FCT_LOW)
*1 byte for the number of data bytes to transmit (N_BYTE)
*n byte(s) of data (DATA) bytes (max. 200 bytes per frame)
*2 bytes for the [http://en.wikipedia.org/wiki/Cyclic_redundancy_check CRC] [http://en.wikipedia.org/wiki/Modbus Modbus] (CRC_HIGH and CRC_LOW)

{| class="wikitable" style="text-align: center; color: green;"
|b0
|b1
|b2
|b3
|b4
|b5
|...
|bn+4
|bn+5
|bn+6
|-
!ID_HIGH
!ID_LOW
!FCT_HIGH
!FCT_LOW
!N_BYTE
!DATA[0]
!...
!DATA[n-1]
!CRC_HIGH
!CRC_LOW
|}

The CRC Modbus can be calculated [http://www.lammertbies.nl/comm/info/crc-calculation.html here]

==Technical Documents==
#[[Hardware]]
#[[...]]

FixmeBus

2014-04-13T01:24:33Z

Jhu: /* The communication protocol is a standard UART... */

__TOC__
__TOC__
==Overview==

[[File:RS-485.gif|thumb|260px]]
[[File:20140412 190054t.jpg|thumb|260px]]
FixmeBus is a field bus based on the half duplex [http://en.wikipedia.org/wiki/RS-485 RS485] famous hardware protocol. It is a master / slave architecture, with every slave chained together.

===The communication protocol is a standard UART...===
... which has these following parameters:

*38,400 bauds
*8 data bits
*1 start and 1 stop bit
*no parity
*no flow control

Each end of the bus is terminated with a 1% 120R resistor. The A/B lines are biased once at the gateway with 2x 1kOhms resistors.

===Every data frame contain chronologically:===

*2 bytes of slave adress (ID_HIGH and ID_LOW) => 65536 slave adress at all
**ID = 0 => Master
**ID = 65535 => order to all slaves (no ack)
**ID = 65000 to 65499 => order to a group of slave (no ack)
**ID = 1000 to 64999 => order to a unique slave (ack)
*2 bytes for the function (FCT_HIGH and FCT_LOW)
*1 byte for the number of data bytes to transmit (N_BYTE)
*n byte(s) of data (DATA) bytes (max. 200 bytes per frame)
*2 bytes for the [http://en.wikipedia.org/wiki/Cyclic_redundancy_check CRC] [http://en.wikipedia.org/wiki/Modbus Modbus] (CRC_HIGH and CRC_LOW)

{| class="wikitable" style="text-align: center; color: green;"
|b0
|b1
|b2
|b3
|b4
|b5
|...
|bn+4
|bn+5
|bn+6
|-
!ID_HIGH
!ID_LOW
!FCT_HIGH
!FCT_LOW
!N_BYTE
!DATA[0]
!...
!DATA[n-1]
!CRC_HIGH
!CRC_LOW
|}

The CRC Modbus can be calculated [http://www.lammertbies.nl/comm/info/crc-calculation.html here]

==Technical Documents==
#[[Hardware]]
#[[...]]

File:Schema102.pdf

2014-04-13T01:07:59Z

Jhu:

FBEG v1.0.2

2014-04-13T01:01:21Z

Jhu: Created page with "__TOC__ ==FBEG v1.0.2== ===Schematics=== File:schema102.pdf"

__TOC__
==FBEG v1.0.2==
===Schematics===

[[File:schema102.pdf]]

IP to FixmeBus gateway

2014-04-13T01:00:52Z

Jhu: /* IP to FixmeBus gateway */

__TOC__
==IP to FixmeBus gateway==
#[[FBEG v1.0.0]]
#[[FBEG v1.0.1]]
#[[FBEG v1.0.2]]
#[[...]]

FBEG v1.0.1

2014-04-13T00:58:41Z

Jhu: /* Schematics */

__TOC__
==FBEG v1.0.1==
===Schematics===

[[File:schema101.pdf]]

File:Schema101.pdf

2014-04-13T00:58:11Z

Jhu:

FBEG v1.0.1

2014-04-13T00:57:52Z

Jhu: Created page with "__TOC__ ==FBEG v1.0.1== ===Schematics=== File:SchemaFBEG2.pdf"

__TOC__
==FBEG v1.0.1==
===Schematics===

[[File:SchemaFBEG2.pdf]]

IP to FixmeBus gateway

2014-04-13T00:57:17Z

Jhu: /* IP to FixmeBus gateway */

__TOC__
==IP to FixmeBus gateway==
#[[FBEG v1.0.0]]
#[[FBEG v1.0.1]]
#[[...]]

FBEG v1.0.0

2014-04-13T00:40:27Z

Jhu: /* Schematics */

__TOC__
==FBEG v1.0.0==
===Schematics===

[[File:SchemaFBEG2.pdf]]

File:SchemaFBEG2.pdf

2014-04-13T00:40:08Z

Jhu:

FBEG v1.0.0

2014-04-13T00:35:12Z

Jhu: /* Schematics */

__TOC__
==FBEG v1.0.0==
===Schematics===

[[File:SchemaFBEG1.pdf]]

File:SchemaFBEG1.pdf

2014-04-13T00:34:47Z

Jhu:

FBEG v1.0.0

2014-04-13T00:17:29Z

Jhu: /* Schematics */

__TOC__
==FBEG v1.0.0==
===Schematics===

[[File:SchemaFBEG v1.0.0.pdf]]

FBEG v1.0.0

2014-04-13T00:15:42Z

Jhu: /* Schematics */

__TOC__
==FBEG v1.0.0==
===Schematics===

[[SchemaFBEG v1.0.0.pdf]]

FBEG v1.0.0

2014-04-13T00:12:59Z

Jhu: /* Schematics */

__TOC__
==FBEG v1.0.0==
===Schematics===

[[File:SchemaFBEG v1.0.0.pdf]]

FBEG v1.0.0

2014-04-13T00:12:24Z

Jhu: /* Schematics */

__TOC__
==FBEG v1.0.0==
===Schematics===

[[File:SchemaFBEG_v1.0.0.pdf]]

File:SchemaFBEG v1.0.0.pdf

2014-04-13T00:11:32Z

Jhu:

FixmeBus

2014-04-12T23:58:41Z

Jhu: /* Every data frame contain chronologically: */

__TOC__
__TOC__
==Overview==

[[File:RS-485.gif|thumb|260px]]
[[File:20140412 190054t.jpg|thumb|260px]]
FixmeBus is a field bus based on the half duplex [http://en.wikipedia.org/wiki/RS-485 RS485] famous hardware protocol. It is a master / slave architecture, with every slave chained together.

===The communication protocol is a standard UART...===
... which has these following parameters:

*38,400 bauds
*8 data bits
*1 start and 1 stop bit
*no parity
*no flow control

Each end of the bus is terminated with a 1% 120R resistor. The A/B lines are biased at one end with 2x 1kOhms resistors.

===Every data frame contain chronologically:===

*2 bytes of slave adress (ID_HIGH and ID_LOW) => 65536 slave adress at all
**ID = 0 => Master
**ID = 65535 => order to all slaves (no ack)
**ID = 65000 to 65499 => order to a group of slave (no ack)
**ID = 1000 to 64999 => order to a unique slave (ack)
*2 bytes for the function (FCT_HIGH and FCT_LOW)
*1 byte for the number of data bytes to transmit (N_BYTE)
*n byte(s) of data (DATA) bytes (max. 200 bytes per frame)
*2 bytes for the [http://en.wikipedia.org/wiki/Cyclic_redundancy_check CRC] [http://en.wikipedia.org/wiki/Modbus Modbus] (CRC_HIGH and CRC_LOW)

{| class="wikitable" style="text-align: center; color: green;"
|b0
|b1
|b2
|b3
|b4
|b5
|...
|bn+4
|bn+5
|bn+6
|-
!ID_HIGH
!ID_LOW
!FCT_HIGH
!FCT_LOW
!N_BYTE
!DATA[0]
!...
!DATA[n-1]
!CRC_HIGH
!CRC_LOW
|}

The CRC Modbus can be calculated [http://www.lammertbies.nl/comm/info/crc-calculation.html here]

==Technical Documents==
#[[Hardware]]
#[[...]]

FixmeBus

2014-04-12T23:58:11Z

Jhu: /* Every data frame contain chronologically: */

__TOC__
__TOC__
==Overview==

[[File:RS-485.gif|thumb|260px]]
[[File:20140412 190054t.jpg|thumb|260px]]
FixmeBus is a field bus based on the half duplex [http://en.wikipedia.org/wiki/RS-485 RS485] famous hardware protocol. It is a master / slave architecture, with every slave chained together.

===The communication protocol is a standard UART...===
... which has these following parameters:

*38,400 bauds
*8 data bits
*1 start and 1 stop bit
*no parity
*no flow control

Each end of the bus is terminated with a 1% 120R resistor. The A/B lines are biased at one end with 2x 1kOhms resistors.

===Every data frame contain chronologically:===

*2 bytes of slave adress (ID_HIGH and ID_LOW) => 65536 slave adress at all
**ID = 0 => Master
**ID = 65535 => order to all slaves (no ack)
**ID = 65000 to 65499 => order to a group of slave (no ack)
**ID = 1000 to 64999 => order to a unique slave (ack)
*2 bytes for the function (FCT_HIGH and FCT_LOW)
*1 byte for the number of data bytes to transmit (N_BYTE)
*n byte(s) of data (DATA) bytes (max. 200 bytes per frame)
*2 bytes for the [http://en.wikipedia.org/wiki/Cyclic_redundancy_check CRC] Modbus (CRC_HIGH and CRC_LOW)

{| class="wikitable" style="text-align: center; color: green;"
|b0
|b1
|b2
|b3
|b4
|b5
|...
|bn+4
|bn+5
|bn+6
|-
!ID_HIGH
!ID_LOW
!FCT_HIGH
!FCT_LOW
!N_BYTE
!DATA[0]
!...
!DATA[n-1]
!CRC_HIGH
!CRC_LOW
|}

The CRC Modbus can be calculated [http://www.lammertbies.nl/comm/info/crc-calculation.html here]

==Technical Documents==
#[[Hardware]]
#[[...]]

FixmeBus

2014-04-12T23:54:08Z

Jhu: /* Every data frame contain chronologically: */

__TOC__
__TOC__
==Overview==

[[File:RS-485.gif|thumb|260px]]
[[File:20140412 190054t.jpg|thumb|260px]]
FixmeBus is a field bus based on the half duplex [http://en.wikipedia.org/wiki/RS-485 RS485] famous hardware protocol. It is a master / slave architecture, with every slave chained together.

===The communication protocol is a standard UART...===
... which has these following parameters:

*38,400 bauds
*8 data bits
*1 start and 1 stop bit
*no parity
*no flow control

Each end of the bus is terminated with a 1% 120R resistor. The A/B lines are biased at one end with 2x 1kOhms resistors.

===Every data frame contain chronologically:===

*2 bytes of slave adress (ID_HIGH and ID_LOW) => 65536 slave adress at all
**ID = 0 => Master
**ID = 65535 => order to all slaves (no ack)
**ID = 65000 to 65499 => order to a group of slave (no ack)
**ID = 1000 to 64999 => order to a unique slave (ack)
*2 bytes for the function (FCT_HIGH and FCT_LOW)
*1 byte for the number of data bytes to transmit (N_BYTE)
*n byte(s) of data (DATA) bytes (max. 200 bytes per frame)
*2 bytes for the CRC (CRC_HIGH and CRC_LOW)

{| class="wikitable" style="text-align: center; color: green;"
|b0
|b1
|b2
|b3
|b4
|b5
|...
|bn+4
|bn+5
|bn+6
|-
!ID_HIGH
!ID_LOW
!FCT_HIGH
!FCT_LOW
!N_BYTE
!DATA[0]
!...
!DATA[n-1]
!CRC_HIGH
!CRC_LOW
|}

==Technical Documents==
#[[Hardware]]
#[[...]]

FixmeBus

2014-04-12T23:53:34Z

Jhu: /* Every data frame contain chronologically: */

__TOC__
__TOC__
==Overview==

[[File:RS-485.gif|thumb|260px]]
[[File:20140412 190054t.jpg|thumb|260px]]
FixmeBus is a field bus based on the half duplex [http://en.wikipedia.org/wiki/RS-485 RS485] famous hardware protocol. It is a master / slave architecture, with every slave chained together.

===The communication protocol is a standard UART...===
... which has these following parameters:

*38,400 bauds
*8 data bits
*1 start and 1 stop bit
*no parity
*no flow control

Each end of the bus is terminated with a 1% 120R resistor. The A/B lines are biased at one end with 2x 1kOhms resistors.

===Every data frame contain chronologically:===

*2 bytes of slave adress (ID_HIGH and ID_LOW) => 65536 slave adress at all
**ID = 0 => Master
**ID = 65535 => order to all slaves (no ack)
**ID = 65000 to 65499 => order to a group of slave (no ack)
**ID = 1000 to 64999 => order to an unique slave (ack)
*2 bytes for the function (FCT_HIGH and FCT_LOW)
*1 byte for the number of data bytes to transmit (N_BYTE)
*n byte(s) of data (DATA) bytes (max. 200 bytes per frame)
*2 bytes for the CRC (CRC_HIGH and CRC_LOW)

{| class="wikitable" style="text-align: center; color: green;"
|b0
|b1
|b2
|b3
|b4
|b5
|...
|bn+4
|bn+5
|bn+6
|-
!ID_HIGH
!ID_LOW
!FCT_HIGH
!FCT_LOW
!N_BYTE
!DATA[0]
!...
!DATA[n-1]
!CRC_HIGH
!CRC_LOW
|}

==Technical Documents==
#[[Hardware]]
#[[...]]

FixmeBus

2014-04-12T23:51:40Z

Jhu: /* Overview */

__TOC__
__TOC__
==Overview==

[[File:RS-485.gif|thumb|260px]]
[[File:20140412 190054t.jpg|thumb|260px]]
FixmeBus is a field bus based on the half duplex [http://en.wikipedia.org/wiki/RS-485 RS485] famous hardware protocol. It is a master / slave architecture, with every slave chained together.

===The communication protocol is a standard UART...===
... which has these following parameters:

*38,400 bauds
*8 data bits
*1 start and 1 stop bit
*no parity
*no flow control

Each end of the bus is terminated with a 1% 120R resistor. The A/B lines are biased at one end with 2x 1kOhms resistors.

===Every data frame contain chronologically:===

*2 bytes of slave adress (ID_HIGH and ID_LOW) => 65536 slave adress
**ID = 0 => Master
**ID = 65535 => order to all slaves (no ack)
**ID = 65000 to 65499 => order to a group of slave (no ack)
**ID = 1000 to 64999 => order to an unique slave (ack)
*2 bytes for the function (FCT_HIGH and FCT_LOW)
*1 byte for the number of data bytes to transmit (N_BYTE)
*n byte(s) of data (DATA) bytes (max. 200 bytes per frame)
*2 bytes for the CRC (CRC_HIGH and CRC_LOW)

{| class="wikitable" style="text-align: center; color: green;"
|b0
|b1
|b2
|b3
|b4
|b5
|...
|bn+4
|bn+5
|bn+6
|-
!ID_HIGH
!ID_LOW
!FCT_HIGH
!FCT_LOW
!N_BYTE
!DATA[0]
!...
!DATA[n-1]
!CRC_HIGH
!CRC_LOW
|}

==Technical Documents==
#[[Hardware]]
#[[...]]

File:RS-485.gif

2014-04-12T23:50:52Z

Jhu:

FixmeBus

2014-04-12T23:50:08Z

Jhu: /* Overview */

__TOC__
__TOC__
==Overview==

[[File:20140412 190054t.jpg|thumb|260px]]
FixmeBus is a field bus based on the half duplex [http://en.wikipedia.org/wiki/RS-485 RS485] famous hardware protocol. It is a master / slave architecture, with every slave chained together.

===The communication protocol is a standard UART...===
... which has these following parameters:

*38,400 bauds
*8 data bits
*1 start and 1 stop bit
*no parity
*no flow control

Each end of the bus is terminated with a 1% 120R resistor. The A/B lines are biased at one end with 2x 1kOhms resistors.

===Every data frame contain chronologically:===

*2 bytes of slave adress (ID_HIGH and ID_LOW) => 65536 slave adress
**ID = 0 => Master
**ID = 65535 => order to all slaves (no ack)
**ID = 65000 to 65499 => order to a group of slave (no ack)
**ID = 1000 to 64999 => order to an unique slave (ack)
*2 bytes for the function (FCT_HIGH and FCT_LOW)
*1 byte for the number of data bytes to transmit (N_BYTE)
*n byte(s) of data (DATA) bytes (max. 200 bytes per frame)
*2 bytes for the CRC (CRC_HIGH and CRC_LOW)

{| class="wikitable" style="text-align: center; color: green;"
|b0
|b1
|b2
|b3
|b4
|b5
|...
|bn+4
|bn+5
|bn+6
|-
!ID_HIGH
!ID_LOW
!FCT_HIGH
!FCT_LOW
!N_BYTE
!DATA[0]
!...
!DATA[n-1]
!CRC_HIGH
!CRC_LOW
|}

==Technical Documents==
#[[Hardware]]
#[[...]]